Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating the Parent Theme should trigger wipe of the cache #145

Closed
raamdev opened this issue May 2, 2014 · 4 comments
Closed

Updating the Parent Theme should trigger wipe of the cache #145

raamdev opened this issue May 2, 2014 · 4 comments
Labels
Milestone

Comments

@raamdev
Copy link
Contributor

@raamdev raamdev commented May 2, 2014

When a site is using a child theme and the parent theme is updated (through the WordPress theme update system), that should trigger a wipe of the cache, just as if the theme itself was being changed.

@raamdev raamdev added this to the Future Release milestone May 2, 2014
@raamdev raamdev added bug labels May 2, 2014
@jaswrks
Copy link

@jaswrks jaswrks commented Jun 17, 2014

I agree. I think that would be true after any component in WordPress is upgraded also. There is a WordPress filter upgrader_process_complete that we could hook into for this.

@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Jun 30, 2014

Punting to Future Release milestone.

@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Sep 20, 2014

Next release changelog:

  • Bug Fix: When any WordPress component is upgraded (core, plugin, theme), Quick Cache now properly clears the site cache to avoid serving a stale cache file to a visitor. See #145.
@jaswrks
Copy link

@jaswrks jaswrks commented Sep 21, 2014

Nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants