wbrubaker.a11n

Currently, if you go through the Shop setup as covered in the documentation at this link it is supposed to set up the Checkout portion. What is going on is Facebook is auto checking/auto activating the Shopify gateway instead of the option to Checkout on another site which is what is needed for WooCommerce, as seen in this screenshot: https://d.pr/i/qNX7Rh

If that option for Instagram/Facebook is left selected with the Turn on Shopify payment method left checked, then that is the type of payment gateway which is set up – which seems to be what happened here.

To remedy this and have WooCommerce work to take payments from Facebook, the option for setting up the Shop needs to be re-done, and the choice to Check on another website needs to be selected:

https://d.pr/i/6wIfiN

Once this is done, we would expect that any order after that will process through WooCommerce normally, and show up under WooCommerce > Orders. Prior orders however will not.

Hi there,

Storefront doesn’t provide any settings that can be used to conditionally prevent widgets from being output. You might want to have a look at something like the Conditional Widgets plugin for this purpose: https://www.ads-software.com/plugins/conditional-widgets/

It’s not hard-coded. I’m not clear what language your site uses, but you can see it in the EN_GB file here: https://translate.www.ads-software.com/projects/wp-themes/storefront/en-gb/default/?filters%5Bterm%5D=Cart&filters%5Bterm_scope%5D=scope_any&filters%5Bstatus%5D=current_or_waiting_or_fuzzy_or_untranslated&filters%5Bcase_sensitive%5D=yes&filters%5Buser_login%5D=&filter=Apply+Filters&sort%5Bby%5D=priority&sort%5Bhow%5D=desc and here in the source code: https://github.com/woocommerce/storefront/blob/trunk/languages/storefront.pot#L844

The two Warnings and Fatals specific to WooCommerce I suspect would be solved by re-installing WooCommerce

That will depend on the shortcode that you are using. Here is some documentation for theShortcodes included with WooCommerce. Specific to attributes see: Scenario 6 – Attribute Display

I suggest you seek out the documentation for whichever shortcode you are using to learn how to use that shortcode.

The Facebook for WooCommerce plugin does not provide any hook that can be used to to scheduled a daily sync.

To avoid needing to manually sync via the product sync button, rather than running an SQL query to update products on the sites, I suggest making WooCommerce REST API calls to update those products which would, in turn, use WooCommerce methods and my expectation is that when doing so, that would trigger a sync for that product so that it would be updated on Facebook as well.

https://woocommerce.github.io/woocommerce-rest-api-docs/

Thanks for that. Do you see any fatal errors in your fatal error logs that match up to this issue date-wise? To check, go to WooCommerce > Status > Logs in your dashboard, open the dropdown by the “View” button, and look for any logs with “fatal-errors” in the name and an appropriate date.

If you see one, please view it by clicking on it and then clicking the “View” button, as shown here: https://d.pr/i/zYVxgL

Could you then copy the contents of the log into pastebin.com, click “Create new paste,” and then share the link so that we could take a look?

Thanks!

It sounds like you’re getting a “Oops, something went wrong.” error during setup of the plugin. There’s some documentation on this here: https://docs.woocommerce.com/document/facebook-for-woocommerce/#i-am-getting-an-oops-something-went-wrong-error-how-can-i-connect-to-my-facebook-account

Looking at the logs:

The logged response doesn’t tell us much we don’t already know, i.e. that the address is invalid. What is the logged request that received that response?

It’s going to depend on what OS you use. On Windows type machines I believe it is ctrl+f to bring up the text search box in your browser. For OSX, it would be ?+f

I’ve just done some testing of this on my own test site here: https://wctesting.tk/product/beanie-with-logo/. I used this plugin: https://github.com/WillBrubaker/maybe-route-request-through-moesif to capture the request that was sent to the FaceBook conversions API and I used the Facebook Pixel Helper Chrome browser extension to view the data that is sent using the FaceBook Pixel. With all of that in place, I added an item to my cart. The pixel event shows that the event_id parameter is populated:

https://d.pr/i/6VmwaF
Likewise, the request that was sent to the API also contains a value in the event_id parameter:

https://d.pr/i/PuImih
I also had a look at the issue tracker here: https://github.com/facebookincubator/facebook-for-woocommerce/issues for any reports of this type of behavior caused by the Facebook for WooCommerce but I was unable to find any. This leads me to believe that this is caused by something external to WooCommerce or Facebook for WooCommerce. If you are able to provide the exact steps that can be taken to reproduce this behavior under the following conditions:

1. An unmodified, default WordPress theme such as Twenty Twenty or Storefront active.
2. No other plugins except for WooCommerce and Facebook for WooCommerce active.

Please do provide those steps and we can take a closer look.
We do understand that placing a site under those conditions may be disruptive. Many people maintain a staging copy of their site for exactly this purpose. That way, testing and troubleshooting can be done on the staging copy without disrupting the operation of the live site. If your host does not provide an easy way to set up a staging site, you might want to use something like the WP Staging plugin for this purpose.

Can you try to deactivate and then reactivate the WooCommerce PayPal Express checkout plugin to see if that helps?

If that doesn’t help, the next step I can suggest would be to remove the option named woocommerce_ppec_paypal_settings from the database and then go through setup again.

I’m guessing that Facebook is showing you a message that indicates that event_id parameter is missing from the tracking data similar to:
https://d.pr/i/OaMkyw
If I’m understanding correctly, I’ve just done some testing of this on my own test site here: https://wctesting.tk/product/beanie-with-logo/. I used this plugin: https://github.com/WillBrubaker/maybe-route-request-through-moesif to capture the request that was sent to the FaceBook conversions API and I used the Facebook Pixel Helper Chrome browser extension to view the data that is sent using the FaceBook Pixel. With all of that in place, I added an item to my cart. The pixel event shows that the event_id parameter is populated:

https://d.pr/i/6VmwaF
Likewise, the request that was sent to the API also contains a value in the event_id parameter:

https://d.pr/i/PuImih
I also had a look at the issue tracker here: https://github.com/facebookincubator/facebook-for-woocommerce/issues for any reports of this type of behavior caused by the Facebook for WooCommerce but I was unable to find any. This leads me to believe that this is caused by something external to WooCommerce or Facebook for WooCommerce. If you are able to provide the exact steps that can be taken to reproduce this behavior under the following conditions:

1. An unmodified, default WordPress theme such as Twenty Twenty or Storefront active.
2. No other plugins except for WooCommerce and Facebook for WooCommerce active.

Please do provide those steps and we can take a closer look.
We do understand that placing a site under those conditions may be disruptive. Many people maintain a staging copy of their site for exactly this purpose. That way, testing and troubleshooting can be done on the staging copy without disrupting the operation of the live site. If your host does not provide an easy way to set up a staging site, you might want to use something like the WP Staging plugin for this purpose.

• This reply was modified 3 years, 8 months ago by wbrubaker.a11n.
• This reply was modified 3 years, 8 months ago by wbrubaker.a11n.

There are a lot of plugins on your site that are outdated. Specifically both WooCommerce and Facebook for WooCommerce. The problems that you are experiencing have potentially been fixed in newer versions. Please do update at your earliest convenience.

If you see data on the Square website that is not as you expect it, but the data does appear to be correct on your WooCommerce site, that is an indication to me that you should contact the support team at Square for an explanation.

I imagine it will be closely related to:

I’ve made orders using the same card with various different names and email addresses.

I imagine that card token gets assigned with the same name and email address that it is first generated for.