ekmania

Implementation Guide for using "Remove Cache Buster Query Parameter" feature

The Super Page Cache for Cloudflare plugin has recently added the feature for using the Cache Everything pagerule withing the ?swcfpc=1 cache buster query paramater. This opens up so many new doors where users previously had to use the Cloudflare Workers to remove the cache buster.

With this new option now users are able to take advantage of Cloudflare Cache Everything page rule and take it to the next level by using the new Rulesets released by Cloudflare. Basically this is achived by taking advantage of the all new Cache Rules feature implemented by Cloudflare.

Setp 1 — Setting up the Cache Rules inside your Cloudflare Dashboard

The first thing that you need to do is, log-in to your Cloudflare Dahsbord and go to the domain/zone doe which you are setting up the [Super Page Cache for Cloudflare](https://wordpress.org/plug

Real-time PHP-FPM Status

This gist will explain you how to enable an undocumented feature of PHP-FPM which will give a real-time performance stats.

Everybody knows the famous phpinfo() and the page it generates, right? Then the real-time PHP-FPM status page design is very similar.

Some informations from the top are not displayed to avoid security issues.

Enable PHP-FPM Status

Adjusting child processes for PHP-FPM (Nginx)

When setting these options consider the following:

How long is your average request?
What is the maximum number of simultaneous visitors the site(s) get?
How much memory on average does each child process consume?

Determine if the max_children limit has been reached.

sudo grep max_children /var/log/php?.?-fpm.log.1 /var/log/php?.?-fpm.log

Naming Classes Without a 'Manager'

	<?php
	// Upload to private url or implement authorization...
	if (isset($_GET["json"])) {
	header("Content-type: application/json");
	exit(json_encode( fpm_get_status() ));
	}
	?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">
	<!--

	<?php

	/**
	* Example useage:
	*
	* maybe_sideload_image( 'https://dummyimage.com/600x400/000/fff.png' ); // Downloads image to the media library and returns an attachment ID
	* maybe_sideload_image( 'https://dummyimage.com/600x400/000/fff.png' ); // Returns an attachment ID as the image has already been downloaded and added to the media library
	*/

	/**

	<?php // <~ don't add me in

	add_action( 'restrict_manage_posts', 'filter_backend_by_taxonomies' , 99, 2);
	/* Filter CPT via Custom Taxonomy */
	/* https://generatewp.com/filtering-posts-by-taxonomies-in-the-dashboard/ */

	function filter_backend_by_taxonomies( $post_type, $which ) {

	// Apply this to a specific CPT
	if ( 'light' !== $post_type )

 function replaceNbspWithSpace($content){
 	$string = htmlentities($content, null, 'utf-8');
 	$content = str_replace("&nbsp;", " ", $string);
 	$content = html_entity_decode($content);
 	return $content;
 }

	http://wordpress.stackexchange.com/questions/139834/obliterate-the-main-query-and-replace-it

	When 'pre_get_posts' is fired, there are a lot of things that WordPress has already done like setup all the query variables (also the query you don't send) and setup all the conditional properties (all the is_* properties). So, if you want completely replace the query you should reset all that things and set your own.

	In fact, even if your code works, WordPress will use page.php as template.

	However there's a simpler approach: act before WordPress do all the things.

	A good place is the 'request' filter hook, at that time WordPress has created the query vars from url and is going to pass that vars to WP_Query, and you can intercept and change query arguments before are sent.

	function numberWithSpaces(nr) {
	return nr.toString().replace(/\B(?=(\d{3})+(?!\d))/g, " ");
	}