wbrubaker.a11n

A lot of times, this will happen because of a missing permission – here’s a link to a screenshot: https://imgur.com/E6HtubA so you might want to check that.

If that doesn’t help, it could be the currency. There’s some more on that 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

The first thing I’d suggest would be to update Square to the most recent version. WooCommerce also.

If the problem persists after updating, the only other reason I can think of that would cause the access token to expire is if scheduled actions on your site are not working as expected. This may be the result of WP_CRON not working properly. The site health tool would alert you to any of those kinds of problems. Tools > Site Health

Hi there.

The CSS as currently written will only apply to an element that would match this CSS rule: .wc-block-checkout__payment-method div#square-credit-card and its child elements.

If there are none of those elements present on any pages on your site then I can’t see any problem with de-queueing the CSS.

When nothing appears in the notes and there is no transaction id and the order does not transition to a paid status, we assume that is caused by a fatal error. Please do see your fatal error logs for the same date that this order happened on for clues as to what caused it.

That’s correct.

No.

Hi there.

So, there is a very specific set of circumstances that this filter is intended to work under, however, I’m not sure that any of those circumstances actually would show any address fields anyhow. The filter is not intended to be a workaround for addresses that won’t validate. What troubleshooting steps have you taken to determine the actual cause of the validation failures?

Neither WooCommerce nor Facebook for WooCommerce would add those query parameters to any GET requests. It seems Facebook resolves it themselves by blocking the information and not allowing you to use it or view it. Getting those errors to stop would involve isolating what is adding those query parameters to your page view events, which, again, is not WooCommerce or Facebook for WooCommerce.

It’s not possible via configuration. It may be possible via custom code.

Do you have Stripe logging enabled? What do the logs tell you?

Can you provide a copy of your system status report please?

We do not want to enable “Save for future use”.

That seems directly at odds with your goal. There is no way to save the card details for future use without enabling the feature to save the card for future use.

The first thing I would suggest is to verify that the city name in the shipping address is valid and if not, correct that. If you have verified that the city name is correct, then please do contact PayPal. The error is returned from PayPal and so they would need to provide an explanation for it if the city is, indeed, correct.

It’s stored in an option with the key wc_facebook_feed_url_secret so I expect you could find it there, e.g. wp-admin/options.php

That feed url that the plugin generates is going to be different based on your own site than it would on someone else’s. The static part is ?wc-api=wc_facebook_get_feed_data&secret= – the secret is generated by the plugin.