Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:cache:litemage:troubleshooting:jquery-is-not-defined [2017/05/01 14:47]
Michael Alegre
litespeed_wiki:cache:litemage:troubleshooting:jquery-is-not-defined [2017/05/01 14:54]
Michael Alegre
Line 2: Line 2:
  
 **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. **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 uses 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.+**Cause**: LiteMage uses ESI to hole punch certain blocks while LiteSpeed Web Server assembles the main HTML page 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"​. ​ **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 ​|}} +{{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​pagespeed-js-error.png?​nolink ​|}}
- +
- +
  • Admin
  • Last modified: 2017/05/08 14:01
  • by Lisa Clarke