This document lists all the situations where WordPress sends an email, along with how to filter or disable each email.
This documentation has moved here: https://github.com/johnbillion/wp_mail
/* global jQuery, wp */ | |
jQuery( function( $ ) { | |
var initializeAllClocks, initializeClock; | |
/** | |
* Find clocks. | |
* | |
* @param [container] Scoping element for finding clock elements. | |
* @returns {void} |
# A heavily customized VCL to support WordPress | |
# Some items of note: | |
# Supports https | |
# Supports admin cookies for wp-admin | |
# Caches everything | |
# Support for custom error html page | |
vcl 4.0; | |
import directors; | |
import std; |
<?php | |
/** | |
* Add params back to oEmbed provider request URL. | |
* | |
* WordPress runs the embed URL through urlencode prior to constructing it's oEmbed provider endpoint call. | |
* This renders any passed in URL query params useless for Vimeo embeds (and probably others). | |
* This filter function will decode those URL query param, and add them as proper query args to the provider URL. | |
* | |
* The first function param, $provider, is the oEmbed provider endpoint. |
<?php | |
/* | |
* Dependent Plugin Activation/Deactivation | |
* | |
* Sources: | |
* 1. https://pippinsplugins.com/checking-dependent-plugin-active/ | |
* 2. http://10up.com/blog/2012/wordpress-plug-in-self-deactivation/ | |
* | |
*/ | |
<?php | |
/** | |
* Whitelist embedded links in the REST API responses | |
* | |
* This is often useful if you want to only get specified resources embedded along with the | |
* main resources, rather than the "all of nothing" approach of passing `?_embed` to the API request. | |
* | |
* You can either pass a comma seperated list of relationships or an array of string via the `_embed_include` query param. | |
* |
This document lists all the situations where WordPress sends an email, along with how to filter or disable each email.
This documentation has moved here: https://github.com/johnbillion/wp_mail
These commands will install multiple dummy sites in a WordPress Multisite environment.
I wrote this to easily create an environment to work on https://core.trac.wordpress.org/ticket/15317.
In the terminal, inside your WordPress directory: simply copy, paste, and run the one-line command.
You can also add it to a location available in your $PATH
and invoke the script from the shell.
# #!/bin/bash | |
# # | |
# # provision.sh | |
# # | |
# # This file is specified in Vagrantfile and is loaded by Vagrant as the primary | |
# # provisioning script whenever the commands `vagrant up`, `vagrant provision`, | |
# # or `vagrant reload` are used. It provides all of the default packages and | |
# # configurations included with Varying Vagrant Vagrants. | |
# # By storing the date now, we can calculate the duration of provisioning at the |
<?php | |
/** | |
* | |
* This script will copy your wordpress from public_html (or wherever) | |
* and place it in a staging folder. | |
* It will then clone the database, reconfigure the config file | |
* and replace URL's from the original URL to your staging URL. | |
* It will then make sure to NOT allow search engines to index the page. | |
* | |
* Use this script to clone your main wp in order to test maintenance work |
register_extended_post_type( | |
'newsletter', | |
array( | |
'capability_type' => 'post', | |
'hierarchical' => false, | |
'menu_position' => 45, | |
'quick_edit' => false, | |
'supports' => array( 'title', 'editor', 'thumbnail' ), | |
'admin_cols' => array( | |
'newsletter-image' => array( |