Cookie

Hello @justin-bigscoots,

Thank you for contacting WP Travel Engine team!

We kindly request information about the caching plugin you are currently utilizing. This is important as the plugin uses a cookie to retrieve and track the current session and cart data within that session. By knowing the caching plugin you employ, we can conduct compatibility tests and, if feasible, provide you with a suitable solution.

Thank you for your cooperation in this matter.

It’s not so much the cache plugin. It’s using a Cloudflare enterprise plan with full-page caching, the cache is automatically bypassed anytime a cookie is set in the response headers, the cookie is set on all pages so essentially cache is bypassed for the entire site.

Hello @justin-bigscoots,

We have thoroughly investigated the problem and are happy to inform you that we have identified the bug and are working diligently on a fix. In our next update, we will ensure that the set-cookie header is appropriately handled to prevent interference with caching mechanisms.

We understand the importance of efficient caching for website performance and user experience. By rectifying this issue, we aim to provide a smoother and more optimized experience for all WP Travel Engine users.

If you have any queries or confusion, please let me know and I will be back.

Thank you!

That is great news! Appreciate you looking into this and coming up with a fix ??

Hi @manjilnepali,
Thanks a lot for your response man. It would be great if you could please make sure that:

1. If the same tracking can be implemented without setting cookies at the PHP level, which will basically add the set-cookie in the response header. Couple of alternate solution would be to take advantage of the browser’s LocalStorage API and tracking the session at the JS level and then finally passing that data to PHP via some Ajax.
   Alternatively, if cookies are must need to be set, it would be great if you set the cookies at the JS level instead of the PHP level – as setting cookies via JS won’t add set-cookie in the response header and you get the same functionality.
2. If for some reason both of those above options are not viable and you must need to set the cookie at the PHP level, then can you make sure that the cookies are only loaded on those exact pages where they are needed instead of loading them across all the pages on the website.
   But if option 1 can be implemented, it would make your plugin super cache friendly.

Hello @isaumya ,

Thank you for considering these suggestions. We look forward to the issue being addressed in the next release update of the plugin.

If you have any queries or confusion, please let me know and I will be back.

Thank you!