geekontheroad

/**
 * This snippet will add a datepicker to the list field of Gravity Forms.
 * Just copy paste this snippet and complete the configuration at the bottom
 * Also make sure that Jquery UI is loaded otherwise this won't work (<script src="https://code.jquery.com/ui/1.13.2/jquery-ui.js"></script>)
 *
 * @author Johan d'Hollander
 * @link <https://geekontheroad.com>
 **/

jQuery(document).ready(function() {

webzunft

# Basic queries to analyse canceled subscriptions using EDD Recurring Payments pre EDD 3.0
# Use EXPLAIN if you have large stores since the "notes" column is not indexed and queries can take some time
# Some of these reports might be worth storing as Views and look at the graphs PHPMyAdmin can also create from them

# List subscription cancelation with creation and cancelation date, as well as the user who canceled
# good as a basis for further queries

SELECT ID,
  created,
  REGEXP_SUBSTR( REGEXP_SUBSTR( notes, '.* Status changed from active to cancelled .*' ), '^[a-z]+ [0-9]+, [0-9]+' ) AS 'date',

carlalexander

<?php

/**
 * By default, cURL sends the "Expect" header all the time which severely impacts
 * performance. Instead, we'll send it if the body is larger than 1 mb like
 * Guzzle does.
 */
function add_expect_header(array $arguments)
{
    $arguments['headers']['expect'] = '';

landbryo

add_filter( 'gform_form_post_get_meta_7', 'add_form_fields' );
function add_form_fields( $form ) {

	// Don't make the parent form messy
	if ( ! GFCommon::is_form_editor() ) {

		// form we are adding fields to
		$parent_id = $form['id'];
		// template form ID
		$childId = 5;

generatepress

add_filter( 'generate_header_element_display', function( $display ) {
	if ( ! has_post_thumbnail() ) {
		return false;
	}
	
	return $display;
} );

joedooley

<?php

/**
 * Filters the API mode for a specific form to 'test'.
 *
 * @param $api_mode string Either 'test' or 'live'
 *
 * @return string Returns 'test' for targeted form. Otherwise,
 *                will return the value for the $api_mode setting.
 */

saltnpixels

<?php
/**
 * Payment subscriptions and updating billing and cancelling subscriptions takes place with these hooks
 * We need the stripe customer user id for updating billing
 * we need the entry id of subscription so we can cancel it.
 */


/**
 * @param $entry

spivurno

<?php
/**
 * WARNING! THIS SNIPPET MAY BE OUTDATED.
 * The latest version of this snippet can be found in the Gravity Wiz Snippet Library:
 * https://github.com/gravitywiz/snippet-library/blob/master/gravity-forms/gw-manual-entries.php
 */
/**
 * Gravity Wiz // Gravity Forms // Manual Entries
 *
 * Create entries manually for Gravity Forms. Adds an "Add New" button next to the page title on all entry-related pages.

spivurno

<?php
/**
 * WARNING! THIS SNIPPET MAY BE OUTDATED.
 * The latest version of this snippet can be found in the Gravity Wiz Snippet Library:
 * https://github.com/gravitywiz/snippet-library/blob/master/gravity-forms/gw-manual-notifications.php
 */
/**
 * Gravity Wiz // Gravity Forms // Send Manual Notifications
 *
 * Provides a custom notification event that allows you to create notifications that can be sent

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.