stephenharris

<?php
/**
 * Lightens/darkens a given colour (hex format), returning the altered colour in hex format.7
 * @param str $hex Colour as hexadecimal (with or without hash);
 * @percent float $percent Decimal ( 0.2 = lighten by 20%(), -0.4 = darken by 40%() )
 * @return str Lightened/Darkend colour as hexadecimal (with hash);
 */
function color_luminance( $hex, $percent ) {
	
	// validate hex string

kozo002

jQuery.fn.brightness = function() {
  var bg_color, rgba, y;
  bg_color = this.css('background-color');
  if ((bg_color != null) && bg_color.length) {
    rgba = bg_color.match(/^rgb(?:a)?\(([0-9]{1,3}),\s([0-9]{1,3}),\s([0-9]{1,3})(?:,\s)?([0-9]{1,3})?\)$/);
    if (rgba != null) {
      if (rgba[4] === '0') {
        if (this.parent().length) return this.parent().brightness();
      } else {
        y = 2.99 * rgba[1] + 5.87 * rgba[2] + 1.14 * rgba[3];

clsource

<?php

/*
 * 401 Response
 * 
 * Sends a 401 Response Unauthorized
 * 
 * @author Camilo Castro
 * 
 * @date 29/07/2014

chriscoyier

How WordPress Plugins Should Handle Front End Resources

This is a WORK IN PROGRESS intended for fleshing out and feedback

It's very common for people to be unhappy with how a WordPress plugin adds front end resources to their site. If a plugin needs CSS, the plugin will add a <link> element to that CSS. If the plugin needs JavaScript, it will add a <script> to that JavaScript.

Plugins do this because it works. It's damn important for a WordPress plugin to work, even in adverse conditions. They rightfully want good ratings and little customer support.

But this comes at the cost of additional HTTP requests. In optimizing front end performance of a site, reducing the number of HTTP requests is a huge thing. Front end developers want to decide and control how front end resources are being handled, and WordPress plugins don't typically make this easy on them.

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;

ferdiunal

<?php
  // Kullanacağımız array'yı belirleyelim
  // Bu herhangi biri olabilir.
  $array = [
        'settings' => [
    			'public'	=>	[
    				'create'	=>	true,
    				'update'	=>	true,
    				'delete'	=>	true,
    			],

mattyza

<?php
/**
 * Plugin Name: Double Post Type Rewrite Rule Example
 * Plugin URI: https://gist.github.com/mattyza/7dfd156992f23835f68e
 * Description: Adds a custom rewrite rule to mimic http://domain.com/post-type-01/post-type-02/.
 * Author: Matty Cohen
 * Author URI: http://matty.co.za/
 * Version: 1.0.0
 * Stable tag: 1.0.0
 * License: GPL v3 - http://www.gnu.org/licenses/old-licenses/gpl-3.0.html

seanmcn

#Insall Ajenti
apt-get update
wget http://repo.ajenti.org/debian/key -O- | apt-key add -
echo "deb http://repo.ajenti.org/ng/debian main main ubuntu" >> /etc/apt/sources.list
apt-get update
apt-get install ajenti
service ajenti restart

# Uninstall Apache2
sudo apt-get autoremove && sudo apt-get remove apache2*

tomazzaman

Gulp workflow for WordPress theme development

Requirements

In order for Livereload to work, you need a Firefox or Chrome extension as Gulp doesn't inset it automatically. Alternatively, you can also manually put the livereload script in footer.php, just make sure to insert it only on development environment:

<script>document.write('<script src="http://' + (location.host || 'localhost').split(':')[0] + ':35729/livereload.js?snipver=1"></' + 'script>')</script>

Yimiprod

/**
 * This code is licensed under the terms of the MIT license
 *
 * Deep diff between two object, using lodash
 * @param  {Object} object Object compared
 * @param  {Object} base   Object to compare with
 * @return {Object}        Return a new object who represent the diff
 */
function difference(object, base) {
	function changes(object, base) {