Sitelet https://web.archive.org/web/20200716214732/https://github.com/python/pythondotorg/issues/1457
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

Admin interface previews of Release page changes no longer purge CDN cache #1457

Open
ned-deily opened this issue Jun 19, 2019 · 3 comments
Open

Comments

@ned-deily
Copy link
Member

@ned-deily ned-deily commented Jun 19, 2019 •

When release managers use the website admin interface to create or modify Release pages, a handy "View On Site" button is available on the input page that allows you to preview the updated release page. As of a recent website update, clicking the "View on Site" button still takes you to a rendered preview page, however changes often are not reflected. This appears to be due to the preview rendering not causing the CDN to be purged so you continue to see an outdated version which is very confusing. Manually sending a PURGE request to the CDN causes the updated page to be shown. While I cannot be 100% certain, I believe that this problem did not exist prior to a recent upgrade (otherwise I would have complained about it before because it is very annoying until you remember what the problem is!). When editing Page objects, which have a similar preview feature, it does appear that the CDN cache is flushed for them as the changes seem to reliably render. So perhaps some change got lost in the website upgrade?

@brainwane
Copy link
Collaborator

@brainwane brainwane commented Aug 11, 2019

@ned-deily I was just running into something like this. Is this still happening for you?

@ned-deily
Copy link
Member Author

@ned-deily ned-deily commented Aug 12, 2019

It was as of a month or two ago. AFAIK nothing has been done to fix it. But this behavior was seen with pages generated from Release objects, something you would not be using, I would think.

@brainwane
Copy link
Collaborator

@brainwane brainwane commented Aug 12, 2019

@berkerpeksag says,

#1457 is a duplicate of #1426 and it more likely be solved by #1427.

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
You can’t perform that action at this time.