• Resolved Geek Goddess

    (@geek-goddess)


    Uncaught Exception: Error while making pue.notices: call to undefined function tribe_is_truthy().
    in?/[redacted]/public_html/wp-content/plugins/the-events-calendar/common/src/Common/Contracts/Container.php?on line?28

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support tristan083

    (@tristan083)

    Hi @geek-goddess ,

    Thank you for reaching out.

    I recognize how challenging this must be; but, let me try to assist you here to the best of my abilities.

    Could you please try doing the following steps, and see if this alleviates the situation?

    Step 1: Remove the Corrupted Option
    The first step is to clean the corrupted option from your database. You can do this in one of two ways:
    a) If Your Site is Accessible:
    Add the following snippet to your site and load it once to clean the corrupted option,

    add_action( 'init', fn() => delete_option( 'tribe_pue_key_notices' ), 1 );

    You can add the code snippet to your site using the?Code Snippets?plugin. Please make sure to configure this snippet to run once (https://i.imgur.com/5AjRWGc.png).

    b) If Your Site is Inaccessible:
    Run the following SQL command directly in your database to remove the corrupted option:

    DELETE FROM wp_options WHERE option_name='tribe_pue_key_notices';

    Important:?Ensure you’re using the correct database table prefix (e.g.,?wp_). Some sites use custom prefixes, so double-check this before running the query.

    Step 2: Remove the Initial Snippet
    If you used the snippet from Step 1 to clean the corrupted option, you can now safely remove it.

    ?Step 3: Update/Re-activate the plugin
    If you already have The Events Calendar plugin on version 6.10.1, try reactivating it. If not, update it and reactivate it.

    Plugin Support tristan083

    (@tristan083)

    Hi ,

    Thank you for your message and the information.

    Our products team have been made aware of this concern, and we’ve created an internal bug report for it, which I’ve added this case into. This way, this thread will get updated as soon as the issue has been sorted out or a fix has been released.

    Your patience on this matter is highly appreciated.


    Internal Bug Ticket Reference: TECTRIA-760

    Thread Starter Geek Goddess

    (@geek-goddess)

    tristan083, your solution doesn’t work as it only fixes part of the issue. However, I was able to fix it (for now) by using code from Serafin Danessa that was posted in the thread (but is now not visible for some reason). Hopefully the team at TEC will put out a quick fix for the issue soon.

    seems like they are working on it according to their tribe common repository:

    https://github.com/the-events-calendar/tribe-common/actions

    I personally would hold off creating bandaids until they commit their fix and you can update the plugin, could cause more issues in long run.

    • This reply was modified 3 weeks, 5 days ago by hubrizer.
    Moderator Support Moderator

    (@moderator)

    If you are not the person who created this topic and you need support then per the forum guidelines please start your own topic.

    https://www.ads-software.com/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too

    You can do so here.

    https://www.ads-software.com/support/plugin/the-events-calendar/

    All of the many “I have this problem too” replies have been archived. Do not pile onto other people’s topics, please start your own.

    Hey there,

    My previous post got flagged, so I’ll add the code again in case it’s useful.
    It basically just combines the hook they provided, with temporarily re-declaring the function to prevent the fatal error.

    That said, given that they are working on a patch, as @hubrizer mentioned, I suppose it’s probably worth waiting for an update, for those that already rolled back to previous versions successfully.

    Remember to remove this after updates are released and tested ??

    add_action( 'init', fn() => delete_option( 'tribe_pue_key_notices' ), 1 );

    if ( ! function_exists( 'tribe_is_truthy' ) ) {
    function tribe_is_truthy( $var ) {
    if ( is_bool( $var ) ) {
    return $var;
    }

    /**
    * Provides an opportunity to modify strings that will be
    * deemed to evaluate to true.
    *
    * @param array $truthy_strings
    */
    $truthy_strings = (array) apply_filters( 'tribe_is_truthy_strings', array(
    '1',
    'enable',
    'enabled',
    'on',
    'y',
    'yes',
    'true',
    ) );
    // Makes sure we are dealing with lowercase for testing
    if ( is_string( $var ) ) {
    $var = strtolower( $var );
    }

    // If $var is a string, it is only true if it is contained in the above array
    if ( in_array( $var, $truthy_strings, true ) ) {
    return true;
    }

    // All other strings will be treated as false
    if ( is_string( $var ) ) {
    return false;
    }

    // For other types (ints, floats etc) cast to bool
    return (bool) $var;
    }
    }
    Thread Starter Geek Goddess

    (@geek-goddess)

    Thank you for reposting that, Serafin. I had taken your previous post and put it into a plugin and it works great. I’m also a WordPress dev and could see what it was doing, so I knew it was OK to use. I know they are working on an update, so hopefully it will be released soon.

    Plugin Support Chika Ibeneme

    (@chikaibeneme)

    Hi There,

    Thank you for your patience.

    We’ve just released a hotfix for the issue:

    “Fatal error: Uncaught TEC\Common\Exceptions\Not_Bound_Exception: Error while making pue.notices:…”

    This fix is included in our latest release:

    Please update to these versions to take advantage of the fix.

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.