We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Further to this forum thread, it would seem sensible to prevent the compat plugin from activating if Classic Commerce itself isn't already activated.
Similarly, if both CC and the compat plugin are active and then CC is deactivated, the compat plugin should be deactivated at the same time.
This may help to prevent some installation / migration issues as mentioned in the forum post.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Further to this forum thread, it would seem sensible to prevent the compat plugin from activating if Classic Commerce itself isn't already activated.
Similarly, if both CC and the compat plugin are active and then CC is deactivated, the compat plugin should be deactivated at the same time.
This may help to prevent some installation / migration issues as mentioned in the forum post.
The text was updated successfully, but these errors were encountered: