Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code-wise this looks good to me.
I would like it if all of our features were better encapsulated so that they could be toggled on/off, but that would probably be a rather large refactor to some areas of WooCommerce Admin.
#6563 is related (and could be closed if this gets merged) |
Added the blocked label here since this is likely something we will need to do a bit of coordination on. In 5.2 of core we will start collecting Tracker data ( for woocommerce.com connected sites ) to get a sense of how many sites are currently toggling wc-admin off via filter. I also feel we might want to do some community outreach here and get some further details from store owners / builders who have deactivated wc-admin and see if there are certain features they would like to toggle off, and maybe we need to expand the feature flag system to allow a finer control over active features. |
Just saw this comment from @lkraav that really speaks to the desire for finer grained controls of wc-admin features. The primary feature, as mentioned in that comment, that I personally feel users will want to disable is Analytics since many sites do already have an analytics toolkit established that they prefer to use. Adding in full feature flag support for analytics might be a bit of work considering how integrated it is, but is definitely feasible. |
Strongly agree. |
We should definitely allow ways for plugins to disable specific or all features of WC Admin. A good use case would be Product Vendors extension where the logged in user is a vendor admin. They have their own customized WP menu items such as custom reports and such however they do share the Products menu with the site admin. WC Admin attempts to hijack this and causes issues for vendor admins where the Products menu item disappears. Since vendor admins don't need to use any of the features, would be good to allow them to disable all of this. Currently the way to do this for Product Vendors is something like this:
Of course we could continue to use this method. |
Thanks @roykho - another great use case we need to consider. |
Some more feedback from @erikmolenaarnl in #6563 (comment).
|
Just noting our own documentation causes a fatal error when WC Admin is disabled with this filter. Issue #6673 |
Another instance where an extension had a fatal error when WC Admin is disabled #6703 Since this PR is blocked, I think we need to raise more awareness about this filter among extension developers. |
Kicked off a thread to discuss this further among the dev teams: pcShBQ-1i-p2 |
This PR has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This PR was automatically closed due to being stale. |
Thanks for the discussion everyone. I'm closing this one in favour of #6568 which hopefully accomplishes the goal of keeping wc-admin the platform while allowing parts to be turned off to keep WooCommerce lean. |
Removes the ability to turn off wc-admin.
Now that wc-admin is in Core, more and more functionality is baked into the plugin, and extensions build off its functionality, it makes less and less sense to allow users or plugins to disable it.
This PR removes the ability to disable the plugin and will be a good space to discuss the ramifications.