You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since there are some issues reported that are related to "Invalid security token" error, it would be a good idea to send no cache headers during payment popup page display.
Another option is to load popup-related data via ajax request on page load, but this would definitely and noticeably slow payment popup display. This could be implemented as experimental option setting for the situations when no cache headers are not working. I've created a new issue for this #179
The text was updated successfully, but these errors were encountered:
This would only help if payment popup is cached by browser, but won't help if it is cached on server and visitors get cached version from server itself.
* Added "Apply Per-Order" option for fixed amount coupons
* Bumped version to 2.0.36t1
* #178
* Rewrote History API handling code on payment popup
Fixes rare popup closing issue on Safari
* Bumped version to 2.0.36t2
* Fixed subtotal was displayed as 0 for quantity products with coupon applied
* Product price is now rounded up to 2 numbers after decimal point
Fixes incosistency between backend and frontend calculations if product price has more than 2 numbers after decimal point
* Force Stripe API version usage
* Bumped version to 2.0.36t3
* Clear caching plugin cache on settings save
* Moved payment popup inline CSS to external file
Payment popup inline CSS is now minified
* Force payment popup page refresh if it's older than one hour #180
* Force Stripe API version `2020-03-02` usage for internal Stripe API handler
* Force Stripe API version `2020-03-02` for frontend stripe.js requests
* Bumped version to 2.0.36t4
Updated readme.txt
* WPCS-related changes
* Added Egyptian Pound (EGP) currency
* Bumped version to 2.0.36
Co-authored-by: E. Rommel <[email protected]>
Since there are some issues reported that are related to "Invalid security token" error, it would be a good idea to send no cache headers during payment popup page display.
Another option is to load popup-related data via ajax request on page load, but this would definitely and noticeably slow payment popup display. This could be implemented as experimental option setting for the situations when no cache headers are not working. I've created a new issue for this #179
The text was updated successfully, but these errors were encountered: