Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:cache:lscwp:troubleshooting:general [2019/06/12 14:14] Lisa Clarke [Logged-in Users Appearing as Logged-out] Added Scheduled event failed |
litespeed_wiki:cache:lscwp:troubleshooting:general [2020/05/04 13:47] Shivam Saluja |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Troubleshooting Guide For LSCWP ====== | ====== Troubleshooting Guide For LSCWP ====== | ||
| + | **Please Note**: This wiki is valid for v2.9.x and below of the LiteSpeed Cache Plugin for WordPress. If you are using v3.0 or above, please see [[https://docs.litespeedtech.com/lscache/lscwp/overview/|the new documentation]]. | ||
| + | |||
| Here are a few common issues and how to deal with them. Please follow these steps first before logging any ticket with us since your issue might have been resolved. | Here are a few common issues and how to deal with them. Please follow these steps first before logging any ticket with us since your issue might have been resolved. | ||
| Line 90: | Line 92: | ||
| 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'' | 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'' | ||
| + | |||
| + | For example: | ||
| + | "The scheduled event, litespeed_imgoptm_trigger, failed to run." | ||
| 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. | 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. | ||