You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you expect to happen? What happened instead?
Updated .wacz files do not show any new data if filename is the same. When downloading a web archive as a .wacz file and saving it in the same path as another web archive, archiveweb.page acts as if the original version was all that was ever saved. This happens when adding or deleting pages, the initial version of the .wacz remains the only version one can browse even if all pages are changed or deleted. I suspect the full .wacz is being cached somewhere without the user's input, with no code to update it.
Step-by-step reproduction instructions
Create a new web archive, download any webpage
Download the archive as a .wacz and store it anywhere on your machine
Without importing the local archive, add a new page to the existing archive in archiveweb.page
Download the archive again, without changing its filename
Overwrite the local .wacz with the new version
Note there are absolutely no observable changes
Change the name of the .wacz file. Suddenly, all changes are visible
Additional details
No response
The text was updated successfully, but these errors were encountered:
ArchiveWeb.page Version
v0.13.3
What did you expect to happen? What happened instead?
Updated .wacz files do not show any new data if filename is the same. When downloading a web archive as a .wacz file and saving it in the same path as another web archive, archiveweb.page acts as if the original version was all that was ever saved. This happens when adding or deleting pages, the initial version of the .wacz remains the only version one can browse even if all pages are changed or deleted. I suspect the full .wacz is being cached somewhere without the user's input, with no code to update it.
Step-by-step reproduction instructions
Additional details
No response
The text was updated successfully, but these errors were encountered: