• Resolved asmaac

    (@asmaac)


    I have hundreds of messages in my error logs similar to

    PHP Warning:  FS_Plugin::__construct(): The script tried to access a property on an incomplete object. Please ensure that the class definition "FS_Plugin" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide an autoloader to load the class definition in /var/www/html/wp-content/plugins/stackable-ultimate-gutenberg-blocks/freemius/includes/entities/class-fs-plugin.php on line 134

    what’s wrong?

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Benjamin Intal

    (@bfintal)

    Hello, thanks for the report. Looks like a bug with the Freemius SDK we’re using, we’ll investigate this.

    In the meantime, I found a source that says that it might have something to do with object preloading – are you using something like this in a caching solution? If you are, try disabling it and see if that fixes things.

    Thread Starter asmaac

    (@asmaac)

    Thanks for your answer.

    I’m using W3 Total Cache, only the page cache option. I disabled the plugin but still see the error in the logs

    @bfintal, based on our current observations, it appears to be a conflict with another plugin rather than a bug.

    @asmaac, this is Leo from Freemius.?Is there a possibility that you are using a plugin called “Docket Cache” with its “Object Cache Precaching” option enabled? If so, could you please disable it to check if it resolves the issue? If not, please contact us via support (at) freemius (dot) com. We need additional information that cannot be shared publicly to be able to investigate further.

    Thread Starter asmaac

    (@asmaac)

    Hi @leorw,

    No, i don’t use “Docket Cache”. I use W3 Total Cache for caching. Here is the list of the other installed plugins: Solid Security, Blocksy Companion, Branda, Simply Static, WooCommerce, Smush, WPForm Lite, and WPS Hide Login.

    James Lee

    (@jameslhc)

    @leorw, troubleshooted the same problem with my site and it appears to be a conflict with Blocksy theme version 2.0.0 and above.

    Since Blocksy uses Freemius as well and they work very closely with you and Stackables, perhaps you can get in touch with their team and work out the problem? This should ideally be resolved quickly since many users are using Blocksy together with Stackables.

    Thank you, @asmaac.

    @jameslhc, thank you for your testing. Did the issue occur even when only the Stackable and Blocksy companion plugins were active during your testing? Was it a localhost site? Would you also please share the versions of PHP and WordPress you’re using on that site?

    James Lee

    (@jameslhc)

    @leorw It’s not the Blocksy Companion plugin, it is the Blocksy theme. The issue occur with just the Blocksy theme >v2.0 and Stackable installed.

    Not localhost. PHP 8.1. WordPress 6.4.1.

    gmakstutis

    (@gmakstutis)

    Hi, just to say that I’m seeing the same issue. I have several other Blocksy sites with Stackable blocks and they are not showing this issue. This only occurs when in a multisite configuration.

    @jameslhc and @gmakstutis, thank you for the information. We’ve successfully reproduced the issue. Our investigation will continue, and we will provide updates here.

    • This reply was modified 10 months, 4 weeks ago by Leo Fajardo.

    I’m experiencing the same issue using a multisite with the Blocksy theme. Has there been any updates on this?

    Thread Starter asmaac

    (@asmaac)

    From another thread with @leorw, it seems the fix should be done on Blocksy Companion plugin. Maybe he can share more details here.

    @asmaac, @jameslhc, @gmakstutis, and @wpcoderca, the Blocksy team has already released a new version the resolves the issue. Would you please update to the latest version and let us know how it goes?

    Thread Starter asmaac

    (@asmaac)

    Hi @leorw, I tested the latest version of Blocksy companion, the issue is fixed, no more errors in the logs.

    Thank you for your help with this issue.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Error: script tried to access a property on an incomplete object’ is closed to new replies.