Wordpress LScache Plugin: PayPal Popup Closes After Opening
Last Updated on: Wed, 15 Apr 2026 00:00:02 Ive had a problem for some time now, just want to see who else has the same problem. Ive got a few ecommerce stores running litespeed cache and since update 2.9.8, it seems to have caused caching issues affecting the paypal smart button from working. The problem in question is when someone goes to pay, they click paypal buy now on the product page, the paypal popup appears and then immediately dissapears. If you clear the cache for all pages, it works fine for some time and then the problem creeps back, it seems to cache something on the page that prevents the buttons from working or passing data to paypal. Ill add some of the console error codes below for the wizards. I had to add /product/ into the excludes for URI which worked for some time until the most recent update, this addition to excludes did not seem to make a difference after 2.9.9. I raised a case to litespeed cache support and was given some code to add into the functions.php to help with the issue but unfortunately this code broke the product pages. jquery-migrate.min.js?ver=1.4.1:2 JQMIGRATE: Migrate is installed, version 1.4.1 custom.js?ver=62aba6f326aa4223327f304f0ecdd854:96 Sun Oct 27 2019 13:17:16 GMT+1100 (Australian Eastern Daylight Time) A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . A cookie associated with a cross-site resource at was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and . logger.js:63 ppxo_unhandled_error stack: Error: TypeError: Cannot read property messages ?s://www.paypalobjects.com/api/checkout.js:8132:3) , errtype: [object Error] , timestamp: 1572142644654, windowID: 70cfa7488e , pageID: 86b132e714 ,?? print @ logger.js:63 log @ logger.js:181 error @ logger.js:234 (anonymous) @ setup.js:36 dispatchPossiblyUnhandledError @ exceptions.js:27 (anonymous) @ promise.js:122 setTimeout (async) reject @ promise.js:120 dispatch @ promise.js:179 reject @ promise.js:127 dispatch @ promise.js:179 reject @ promise.js:127 dispatch @ promise.js:186 reject @ promise.js:127 (anonymous) @ promise.js:157 dispatch @ promise.js:184 reject @ promise.js:127 (anonymous) @ promise.js:51 respond @ client.js:147 _RECEIVE_MESSAGE_TYPE. @ types.js:126 receiveMessage @ index.js:114 messageListener @ index.js:140 types.js:121 Uncaught Error: TypeError: Cannot read property messages of undefined at wc-gateway-ppec-smart-payment-buttons.js:125 at ZalgoPromise.dispatch (promise.js:170) at ZalgoPromise.resolve (promise.js:96) at promise.js:43 at XMLHttpRequest.xhrLoad (http.js:117) at Object._RECEIVE_MESSAGE_TYPE. [as postrobot_message_response] (types.js:121) at receiveMessage (index.js:114) at messageListener (index.js:140) _RECEIVE_MESSAGE_TYPE. @ types.js:121 receiveMessage @ index.js:114 messageListener @ index.js:140 setTimeout (async) dispatchPossiblyUnhandledError @ exceptions.js:16 (anonymous) @ promise.js:122 setTimeout (async) reject @ promise.js:120 dispatch @ promise.js:179 reject @ promise.js:127 dispatch @ promise.js:179 reject @ promise.js:127 dispatch @ promise.js:186 reject @ promise.js:127 (anonymous) @ promise.js:157 dispatch @ promise.js:184 reject @ promise.js:127 (anonymous) @ promise.js:51 respond @ client.js:147 _RECEIVE_MESSAGE_TYPE. @ types.js:126 receiveMessage @ index.js:114 messageListener @ index.js:140 serialize.js:175 Uncaught Error: Error: TypeError: Cannot read property messages of undefined at wc-gateway-ppec-smart-payment-buttons.js?ver=1.6.17:125 at ZalgoPromise.dispatch (promise.js:170) at ZalgoPromise.resolve (promise.js:96) at promise.js:43 at XMLHttpRequest.xhrLoad (http.js:117) at Object._RECEIVE_MESSAGE_TYPE. [as postrobot_message_response] (types.js:121) at receiveMessage (index.js:114) at messageListener (index.js:140) at deserializeError (serialize.js:175) at serialize.js:212 at util.js:140 at eachArray (util.js:102) at each (util.js:116) at replaceObject (util.js:138) at util.js:147 at eachObject (util.js:109) at each (util.js:118) at replaceObject (util.js:138) deserializeError @ serialize.js:175 (anonymous) @ serialize.js:212 (anonymous) @ util.js:140 eachArray @ util.js:102 each @ util.js:116 replaceObject @ util.js:138 (anonymous) @ util.js:147 eachObject @ util.js:109 each @ util.js:118 replaceObject @ util.js:138 (anonymous) @ util.js:147 eachObject @ util.js:109 each @ util.js:118 replaceObject @ util.js:138 deserializeMethods @ serialize.js:202 receiveMessage @ index.js:111 messageListener @ index.js:140 setTimeout (async) onError @ component.jsx:828 (anonymous) @ promise.js:40 _try @ promise.js:409 promisifyWRapper @ promise.js:39 resultValue @ props.js:88 onceWrapper @ fn.js:35 (anonymous) @ serialize.js:34 _try @ promise.js:409 (anonymous) @ serialize.js:33 (anonymous) @ types.js:68 _try @ promise.js:409 _RECEIVE_MESSAGE_TYPE. @ types.js:56 receiveMessage @ index.js:114 messageListener @ index.js:140Expand t ttThis topic was modified 3 years ago by extremist87. , Hi @extremist87, I found a similar topic on our ticket system, may I confirm is that your submission? ]
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference