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
<?php | |
// DEPRECATED. See https://github.com/alleyinteractive/wp-bulk-task as the successor to this trait. | |
/** | |
* Chunk up the task when you need to iterate over many posts. | |
* | |
* For instance, to iterate over every post on the site and add post meta: | |
* | |
* $this->bulk_task( function( $post ) { |
<?php | |
/** | |
* Add featured image url to api response | |
* This will (hopefully) be unnecessary if the API team adds it to core | |
* | |
*/ | |
add_action( 'rest_api_init', 'sb_register_featured_urls' ); | |
function sb_register_featured_urls() { | |
register_api_field( 'post', |
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.
# This is a template .gitignore file for git-managed WordPress projects. | |
# | |
# Fact: you don't want WordPress core files, or your server-specific | |
# configuration files etc., in your project's repository. You just don't. | |
# | |
# Solution: stick this file up your repository root (which it assumes is | |
# also the WordPress root directory) and add exceptions for any plugins, | |
# themes, and other directories that should be under version control. | |
# | |
# See the comments below for more info on how to add exceptions for your |
<?php | |
namespace DisableComments; | |
add_action( 'init', 'DisableComments\disable_comments_post_types_support' ); | |
add_filter( 'comments_array', 'DisableComments\disable_comments_hide_existing_comments', 10, 2 ); | |
add_action( 'admin_menu', 'DisableComments\disable_comments_admin_menu' ); | |
add_action( 'admin_init', 'DisableComments\disable_comments_admin_menu_redirect' ); | |
add_action( 'admin_init', 'DisableComments\disable_comments_dashboard' ); | |
add_action( 'init', 'DisableComments\disable_comments_admin_bar' ); |
INITIALISATION | |
============== | |
load wp-config.php | |
set up default constants | |
load wp-content/advanced-cache.php if it exists | |
load wp-content/db.php if it exists | |
connect to mysql, select db | |
load object cache (object-cache.php if it exists, or wp-include/cache.php if not) | |
load wp-content/sunrise.php if it exists (multisite only) |
upstream phpfpm { | |
server unix:/var/run/php5-fpm.sock; | |
} | |
upstream hhvm { | |
server unix:/var/run/hhvm/hhvm.sock; | |
} | |
# SSL | |
ssl_protocols TLSv1 TLSv1.1 TLSv1.2; |
<?php | |
/** | |
* Plugin Name: MU plugins subdirectory loader | |
* Plugin URI: http://code.ctlt.ubc.ca | |
* Description: Enables the loading of plugins sitting in mu-plugins (as folders) | |
* Version: 0.1 | |
* Author: iamfriendly, CTLT | |
* Author URI: http://ubc.ca/ | |
* |
This is a guide on how to email securely.
There are many guides on how to install and use PGP to encrypt email. This is not one of them. This is a guide on secure communication using email with PGP encryption. If you are not familiar with PGP, please read another guide first. If you are comfortable using PGP to encrypt and decrypt emails, this guide will raise your security to the next level.