mboynes

<?xml version="1.0"?>
<ruleset name="WordPress Theme Coding Standards Configuration">
	<!-- Set a description for this ruleset. -->
	<description>Code standard rules to check against a WordPress Theme.</description>

	<exclude-pattern>tests/*</exclude-pattern>
	<exclude-pattern>inc/cli.php</exclude-pattern>

	<!-- Include the WordPress VIP ruleset -->
	<rule ref="WordPress-VIP">

mboynes

<?php
// put this in functions.php or an include file
add_action( 'fm_post_post', function() {
    $fm = new Fieldmanager_Group( array(
        'name' => 'contact_information',
        'children' => array(
            'name' => new Fieldmanager_Textfield( __( 'Name', 'your-domain' ) ),
            'phone_number' => new Fieldmanager_Textfield( __( 'Phone Number', 'your-domain' ) ),
            'website' => new Fieldmanager_Link( __( 'Website', 'your-domain' ) ),
        ),

mboynes

<?php
// using Fieldmanager for a slideshow - any number of slides,
// with any number of related links
add_action( 'fm_post_post', function() {
    $fm = new Fieldmanager_Group( array(
        'name' => 'slideshow',
        'limit' => 0,
        'label' => __( 'New Slide', 'your-domain' ),
        'label_macro' => array( __( 'Slide: %s', 'your-domain' ), 'title' ),
        'add_more_label' => __( 'Add another slide', 'your-domain' ),

mboynes

<?php

if ( class_exists( 'Fieldmanager_Context_Term' ) ) {

	/**
	 * Use fieldmanager to create meta boxes on a subpage from a term
	 */
	class Fieldmanager_Context_Termpage extends Fieldmanager_Context_Term {

		/**

mboynes

<?php

// DEPRECATED. See https://github.com/alleyinteractive/wp-bulk-task as the successor to this trait.

/**
 * Chunk up the task when you need to iterate over many posts.
 *
 * For instance, to iterate over every post on the site and add post meta:
 *
 *     $this->bulk_task( function( $post ) {

mboynes

<?php

if ( class_exists( 'Fieldmanager_Datasource' ) ) {

	/**
	 * Custom Fieldmanager Datasource for Co-Authors Plus.
	 */
	class Fieldmanager_Datasource_CAP extends Fieldmanager_Datasource {

		/**

mboynes

<?php

require_once( __DIR__ . '/inc/class-fieldmanager-datasource-cap.php' );
add_action( 'fm_post_post', function() {
	$fm = new \Fieldmanager_Group( [
		'name' => 'byline',
		'limit' => 0,
		'label' => __( 'Author', 'cap-sandbox' ),
		'sortable' => true,
		'add_more_label' => __( 'Add a coauthor', 'cap-sandbox' ),

mboynes

<?php
namespace Alley;

/**
 * Popular Posts
 */
class Popular_Posts {

	/**
	 * The number of days to query for post views.

mboynes

How to develop with Jetpack locally with ngrok

To connect Jetpack in your local installation, you'll need a way for WP.com servers to reach your server. That can be done in a number of different ways:

• You can open your router's ports and use your public IP
• You can use some kind of Dynamic DNS provider.

But these options fall short of ngrok, which is a "localhost tunnel". It basically allows the Internet to hit a local port on your machine without worrying about ports or IPs.

As long as ngrok is running, Jetpack / WP.com will be able to communicate with your local site. This will allow remote modules like Site Search and Manage to work.

mboynes

<?php
// If you can edit pages, you can edit widgets

add_filter( 'user_has_cap',
function( $caps ) {
    if ( ! empty( $caps['edit_pages'] ) )
        $caps['edit_theme_options'] = true;
    return $caps;
} );