jjeaton

function Selector_Cache() {
	var elementCache = {};

	var get_from_cache = function( selector, $ctxt, reset ) {

		if ( 'boolean' === typeof $ctxt ) { reset = $ctxt; }
		var cacheKey = $ctxt ? $ctxt.selector + ' ' + selector : selector;

		if ( undefined === elementCache[ cacheKey ] || reset ) {
			elementCache[ cacheKey ] = $ctxt ? $ctxt.find( selector ) : jQuery( selector );

markjaquith

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;

jashkenas

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

norcross

<?php
function rkv_limit_users_delete( $query ) {

	// first fetch the screen
	$screen	= get_current_screen();
	// bail if we aren't on our user screen
	if ( ! is_object( $screen ) || empty( $screen->base ) || ! empty( $screen->base ) && $screen->base != 'users' ) {
		return $query;
	}

jtsternberg

function Selector_Cache() {
	var elementCache = {};

	var get_from_cache = function( selector, $ctxt, reset ) {

		if ( 'boolean' === typeof $ctxt ) {
			reset = $ctxt;
			$ctxt = false;
		}
		var cacheKey = $ctxt ? $ctxt.selector + ' ' + selector : selector;

trepmal

<?php

if ( !defined( 'WP_CLI' ) ) return;

/**
 * Comment Generate
 */
class Comment_Generate extends WP_CLI_Command {

	/**

danielbachhuber

<?php
/**
 * Post-style permalinks for your custom post types
 * e.g. %year%/%monthnum%/%day%/%postname%
 */
function dbx_get_post_types() {
	return array(
		// replace with your custom post types
		'my-custom-post-type'
	);

philiparthurmoore

<?php
/**
 * Debugging WordPress things.
 *
 * All of this belongs in your wp-config.php file.
 *
 * This will make sure that the code you release is, at a minimum,
 * relatively free of PHP notices and warnings.
 *
 * - WP_DEBUG: This turns on debugging mode.

adamsilverstein

function expanded_alowed_tags() {
	$my_allowed = wp_kses_allowed_html( 'post' );
	// iframe
	$my_allowed['iframe'] = array(
		'src'             => array(),
		'height'          => array(),
		'width'           => array(),
		'frameborder'     => array(),
		'allowfullscreen' => array(),
	);

bradyvercher

<?php
add_filter( 'http_request_args', function( $r, $url ) {
	// If this isn't an update request, bail immediately.
	// Regex source: https://github.com/cftp/external-update-api/blob/master/external-update-api/euapi.php#L45
	if ( false === strpos( $url, 'api.wordpress.org' ) || ! preg_match( '#://api\.wordpress\.org/(?P<type>plugins|themes)/update-check/(?P<version>[0-9.]+)/#', $url, $matches ) ) {
		return $r;
	}

	$api_type = $matches['type'];
	$api_version = floatval( $matches['version'] );