Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter mafields

    (@mafields)

    We’re using the Local engine.

    Thanks for confirming the issue, we’ll keep an eye on the changelog and hope to see a fix soon!

    It looks like there is an infinite loop problem with the latest version.

    The wp:tribe/event-links block calls googleCalendarLink, which gets the contents of the post, which calls do_block, which executes the wp:tribe/event-links block, which calls googleCalendarLink, etc, etc, etc.

    It looks like this was attempted to be fixed via the call to remove_filter, which prevents the blocks from executing during googleCalendarLink, but it’s called after the calendar link is fetched, so the infinite loop happens anyway.

    Moving “remove_filter( ‘the_content’, ‘do_blocks’, 9 );” in src/views/blocks/event-links.php up to just after the very first if statement fixes the issue for me.

    Thread Starter mafields

    (@mafields)

    I see this was added. Thanks!

    I had to revert as well, for the same reason. 3.2.0 works fine.

    It looks like in 3.2.1 the following change was made:
    /wp-content/plugins/stream/connectors/class-connector-settings.php
    – line 718

    Before:
    $changed_options[] = array(
    ‘label’ => $this->get_field_label( $option ),
    ‘option’ => $option,
    ‘context’ => $context,
    // Prevent fatal error when saving option as array
    ‘old_value’ => (string) maybe_serialize( $old_value ),
    ‘value’ => (string) maybe_serialize( $value ),
    );

    After:
    $changed_options[] = array(
    ‘label’ => $this->get_field_label( $option ),
    ‘option’ => $option,
    ‘context’ => $context,
    ‘old_value’ => (string) $old_value,
    ‘value’ => (string) $value,
    );

    This means that any array or object results in a fatal error when it is cast to a string unless it is an object with a __toString method.

    Reverting this change should fix the error.
    Eagerly awaiting this patch.

    Thread Starter mafields

    (@mafields)

    Yes, the development version you linked fixes the issue. I assume this fix will be applied to the Pro version as well (as it shares the same problem)?

    Thanks so much for the quick turnaround!

Viewing 5 replies - 1 through 5 (of 5 total)