Differences

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

Link to this comparison view

Both sides previous revision Previous revision
litespeed_wiki:cache:lscwp:error-codes [2017/10/19 13:57]
Lisa Clarke [9040] Added 9041 and 9042
litespeed_wiki:cache:lscwp:error-codes [2017/10/19 16:12] (current)
Lisa Clarke Extensive reformatting and enhancement of descriptions
Line 1: Line 1:
 ====== LSCWP Error Codes ====== ====== LSCWP Error Codes ======
  
-This page will explain the error codes received in the plugin in detail ​and any possible ​fixesif available.+LiteSpeed Cache for WordPress sometimes encounters errors. Explanations ​and possible ​solutions to these codes are listed below. If the suggested courses of action don't solve your problemplease do not hesitate to contact us via [[https://​wordpress.org/​support/​plugin/​litespeed-cache|the plugin'​s support forum]].
  
-===== 1xxx =====+===== 1000 - 1999 ===== 
 + 
 +LSCWP has minimum requirements for the software on which it relies. These error codes pop up when the software fails to meet these requirements.
  
 ==== 1000 ==== ==== 1000 ====
 === Error Message: === === Error Message: ===
-The installed PHP version is too old for the LiteSpeed Cache Plugin. +  ​The installed PHP version is too old for the LiteSpeed Cache Plugin. 
- +   
-The LiteSpeed Cache Plugin requires at least PHP 5.3. The currently installed version is PHP <​PHP_VERSION>,​ which is out-dated and insecure. Please upgrade or go to active plugins and deactivate the LiteSpeed Cache plugin to hide this message. +  The LiteSpeed Cache Plugin requires at least PHP 5.3. The currently installed version is PHP <​PHP_VERSION>,​ which is out-dated and insecure. Please upgrade or go to active plugins and deactivate the LiteSpeed Cache plugin to hide this message. 
 +  
 === Solution: === === Solution: ===
-== Server Admins== +== Server Admins == 
-Upgrade the PHP version used. If needed, set up a new PHP version [[litespeed_wiki:​php:​|here]]. +Upgrade the PHP version used. If needed, set up a new PHP version ​as described  ​[[litespeed_wiki:​php:​|here]]. 
- +== Everyone Else ==
-== All others: ​==+
 Select an upgraded PHP version if possible. If not, please contact the server administrator for options. Select an upgraded PHP version if possible. If not, please contact the server administrator for options.
  
 ==== 1010 ==== ==== 1010 ====
 === Error Message: === === Error Message: ===
-The installed WordPress version is too old for the LiteSpeed Cache Plugin.+  ​The installed WordPress version is too old for the LiteSpeed Cache Plugin
 +   
 +  The LiteSpeed Cache Plugin requires at least WordPress 3.3. Please upgrade or go to active plugins and deactivate the LiteSpeed Cache plugin to hide this message.
  
-The LiteSpeed Cache Plugin requires at least PHP 3.3. Please upgrade or go to active plugins and deactivate ​the LiteSpeed Cache plugin to hide this message.+=== Solution: === 
 +Upgrade ​to the latest version of WordPress.
  
-=== Solution: ​=== +===== 2000 - 2999 ===== 
-Upgrade the WordPress version used.+ 
 +These codes relate to errors that occur during cache management tasks.
  
-===== 2xxx ===== 
 ==== 2000 ==== ==== 2000 ====
 === Error Message: === === Error Message: ===
-Something went wrong with the form! Please try again.+  ​Something went wrong with the form! Please try again.
  
 === Solution: === === Solution: ===
