Differences

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

--- litespeed_wiki:cache:litemage:troubleshooting:jquery-is-not-defined [2017/05/01 14:46]
Michael Alegre Added more info to the cause section.
+++ litespeed_wiki:cache:litemage:troubleshooting:jquery-is-not-defined [2017/05/01 15:27]
Ron Saad
@@ Line 1: / Line 1: @@
-====== JS error:"jQuery is not defined" after enabling LiteMage ======
+====== JS error: "jQuery is not defined" after enabling LiteMage ======
 **Problem**: After enabling LiteMage, Magento shows the JS error "jQuery is not defined". This error can also be seen from the Chrome/Firefox development console.
-{{ :litespeed_wiki:cache:litemage:troubleshooting:litemage-jqueryerror.png?direct |}}
+{{ :litespeed_wiki:cache:litemage:troubleshooting:litemage-jqueryerror.png?nolink |}}
-**Cause**: LiteMage used ESI to hole punche certain blocks while LiteSpeed Web Server assembles the main html and those ESI blocks from different responses. When hole punched blocks (ESI blocks) also contain javascript, the javascript minifier filter will process the partial html again, causing incompatible javascript references for the whole page.
-**Solution**: Locate the module throwing this error, the pagespeed module in this example, and either disable it or modify it's configuration settings. For this case, pagespeed's Javascript "Enabled" setting had to be changed from "Yes" to "No".
-{{ :litespeed_wiki:cache:litemage:troubleshooting:pagespeed-js-error.png?direct |}}
+**Cause**: LiteMage uses ESI to hole-punch certain blocks, which are then used by LiteSpeed Web Server when assembling the main HTML page. Each ESI block yields a separate HTTP response, and each of these responses passes through the JavaScript Minifier filter.
+When a hole-punched (ESI) block also contains JavaScript, the JavaScript Minifier filter processes the partial HTML as if it were an independent page, causing incompatible JavaScript references for the rest of the assembled main HTML page.
+**Solution**: Locate the module throwing this error (in this example, the PageSpeed module), and either disable it, or modify its configuration settings. For this case, PageSpeed's JavaScript "Enabled" setting had to be changed from "Yes" to "No".
+{{ :litespeed_wiki:cache:litemage:troubleshooting:pagespeed-js-error.png?nolink |}}