PhpStorm now bundles WordPress coding style natively, starting from version 8.
- Go to
Project Settings
>Code Style
>PHP
. - Select
Set From...
(top right of window) >Predefined Style
>WordPress
.
No longer need to muck with this import! :)
This gist assumes:
<?php | |
// Edit Settings | |
$username = "admin"; | |
$password = "password"; | |
$ip = "192.168.1.1:8081"; | |
$api = "1234"; | |
// End Settings | |
// Check if username is available, set URL |
var countries_data = {"type":"FeatureCollection","features":[ | |
{"type":"Feature","geometry":{"type":"MultiPolygon","coordinates":[[[[74.92,37.24],[74.57,37.03],[72.56,36.82],[71.24,36.13],[71.65,35.42],[71.08,34.06],[69.91,34.04],[70.33,33.33],[69.51,33.03],[69.33,31.94],[66.72,31.21],[66.26,29.85],[62.48,29.41],[60.87,29.86],[61.85,31.02],[60.84,31.5],[60.58,33.07],[60.94,33.52],[60.51,34.14],[61.28,35.61],[62.72,35.25],[63.12,35.86],[64.5,36.28],[64.8,37.12],[66.54,37.37],[67.78,37.19],[69.32,37.12],[70.97,38.47],[71.59,37.9],[71.68,36.68],[73.31,37.46],[74.92,37.24]]]]},"properties":{"name":"Afghanistan"},"id":"AF"}, | |
{"type":"Feature","geometry":{"type":"MultiPolygon","coordinates":[[[[19.44,41.02],[19.37,41.85],[19.65,42.62],[20.07,42.56],[20.59,41.88],[20.82,40.91],[20.98,40.86],[20.01,39.69],[19.29,40.42],[19.44,41.02]]]]},"properties":{"name":"Albania"},"id":"AL"}, | |
{"type":"Feature","geometry":{"type":"MultiPolygon","coordinates":[[[[2.96,36.8],[8.62,36.94],[8.18,36.52],[8.25,34.64],[7.49,33.89],[9.06,3 |
auth_basic "Restricted"; | |
auth_basic_user_file /etc/nginx/htpasswd; |
Two files must be modified for this fix to work:
# modified: wp-content/plugins/wp-bannerize/js/jquery-ui.min.js
# modified: wp-content/plugins/wp-bannerize/js/jquery.timepicker.min.js
wp-content/plugins/wp-bannerize/js/jquery.timepicker.min.js
with the contents of the latest version.wp-content/plugins/wp-bannerize/js/jquery-ui.min.js
with the contents of jquery-ui.min.js
from this gist.While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.
Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.
lib/
is intended for code that can run as-issrc/
is intended for code that needs to be manipulated before it can be used<!DOCTYPE html> | |
<html> | |
<head> | |
<meta name="viewport" content="initial-scale=1.0, user-scalable=no"> | |
<meta charset="UTF-8"> | |
<title>Drawing Tools</title> | |
<script type="text/javascript" | |
src="http://maps.google.com/maps/api/js?sensor=false&libraries=drawing"></script> | |
<style type="text/css"> | |
#map, html, body { |
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
<?php | |
/** | |
* deploy.php by Hayden Schiff (oxguy3) | |
* Available at https://gist.github.com/oxguy3/70ea582d951d4b0f78edec282a2bebf9 | |
* | |
* No rights reserved. Dedicated to public domain via CC0 1.0 Universal. | |
* See https://creativecommons.org/publicdomain/zero/1.0/ for terms. | |
*/ | |
// random string of characters; must match the "Secret" defined in your GitHub webhook |