-Refresh the page and try the purge action ​again.  +Something went wrong when attempting to submit the purge action. ​Refresh the page and try again.
- +
-This error indicates that something went wrong in the action submission. If refreshing does not work, please [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+
  
 ==== 2010 ==== ==== 2010 ====
 === Error Message: === === Error Message: ===
-Tried to purge list with empty list.+  ​Tried to purge list with empty list.
 === Solution: === === Solution: ===
-Purge list requires ​a list of entries to purge.+The **Purge List** button was pressed but the **Purge By...** box was empty. Please enter a list of categories, tags, or URLs, on per line, and try again.
  
 ==== 2020 ==== ==== 2020 ====
 === Error Message: === === Error Message: ===
-Bad Purge By selected value.+  ​Bad Purge By selected value.
 === Solution: === === Solution: ===
-Somehow, an invalid Purge By type was selected. Refresh the page and try again. If that does not work, please [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+Somehow, an invalid ​**Purge By** type was selected. Refresh the page and try again.
  
 ==== 2030 ==== ==== 2030 ====
 === Error Message: === === Error Message: ===
-Failed to purge by category, invalid category slug.+  ​Failed to purge by category, invalid category slug.
 === Solution: === === Solution: ===
-Purging by category ​should use the category slug. Check the category list to make sure that the slug is correctIf it still does not work, please [[https://wordpress.org/support/plugin/litespeed-cache|contact us]].+Purging by category ​requires ​the category slug. You can find a category'​s slug in the category list found at **Posts > Categories**. Or, if you know the category'​s URL, you can get the slug from thatIn ''<​nowiki>​http://www.example.com/category/my-category<​/nowiki>''​ the slug would be ''​my-category''​.
  
 ==== 2040 ==== ==== 2040 ====
 === Error Message: === === Error Message: ===
-Failed to purge by tag, invalid tag slug.+  ​Failed to purge by tag, invalid tag slug.
 === Solution: === === Solution: ===
-Purging by tag should use the tag slug. Check the tag list to make sure that the slug is correctIf it still does not work, please [[https://wordpress.org/support/plugin/litespeed-cache|contact us]].+Purging by tag requires ​the tag slug. You can find a tag's slug in the category ​list found at **Posts > Tags**. Or, if you know the tag's URL, you can get the slug from thatIn ''<​nowiki>​http://www.example.com/tag/my-tag</nowiki>''​ the slug would be ''​my-tag''​.
  
 ==== 2050 ==== ==== 2050 ====
 === Error Message: === === Error Message: ===
-Failed to purge by url, contained "<"​.+  ​Failed to purge by url, contained "<"​.
 === Solution: === === Solution: ===
-One or more of the URLs listed contained a "<". This is strictly forbidden. Please try listing the URLs again, making sure to avoid using this character.+One or more of the URLs listed contained a ''​<''​. This is strictly forbidden. Please try listing the URLs again, making sure to avoid using this character.
  
 ==== 2500 ==== ==== 2500 ====
 === Error Message: === === Error Message: ===
-Failed to purge by Post ID, given ID is not numeric: <ID>+  ​Failed to purge by Post ID, given ID is not numeric: <ID>
 === Solution: === === Solution: ===
-One or more of the Post IDs listed is not numeric. Please try listing the IDs again, making sure that all IDs listed are numeric.+One or more of the Post IDs listed is not numeric. Every post has an ID that is a number. Please try listing the IDs again, making sure that all IDs listed are numeric.
  
 ==== 2510 ==== ==== 2510 ====
 === Error Message: === === Error Message: ===
-Failed to purge by Post ID, given ID does not exist or is not published: <ID>+  ​Failed to purge by Post ID, given ID does not exist or is not published: <ID>
 === Solution: === === Solution: ===
-One or more of the Post IDs listed does not exist or the post is not published. Please verify the ID list with the Posts list to make sure that the correct IDs are used.+One or more of the Post IDs listed does not exist or the post is not published. Please verify ​that the correct Post ID was used. Check **Posts > All Posts** and hover over the title of the post in question. You should be able to get the ID from the URL
  
 ==== 2520 ==== ==== 2520 ====
 === Error Message: === === Error Message: ===
-Failed to purge by URL, invalid input: <URL>+  ​Failed to purge by URL, invalid input: <URL>
 === Solution: === === Solution: ===
-One or more of the URLs listed has an invalid format. As an example__/​2016/​02/​24/​hello-world/​__ should be used for %%http://​www.myexamplesite.com%%__/​2016/​02/​24/​hello-world/​__.+You may purge by URI or full URL, that is''​/​2016/​02/​24/​hello-world/​''​ or ''<​nowiki>​http://​www.myexamplesite.com/​2016/​02/​24/​hello-world/​</​nowiki>''​. If your URL is in any other format, it will be rejected.
  
 ==== 2530 ==== ==== 2530 ====
 === Error Message: === === Error Message: ===
-Failed to purge by category, does not exist: <​CATEGORY>​+  ​Failed to purge by category, does not exist: <​CATEGORY>​
 === Solution: === === Solution: ===
-The given category ​slug does not exist. ​Check the category list to make sure that the slug is correct. If it still does not work, please [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The category ​specified doesn'​t ​exist. ​Visit **Posts > Categories** ​to verify ​that you've entered ​the correct category ​slug.
  
 ==== 2540 ==== ==== 2540 ====
 === Error Message: === === Error Message: ===
-Failed to purge by tag, does not exist: <TAG>+  ​Failed to purge by tag, does not exist: <TAG>
 === Solution: === === Solution: ===
-The given tag slug does not exist. ​Check the tag list to make sure that the slug is correctIf it still does not work, please [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The tag specified doesn'​t ​exist. ​Visit **Posts > Tags** ​to verify ​that you've entered ​the correct tag slug. 
 + 
 +===== 3000 3999 ===== 
 + 
 +The following error codes are related to problems with data entered into various Settings fields.
  
-===== 3xxx ===== 
 ==== 3000 ==== ==== 3000 ====
 === Error Message: === === Error Message: ===
-Invalid data in Admin IPs.+  ​Invalid data in Admin IPs.
 === Solution: === === Solution: ===
-One of the entered ​IPs returned as an invalid ​IPRe-enter the list of IPs again. If it still does not work and they are all valid IPs, please [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The **Admin IPs** setting on the **Debug** tab allows you to specify IPs that may perform certain admin actions from their browsers. This error indicates that one or more of the entered ​IP addresses is invalid. ​Double-check the IPs and try again.
  
 ==== 3010 ==== ==== 3010 ====
 === Error Message: === === Error Message: ===
-Invalid data in Test IPs.+  ​Invalid data in Test IPs.
 === Solution: === === Solution: ===
-One of the entered IPs returned as an invalid IP. Re-enter the list of IPs again. If it still does not work and they are all valid IPsplease ​[[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+This error message has been deprecated. If you are seeing thisyou are using a version of LSCWP that is pretty old! Why not [[https://​wordpress.org/​plugins/​litespeed-cache/|update]]?
  
 ==== 3020 ==== ==== 3020 ====
 === Error Message: === === Error Message: ===
-Invalid Site IP: 1.2.3.4+  ​Invalid Site IP: <IP ADDRESS>
 === Solution: === === Solution: ===
-The IP address ''​1.2.3.4'' ​(for example) ​is not valid. Check your site's IP address ​and try again.+The IP address ​you entereed, ​''​<IP ADDRESS>''​is not valid. Check your site's IP and try again.
  
 ==== 3030 ==== ==== 3030 ====
 === Error Message: === === Error Message: ===
-Can not fetch Custom Sitemap: ​<​nowiki>​http://​www.example.com/​sitemapfile.xml</​nowiki>​+  ​Can not fetch Custom Sitemap: http://​www.example.com/​sitemapfile.xml
 === Solution: === === Solution: ===
 The sitemap file name you entered is invalid or the file is unavailable. Double-check the URL and try again. Be sure that you are entering the full URL to the file. The sitemap file name you entered is invalid or the file is unavailable. Double-check the URL and try again. Be sure that you are entering the full URL to the file.
Line 124: Line 129:
 ==== 3031 ==== ==== 3031 ====
 === Error Message: === === Error Message: ===
-Can not parse custom sitemap xml file: <​nowiki>​http://​www.example.com/​sitemapfile.xml</​nowiki>​.+  ​Can not parse custom sitemap xml file: http://​www.example.com/​sitemapfile.xml.
 === Solution: === === Solution: ===
-The sitemap file was fetched but cannot be read. Make sure the sitemap is in XML format and that you have installed the php-xml extension on your server. +The sitemap file was fetched but cannot be read. Make sure the sitemap is in XML format and that you have installed the ''​php-xml'' ​extension on your server.
  
 ==== 3500 ==== ==== 3500 ====
 === Error Message: === === Error Message: ===
-<TTL NAME> TTL must be an integer between <​MINIMUM>​ and 2147483647.+  ​<CONTENT TYPE> TTL must be an integer between <​MINIMUM>​ and 2147483647.
 === Solution: === === Solution: ===
-The <TTL NAMETTL entered was either not an integer or did not fit within the range listed. Please try a different value.+The ''​<CONTENT TYPE>''​ Time To Live entered was either not an integer or did not fit within the range listed. Please try a different value. TTL is the time in seconds before a given type of content expires. Most of these settings list a valid range in their tool tips, so be sure to read them.
  
 ==== 3510 ==== ==== 3510 ====
 === Error Message: === === Error Message: ===
-Removed category "<​CATEGORY>"​ from list, ID does not exist.+  ​Removed category "<​CATEGORY>"​ from list, ID does not exist.
 === Solution: === === Solution: ===
-The input <​CATEGORY> ​is not a valid category. It was removed from the input list.+Categories are listed one-per-line by slug. One ''​<​CATEGORY>​''​ you entered wasn't found, and so it was removed from the **Do Not Cache Categories** ​list. You can find a category'​s slug in the category list found at **Posts > Categories**. Or, if you know the category'​s URL, you can get the slug from that. In ''<​nowiki>​http://​www.example.com/​category/​my-category</​nowiki>''​ the slug would be ''​my-category''​.
  
 ==== 3520 ==== ==== 3520 ====
 === Error Message: === === Error Message: ===
-Removed tag "<​TAG>"​ from list, ID does not exist.+  ​Removed tag "<​TAG>"​ from list, ID does not exist.
 === Solution: === === Solution: ===
-The input <​TAG> ​is not a valid tag. It was removed from the input list.+Tags are listed one-per-line by slug. One ''​<TAG>''​ you entered wasn't found, and so it was removed from the **Do Not Cache Tags** ​list. You can find a tag's slug in the tag list found at **Posts > Tags**. Or, if you know the tag's URL, you can get the slug from that. In ''<​nowiki>​http://​www.example.com/​category/​my-tag</​nowiki>''​ the slug would be ''​my-tag''​.
  
 ==== 3530 ==== ==== 3530 ====
 === Error Message: === === Error Message: ===
-Invalid login cookie. Invalid characters found: <LOGIN COOKIE>+  ​Invalid login cookie. Invalid characters found: <LOGIN COOKIE>
 === Solution: === === Solution: ===
-The login cookie entered ​has invalid characters. ​The accepted characters are: alphanumeric characters, '​_', ​and '​-'​.+''<​LOGIN COOKIE>'' ​has invalid characters. ​Try again, entering a login cookie value that contains only alphanumeric characters, ​''_'', ​or ''​-'​'. You can make up any string you like for this setting, as long as it contains valid characters.
  
 ==== 3540 ==== ==== 3540 ====
 === Error Message: === === Error Message: ===
-Invalid Rewrite List. Empty or invalid rule. Rule: <​OPTION>,​ list: <​LIST>​+  ​Invalid Rewrite List. Empty or invalid rule. Rule: <​OPTION>,​ list: <​LIST>​
 === Solution: === === Solution: ===
-The input is tested on save. If this message is displayed, that means that the input entered is not valid one+This error is used with pairs of settings such as **Cache Mobile** and **List of Mobile User Agents**One setting is the ON/OFF switch (''<​OPTION>''​),​ while the other setting gives the parameters (''<​LIST>''​) for the switch when it is turned ON.  
-If <​LIST>​ is EMPTY, that means the rewrite list was empty at a point when it cannot ​be emptysuch as when the Enable Separate Mobile Views is checkedAt that point, ​the List of Mobile View User Agents must not be empty.+If this message is displayed, that means that the list entered is not valid for the option that has been enabled
 +If <​LIST>​ is blank, that means the rule expected some parameters to be definedbut none were. 
 + 
 +===== 4000 - 9999 ===== 
 + 
 +Errors in the this range are related to various problems reading, writing, or interpreting configuration files stored on disk.
  
-===== 4xxx ===== 
 ==== 4000 ==== ==== 4000 ====
 === Error Message: === === Error Message: ===
-Tried to parse for existing login cookie. .htaccess file not valid. Please verify contents.+  ​Tried to parse for existing login cookie. .htaccess file not valid. Please verify contents.
 === Solution: === === Solution: ===
-On upgrade, check to see if a login cookie was manually inserted. If the .htaccess file is corrupted in any way, this warning will output. This may indicate mismatched tags.+On upgrade, ​we check to see if a login cookie was manually inserted. If the ''​.htaccess'' ​file is corrupted in any way, this warning will output. This may indicate mismatched tags.
  
 ==== 4500 ==== ==== 4500 ====
 === Error Message: === === Error Message: ===
-Could not find <​CONTENT>​.+  ​Could not find <​CONTENT>​.
 === Solution: === === Solution: ===
-Receiving this error message means that the .htaccess file was modified in an unexpected manner. This resulted in missing tags, rules, or comments that are expected to be there. The easiest way to resolve this is to: +Receiving this error message means that the ''​.htaccess'' ​file was modified in an unexpected manner, which resulted in missing tags, rules, or comments that are expected to be there. The easiest way to resolve this is to: 
-  - Back up the .htaccess file  +  - Back up the ''​.htaccess'' ​file  
-  - Delete the contents ​including and within the LSCACHE START PLUGIN/​LSCACHE END PLUGIN comments.  +  - Delete the contents within the ''​LSCACHE START PLUGIN''​/''​LSCACHE END PLUGIN'' ​comments ​and those comments themselves
-  - In the wp-admin, change ​a LSCWP setting and save. +  - In your WordPress Dashboard, change ​any LiteSpeed Cache setting and save. LSCWP will write a new set of rules to ''​.htaccess''​
-  - Revert the change if required ​(optional ​step). +  - Revert the change ​you just made if desired ​(optional). 
-This should ​result in the plugin adding back the missing pieces. If this produces another error or if you would like us to take a look, just [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]], we'll be happy to help.+This should ​fix the problem.
  
-===== 5xxx ===== 
 ==== 5000 ==== ==== 5000 ====
 === Error Message: === === Error Message: ===
-This site is a subdirectory install. Login cookies do not match. Please remove both and set the login cookie in LiteSpeed Cache advanced settings.+  ​This site is a subdirectory install. Login cookies do not match. Please remove both and set the login cookie in LiteSpeed Cache advanced settings.
 === Solution: === === Solution: ===
-On upgrade, check to see if a login cookie was manually inserted. The plugin detected that this was a subdirectory install and determined that the login cookie for the two .htaccess files did not match.+On upgrade, ​we check to see if a login cookie was manually inserted. The plugin detected that this was a subdirectory install and determined that the login cookie for the two ''​.htaccess'' ​files did not match
 +To fix this problem, remove the login cookies from both installs and set again in **LiteSpeed Cache > Settings > Advanced**.
  
-===== 6xxx ===== 
 ==== 6000 ==== ==== 6000 ====
 === Error Message: === === Error Message: ===
-Notice: This plugin requires a LiteSpeed Server with the LSCache Module enabled. If you are unable to change your server stack, please contact your hosting provider to request the required changes. This plugin will NOT work properly.+  ​Notice: This plugin requires a LiteSpeed Server with the LSCache Module enabled. If you are unable to change your server stack, please contact your hosting provider to request the required changes. This plugin will NOT work properly.
 === Solution: === === Solution: ===
-As the error states, this plugin requires a LiteSpeed Server with the LSCache Module enabled.+This plugin requires a LiteSpeed Server with the LSCache Module enabled, and will not function without one.
 == Server Admins: == == Server Admins: ==
 If a LiteSpeed Server is already installed, it may just require switching from Apache to LiteSpeed. Note: If the license that is being used is not at least a 2-CPU license, then the LSCache Module may be not included. In this case, either upgrade the license to a 2-CPU+ license or purchase the LSCache Module addon. If a LiteSpeed Server is already installed, it may just require switching from Apache to LiteSpeed. Note: If the license that is being used is not at least a 2-CPU license, then the LSCache Module may be not included. In this case, either upgrade the license to a 2-CPU+ license or purchase the LSCache Module addon.
Line 196: Line 203:
 As a LiteSpeed Server is required, please contact the server admin for the possibility of switching to a LiteSpeed Server. As a LiteSpeed Server is required, please contact the server admin for the possibility of switching to a LiteSpeed Server.
  
- 
-===== 9xxx ===== 
 ==== 9000 ==== ==== 9000 ====
 === Error Message: === === Error Message: ===
-LiteSpeed Cache was unable to write to the wp-config.php file. Please add the following to the wp-config.php file: ''​define('​WP_CACHE',​ true);''​.+  ​LiteSpeed Cache was unable to write to the wp-config.php file. Please add the following to the wp-config.php file: define('​WP_CACHE',​ true);.
 === Solution: === === Solution: ===
-Check the wp-config.php file permissions. This error indicates that we attempted to set WP_CACHE to true, but was unable to write to the file.+Check the ''​wp-config.php'' ​file permissions. This error indicates that we attempted to set WP_CACHE to true, but was unable to write to the file. 
 +You can either change the permissions on ''​wp-config.php''​ and try again, or you can manually add the line ''​define('​WP_CACHE',​ true);'' ​to the file.
  
 ==== 9010 ==== ==== 9010 ====
 === Error Message: === === Error Message: ===
-Failed to back up file, aborted changes.+  ​Failed to back up file, aborted changes.
 === Solution: === === Solution: ===
-The plugin attempted to make changes to the .htaccess file, however in its attempt to create ​a backup, ​it failedPlease check the permissions of the WordPress root and .htaccess files to make sure that the directory/​files are writable. If assistance is required, feel free to [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+Before making any changes to the ''​.htaccess'' ​file, the plugin always creates ​a backup. If the backup failsyou see this error, and the changes are aborted. 
 +Check the permissions of the WordPress root and ''​.htaccess'' ​files to make sure that the directory/​files are writable.
  
 ==== 9020 ==== ==== 9020 ====
 === Error Message: === === Error Message: ===
-Failed to put contents into .htaccess.+  ​Failed to put contents into .htaccess.
 === Solution: === === Solution: ===
-The plugin attempted to make changes to the .htaccess file, however in its attempt ​to save the file, it failed. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/​files are writable. If assistance is required, feel free to [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The plugin attempted to make changes to the ''​.htaccess'' ​file, but was unable ​to successfully ​save the file. Please check the permissions of the WordPress root and ''​.htaccess'' ​files to make sure that the directory/​files are writable.
  
 ==== 9030 ==== ==== 9030 ====
 === Error Message: === === Error Message: ===
-Failed to get .htaccess file contents.+  ​Failed to get .htaccess file contents.
 === Solution: === === Solution: ===
-The plugin attempted to read the .htaccess file, however in its attempt ​to open the file, it failed. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/​files are readable. If assistance is required, feel free to [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The plugin attempted to read the ''​.htaccess'' ​file, but was unable ​to open it. Please check the permissions of the WordPress root and ''​.htaccess'' ​files to make sure that the directory/​files are readable.
  
 ==== 9040 ==== ==== 9040 ====
 === Error Message: === === Error Message: ===
-.htaccess file not readable or not writable.+  ​.htaccess file not readable or not writable.
 === Solution: === === Solution: ===
-The plugin attempted to read or write to the ''​.htaccess''​ file, however in checking the file permissions,​ it returned either not readable or not writable. Please check the permissions of the WordPress root and ''​.htaccess''​ files to make sure that the directory/​files are readable. If assistance is required, feel free to [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The plugin attempted to read or write to the ''​.htaccess''​ file, however in checking the file permissions,​ it returned either not readable or not writable. Please check the permissions of the WordPress root and ''​.htaccess''​ files to make sure that the directory/​files are readable.
  
 ==== 9041 ==== ==== 9041 ====
 === Error Message: === === Error Message: ===
-.htaccess file not readable.+  ​.htaccess file not readable.
 === Solution: === === Solution: ===
-The plugin attempted to read the ''​.htaccess''​ file, however in checking the file permissions,​ it returned not readable. Please check the permissions of the WordPress root and ''​.htaccess''​ files to make sure that the directory/​files are readable. If assistance is required, feel free to [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The plugin attempted to read the ''​.htaccess''​ file, however in checking the file permissions,​ it returned not readable. Please check the permissions of the WordPress root and ''​.htaccess''​ files to make sure that the directory/​files are readable.
  
 ==== 9042 ==== ==== 9042 ====
 === Error Message: === === Error Message: ===
-.htaccess file not writable.+  ​.htaccess file not writable.
 === Solution: === === Solution: ===
-The plugin attempted to write to the ''​.htaccess''​ file, however in checking the file permissions,​ it returned not writable. Please check the permissions of the WordPress root and ''​.htaccess''​ files to make sure that the directory/​files are writable. ​If assistance is required, feel free to [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The plugin attempted to write to the ''​.htaccess''​ file, however in checking the file permissions,​ it returned not writable. Please check the permissions of the WordPress root and ''​.htaccess''​ files to make sure that the directory/​files are writable. 
 ==== 9050 ==== ==== 9050 ====
 === Error Message: === === Error Message: ===
-Prefix was found after suffix.+  ​Prefix was found after suffix.
 === Solution: === === Solution: ===
-Receiving this error message means that the .htaccess file was modified in an unexpected manner. This resulted in missing tags, rules, or comments that are expected to be there. The easiest way to resolve this is to: +Receiving this error message means that the ''​.htaccess'' ​file was modified in an unexpected manner, which resulted in missing tags, rules, or comments that are expected to be there. The easiest way to resolve this is to: 
-  - Back up the .htaccess file  +  - Back up the ''​.htaccess'' ​file  
-  - Delete the contents ​including and within the LSCACHE START PLUGIN/​LSCACHE END PLUGIN comments.  +  - Delete the contents within the ''​LSCACHE START PLUGIN''​/''​LSCACHE END PLUGIN'' ​comments ​and those comments themselves
-  - In the wp-admin, change ​a LSCWP setting and save. +  - In your WordPress Dashboard, change ​any LiteSpeed Cache setting and save. LSCWP will write a new set of rules to ''​.htaccess''​
-  - Revert the change if required ​(optional ​step). +  - Revert the change ​you just made if desired ​(optional). 
-This should ​result in the plugin adding back the missing pieces. If this produces another error or if you would like us to take a look, just [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]], we'll be happy to help.+This should ​fix the problem.
  
 ==== 9060 ==== ==== 9060 ====
 === Error Message: === === Error Message: ===
-Failed to overwrite .htaccess.+  ​Failed to overwrite .htaccess.
 === Solution: === === Solution: ===
-The plugin attempted to make changes to the .htaccess file, however in its attempt ​to save the file, it failed. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/​files are writable. If assistance is required, feel free to [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+The plugin attempted to make changes to the ''​.htaccess'' ​file, but was unable ​to successfully ​save the file. Please check the permissions of the WordPress root and ''​.htaccess'' ​files to make sure that the directory/​files are writable.
  
 ==== 9070 ==== ==== 9070 ====
 === Error Message: === === Error Message: ===
-The wp-config file not writeable for ''​'​WP_CACHE''​'.+  ​The wp-config file not writeable for '​WP_CACHE'​.
 === Solution: === === Solution: ===
-Check the wp-config.php file permissions. This error indicates that we attempted to set WP_CACHE to true, but was unable to write to the file. If this doesn'​t work, please [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]].+Check the ''​wp-config.php'' ​file permissions. This error indicates that we attempted to set WP_CACHE to true, but were unable to write to the file.
  
 ==== 9080 ==== ==== 9080 ====
 === Error Message: === === Error Message: ===
-wp-config file did not find a place to insert define.+  ​wp-config file did not find a place to insert define.
 === Solution: === === Solution: ===
-Please [[https://​wordpress.org/​support/​plugin/​litespeed-cache|contact us]], this error indicates that there is a custom wp-config.php set up. Alternatively,​ please ​add the define in the desired customized location. A suggested location is just above where ''​$table_prefix''​ is set.+This error indicates that there is a custom ​''​wp-config.php'' ​set up. Manually ​add the define in the desired customized location. A suggested location is just above where ''​$table_prefix''​ is set. If this is beyond your comfort level, contact us via [[https://​wordpress.org/​support/​plugin/​litespeed-cache|the plugin'​s support forum]].
  
  • Admin
  • Last modified: 2017/10/19 16:12
  • by Lisa Clarke