markjaquith

<?php
/**
 * Plugin Name: YOUR PLUGIN NAME
 */

include( dirname( __FILE__ ) . '/lib/requirements-check.php' );

$your_plugin_requirements_check = new YOUR_PREFIX_Requirements_Check( array(
	'title' => 'YOUR PLUGIN NAME',
	'php'   => '5.4',

thierrypigot

<?php
if( !class_exists('acf') )
{
	$tp_acf_notice_msg = __( 'This website needs "Advanced Custom Fields Pro" to run. Please download and activate it', 'tp-notice-acf' );
	
	/*
	*	Admin notice
	*/
	add_action( 'admin_notices', 'tp_notice_missing_acf' );
	function tp_notice_missing_acf()

sushicodeur

Trouver les fichiers terminant par un tag de fermeture php suivi d’espaces ou de lignes vides

D’un coup le site ne parvient plus à rendre les fichiers XML générés, sous prétexte que le fichier commence par des lignes blanches en début de fichier.

La cause est connue, mais trouver le coupable à la main est fastidieux. Cette commande permet de faire la liste des fichiers php susceptibles d’insérer ces lignes blanches en début de fichier.

pcregrep -rMl '\?>[\s\n]+\n\z' * > php_file_ending_with_blank_lines

Le résultat est écrit dans le fichier php_file_ending_with_blank_lines

johnbillion

INITIALISATION
==============

load wp-config.php
set up default constants
load wp-content/advanced-cache.php if it exists
load wp-content/db.php if it exists
connect to mysql, select db
load object cache (object-cache.php if it exists, or wp-include/cache.php if not)
load wp-content/sunrise.php if it exists (multisite only)

helen

#!/bin/bash

# args
MSG=${1-'deploy from git'}
BRANCH=${2-'trunk'}

# paths
SRC_DIR=$(git rev-parse --show-toplevel)
DIR_NAME=$(basename $SRC_DIR)
DEST_DIR=~/Sites/wp-plugins/$DIR_NAME/$BRANCH

justintadlock

<?php

# Register custom post types on the 'init' hook.
add_action( 'init', 'my_register_post_types' );

/**
 * Registers post types needed by the plugin.
 *
 * @since  1.0.0
 * @access public

lucasfais

Sublime Text 2 – Useful Shortcuts (Mac OS X)

General

⌘T	go to file
⌘⌃P	go to project
⌘R	go to methods
⌃G	go to line
⌘KB	toggle side bar
⌘⇧P	command prompt

scribu

#!/usr/bin/env bash

# args
MSG=${1-'deploy from git'}
BRANCH=${2-'trunk'}

# paths
SRC_DIR=$(git rev-parse --show-toplevel)
DIR_NAME=$(basename $SRC_DIR)
DEST_DIR=~/svn/$DIR_NAME/$BRANCH

gist:545079

if (navigator.userAgent.match(/iPhone/i) || navigator.userAgent.match(/iPod/i) || navigator.userAgent.match(/iPad/i)) {
	$(document).ready(function () {
		$('label[for]').click(function () {
			var el = $(this).attr('for');
			if ($('#' + el + '[type=radio], #' + el + '[type=checkbox]').attr('selected', !$('#' + el).attr('selected'))) {
				return;
			} else {
				$('#' + el)[0].focus();
			}
		});

redoPop

# This is a template .gitignore file for git-managed WordPress projects.
#
# Fact: you don't want WordPress core files, or your server-specific
# configuration files etc., in your project's repository. You just don't.
#
# Solution: stick this file up your repository root (which it assumes is
# also the WordPress root directory) and add exceptions for any plugins,
# themes, and other directories that should be under version control.
#
# See the comments below for more info on how to add exceptions for your