Fernando a11n

Hi @sanchitgoyal – thanks for sharing those additional details.

Most issues we see with the AddToCart event are related to theme conflicts. A theme that utilizes custom actions or custom AJAX calls for the cart functionality can often result in this type of conflict.

I’d recommend checking for conflicts by temporarily switching the theme of your site to the free Storefront theme. You can enable this theme directly from your site’s Dashboard at Appearance > Themes > Add new.

Let us know if switching to the Storefront theme enables the AddToCart event to work more reliably.

Hi @judyangel! This is one I haven’t seen before.

I’ve tried to replicate this on a site of my own but I have been unable to do so. I don’t see this error when processing an order.

The message would indicate that there’s something on the site that is allowing the checkout form to communicate with WooCommerce Payments without passing on the phone field. To start troubleshooting this, I’d recommend a conflict test. That will allow you to confirm whether a plugin or theme installed on the site might be the one creating that block.

Here’s what I’d suggest:

1. Switch the theme of your website to the free Storefront theme.

2. Deactivate all the plugins except for WooCommerce and WooCommerce Payments. Then, check if the issue persists. If the problem is resolved then please move on to the next step.

3. Activate features one by one while testing for the issue, until you find the one that is causing this behavior.

We recommend that these steps are taken on a staging site, which is a clone of your live site that you can modify without risking making any permanent damage to your live site. You can create it using a plugin like WP-Staging. This plugin lets you copy and redeploy a WordPress site with minimal work.

Hopefully that helps you narrow down the source. Let us know what you find out!

Thanks for clarifying here – I’m glad that as resolved.

Remember you can find documentation for the PayPal Checkout plugin at the following link:

https://docs.woocommerce.com/document/paypal-express-checkout/

Hi @mjmontero, I’d like to see a few more details about the way your prices and taxes are configured. It’s definitely strange that the Facebook catalog is picking up a completely different price for both the regular AND sale price.

Can you share a screenshot of both prices (regular and sale) as configured in the Edit Product page?

Additionally, can you also share details about your tax setup? You can share a screenshot of the settings at WooCommerce > Settings > Tax > Tax options, as well as talk us through what rates are you currently using there.

You can use a service like https://snipboard.io/ to take and upload a screenshot. Once you upload it there, please copy the image’s URL and paste it on this thread.

Hi @z8eldred! If you are having issues with the PayPal Checkout plugin itself, we encourage to open up a thread in the Forum here.

To clarify, we do not provide any development services. PayPal Checkout is a free plugin that can be downloaded, installed, and used with all its default features without needing additional development.

@neal86 I recommend following the instructions outlined above, in step 2. Let us know what you find out!

Hi @neal86, I’d recommend two things to start:

1. Can you check the browser console on that blank page? When you go to the Analytics Settings and receive an empty page, as shown in your screenshot, please open the console in your browser. Does it show any errors?

2. Regardless of the above, a great first step for troubleshooting is running a conflict test. You’ll want to temporarily switch your theme to Storefront. Then, disable all plugins on the site except for WooCommerce, and test for the issue.

If the issue is gone, you’ll then have to re-enable features one by one, while testing for the issue; until you find out which one is causing this behavior.

We recommend that these steps are taken on a staging site, which is a clone of your live site that you can modify without risking making any permanent damage to your live site. You can create it using a plugin like WP-Staging: https://www.ads-software.com/plugins/wp-staging/

Hi @epicmat, I agree with your assessment that this is most likely a styling issue. That’s usually caused by a theme that is not compatible with that particular functionality.

To verify this, I suggest temporarily switching to the default “Storefront” theme. If the buttons display correctly under Storefront, then you know that the issue is coming from the theme you are using.

We recommend that these steps are taken on a staging site, which is a clone of your live site that you can modify without risking making any permanent damage to your live site. You can create it using a plugin like WP-Staging: https://www.ads-software.com/plugins/wp-staging/

@mbdireccion I’m not fully understanding what you are trying to achieve. Can you clarify what do you mean by the following sentence?

“avoid define Facebook cookie _fbp before consent”

The more details you can share, the better!

@davidino77 Were there any particular steps that you completed before it was fixed? It might help other users in the future who face similar issues.

Hi @mpagery. This forum is intended for questions about the core WooCommerce plugin.

If you have an active license for the AutomateWoo extension, please head to the following page to contact the support team of the WooCommerce.com marketplace:

https://woocommerce.com/my-account/create-a-ticket/

Once there, select “Help with my purchased products”, and under the “I need help with:” menu, make sure that you select AutomateWoo. Please note that the option will only appear when logged in to the account that owns the active license for the extension.

I hope that helps.

• This reply was modified 3 years, 9 months ago by Fernando a11n.

Hi @natebc1, this forum is intended for questions about the core WooCommerce plugin. Since this is an enquiry about a third-party plugin that I’m not familiar with, I can’t provide much advice.

If the developer of that plugin isn’t being very responsive, you may consider switching to a different plugin that better fits your needs. If you’d like to reach out to other people in the community who might be able to give advice, there is also the [Advanced WooCommerce](https://www.facebook.com/groups/advanced.woocommerce/) Facebook Group. Maybe someone there who uses the same plugin might be able to assist.

it seems some how the Customer Invoice/Order is set up for manually sent.

@anharvey, based on the above it sounds like you are concerned about this email being set up for manual submission only:

I can confirm that this is ok an expected. That template is the one used when you manually select to resubmit order details to the customer. That can be triggered from the order page, in the “Order actions” menu.

However, this is only meant to be used on special occasions where you need to re-submit those details. By default, customers will receive their order details as part of the confirmation they get after purchasing. The exact email they receive will depend on the status of the order, but it’s normally the “Processing order” or “Completed order” email that you can see in that same section.

I hope this helps clarify things.

@hipoglucido I haven’t seen this sort of behavior before. Could you provide a screenshot of what this looks like on your site?

Make sure to block any sensitive information that might be included in the order page.

@eskruolis I know you were looking for some coding advice to fix the above snippets. However, in case you’d like to explore a plugin option, I thought you might be able to give Checkout Field Editor a shot.

It would likely not help for longer text elements, but if this would be more of a heading, the extension does include the option to add extra headings on the checkout form. See an example here:

Hope that helps.