Title: timematcher's Replies | WordPress.org

---

# timematcher

  [  ](https://wordpress.org/support/users/timematcher/)

 *   [Profile](https://wordpress.org/support/users/timematcher/)
 *   [Topics Started](https://wordpress.org/support/users/timematcher/topics/)
 *   [Replies Created](https://wordpress.org/support/users/timematcher/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/timematcher/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/timematcher/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/timematcher/engagements/)
 *   [Favorites](https://wordpress.org/support/users/timematcher/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Session expired](https://wordpress.org/support/topic/session-expired-1/)
 *  [timematcher](https://wordpress.org/support/users/timematcher/)
 * (@timematcher)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/session-expired-1/#post-6199483)
 * Hi
    I had the same problem and and kept me awake for two nights. Turns out, that
   I had installed **wp super cache** and modified wp-config.php to include the 
   cache path.
 * Then one day, I switched the caching engine to Zencache or somethign else ( I
   was experimenting with cache engines LOL) and cleared the cache.
 * From that day onwards, I tried everything but login prompt would reappear when
   custmizing the theme…
 * Today, I analyzed the settings in wp-config.php and found the culprit.
    // **
   MySQL settings – You can get this info from your web host ** // /** The name 
   of the database for WordPress */ define( ‘WPCACHEHOME’, ‘C:\inetpub\xxxxxxxxxxx.
   com\wp-content\plugins\wp-super-cache/’ ); //Added by WP-Cache Manager
 * and commenting out this define fixed the issue.
 * **New users coming to this page for solution:**
 * Please note this worked because I was no longer using wp cache and had wpcachehome
   defined which was probably causing this conflict! You guys must try out the above
   steps first and see if it resolves the problem.
 * Thanks

Viewing 1 replies (of 1 total)