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

Purge AMP cache on post save / update #192

Closed
janvitos opened this issue Jan 29, 2021 · 3 comments
Closed

Purge AMP cache on post save / update #192

janvitos opened this issue Jan 29, 2021 · 3 comments

Comments

@janvitos
Copy link

Hi,

I noticed that when I save / update a post, the cache for AMP pages is NOT purged. Looking at the cache folders, I see that the /amp/ folder inside the main article folder has the same timestamp as before the update.

It would be great if the plugin would also purge the /amp subdirectory on post save / update. I know there are many different amp locations (/amp/, /?amp, /?amp=1, etc.) so it might be tricky to get them all purged.

Thank you.

@coreykn
Copy link
Contributor

coreykn commented Feb 1, 2021

We don't plan on adding this type of handling in the current branch (1.6) but have it on our list to evaluate in the future. In the meantime the function in the following post can be used: https://wordpress.org/support/topic/amp-cache-is-not-cleared/#post-13809107

@janvitos
Copy link
Author

janvitos commented Feb 5, 2021

I will check this out. Thanks.

@coreykn
Copy link
Contributor

coreykn commented Aug 4, 2021

We do not plan on adding support for this directly to Cache Enabler. However, we are looking adding this type of support by introducing something like #229. That way snippets like I shared above can easily be added to extend Cache Enabler for specific uses cases, like clearing the AMP cache if the website is using an AMP plugin.

@coreykn coreykn closed this as completed Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants