Improve Portability for Disabling Various Plugin Features

[alexstandiford]

Hey @szepeviktor! I love this concept, but I find myself wondering if this could be done in a more portable fashion. I look and see all of the files in this and wish that I could just take pieces of the code ad-hoc for different sites, without needing to make sure it all stays up-to-date.

For example, some of my clients don't use Divi, so I wouldn't need that, but a lot of my clients use WooCommerce, so it would be good to have the things that cut back on how much Woo is doing when possible. I have a client, for example, that doesn't use shipping at all, and it would be really useful if there was a way to disable it entirely (although that may be out of scope, just an example).

I think there's a couple different ways that could be solved, but the first that comes to mind for me is using composer with several small packages that split up the different filters to remove.

for example, it could be something like composer require wplite/woocommerce-shipping or something, which disables the shipping feature in woocommerce.

What might be a simpler, and more approachable alternative, however, is to create a WordPress utility plugin that includes an admin interface to enable/disable different plugin features. You could even set it up so that the system detects if common plugins are active and only shows the features that can be disabled for that specific plugin.

[szepeviktor]

for example, it could be something like composer require wplite/woocommerce-shipping or something, which disables the shipping feature in woocommerce.

Yes. That would give me ~100× more work.

Plugins in the mu-plugins folder are templates. When I copy them to a new site I manually edit some of them.
For example the "disable features" for WooCommerce disables ALL features. That does not fit any of the stores. That list must be manually pruned.

[szepeviktor]

AFAIK WC shipping can be disabled by locking woocommerce_ship_to_countries to 'disabled'.