Fix a fatal error when CC is active and the user tries to activate Woo #175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All Submissions:
Changes proposed in this Pull Request:
Currently when Classic Commerce is active and a user tries to activate WooCommerce, a fatal error occurs because WooCommerce tries to redefine the global function
wc()
which is already defined by Classic Commerce.There is existing code in Classic Commerce to try to prevent this situation, but it doesn't work in this case because on the request where a new plugin is activated it runs after other plugins load and even after the
init
action. Reference:The fix in this PR is to intercept any request that represents an attempt to activate WooCommerce while Classic Commerce is still active. I wouldn't say this is beautiful but it is the only way I could find to get it working.
This is a follow up to #165 #173 and other related changes.
How to test the changes in this Pull Request:
Screenshot - before:
Screenshot - after:
Changelog entry