Gaurav Tiwari

Currently it parses shortcodes to fields were bricks supports any shortcode, for example Content element. Bricks already have date based {shortcodes} but I see that it could be useful in the wider context. I will push an update for this. Thank you for reporting.

Added in 1.7.1:

Disable all core filters (shortcodes will work but will only work in post content and blocks):

add_filter( 'dmyip_core_filters', '__return_empty_array' );

Disable specific filters — e.g., stop do_shortcode on the_title (fixes ACF field name conflicts):

add_filter( 'dmyip_core_filters', function ( $filters ) {
    $filters['the_title'] = false;
    return $filters;
} );

Disable multiple filters at once:

add_filter( 'dmyip_core_filters', function ( $filters ) {
    $filters['the_title']         = false;
    $filters['single_post_title'] = false;
    $filters['wp_title']          = false;
    return $filters;
} );

Only keep excerpt processing (disable everything else):

add_filter( 'dmyip_core_filters', function () {
    return array(
        'the_title'             => false,
        'single_post_title'     => false,
        'wp_title'              => false,
        'the_excerpt'           => true,
        'get_the_excerpt'       => true,
        'get_the_archive_title' => false,
    );
} );

Available filter keys Key WordPress filter What it does the_titlethe_title Processes shortcodes in post titles displayed on the page single_post_titlesingle_post_title Processes shortcodes in the browser tab title (single posts) wp_titlewp_title Processes shortcodes in wp_title() output the_excerptthe_excerpt Processes shortcodes in displayed excerpts get_the_excerptget_the_excerpt Processes shortcodes when retrieving raw excerpt get_the_archive_titleget_the_archive_title Processes shortcodes in archive page titles

All default to true. Set to false to disable.

I will add a filter to avoid adding do_shortcode to the native WP elements. It’s not just about ACF – maybe the user doesn’t want it at all.

I just don’t want to add a settings page, otherwise the plugin could have been very customizable.

Thank you so much! Really appreciate it. Feel free to create a support thread, if you ever need some help.

Nice ideas. Implemented. Please update to 1.3.9 and let me know if something is still broken.

Thanks for the report. I can confirm that this is the case. It hasn’t been tested a lot with FSE themes. I will start working on an update to improve this.

This is a very specific use case @paulryken .

You can use this into your child theme’s functions.php or Code Snippets plugin.

add_shortcode('specialdate', 'dmyip_rmd_specialdate');
function dmyip_rmd_specialdate($atts) {
    // Set default attributes and merge with user input
    $attributes = shortcode_atts(array(
        'floor_date' => 'today',
        'ceiling_date' => 'last sunday of january next year'
    ), $atts);

    // Parse the floor date using strtotime
    $floor_date = strtotime($attributes['floor_date']);
    if (!$floor_date) {
        return ''; // Clear any error messages
    }

    // Parse the ceiling date using strtotime
    $ceiling_date = strtotime($attributes['ceiling_date']);
    if (!$ceiling_date) {
        return ''; // Clear any error messages
    }

    // Calculate the ceiling date next year
    $ceiling_date_next_year = strtotime('+1 year', $floor_date);

    // Get today's date
    $today = time();

    // Determine if today's date is between the floor date and the ceiling date next year
    if ($today >= $floor_date && $today <= $ceiling_date_next_year) {
        // Format the ceiling date with day, month, and year
        $display_date = date_i18n('j F Y', $ceiling_date);
        return esc_html($display_date);
    }

    return '';
}

add_shortcode('specialyear', 'dmyip_rmd_specialyear');
function dmyip_rmd_specialyear($atts) {
    // Set default attributes and merge with user input
    $attributes = shortcode_atts(array(
        'floor_date' => 'today',
        'ceiling_date' => 'last sunday of january next year'
    ), $atts);

    // Parse the floor date using strtotime
    $floor_date = strtotime($attributes['floor_date']);
    if (!$floor_date) {
        return ''; // Clear any error messages
    }

    // Parse the ceiling date using strtotime
    $ceiling_date = strtotime($attributes['ceiling_date']);
    if (!$ceiling_date) {
        return ''; // Clear any error messages
    }

    // Calculate the ceiling date next year
    $ceiling_date_next_year = strtotime('+1 year', $floor_date);

    // Get today's date
    $today = time();

    // Determine if today's date is between the floor date and the ceiling date next year
    if ($today >= $floor_date && $today <= $ceiling_date_next_year) {
        // Format the ceiling date to show just the year
        $display_year = date_i18n('Y', $ceiling_date);
        return esc_html($display_year);
    }

    return '';
}

It has two components.

[specialdate ceiling_date="last sunday of january next year"] will show the full date like 28 January 2025.

[specialyear ceiling_date="last sunday of january next year"] will just show 2025.

In the ceiling_date argument you can ask for dates in natural language.

Let me know if this works.

I will be adding this to the plugin as well but only after someone else asks for it.