-
Notifications
You must be signed in to change notification settings - Fork 12
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
Parsoid error when starting VisualEditor on wiki page with embedded video #1025
Comments
Is this not an upstream issue? We don't run customised mediawiki code. |
Yes, it probably is an upstream issue in some sense, but I didn’t have quite enough information to report it in Wikimedia’s issue tracker, since the error is so generic. The theory was that maybe there would be a more specific error message on the server side. |
Able to reproduce using the docker image for MediaWiki 1.39.6 (after enabling VisualEditor, InstantCommons, TimedMediaHandler, asking it to spit out errors, and not having the name of the wiki be an ipv6 address…you know the drill). This doesn't happen on the latest 1.42.0 running on Wikipedia, looks like it was fixed but it's worth seeing if it can be backported as 1.39 is labeled "LTS". https://phabricator.wikimedia.org/T350594
|
We'll upgrade to the next LTS release once it is out. It is expected maybe this month. |
If you attempt to open VisualEditor on any wiki page with an embedded video, VisualEditor fails to load, reporting an internal server error.
To reproduce, attempt to visually edit this revision of the “Key:wikidata” page. The following error appears:
This error comes from a JSON payload returned in a request for a parsed version of the page. The page contains this WebM video hosted on Wikimedia Commons (introduced here).
A similar error does not occur when visually editing a page that embeds a Commons video on another wiki, such as Wikipedia. This raises the possibility of a configuration issue in the OSM Wiki. Ultimately this could be an upstream issue, but someone with server access might need to pull a log for more details.
This issue was originally reported on Slack.
The text was updated successfully, but these errors were encountered: