Support » Plugin: Stream » Had to roll back to 3.2.0

  • Resolved nseeger

    (@nseeger)


    Hi,

    Just a heads up I think there may be an incompatibility? We updated Stream on three websites, one gave a blank white screen, another with this error:

    Catchable fatal error: Object of class stdClass could not be converted to string in /wp-content/plugins/stream/connectors/class-connector-settings.phpon line 722

    I updated the latest on The Events Calendar Plugin (both free and pro) and Yoast 5.4. After testing, it is definitely The Events Calendar Plugins when I get a white screen.

Viewing 15 replies - 1 through 15 (of 20 total)
  • 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.

    This is a total pain – I have had to set 76 WordPress installations to reverted or deactivated this morning because of this problems.

    Same problem, I think. This is the fatal error I’m seeing on our sites:

    PHP Catchable fatal error: Object of class stdClass could not be converted to string in /nas/content/live/sitename/wp-content/plugins/stream/connectors/class-connector-settings.php on line 722

    I am getting a 500 server error when updating the plugin to the new version.

    Also, receiving this error.

    /nas/content/live/sitename/wp-content/plugins/stream/connectors/class-connector-settings.php

    davidsteindesign

    (@davidsteindesign)

    Ditto! Same error:

    PHP Catchable fatal error: Object of class stdClass could not be converted to string in /nas/content/live/sitename/wp-content/plugins/stream/connectors/class-connector-settings.php on line 722

    On sites that use Event Calendar (free & pro) as well as sites that aren’t using that p/i.

    Ted Slater

    (@tedslater)

    Just pushing this back to the attention of the developer of this fine plugin: The latest version has a fatal bug in it.

    Tobias_Conrad

    (@tobias_conrad)

    Here too:

    [12-Sep-2017 10:28:30 UTC] PHP Recoverable fatal error: Object of class stdClass could not be converted to string in /var/www/clients/client1/web3/web/wp-content/plugins/stream/connectors/class-connector-settings.php on line 722

    PHP 7.1 ngnix server

    pagan11460

    (@pagan11460)

    Me, too. Is anyone around to fix this? Stream is a great plugin! I hope you can fix this.

    • This reply was modified 3 months ago by  pagan11460.
    Ted Slater

    (@tedslater)

    I’ve tweeted the 4 developers for this plugin, notifying them of this thread. Hopefully they’re able to resolve this issue shortly.

    pagan11460

    (@pagan11460)

    Thanks, Ted. Did they acknowledge your tweet?

    Ted Slater

    (@tedslater)

    Not yet …

    Plugin Contributor Stream

    (@stream)

    I’ll try to get this fixed this morning with a 3.2.2 release. I should really close out our Twitter account since it’s almost never used. Sorry about missing that.

    • This reply was modified 3 months ago by  Stream.
    Plugin Contributor Stream

    (@stream)

    @nseeger et. al.,

    I was unable to replicate the fatal error on any of my setups, using Stream 3.2.1 and the latest version of The Events Calendar (free).

    Based on the information everyone was able to provide above, I created what I _think_ should be a fix. It’s on the latest development branch on Github. You can download it here: https://github.com/xwp/stream/archive/develop.zip

    Could somebody please get back to me to let me know if that fixes the problem?

    Ted Slater

    (@tedslater)

    Thanks! FWIW, we’re using WP Engine managed hosting for our sites, the Enterprise level. Not sure if that bit of info helps.

    Plugin Contributor Stream

    (@stream)

    No worries. If a couple people can confirm that this fixes the issues, I’ll release it.

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