multiple WooCommerce issues

Hi @ssstil,

I’m sorry to hear about the experience you’ve had so far. I can understand how frustrating it must be to run into several issues at once, especially after spending hours troubleshooting on your own. Let’s work through these step-by-step so we can get things running smoothly.

1. “On behalf of” showing in emails
   This typically happens when the domain your email is being sent from doesn’t match the server sending it. Since you’re using Post SMTP, it’s usually a matter of updating your SMTP settings to match the “From” email domain or setting up an SPF/DKIM record with your hosting provider to allow your store’s email to send directly without the “on behalf of” notice.
   
   Could you confirm if your “From” email address matches the domain authenticated in your Post SMTP settings?
   
2. Plugin conflict with WP Activity Log
   Conflicts like this often happen when both WooCommerce and the logging plugin are hooking into the same product-save process. If you can share your System Status Report, we can check for any known compatibility notes.
   
   You can get a System Status Report by going to WooCommerce > Status > Get system report, then paste it into https://pastebin.com or https://gist.github.com
   
   You could also share any fatal error log entries from WooCommerce → Status → Logs for the date the error occurred.
   
3. Editing WooCommerce email templates and button text
   You can still customize email templates by copying them from:
   /wp-content/plugins/woocommerce/templates/emails/ into /wp-content/themes/yourtheme/woocommerce/emails/ and then editing them.
   
   For buttons and other strings like “Checkout” or “Cart”, you can use the Loco Translate plugin to change the wording without touching code. If you’d like, I can walk you through both methods in detail.
   
4. Adding Mr/Mrs/Ms dropdown
   This would need a checkout field customization. You can do it with a small code snippet added to your theme’s functions.php or with a plugin like Checkout Field Editor. Do you want me to provide a ready-to-use snippet for this?
   
5. 404 error on order-received page and redirecting customers
   A 404 after payment often means the “Checkout → Order received” page is missing or not correctly linked in WooCommerce → Settings → Advanced. Please check that the “Order received” endpoint exists and that your permalinks are refreshed under Settings → Permalinks → Save.
   
   For redirecting customers after payment, WooCommerce doesn’t have a built-in setting, but it can be done with a small snippet or a lightweight plugin. Once we fix the 404 issue, I can share options for adding the redirect.

If you can share your System Status Report and any relevant error logs privately via Pastebin, we’ll be able to see the full setup and suggest the safest fixes.

We’ll take this one step at a time. I’m confident we can get you from “frustrating” to “working smoothly.”

Hi @ssstil,

Thank you for getting back and for the clarification. I’ll go over your responses one after the other.

1. You may need to reach out to your SMTP plugin author or support team, as they are best suited to help with this issue.
2. This error can happen if someone is editing a product or order while the log monitor plugin is attempting to fetch data, or it may be caused by an internal conflict within the plugin. In either case, it’s best to contact the plugin author or create a support topic in their forum for assistance.
3. If you prefer not to edit the email manually, you can use a WooCommerce email customizer to modify your emails. Some examples of plugins you can use are:
   — Email Customizer for WooCommerc
   — Email Template Customizer for Woo
   — Email Customizer for WooCommerce
4. Because this involves a third-party plugin, please open a support topic with the Checkout Field Editor plugin you’re using to get assistance from the appropriate support channel.

yes, the order received field looks exactly like this: “order-received”. Still, I get a 404 error page not found, after the test transaction was completed.

Could you please share your system status report so we can get a clearer picture of what’s happening behind the scenes? You can get your report from woocommerce > status > get report > copy for support and share it using pastebin.

Hi @ssstil,

Thank you for the clarification and for getting back. I completely understand your perspective, but that’s not exactly how things work.

To clarify, WooCommerce and WordPress are the core/base products. Plugins like WP Activity Log are third-party add-ons, and it’s the responsibility of those plugin developers to ensure compatibility with WooCommerce and WordPress—not the other way around—since these plugins hook into WooCommerce’s features and functions.

When a conflict arises between WooCommerce and another plugin, we typically advise merchants to contact the plugin’s developer or support team. They are in the best position to review their own code to identify the cause of the conflict. If, after reviewing, they determine the issue is due to a WooCommerce bug, they can open an issue on GitHub to work with the WooCommerce development team. Alternatively, if they find the problem lies in their own code, they can update it to meet WooCommerce requirements and release a fix.

4) Your colleague was at least kind enough to offer me a “ready-to-use” snippet for the checkout field editor, therefor I am kindly asking again to be provided with the snippet/code in question.

I understand that my colleague offered to provide a ready-to-use snippet, but after checking with him, it seems he may have misunderstood your request. Apologies for the confusion. Custom code like this generally falls outside our support scope. If it were a simple snippet we already had available or could easily create, we would have shared it. However, since this involves customizing the email template, I recommended using a plugin instead, as it’s a safer and more reliable approach.

Regarding the checkout field, it’s best to use a checkout field editor plugin, such as this one: https://wordpress.org/plugins/woo-checkout-field-editor-pro/, which allows you to easily add custom fields to your checkout.

There is no error recorded. I have just made a new attempt as a test, the order went through, I receive the confirmation email, but I still get a 404 page not found error.

Thank you for the clarification and for getting back. To better understand the behavior you’re experiencing and your current setup, could you please share your system status report, as my colleague previously requested? This will help us review your setup before proceeding to test the behavior on a staging environment.

Hi @ssstil,

Thanks for getting back to me and for sharing the report. I’ve reviewed your plugin list and noticed a few that might be interfering with WooCommerce’s link structure.

You’re correct that others have also reported the thank you page showing a 404 error. However, the causes tend to differ—most often plugin conflicts or permalink changes by merchants.

To troubleshoot further, please set up a copy of your live site in a staging environment (for example, on a subdomain, directory, or using your host’s staging feature). On the staging site, disable all plugins except WooCommerce and WooPayments, then switch WooPayments to test mode and change the theme to Storefront.

Once that’s done, please share the staging site’s system status report with us so we can run tests on our side. You’ll need to include the site link in the report, and you can remove the pastebin once we’re finished.

Hi @ssstil,

Thank you for getting back to me with the update. I’m glad you were able to connect the test payment and do some troubleshooting.

To help narrow this down further, have you tried switching to the Vibra theme on your staging site (with all plugins disabled) to see if the issue still occurs? If not, please give this a try—it will help confirm whether the theme is the cause or not.

• If the issue does occur, then the theme is likely responsible. Since it’s a ThemeForest purchase, you can reach out to the theme developer through their platform for dedicated support.
• If the issue doesn’t occur, the next step would be to enable your plugins one by one, checking after each activation to see which one reintroduces the problem.

I’ll be here waiting for your observations and feedback.