Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:cache:lscps:troubleshooting:some-page-do-not-show-logged-in-username [2019/01/14 21:07]
Jackson Zhang
+++ litespeed_wiki:cache:lscps:troubleshooting:some-page-do-not-show-logged-in-username [2019/01/14 21:53]
Lisa Clarke
@@ Line 1: / Line 1: @@
-====== Some Pages do not show logged-in username after logged-in ======
+====== Some Pages Not Showing Logged-in Username ======
-The user is running Prestashop 1.6. After enabling LSCPS and logged-in as a user, some pages show logged-in username but some pages do not.
+In PrestaShop 1.6, with LiteSpeed Cache for PrestaShop enabled, a logged-in visitor may see their logged-in usernames on some pages but not on others.
 {{ :litespeed_wiki:cache:lscps:troubleshooting:prestashop-overrides-must-be-enabled-1.png?800 |}}
@@ Line 6: / Line 6: @@
 {{ :litespeed_wiki:cache:lscps:troubleshooting:prestashop-overrides-must-be-enabled-2.png?800 |}}
-The problem is actually an ESI hole punching issue.
+This is caused by incorrect ESI hole-punching.
-First, you will need to ensure ''overrides'' enabled.  In Prestashop admin → Advanced Parameters → Debug mode → Disable all overrides → “NO”. This setting has to be “NO” since both Prestashop 1.6 & 1.7 will rely on overrides to do hole punch.
+To fix the problem, enable overrides, like so:
-After setting it to "NO", Prestashop is working fine with the correct logged-in username for all pages.
+Navigate to **PrestaShop Admin > Advanced Parameters > Debug mode** and set **Disable all overrides** to ''NO''. This setting must be ''NO'', because both PrestaShop 1.6 & 1.7 rely on overrides to execute ESI hole punching.
-For some cases especially for Prestashop 1.7, the above may not easily fix the problem as it does for Prestashop 1.6. The Prestashop theme code may need to be analyzed to be able to identify the root cause. It could be very time consuming and you can engage us through paid support. Feel free to ask a quote if you have such need.
+NOTE: For some cases, especially for PrestaShop 1.7, the above solution may not be sufficient. The PrestaShop theme code may need to be analyzed to be able to identify the root cause. This may be a very time-consuming process. If you'd like someone else to do it, you can engage LiteSpeed through paid support. Feel free to ask for a quote if you have such a need.