Skip to content
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.

Allow local cache to be cleared from the admin interface #8

Open
vittala opened this issue Jun 14, 2011 · 0 comments
Open

Allow local cache to be cleared from the admin interface #8

vittala opened this issue Jun 14, 2011 · 0 comments
Assignees

Comments

@vittala
Copy link
Contributor

vittala commented Jun 14, 2011

The mechanism the component uses to determine when to cache entries is a bit simplistic. The component needs better cache control in the form of:

  • Manual clearing of a cache for a given blog
  • Setting of a cache timeout time period on a per-blog basis.
cognidox pushed a commit that referenced this issue Jun 14, 2011
If the local page cache for a blog is invalid, the component
will continue to load data from the local page cache, meaning
the blog won't appear to update in Joomla. This update allows
a URL parameter to be added to an entries view on the Joomla
frontend that forces a feed request to WP to get the page.
To use, add 'nocache=true' to the entries view URL.
@ghost ghost assigned vittala Jun 15, 2011
cognidox pushed a commit that referenced this issue Aug 19, 2011
There has been an issue where lists of blog posts were
permanently cached. As a result, new posts added to Wordpress
were not appearing in Joomla. This update introduces a
per-blog cache timeout value, which will invalidate the
post entries cache after the timeout has been reached.

The cache timeout can be altered on a blog by setting the
Cache timeout parameter on the blog's menu item.

This does not deal with invalidating individual post
entries though.
cognidox pushed a commit that referenced this issue Jul 23, 2012
Adds a link to clear the cache for a blog in the admin pages.
Saves the bother of going to the menu and setting the cache
time to zero if you need to flush the cache.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant