Talk:Parsoid/Releases

See https://www.mediawiki.org/wiki/Topic:X0u0la9g27gx5uzg

I'm trying to understand the real error behing this vague message: https://stackoverflow.com/questions/73238686/mediawiki-trying-to-investigate-visualeditor-error-contacting-the-parsoid-rest

Which part of the round trip doesn't work?

It looks like starting in v0.15, an argument to pushList went from a stdClass to a DataParsoid object,

https://github.com/wikimedia/parsoid/commit/a078badac2379b1dcc7174454c9a2094eab6193b

Did you upgrade from v0.14 and not restart php after? It seems like something is cached and needs busting

This release is breaking (switching between visual and source editing) for versions of MediaWiki 1.31.x, possibly also 1.32.x and lower.

@SSastry (WMF): I have no idea what the minimum requirement for MediaWiki/VisualEditor is with this release. Is it safe to use it with MW 1.31 LTS?

I am pretty sure now that this is breaking for MW 1.31 LTS. It would have been nice to know this in advance. Probably the HTML 2.1 version was meant to convey just this info.

I added a note about the incompatibility. I guess this is ok.

Thanks for catching this and flagging it on the page. We didn't test this with older versions (MW 1.31) but in retrospect, should have, and flagged this. Anyway, this is the last release and going forward, this version issue will not ever arise since the appropriate Parsoid version will be bundled with the MW release.

Just to double-check -- switching between source and visual editing was always somewhat broken if you weren't using RESTBase to support stashing. Are you sure this is a new regression and not just a configuration issue?

In my cases RESTBase is not involved. The issue already appears if you want to discard changes done in visual editing. Usually on gets asked to confirm that the changes are lost if you switch to source editing. With 0.11.0 you do not even get that far. An error 406 is issued for the api on MW 1.31. On 1.33 everything continues to work as expected. Both wikis are configured identically and use the same parsoid service. After downgrading to 0.10.0 MW 1.31 works again.