For the use case of a shortcode within a Pods Template within a looped block such as Pods Item List within a page builder such as Gutenberg:
The block in this case, similar to elements or other page builders, does not currently have a way to inform the shortcode of the block’s context.
Below is one solution, version 2 (full plugin), which requires the format [is_past my_date_field id="{@ID}"] …Content… [/is_past] for use in a Pods Template:
<?php
/**
* Plugin Name: Shortcodes - Past/Future
* Description: For a field named <code>my_date_field</code>, <code>[is_past my_date_field]Commentary[/is_past]</code> will display <code>Commentary</code> if the date/time in field <code>my_date_field</code> is before now. For use in Pods Templates, use <code>[is_past my_date_field id="{@ID}"]...Commentary...[/is_past]</code>.
* Version: 2
*/
/**
* [is_past name_of_field]...content...[/is_past]
*/
add_shortcode(
'is_past',
function( $atts, $content, $tag ) {
$timestamp = date_field_to_timestamp( $atts );
if (
! empty( $timestamp ) // Timestamp is not empty, false, or zero.
&& $timestamp < time() // Timestamp is in the past.
) {
return $content;
}
return '';
}
);
/**
* [is_future name_of_field]...content...[/is_future]
*/
add_shortcode(
'is_future',
function( $atts, $content, $tag ) {
$timestamp = date_field_to_timestamp( $atts );
if (
! empty( $timestamp ) // Timestamp is not empty, false, or zero.
&& $timestamp > time() // Timestamp is in the future.
) {
return $content;
}
return '';
}
);
/**
* A date field is a string (text characters).
* A timestamp is an integer representing seconds since Jan 1 1970 UTC.
*/
function date_field_to_timestamp( $atts ) {
$field_name = (
array_key_exists( 0, $atts )
&& ! empty( $atts[0] )
) ? $atts[0] : DEFAULT_DATE_FIELD_FOR_COMPARISONS;
// Pods Templates: Pass {@ID} to shortcode via id="{@ID}".
$post_id = ! empty( $atts['id'] ) ? absint( $atts['id'] ) : get_the_ID();
$field_value = (string) get_post_meta( $post_id, (string) $field_name, true );
if ( empty( $field_value ) ) {
return false;
}
$timestamp = (int) strtotime( $field_value );
if ( -62169984000 === $timestamp ) {
return false;
}
return $timestamp;
}
Alternatively, the plugin below can be added to make the id="{@ID}" addition unnecessary.
The additional filter below changes the way Pods templates handle context — shortcodes within looped Pods Templates will have access to the global Post object the template is looping over.
The filter below might align more closely with how some users may expect things should behave.
It may also have consequences which could cause other unexpected behavior, as it transfers a partial shared context between systems which operate on different foundational assumptions.
<?php
/**
* Plugin Name: Pods Templates - Global Post for Shortcodes
* Description: Cause global <code>$post</code> functions to be available to shortcodes used in Pods Templates.
* Version: 1
*/
/**
* May have unexpected consequences related to shortcode / magic tag processing order.
* Does not change behavior of other query objects, e.g., taxonomies, users, etc.
*/
add_filter(
'pods_templates_do_template',
function( $output, $code, $pod ) {
if (
! is_object( $pod )
|| empty( $pod->pod_data )
|| 'post_type' !== pods_v( 'type', $pod->pod_data, '' )
|| empty( $pod->id() )
) {
return $output;
}
( new WP_Query( [ 'ID' => $pod->id() ] ) )->the_post();
$output = do_shortcode( $output );
wp_reset_postdata();
return $output;
},
10,
3
);
