HTML Pages caches an old version

I just tried the new HTML pages. I upload a ZIP-Archive and it works as expected and is a great feature.

I upload a new version of the ZIP-Archive and some pages are not updated. Seemed they are not deleted during the update and/or cached by the app. I try it with a different brwoser to avoid browser caching.

When I create a new HTML page, delete the old one and upload the new ZIP, it works, but the page-id is not valid anymore, because the new page has a new page-id.

But this is not a solution. I need a static, not changing URL for the HTML page.

Any ideas?

In an HTML page, there is an index.html and other referenced JS/CSS files.

Can you check if the index.html is not updated or the referenced JS/CSS files are not updated?

JS/CSS is not a problem (right now). The index.html is change always because it includes a timestamp. I am not sure if I used a different name for the archive. I will test it …

I just switch to the Seatable App. Today, the content was correct. Seemed to be a caching/TTL problem.

And I tested it again today with new HTML pages and a different filename for the archive. Same problem. I can reload the starting page (index.html) and it works - I got the new version. But when I reload another page it switches to the start page but never reloads and the other page still has the old version.

I manually deleted all cookies and cached pages and it works. But I cannot tell the user to delete the cookies manually. For some reason the change is not detected. Because all pages are generated with a timestamp all pages changed. This should be detected.

Can you try to add timestamp to your JS/CSS files like in: document HTML page asset cache busting by zwfxxxxx · Pull Request #58 · seatable/seatable-developer-docs · GitHub