This document lists all the situations where WordPress sends an email, along with how to filter or disable each email.
This is accurate as of WordPress 4.9.
There are a few TODOs left. Please bear with me.
This document lists all the situations where WordPress sends an email, along with how to filter or disable each email.
This is accurate as of WordPress 4.9.
There are a few TODOs left. Please bear with me.
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) |
Matches: subject:([WordPress Trac]) "added -- Ticket URL:" | |
Do this: Mark as read | |
Matches: subject:([WordPress Trac]) "Changes (by johnbillion)" | |
Do this: Mark as read | |
Matches: subject:([WordPress Trac]) "Comment (by johnbillion)" | |
Do this: Mark as read |
<?php | |
/* Plugin Name: Damn Vulnerable WordPress Plugin | |
* Description: Intentionally vulnerable plugin for plugin author education | |
* Version: 0.1 | |
* Plugin URI: http://make.wordpress.org/plugins/2013/04/09/intentionally-vulnerable-plugin/ | |
* Author: Jon Cave | |
* Author URI: http://joncave.co.uk | |
* License: GPLv2+ | |
* | |
* DO NOT RUN THIS PLUGIN ON AN INTERNET ACCESSIBLE SITE |
<?php | |
/* | |
WordPress Template Hierarchy (as of WordPress 4.8) | |
is_404() -------------------------------------------------------------------------------------------------> 404.php | |
is_search() ----------------------------------------------------------------------------------------------> search.php | |
is_front_page() ------------------------------------------------------------------------------------------> front-page.php | |
is_home() ------------------------------------------------------------------------------------------------> home.php |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
#!/bin/bash | |
IFS=$'\n' | |
files=($(git diff --name-only $1 $2)) | |
git archive -o $3 $2 "${files[@]}" |
git rm -r --cached . | |
git add . | |
git commit -am 'git cache cleared' | |
git push |