deeveedee
Forum Replies Created
-
This issue (described in detail below) is now fixed by WooCommerce 3.0.6. Thank you @mikejolley!
Details about this error and the fix:
When using Postman SMTP (PS) plugin version 1.7.2 with e-mail validation enabled, WooCommerce (WC) 3.0.0-3.0.5 would not send new order notifications if the customer name and e-mail billing fields were empty (which would happen if the name and billing fields are “unset” via thewoocommerce_checkout_fieldsfilter). PS would throw an ‘invalid Reply-to’ error. This happened, because WC would insert the text ‘Reply-to’ in the e-mail header without a Reply-to address. The work-around when using PS and WC was to disable PS e-mail validation.WooCommerce 3.0.6 added a check, so that the Reply-to field is only added to the e-mail header if the customer name and e-mail billing fields are populated. As a result of this WC 3.0.6 fix, Postman SMTP 1.7.2 will nolonger throw an ‘invalid Reply-to’ error if the customer billing fields are not populated.
@cryogene – I had started posting some suggestions but just re-read your posts and see you’ve been very thorough with your testing methodology. Sorry you’re still having issues and wish I had a good suggestion for you.
@mikejolley – I looked throught the WooCommerce changelog and see that “Reply-to” was added to admin e-mails in WC 3.0.0, so this explains why everything worked for me in 2.6.14 when the customer’s name and e-mail were not present in my WooCommerce billing fields.
If I understand the change that you added after 3.0.5 (to ensure that “the data is there”), I believe that should fix the problem I’m observing. WooCommerce should only add Reply-to to the admin e-mail header if the billing name and billing e-mail address are populated (leaving Reply-to completely out of the e-mail header if the billing fields are not set).
Thank you.
@mikejolley – thank you very much. I will retest with the next version of WooCommerce. I don’t require the customer’s name/e-mail for PayPal orders but do require the customer’s name/e-mail when paid by check. I unset the name and e-mail order fields for PayPal orders and leave them set for orders paid by check. Since you’re generating the Reply-To from the order fields, I understand why the behavior I’m seeing is different for the PayPal and Check payment gateways.
What I still don’t understand is why this wasn’t a problem with WC 2.6.14 and is now a problem with WC 3.0.5.
Thanks again for your help and great support.
I’d be leading you down the wrong path if I guessed, but if sending works fined with WooCommerce 2.6.14 and does not work with WooCommerce 3.0.5, then that should be a clue about the source of the problem: WooCommerce.
If you haven’t done so already, confirm that you can revert to a previous version of WooCommerce to restore proper functionality. Then post your issue in the WooCommerce support forum, along with the following info:
- Specify that you are using Postman SMTP (along with the plugin version)
- List the specific SMTP e-mail service that you are using with Postman SMTP
- Specify the last WooCommerce version that worked properly for you (and the WooCommerce version where you first observed the problem)
- Indicate that you can revert to the working WooCommerce version (and name the version) to restore proper functionality to show that your problem is repeatable and duplicable
- Explain that the Postman SMTP e-mail log reports the notification e-mail as “Sent” without any errors
- Indicate that you can “force” the e-mail to send by manually resending (via the WooCommerce order view)
Good luck. Mike Jolley was quick to respond to my issue reported as part of another WooCommerce thread here: https://github.com/woocommerce/woocommerce/issues/14151
Sorry my “fix” didn’t work for you. I’m not a Postman SMTP expert, but am open to trying things if you are. Do you have a Postman SMTP log that reports the status of the sent (or not-sent) e-mails? You’ll find the Postman SMTP log in your WordPress Dashboard under Tools->Email Log. It was this log that pointed me toward the work-around I reported.
I noticed what might be the same problem and posted the results of my investigation and a temporary work-around here: https://wordpress.org/support/topic/new-order-notifications-not-sent-after-upgrade-from-2-6-14-to-3-0-5/
If you try my suggested temporary work-around (Postman SMTP Settings -> All Settings -> Message Tab -> Disable e-mail validation), please post the results of your testing. Thank you.
Forum: Plugins
In reply to: [WooCommerce] Woocommerce not sending emails after 3.0 updateI published my own post before seeing this one. The results of my investigation and my temporary work-around are posted here: https://wordpress.org/support/topic/new-order-notifications-not-sent-after-upgrade-from-2-6-14-to-3-0-5/
Forum: Plugins
In reply to: [WooCommerce Autocomplete Orders] Deprecated CallsI was able to get WC 3.0.5 working with Postman SMTP plugin (version 1.7.2). It appears that WC 3.0.5 is sending a blank “Reply-To” e-mail field to the Postman SMTP Plugin (which Postman SMTP flags as an e-mail validation error). The Reply-To e-mail field was not sent by WC 2.6.14 (the Reply-To e-mail field is not present in the Postman SMTP log entries for e-mails sent by WC 2.6.14, but the Reply-To e-mail field is present in Postman SMTP log entries for e-mails sent by WC 3.0.5). By checking the “Disable email validation” checkbox in Postman SMTP settings (Postman SMTP Settings -> All Settings -> Message Tab -> Disable e-mail validation), I was able to restore e-mail notification functionality for WooCommerce 3.0.5. The Reply-To e-amail is still blank, but Postman SMTP now ignores this error.
I’m not sure if this is related to your first post, but there is a difference between the information that WooCommerce 2.6.14 provides to the Postman SMTP Plugin and the information that WooCommerce 3.0.5 provides to the Postman SMTP plugin.
Forum: Plugins
In reply to: [Postman SMTP Mailer/Email Log] Invalid "From" e-mail address ""Thanks for the tip! When I upgraded from WooCommerce 2.6.14 to WooCommerce 3.0.5, WooCommerce stopped sending new order notifications. I haven’t completely figured out what’s going on, but the Postman SMTP log shows that e-mails sent by WooCommerce 3.0.5 have a blank Reply-To e-mail address (which fails Postman SMTP E-mail validation). Postman SMTP log entries for e-mail sent by WooCommerce 2.6.14 do not have a Reply-To e-mail address. While I don’t know why WooCommerce 3.0.5 is adding a blank Reply-To e-mail address (could possibly be a WooCommerce 3.0.5 bug), disabling e-mail validation in Postman SMTP allowed new order notifications to be sent from WooCommerce 3.0.5.
Note that in Postman SMTP 1.7.2, the “disable e-mail validation” option is visible under the Settings->Show All Settings->Message Tab.
Forum: Plugins
In reply to: [WooCommerce Autocomplete Orders] Deprecated CallsI have just started trying to figure out why my order notification e-mails aren’t working after I upgraded from WC 2.6.14 to WC 3.0.5. Like you, all works great for me with 2.6.14. Despite the error messages that you’re seeing, are your orders completing and are notification e-mails being sent?
Thanks
Forum: Themes and Templates
In reply to: [Fruitful] Compatibility with Woocommerce 3.0.0We looked at the product-image.php file at the link you provided above (https://github.com/Fruitfulcode/Fruitful). This file is version 2.6.3 which is older than the 2.6.4 version that we already have installed and that, according to WooCommerce 3.0.x, is outdated.
We continue to enjoy the use of your Fruitful theme and thank you for your great support and development efforts.
Thank you.
Forum: Themes and Templates
In reply to: [Fruitful] Compatibility with Woocommerce 3.0.0We can certainly get the latest version from github (as we have done before with a previous template version) but would prefer to retrieve all WordPress content via formal WordPress channels. Is there a reason that you are no longer checking in Fruitful Theme for standard WordPress notification/download?
Thank you.
Forum: Plugins
In reply to: [Download Manager] Toolbar style changed after upgrading to 2.9.42@w3eden – Thanks for the update.
Forum: Themes and Templates
In reply to: [Fruitful] Compatibility with Woocommerce 3.0.0@fruitfulcode – we’re still running Fruitful Theme 3.3.1 and suspect that this isn’t the latest version (but we’re not seeing a theme update notification in our WordPress 4.7.3 dashboard). WooCommerce 3.0.1 indicates that
fruitful/woocommerce/single-product/product-image.php version 2.6.4 is out of dateIs there a newer version of Fruitful Theme (newer than 3.3.1) that fixes this WooCommerce template?
Thank you very much for your support and your great theme!