Title: freshaspect's Replies | WordPress.org

---

# freshaspect

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

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

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[W3 Total Cache] Finally cracked why W3TC doesn't work properly!](https://wordpress.org/support/topic/finally-cracked-why-w3tc-doesnt-work-properly/)
 *  Thread Starter [freshaspect](https://wordpress.org/support/users/freshaspect/)
 * (@freshaspect)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/finally-cracked-why-w3tc-doesnt-work-properly/#post-7162077)
 * Not sure if it’s related to that and it has nothing to do with the URLs of the
   actual pages – it’s how W3TC handles those URLs internally.
 * Essentially in one part of the code (retrieving cached pages) they are handled
   one way. In another part of the code (when you update a page and it invalidates
   the cached version of that page) they are handled a different way.
 * The net result is that updating a page doesn’t result in you seeing the updated
   page on the frontend.
 * All of this is with memcache. I think it’s fine when you use file-based cacheing
   as I don’t think that uses cache keys.

Viewing 1 replies (of 1 total)