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
In my investigation of #82 and submission of #83 I realized that woocommerce_email hook is loaded on every page, frontend (guest and user) and backend. For sites that have "Fix for WooCommerce emails" enabled (after #83 is merged), that the setting will be applied to all emails.
I'm working on identifying a better hook right now, but this is a problem that should hold #83 until it's resolved.
It is preferable that the action in use:
is only called when a WooCommerce email is about to be sent
is an actual action, and not a filter
is guaranteed to run regardless of customization or source
The text was updated successfully, but these errors were encountered:
From the research I've done so far, there's not really a great action to work with: most of the actions are used to customize the template, and are not guaranteed to be on all emails.
@MillerMedia Instead of attempting to identify emails from WooCommerce, is it acceptable to adjust the setting to be more generic to HTML emails, and functionally look for Content-Type: text/html in the email headers?
In my investigation of #82 and submission of #83 I realized that
woocommerce_email
hook is loaded on every page, frontend (guest and user) and backend. For sites that have "Fix for WooCommerce emails" enabled (after #83 is merged), that the setting will be applied to all emails.I'm working on identifying a better hook right now, but this is a problem that should hold #83 until it's resolved.
It is preferable that the action in use:
The text was updated successfully, but these errors were encountered: