Title: Updaet problem
Last modified: May 25, 2020

---

# Updaet problem

 *  Resolved [orlovsky](https://wordpress.org/support/users/orlovsky/)
 * (@orlovsky)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/updaet-problem/)
 * In the previous version of LiteSpeed I had custom cache folder as /min/, after
   update to version 3.1 it trying to load scripts from /wp-content/litespeed/ (
   which does not exist). And there are no files in the old folder neither in the
   new one.
 * Where I may check the cache folder setting in the new UI?

Viewing 1 replies (of 1 total)

 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/updaet-problem/#post-12887432)
 * Hi,
 * It’s hard-coded path into wp-content/litespeed/ , this directory will be created
   if not exist , if it didn’t create, please check permission/ownership of parent
   dir , and make sure your PHP process has write permission to wp-content dir.
 * Please try perform a purge all , and try again.
 * Best regards,

Viewing 1 replies (of 1 total)

The topic ‘Updaet problem’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

## Tags

 * [cache](https://wordpress.org/support/topic-tag/cache/)
 * [folder](https://wordpress.org/support/topic-tag/folder/)

 * 1 reply
 * 2 participants
 * Last reply from: [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * Last activity: [5 years, 11 months ago](https://wordpress.org/support/topic/updaet-problem/#post-12887432)
 * Status: resolved