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
Currently, vars for payment buttons are generated on server side and passed to frontend JS via wp_localize_script function (or analogue), which puts those in the HTML code of the page. This can cause some random issues on sites with excessive caching.
To prevent that, an experimental option can be added. When enabled, plugin won't pass the vars inside HTML page, but will be requesting those via AJAX on page load.
This has some disadvantages though. On slow websites, it would increase the time required for payment buttons (and payment pop-ups) to be operational.
The text was updated successfully, but these errors were encountered:
Currently, vars for payment buttons are generated on server side and passed to frontend JS via
wp_localize_script
function (or analogue), which puts those in the HTML code of the page. This can cause some random issues on sites with excessive caching.To prevent that, an experimental option can be added. When enabled, plugin won't pass the vars inside HTML page, but will be requesting those via AJAX on page load.
This has some disadvantages though. On slow websites, it would increase the time required for payment buttons (and payment pop-ups) to be operational.
The text was updated successfully, but these errors were encountered: