abwaita a11n

Hi @ttoaster,

I totally get that the error hasn’t been an ideal experience for you, and we’ve been working with our developers on resolving it.

We shared all the relevant details about this error when you first reported it here to our developers and a high-priority bug has been in the fix for this.

You’d mentioned something that I’d like to clarify:

this thread has all the data you need to identify the exact line and file in your plugin that is causing the error.
+
Looking at the error, I would say that the latest update is missing a file from the package

It may seem that it’s simply a missing file, but that’s not the case. The error message implies that the CoreInterfaces\Http\HttpConfigurations class can’t be found. We’ve verified that the file that contains this class does exist in the plugin, so that’s not the reason.

That out of the way, our developers have explored 4 other potential causes that could lead to this issue. At the moment, they’re in the process of working on creating a fix, and we anticipate that it will be in a future Square release version 3.7.

For now, if possible you can reach us via a ticket so that we can get in touch with you when the fix is ready.

Hi @wpdev1888!

Glad to hear that you were able to reconnect, and hopefully that sorted out everything.

We just want to check the cause of the disconnection so that we can prevent it.

If a Square API request returns ACCESS_TOKEN_EXPIRED, a connection refresh is attempted to generate a new token. Normally, this happens without requiring any action/input from your side.

However, in this case, it looks like the token couldn’t be refreshed, so a manual reconnection was required, which you’ve now done.

For now, we could advise that you keep an eye on this and incase it happens repeatedly, please let us know.
Thanks!

Hi @jlqz27,

Thanks for getting back.

We understand that you’re unable to see/enable PayNow under our Stripe’s additional payment method.

The reason is that we’ve not yet added it to our extension. Here’s a list of the additional payment methods that our Stripe extension currently offers – https://woocommerce.com/document/stripe/#additional-payment-methods.

You will note that there are a few additional payment methods from Stripe that have not yet been built into our Stripe extension, PayNow being one of them.

We would like to recommend adding this as a feature request for our developers to consider adding PayNow to our Stripe plugin – https://woocommerce.com/feature-requests/stripe/.

Thanks.

Hi @rhaenys!

As you’ve created a ticket with us, from here, we’re going to assist you directly through that ticket.

Just a heads up, we’re also going to set this thread as resolved to prevent duplicate efforts.

Thanks!

Hi @gohandgeo,

I’ve tested without the mentioned plug-ins and still the same warning pops up.

Thanks for mentioning that.

As it seems that the two (Code Snippets and Header Footer Code Manager) might not be the culprits, we’d like you to check through the whole list of plugins as well as the theme you’re using to see what could be causing the conflict.

Therefore, could you kindly perform a full conflict test and let us know if you’re able to find the tool that’s causing the issue?

Thanks.

Hi @lomiglobalfoods,

I understand that you’re seeing this error when completing your WooCommerce Payments setup:

There was a problem redirecting you to the account connection page. Please try again.

In most cases, this happens when there’s an issue with your site’s Jetpack connection.

I would recommend resetting the Jetpack connection to resolve any issues there. While the Jetpack plugin is not required in order to use WooCommerce Payments, it is needed to reset the connection.

You will want to follow these steps:

• Ensure you’ve installed and activated Jetpack
• Go to Jetpack > Dashboard
• Scroll down to the Connections section
• Click Manage site connection
• Click Disconnect
• Wait for disconnection to complete.
• Go to WP-Admin → Payments
• Click Set up to re-establish the connection.

You can read more about the steps required in our documentation: Error determining the connection status.

Let us know how it goes.
Thanks.

Hi @hypernurb,

Thanks for testing that. I take it that the widget didn’t show even when running WooCommerce and a default theme.

You’d mentioned earlier:

I have created a widget for these attributes and loaded it onto the page but it doesn’t show.

Could you share with us a screenshot of how you’ve set this up from your admin side?

What I do notice in the Widget section, underneath the attribute filter I have added to the sidebar, a white box with black outline is visible with the text: Filter products by attribute – No example available.

While checking your site, I wasn’t able to see this. If possible, please also share with us a screenshot of this.

—

I recommend https://snipboard.io for sharing screenshots – please follow the instructions on the page, then paste the URL in your reply. It works with Chrome, Firefox, Safari, and Edge.

Thanks.