radstu

Any luck on this? I’ve encountered this same error (Error Processing Checkout. Please try again) with a different platform, also WooCommerce. It also has a 500 error on ?wc-ajax=checkout

We ran into the same issue here. The payment gateways couldn’t invoke and customers were stuck on the /checkout/ page … largely it seemed because the data being sent to Vend was malformed (missing SKU / Product ID’s and non-standard pricing like 9.949999 for the amount instead of 9.95) and the error responses by the plugin were not strict JSON, causing WooCommerce to fail on checkout (since Woo 2.4+)

Ultimately disabling this plugin and relying only on the direct API integration from Vend solved this issue for us.

Oops! Roger

When I navigate to the file via FTP, it is 26 KB, but when I attempt to view it directly via https://www.bsa-dev.com.php7-34.lan3-1.websitetestlink.com/wp-content/uploads/2017/09/broadway-station-logo-1.svg it shows an error message:

This page contains the following errors:

error on line 1 at column 1: Document is empty
Below is a rendering of the page up to the first error.

Here it is inserted in the logo slot, but not displaying as an SVG:

And here is a larger version, showing it display correctly as raw HTML:

Thank you.

I thought that I had enabled the Web Fonts Developer API, but when I logged in, I observed it was off.

I also noticed: https://screencast.com/t/TFRSalRch36R … it seems like my connection requests are reaching google, although I can’t yet locate where to find out details about the errors specifically.

I’ve double checked the rest of those settings relating to the credentials, and those are still all working as noted in my earlier post: https://screencast.com/t/cdmFZJcCAmF0

This morning as I tested, things were not working. However, now that I’ve gone through and re-saved everything at google and also over on WordPress, I’m now seeing the following message on worpdress that was missing before:

Your Google API Key is valid and automatic font updates are enabled.

Further tests show it’s working now as expected, so everything is resolved. Thank you for your help!

It seems like I’m experiencing the same issue as Saratorge.

I’ve installed the plugin, gone through the video, and in my drop down, all I am able to see are the standard web fonts, not the google fonts.

I walked myself through the options to issue credentials for the web fonts api here:

https://screencast.com/t/cdmFZJcCAmF0 and that seems to be working fine.

For kicks I also regenerated my key in case the first one was borked in some fashion.

The plugin works great on the standard web fonts, but I can’t get it to load googles web fonts at all.

Thank you Shellbot, both for the very speedy reply as well as for the good suggestion on how to resolve the problem.