boonebgorges

<?php

	/**
	 * Recursive argument parsing
	 *
	 * This acts like a multi-dimensional version of wp_parse_args() (minus
	 * the querystring parsing - you must pass arrays).
	 *
	 * Values from $a override those from $b; keys in $b that don't exist
	 * in $a are passed through.

boonebgorges

<?php

$categories = get_the_category();

// Assemble a tree of category relationships
// Also re-key the category array for easier
// reference
$category_tree = array();
$keyed_categories = array();

boonebgorges

<?php
/**
 * Note that CAC_VERSION is a custom constant. Replace as necessary.
 */
function cac_asset_ver( $tag, $handle, $src = '' ) {
	// 'style_loader_tag' doesn't pass a src, so we sniff it from the tag.
	if ( ! $src ) {
		preg_match( '/href\=\'([^\']+)\'/', $tag, $src_matches );
		if ( $src_matches ) {
			$src = $src_matches[1];

boonebgorges

<?php

$site_id = 7177;

switch_to_blog( $site_id );
$links = get_bookmarks( array(
	'category_name' => 'Course Blogs',
) );

$urls = wp_list_pluck( $links, 'link_url' );

boonebgorges

<?php

$comment = get_comment( 12345 );
$post_id = $comment->comment_post_ID();
$post = get_post( $post_id ); // Let's say post_title = Foo

do_action( 'comment_goodies', $comment, $post );

var_dump( $post );

boonebgorges

import React, { Component } from 'react';

export default class LaTeX extends Component {
	componentDidMount() {
		this.updateTeX()
	}

	componentDidUpdate() {
		this.updateTeX()
	}

boonebgorges

import React from 'react';
import LaTeX from './LaTeX'

const FormattedProblem = React.createClass( {
	getDefaultProps: function() {
		return {
			isVisible: true
		}
	},

boonebgorges

var iffRecursion = false;
window.Parsley.addValidator( 'iff', {
	validateString: function( value, requirement, instance ) {
		var $partner = $( requirement );
		var isValid = $partner.val() == value;

		if ( iffRecursion ) {
			iffRecursion = false;
		} else {
			iffRecursion = true;

boonebgorges

<input
  name="password"
  id="password"
  data-parsley-trigger="blur"
  data-parsley-iff="#password-confirm"
  data-parsley-iff-message=""
/>

<input
  name="password-confirm"

boonebgorges

Preparing Plugins for Term Splitting

Historically, two terms in different taxonomies with the same slug (for instance, a tag and a category sharing the slug "news") have shared a single term ID. Beginning in WordPress 4.2, when one of these shared terms is updated, it will be split: the updated term will be assigned a new term ID.

In the vast majority of situations, this update will be seamless and uneventful. However, some plugins and themes store term IDs in options, post meta, user meta, or elsewhere. WP 4.2 will include two different tools to help authors of these plugins and themes with the transition.

The 'split_shared_term' action

When a shared term is assigned a new term ID, a new 'split_shared_term' action is fired. Plugins and themes that store term IDs should hook to this action to perform necessary migrations. The documentation for the hook is as follows: