paulgibbs

<?php
/**
 * Plugin Name: Disable Gutenberg
 */

add_filter('use_block_editor_for_post', '__return_false');

paulgibbs

+----------------+--------------------------------+-------------------------+-------------+--------+---------------------+
| language       | english_name                   | native_name             | status      | update | updated             |
+----------------+--------------------------------+-------------------------+-------------+--------+---------------------+
| de_CH          | German (Switzerland)           | Deutsch (Schweiz)       | uninstalled | none   | 2018-07-08 16:40:04 |
| de_CH_informal | German (Switzerland, Informal) | Deutsch (Schweiz, Du)   | uninstalled | none   | 2018-07-08 16:42:22 |
| de_DE          | German                         | Deutsch                 | uninstalled | none   | 2018-07-10 10:18:08 |
| de_DE_formal   | German (Formal)                | Deutsch (Sie)           | uninstalled | none   | 2018-07-10 10:21:23 |

| es_AR          | Spanish (Argentina)            | Español de Argentina    | uninstalled | none   | 2018-06-16 04:48:17 |
| es_CL          | Spanish (Chile)     

paulgibbs

diff --git a/src/humans.txt b/src/humans.txt
index 5af7e71a4..6306ece57 100644
--- a/src/humans.txt
+++ b/src/humans.txt
@@ -99,6 +99,10 @@ Title: Core Developer
 Twitter: slaFFik
 Favorite Food: Cakes
 
+Name: Venutius
+Title: Community Support

paulgibbs

default:
  suites:
    default:
      contexts:
        - PaulGibbs\WordpressBehatExtension\Context\SiteContext
        - PaulGibbs\WordpressBehatExtension\Context\WordpressContext
        - Behat\MinkExtension\Context\MinkContext
        - PaulGibbs\WordpressBehatExtension\Context\ContentContext
        - PaulGibbs\WordpressBehatExtension\Context\DashboardContext
        - PaulGibbs\WordpressBehatExtension\Context\UserContext

paulgibbs

* Use a Post Type for email templates.
	* The intention is to use the standard wp-admin interface to allow people to change the contents of the email.
	* Mustache-like token syntax.
* Use the WP Customiser to visually customise those emails.
* Use a Taxonomy to store the distinct types of emails we send (e.g. new_user, new_site, new_activity_mention, etc).
* Add a HTML email template for the post type.

Direct calls to `wp_mail()` replaced with custom function `bp_send_mail()` that, basically, wraps `wp_mail`:
	* I surveyed all the mail replacement plugins I could find (like Mandrill's), and they all re-declare `wp_mail` to implement support for their custom service. Therefore, if `wp_mail()` is redeclared, *or* something has been filtered to get WP to send HTML emails, I'm assuming there's some dark voodoo at work -- and for reasons of trying to be compatible as possible, BP will treat emails the same way it does today (we'll pass it straight through to whatever `wp_mail()` is).
	* `bp_send_mail` does three 

paulgibbs

<?xml version="1.0"?>
<ruleset name="WordPress Coding Standards">
	<description>Apply WordPress Coding Standards to all Core files</description>

	<rule ref="WordPress-Core">
		<exclude name="WordPress.PHP.YodaConditions.NotYoda" />
		<exclude name="WordPress.WP.I18n.MissingTranslatorsComment" />
		<exclude name="WordPress.Files.FileName.InvalidClassFileName" />
		<exclude name="PEAR.NamingConventions.ValidClassName.Invalid" />
		<exclude name="WordPress.WP.PreparedSQL.NotPrepared" />

paulgibbs

gg

paulgibbs

<?php
/**
 * Remove bbPress script/style from non-bbPress pages.
 *
 * @param \BBP_Theme_Compat $bbpress_theme bbPress' theme object.
 */
add_action( 'bbp_theme_compat_actions', function( $bbpress_theme ) {
	if ( is_bbpress()  ) {
		return;
	}

paulgibbs

$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Cloning VM...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
==> default: Setting the name of the VM: bporg_default_1500458217639_11998
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly

paulgibbs

$ composer require wp-cli/wp-cli
You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug
Using version ^1.2 for wp-cli/wp-cli
./composer.json has been created
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - wp-cli/wp-cli v1.2.0 requires wp-cli/autoload-splitter ^0.1 -> satisfiable by wp-cli/autoload-splitter[v0.1.0, v0.1.1, v0.1.2, v0.1.3].