Disable Bloat

@lukefiretoss

There’s an option built into WooCommerce that allows to change the behavior of the new product editor, but I’m sure that adding such settings to the plugin will make it useful.

View post on imgur.com

Dear @finalwebsites

Could you please provide a screenshot showing the API calls in your WordPress? As I was unable to replicate the issue on my end, I think it might be related to the fact that you can’t connect to Freemius server. I also think there might be a quite easy solution for your problem.

Please send me the screenshot and I will try to help you ASAP.

Thanks

Hello @finalwebsites

?Of course, we know the disadvantages of the Freemius platform.

?We are currently looking at AppSero and LemonSqueezy as an alternative. At this moment, it looks that both of them are missing crucial (for us) features. ?We are still investigating the pros and cons of switching to different license platforms.

Please give us some time to choose the best possible solution.

Hello @nanasflowers

The issue was caused by the fact that some of the plugin logic has been moved from the main plugin file to one of the included files.

It has now been fixed in version 3.1.15. Please update the plugin to the latest version and let me know if the issue is solved. Thanks

Dear @eletsohu @ingenuitor

With a big help of @ingenuitor the issue has been replicated and fixed in plugin version 3.1.14

Please update the plugin to the latest version. Is the problem solved in your site now?

Hi @mercurydan

These warnings come from WordPress core (to be more specific, the Requests library), not the plugin. The Query Monitor is showing Disable Bloat, but these are false positives.

Please note that WordPress still does not have full support for PHP 8.1 (it’s still “beta” support). To get rid of these warnings, you can either downgrade to PHP 8.0 or manually upgrade the Requests library.

You can read more about this here: https://roots.io/wordpress-php-8-1-support-not-found/

I’m marking this thread as resolved, as this issue is not related to the plugin.

As @neikoloves did not respond, I assume that the problem has been resolved. The thread has been mark as resolved.

Dear @neikoloves , if your problem is still occurring, please create a new thread.

Hello @tadeaskula

The compatibility with WooCommerce HPOS (Custom order tables) has been added to the plugin. Please update the plugin to the latest version and let me know if everything is alright.

Thanks!

Hello @zecamaral

could you please make sure that you have Disable WooCommerce Blocks (front-end) option unchecked?

View post on imgur.com

Could you provide a link to your shop?

Hello @titsmaker

Please note that these warnings come from disable-comments plugin, as your error log says:

Deprecated: Creation of dynamic property DisableComments_Plugin_Tracker::$notice_options is deprecated in \wp-content\plugins\disable-comments\includes\class-plugin-usage-tracker.php on line 657

Please contact the developer of the plugin you are using. If you happen to find any notices coming from our plugin, please create a new thread. I’m marking this thread as resolved.

Dear @eletsohu

I was unable to replicate this issue using our test environments.

Could you please check the WooCommerce folder name in your wp-content/plugins directory?

Please make sure that the WooCommerce folder should be named simply woocommerce. Is it named that way or does it have a different folder name?

Hello @galbaras

Thank you for noticing and reporting. It is indeed a human error that occurred during the process of rewriting the plugin and pasting the phrases into the PHP code.

It will be fixed in the upcoming release. Play stay tuned for updates. I’m marking this thread as resolved.

Dear @cheekymate06

Did you manage to update the plugin on your website to version 3.1.11 safely? You are right, the changelog is missing information about this version – it will be fixed in the upcoming days. But in fact, there were not many changes between 3.1.11 and the previous version.

@gdm57 Please let me know if everything is fine with your website now.

I’m marking this thread as resolved. If you encounter any problems, please feel free to post in this topic or create a new thread.

Dear @luboslives @gdm57 @ashbyvagg and many more,

In the past hours, a new, broken release has been published. It has been available for 1-2 hours, so if one of you has updated the plugin during this time (or using an automatic updates system), you might encounter some errors. Updating to this version might result in crashing your site. It is definitely an unacceptable situation in the whole Web development industry and I’m sorry that you had to deal with this.

I’m now investigating this issue and trying to analyze which steps of our workflow lead to deploying a broken version with missing files. The whole release has been tested and confirmed that it is working fine, but at some point, it turned out that the published version of the plugin was different from the one that has been tested by us.

Sorry about that. We will now enhance our workflow to ensure that this situation won’t happen again.

You can now safely update to version 3.1.11. This version is working correctly and you can be sure that your site will be working correctly after updating to version 3.1.11.