Happens on other wikis too, including sv and pl.

• Bug 56584 has been marked as a duplicate of this bug. ***

(gwicke restored working version of the code. Awaiting a post-mortem :) )

This is fixed now that the Parsoid update has been reverted.

Post mortem has been posted at https://wikitech.wikimedia.org/wiki/Incident_documentation/20131104-Parsoid

Relabelling and moving to the correct component.

Not that it matters, but there is no Apache involved here. Moved it to General.

Wikifram wrote:

Why "Wikimedia"? It only happened to VE edits, so for the sake of being able to track bugs in VE editing (fixed and non-fixed, major and minor), I have moved this back to VisualEditor. Wikimedia is much too vague for this...

Reverting. This was a bug with config, not with code, and so belongs in "Wikimedia". Also, it was a bug with Parsoid, not with VisualEditor.

Wikifram wrote:

(In reply to comment #9)

Reverting. This was a bug with config, not with code, and so belongs in
"Wikimedia". Also, it was a bug with Parsoid, not with VisualEditor.

This means that people looking for VE bugs won't find it though; this may make sense from a devs point of view, but not from an editor's point of view. They encountered severe problems when editing with VE (and not with wikitext editing), but can't find that bug when searching VisualEditor bugs.

Take a look at the "search" box for Bugzilla; first is status, second is product; how many people trying to find info on this or similar bugs will look for "Wikimedia"?

Bugzilla is primarily a tool for developers and its primary classification is based on codebases (products and components).

Let's just add "VisualEditor" to the summary to make this easier to find.

Wikifram wrote:

Thank, Bartosz