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
Last revision Both sides next revision
litespeed_wiki:cache:lscwp:troubleshooting:general [2018/10/31 15:22]
Jackson Zhang [Cache Always Misses]
litespeed_wiki:cache:lscwp:troubleshooting:general [2019/06/12 14:14]
Lisa Clarke [Logged-in Users Appearing as Logged-out] Added Scheduled event failed
Line 86: Line 86:
  
 This problem is caused when using multiple web applications under a single domain. You can find more information on this issue and how to resolve it in our [[litespeed_wiki:​cache:​common:​logged-in-cookie-conflicts|Handling Logged-in Cookie Conflicts page]]. This problem is caused when using multiple web applications under a single domain. You can find more information on this issue and how to resolve it in our [[litespeed_wiki:​cache:​common:​logged-in-cookie-conflicts|Handling Logged-in Cookie Conflicts page]].
 +
 +==== A Scheduled Event has Failed =====
 +
 +The following notice may appear in the Health Check plugin: ''​The scheduled event, litespeed_xxxx[image or ccss]_trigger,​ failed to run, Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended''​
 +
 +Technically,​ this is not a LiteSpeed issue, but is due to WordPress itself. This usually happens when WP does a version update. It will usually clear up on its own in a day or so, once the WP-Cron is back to normal.
 +
 +If you don't want to wait, you can disable WP-Cron and use a 3rd party cron like cPanel cron.
  
 ===== Advanced Issues ===== ===== Advanced Issues =====
Line 94: Line 102:
   * In the **Debug** settings tab, disable **Check Advanced Cache**.   * In the **Debug** settings tab, disable **Check Advanced Cache**.
   * Verify that the cache directory (found in ''​wp-content/​cache''​) has the proper permissions (0755)   * Verify that the cache directory (found in ''​wp-content/​cache''​) has the proper permissions (0755)
-  * Some CDN cache settings ​may break LScache ​and make ''​X-LiteSpeed-Cache:​ miss" ​appear all the time but accessing ​to backend server directly ​will see "x-litespeed-cache: hit"You should ​turn off such CDN cache functions. ​+  * Some CDNs have cache settings ​that can break LSCache ​and cause ''​X-LiteSpeed-Cache:​ miss''​ to appear ​at all times. However, ​accessing ​the backend server directly ​achieves ''​X-LiteSpeed-Cache: hit''​If this happens, ​turn off the CDN'​s ​cache functions. ​ 
  
 ==== Currency/​Language Switcher Plugins ==== ==== Currency/​Language Switcher Plugins ====
  • Admin
  • Last modified: 2019/07/08 20:54
  • by Jackson Zhang