| require 'digest/md5' | |
| =begin | |
| About: | |
| This script automatically runs on a 2-second loop, searches the current directory for haml & sass files that have been modified since the last iteration and builds them as needed into a file with the same name minus the .haml/sass extension. I wrote it so I could use Haml & Sass to develop Wordpress themes. | |
| How-to: | |
| 1) Name your source files with the extension you'd like them to have, then add ".haml" or ".sass" as appropriate... | |
| For example: index.php.haml and styles.css.sass |
| # 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 |
This gist assumes:
| <?php | |
| /* | |
| * Plugin Name: Password Reset Removed | |
| * Description: Removes the ability for non admin users to change/reset their passwords. | |
| * Version: 1.0 | |
| * Author: Derek Herman | |
| * Author URI: http://valendesigns.com | |
| */ | |
| class Password_Reset_Removed | |
| { |
| if ($_SERVER['REMOTE_ADDR']=='127.0.0.1') { | |
| define('WP_ENV', 'local'); | |
| } elseif ($_SERVER['HTTP_HOST']=='develop.project.com') { | |
| define('WP_ENV', 'develop'); | |
| } elseif ($_SERVER['HTTP_HOST']=='master.project.com') { | |
| define('WP_ENV', 'develop'); | |
| } else { | |
| define('WP_ENV', 'production'); | |
| } |
Revised date: 07/11/2012
Between us [company name] and you [customer name]
We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.
| <?php | |
| /** | |
| * Conditional Confirmations (with Merge Tag Support) | |
| * http://gravitywiz.com/2012/08/18/conditional-confirmations/ | |
| * | |
| * Provides the ability to register conditional confirmations. To register a new conditional confirmation | |
| * use the GWConditionalConfirmations::add_conditional_confirmation() function. | |
| * | |
| * GWConditionalConfirmations::add_conditional_confirmation($form_id, $field_id, $operator, $value, $confirmation); |
| # Gravity Forms | |
| add_action('admin_init','add_grav_forms'); | |
| function add_grav_forms(){ | |
| $role = get_role('editor'); | |
| $role->add_cap('gform_full_access'); | |
| } | |
| add_filter("gform_validation_message", "change_message", 10, 2); |
| /** | |
| * Add a Gravity forms form to product upon database save. | |
| * | |
| * Requires Gravity Forms and WooCommerce - Gravity Forms Product Add-Ons. | |
| * | |
| * Search for '_gravity_form_data' in wp_postmeta and set $raw_form_data to the serialized string. | |
| * | |
| * @return void | |
| **/ | |
| function mb_woo_product_insert_form($product_ID) { |