Disable Bloat

Hello @savethefrogs

As you know, Stripe configuration page requires WooCommerce Admin to be active. And if you disable WooCommerce Admin, the Stripe configuration page might be inaccessible. That’s why we have added a notice to this page one year ago.

https://imgur.com/a/eWSvM9

You are now reporting that is is again an issue? Could you please be more specific? Is the notice not being displayed anymore? Is the notice insufficient?

Hello @nanasflowers

Thank you for letting us know about this. You’re correct, the latest update of the plugin introduced a problem that is causing some functions related to WooCommerce to not work correctly.

To fix this issue, please update the plugin to version 3.2.6. This update addresses the problem and should resolve it.

Thank you for letting me know @savethefrogs

Version 3.2.5 of the plugin has been released. Now it shows the notice on the Stripe payment gateway configuration screen.

This info will also be added to the FAQ and plugin documentation. Hope it will make the configuration process more clear to other users!

Thanks for your feedback @savethefrogs

We always thought that adding new notices, distracting elements, banners, and so on is not the primary goal of the plugin, which is supposed to reduce them.

We will definitely add this information to plugin’s FAQ.

What do you think about adding such a notice on Stripe configuration page? Do you think it is helpful and informative enough?

View post on imgur.com

Hello @savethefrogs

Due to WooCommerce limitations, there is no currently an easy way to fix this issue. The only known workaround is disabling the Disable Bloat plugin or its options during Stripe configuration.

Since the Stripe plugin relies heavily on the WooCommerce Admin scripts, it currently requires their presence to function properly, including the modal for adding the Stripe webhook. This dependency is causing the issue you described.

To work around this problem, you can follow these steps:

1. In your plugin settings, uncheck the “Disable WooCommerce Admin” option and save the changes.
2. Configure the Stripe plugin as you normally would, which should allow you to access the modal for adding the webhook.
3. Once you have completed the Stripe configuration, you can restore your plugin configuration by re-enabling the “Disable WooCommerce Admin” option

Hello @lukassasso

Thank you for reaching out.

I have tried to replicate this error in my environment, but it didn’t happen.

It seems that the error is not from our plugin.

The error message you shared suggests that there is an issue with the “is_internal_meta_key” function and the use of generic add/update/get meta methods for internal meta data. Specifically, it mentions the “_billing_phone” meta data. This error message is related to the core WooCommerce functionality and not directly associated with our plugin.

To troubleshoot this issue, we recommend following these steps:

1. Deactivate the Note Finder for WooCommerce plugin temporarily.
2. Check your error logs for more detailed information on the error.
3. Look for any other plugins or themes that might be conflicting with WooCommerce or causing the error.

Please let us know if you have any further questions or if there’s anything else we can assist you with.

Hello @titsmaker

Thank you for reporting this.

The PHP warning is caused by the previous update.

A new version (3.2.4) has just been released. Could you update the plugin and see if the PHP warning is gone?

Hello @ztefani

The plugin has built-in support for multisite, but only on individual site level.

There’s currently no way to adjust global settings for the whole network. We might consider adding such a feature, but until now nobody had reported a need for such feature. Is it something you would find useful?

The unnecessary empty admin menu visible in the multisite admin panel was an error. It has just been removed in the new version – 3.2.3. Please update the plugin to the latest version,

Thank you for a 5-star rating, @hollowdev !

It’s great to hear that you find the plugin convenient.

Hello @wayneoz

Thank you for saying your opinion. You are right – a new user can be easily overwhelmed by the number of PRO options.

But, please keep in mind the history, vision and the main role of this plugin.

At first, the plugin was developed only for WooCommerce and was 100% free. As you can see from my screenshot below, almost all WooCommerce options are available for free. But at that moment there was a feeling that we have to go further and expand among WooCommerce.

We are adding more ans more free options, as you can see from on of the updates this month:

[3.2.0] – 2023-03-01 =

• Added: Choose which WooCommerce Admin features to disable
• Added: Remove the “Get the app” from WooCommerce emails
• Added: Hide the “Discover other payment providers” link on the WooCommerce Payments configuration screen
• Added: Disable WooCommerce email notifications
• Added: Disable WordPress Dashicons on the front-end
• Added: Disable WP Desk Dashboard widget

These options are available in the free version and have been added in only one update, so you can imagine our current vision.

Also, please look at the refund policy. It says that you will get 100% refund if you experience any troubles.

View post on imgur.com

Hello @everpress

The issue has been fixed. Please update the plugin to version 3.2.1. Is the fatal error gone now?

Hello @metacortex

Thank you for your 5-star rating! Your suggestions are worth a lot. I have analyzed all of them and below I will add some info regarding each of them. Please, acknowledge the main and only goal of the plugin is disabling bloat, and removing unused elements, scripts, and so on. Not changing WordPress settings or behavior.

Contact Form Auto P

We believe that using paragraphs instead of double line-breaks is a good standard and we think that the standard autop filter is a good solution.

WP Memory Limit

That functionality is rather modyfing WordPress core settings than making the site lighter. I think that modyfing a memory limit is not always a good practice and it does not align with plugin’s vision. But, why not, we may change the vision in the future.

Autosave future

This is definitely a great idea. I’m sure it is worth implementing in one of the upcoming releases. Please stay tuned for updates.

Block external connections

Same as above. Thanks!

You are very kind. I hope someday these settings will be implemented into the WordPress core and such plugins won’t be needed anymore.

Hello @lukefiretoss

Thank you for this suggestion.

This is definitely a great idea. I’m sure it is worth implementing in one of the upcoming releases. Please stay tuned for updates. Let me mark this thread as resolved, as the idea has been added to our features backlog.

Dear @lukefiretoss

Please update the plugin to version 3.2.0. The requested option has been implemented.

Dear @finalwebsites

Could you update the plugin to version 3.2.0 and check if the issue is gone?

If you are still experiencing problems, please follow my request from the message above and provide the screenshots. Thanks.