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

Reproduction warc archives #180

Closed
steper70 opened this issue Jun 15, 2023 · 3 comments · Fixed by #181
Closed

Reproduction warc archives #180

steper70 opened this issue Jun 15, 2023 · 3 comments · Fixed by #181

Comments

@steper70
Copy link

After the last update warc archives uploaded to replayweb.page no longer play

@ikreymer
Copy link
Member

That is not correct, just tested with a few different WARCs which load fine, as before.
If you'd like us to take a look at a specific issue, please provide an example.

@steper70
Copy link
Author

I made a test acquisition.
This archive is played with version "ReplayWeb.page-1.7.14". However, it does not work with the ReplayWeb.page-1.8.0 version
I attach warc and wacz shared folder link and related screenshots.

https://1drv.ms/f/s!AtLWnnMaFSeQ6wK69DOK6uoyp2Bc?e=Uj1sJW

ikreymer added a commit that referenced this issue Jun 16, 2023
@ikreymer
Copy link
Member

Thanks for the repro! Very oddly, this seems to be related to the latest version of Ruffle, for some reason, this stops loading with Ruffle release >2023-05-13. For now, switching back to that version.
Will open an issue with ruffle.

ikreymer added a commit that referenced this issue Jun 16, 2023
#181)

* ruffle:
- switch to ruffle 2023-05-13 release, later versions interfere with loading, it seems (see #180)
fixes #180

* add ruffle toggling options
- disable by default in embed mode, can be enabled with 'useruffle' attr
- enable by default in standalone, can be disabled with 'skipruffle' attr
- fixes #182

* update CHANGES for 1.8.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants