You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up to Issue #1170, where the Plugin Dependencies feature was introduced (thanks @ryanhungate for adding this! 🙏 ), but the existing WooCommerce plugin check was not removed.
Since WordPress now handles plugin dependencies natively, ideally, we don't need to check the plugin now.
Problem:
Users with non-standard WooCommerce folder names still encounter error messages. Specifically, the Mailchimp for WooCommerce plugin is available in the WooCommerce onboarding wizard. However, when they use a custom folder name for WooCommerce, this causes an issue that users will get an error message.
To bypass this error, I understand that users can define the RUNNING_CUSTOM_WOOCOMMERCE constant, but it's not a good user experience.
Maintaining redundant code adds unnecessary complexity and potential points of failure.
Suggested Changes:
Deprecate/remove the mailchimp_check_woocommerce_plugin_status and mailchimp_check_woocommerce_is_installed functions.
Description:
This is a follow-up to Issue #1170, where the Plugin Dependencies feature was introduced (thanks @ryanhungate for adding this! 🙏 ), but the existing WooCommerce plugin check was not removed.
Since WordPress now handles plugin dependencies natively, ideally, we don't need to check the plugin now.
Problem:
RUNNING_CUSTOM_WOOCOMMERCE
constant, but it's not a good user experience.Suggested Changes:
mailchimp_check_woocommerce_plugin_status
andmailchimp_check_woocommerce_is_installed
functions.References:
The text was updated successfully, but these errors were encountered: