quasel

<?php

//Display Fields
add_action( 'woocommerce_product_after_variable_attributes', 'variable_fields', 10, 3 );
//JS to add fields for new variations
add_action( 'woocommerce_product_after_variable_attributes_js', 'variable_fields_js' );
//Save variation fields
add_action( 'woocommerce_save_product_variation', 'save_variable_fields', 10, 1 );

/**

quasel

<?php
    //set up pods::find parameters to limit to 5 items
    $param = array(
        'limit' => 5,
    );
    //create pods object
    $pods = pods('pod_name', $params );

    //check that total values (given limit) returned is greater than zero
    if ( $pods->total() > 0 ) {

quasel

Why objects (usually) use less memory than arrays in PHP

This is just a small post in response to [this tweet][tweet] by Julien Pauli (who by the way is the release manager for PHP 5.5). In the tweet he claims that objects use more memory than arrays in PHP. Even though it can be like that, it's not true in most cases. (Note: This only applies to PHP 5.4 or newer.)

The reason why it's easy to assume that objects are larger than arrays is because objects can be seen as an array of properties and a bit of additional information (like the class it belongs to). And as array + additional info > array it obviously follows that objects are larger. The thing is that in most cases PHP can optimize the array part of it away. So how does that work?

The key here is that objects usually have a predefined set of keys, whereas arrays don't:

quasel

<?php 
    	//get Pods object for current post
    	$pod = pods( 'pod_name', get_the_id() );
	//get the value for the relationship field
	$related = $pod->field( 'relationship_field' );
	//loop through related field, creating links to their own pages
	//only if there is anything to loop through
	if ( ! empty( $related ) ) {
		foreach ( $related as $rel ) { 
			//get id for related post and put in ID

quasel

<?php

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

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

quasel

<?php

function ms_add_tax_to_api() {
    $taxonomies = get_taxonomies( '', 'objects' );
    
    foreach( $taxonomies as $taxonomy ) {
	    $taxonomy->show_in_rest = true;
    }
}
add_action( 'init', 'ms_add_tax_to_api', 30 );

quasel

add_action( 'woocommerce_cart_actions', 'move_proceed_button' );
function move_proceed_button( $checkout ) {
	echo '<a href="' . esc_url( WC()->cart->get_checkout_url() ) . '" class="checkout-button button alt wc-forward" >' . __( 'Proceed to Checkout', 'woocommerce' ) . '</a>';
}

quasel

<?php
/**
 * Template Name: Library Resource List
 *
 * This is the template that displays all pages by default.
 * Please note that this is the WordPress construct of pages
 * and that other 'pages' on your WordPress site will use a
 * different template.
 *
 * @package asotin_county_library

quasel

<?php
/**
 * @package    ThemeName
 * @version    0.1.0
 * @author     Your Name <you@youremailprovider.com>
 * @copyright  Copyright (c) 2013, Your Name
 * @link       http://yoursite.com/themes/theme-slug
 * @license    http://www.gnu.org/licenses/old-licenses/gpl-2.0.html
 */

quasel

/**
* Check if your WooCommerce custom product attributes are taxonomies.
*
* This will show custom product attributes on your product page
* above the Add to Cart button.
* 
* THIS WILL ALSO SHOW A NOTICE ON THE PRODUCT PAGE
* RIGHT UNDER THE ATTRIBUTES.
*
* THE NOTICE WILL EITHER SAY: