madeincosmos

@tatifox is right ?? These default styles can be also overridden using the following filters:

– wc_braintree_paypal_cart_button_styles for the cart page,
– wc_braintree_paypal_button_styles for the checkout page.

Cheers!

Hi everyone,

I’ve seen this error after the last update, and so far it was due to a caching plugin (like Autooptimize, W3 Total Cache, etc) delaying the loading of Braintree payment code, which resulted in an error. If you are using one of such plugins, its authors can help you exclude Braintree scripts from cache / minify. The file name to exclude is:

wp-content/plugins/woocommerce-gateway-paypal-powered-by-braintree/assets/js/frontend/wc-braintree.min.js

If you’re not using any cache / minify plugins, can you please share a link to your site? We’d like to take a look at the checkout page and see where these errors could originate from.

Thanks!

• This reply was modified 6 years, 9 months ago by madeincosmos.

Hi there,

Thanks for letting us know about this problem! I just checked the checkout page and I’m able to insert the credit card details there without any problems:

https://cld.wthms.co/PPLPL8

Have you solved the problem already, or does it happen for certain browsers only?

By the way, I noticed some strange checkbox icons showing next to each credit card form row. These seem to be added in the Suprema theme code (see the screenshot above), so if you’d like to get rid of them you can check this with the theme authors directly. Here you will find their support forum:

https://themeforest.net/item/suprema-multipurpose-ecommerce-theme/15105482/support

Cheers!

Hi there,

If you enable Detailed Decline Messages, the customer will see the full decline reason as it is sent over from Braintree. Here is a list of all decline codes that Braintree supports – not all of them may be applicable to WooCommerce payments, but this should give you a good enough overview at least:

https://articles.braintreepayments.com/control-panel/transactions/declines#authorization-decline-codes

Cheers!

Hi @zackdn,

I’m not seeing Stripe enabled on the checkout page at https://drivertraining.staging.wpengine.com/checkout/

If you’re still having this problem, can you please submit a support ticket on https://woocommerce.com/my-account/tickets/ so we can check this in details?

@mcgregormedia, please submit a ticket with us too ??

I’ll mark this thread as resolved so we can continue the troubleshooting there.

Cheers!

Hi @zackdn,

Thanks for the explanation! I double checked this in the plugin code, but there’s no filter that would allow changing the Stripe payment gateway ID. This is the unique identifier used everywhere in WooCommerce to identify the plugin, so all other extensions integrating with Stripe will recognise it by this ID alone. To make things even more complicated, having two payment methods sharing the same IDs could give very unpredictable results and possibly errors at the checkout.

Wish I could help you more here, but changing the integration logic is much safer than risking payment method conflicts. I’ll tag this thread resolved for now, but feel free to start a new one if you have some more questions!

Cheers,

Hi

Thanks for letting us know! I just checked the checkout page in Internet Explorer 11 on Windows 10 machine and everything looks fine for me now.

Screenshot: https://cld.wthms.co/VpYoXf

I’ll mark this thread resolved for now – if you notice anything out of place again, feel free to start a new one.

Cheers!

Hi @pipoulito,

Can you please share a link to your site so we can take a look? Some caching plugins minimize JavaScript files used by the Stripe plugin which can lead to an error, so I’d like to make sure this is not the case here.

Thanks!

Thanks for the System Status Report! I managed to reproduce the same problem on a test site. This doesn’t look right to me, so I reported this a bug in the plugin repo. You can keep track of the progress here:

https://github.com/woocommerce/woocommerce-gateway-stripe/issues/508

Have a great day!

Hi @aucreuxdunarbre,

Did you have a chance to check the error? I checked this error in details, and it seems like a problem with incorrect script loading order due to Autooptimize delaying some of them.

Can you please try deactivating Autooptimize to see if it solves the problem?

Thanks!

Hi @wrip,

Is there any particular reason why you’d like to replace the existing checkout form? It’s deeply tied with nearly every single WooCommerce feature, so even if you found a way to make it work through Gravity Forms, all WooCommerce extension plugins such as payment gateways would almost certainly not be ready to work with it.

If you need Gravity Forms to rearrange/rename/hide some of the default fields, you might want to try the Checkout Field Editor instead:

https://woocommerce.com/products/woocommerce-checkout-field-editor/

Alternatively if you’d like to add some extra paid options (like gift wrapping) at the checkout, the Checkout Add-Ons plugin should get that solved for you:

https://woocommerce.com/products/woocommerce-checkout-add-ons/

Cheers!

Hi @boodschap,

We have a ticketing extension called Box Office that will let you manage the number of tickets available for certain events, and collect customer information for each person buying the ticket. Here you will find more info on how it works:

https://docs.woocommerce.com/document/woocommerce-box-office/

Cheers!

Hi @flyfisher842,

That’s a great question! Product IDs in WooCommerce are just WordPress post IDs. They are also used by many other types of things in WordPress (including posts, pages, media items, WooCommerce orders, etc), so it may not be possible to match your previous ID structure.

What I’d recommend instead is to set products SKU in WooCommerce to match your old IDs: https://cld.wthms.co/KZuhUm

These are unique indexed identifiers that can be set on each product or variation, and are often used to reference the product in external systems.

Cheers!

Hi

If there’s just a single item purchased in an order, the cart discount and single item discount will be the same. They start to differ if there’s more than one item bought at a time – in such case the _cart_discount will be a sum of discount_amount for all the items:

https://cld.wthms.co/TdDGjD

Depending on the requirements of your accounting calculations, you may want to use either of these values or both ??

Cheers!

Hi @alvima,

Thank you so much for reporting this! I fully agree that it’s confusing for the customers to filter by a certain price and get products outside of that range in results. I’m able to reproduce the same behavior on my own site too, so I’ve logged this for our developers to fix. You can keep track of the progress here:

https://github.com/woocommerce/woocommerce/issues/18170

Cheers!