Parsoid: When Parsoid is used (e.g. for VisualEditor), MediaWiki has a dependency on a non-PHP service to work
OpenPublic

Description

The VisualEditor extension currently requires a Parsoid instance to handle wikitext (cf. $wgVisualEditorParsoidURL in VisualEditor.php). This makes installing and using the extension very difficult (or impossible) for third-party users wishing to use the extension with their MediaWiki installations.

Ideally, calling out to an external Parsoid instance should not be necessary.


Version: unspecified
Severity: normal

bzimport added a project: Parsoid.Via ConduitNov 22 2014, 12:48 AM
bzimport set Reference to bz38484.
MZMcBride created this task.Via LegacyJul 19 2012, 4:40 AM
Jdforrester-WMF added a comment.Via ConduitJul 19 2012, 5:37 PM

Re-wording to be specific. I know Gabriel (and Tim Starling) are already looking at solutions to this issue.

GWicke added a comment.Via ConduitJul 19 2012, 6:18 PM

Our plan is to port Parsoid to a C library and interface it to PHP as an extension and (for shared hosting) as a near-static binary following Tim's strategy for Lua. We have some issues to address in the JS implementation before we embark on that, so don't expect that to happen before October.

We could later also port Parsoid to pure PHP, but PHP's less-than-stellar performance for memory-heavy workloads would make this only useful for very small wikis. See http://shootout.alioth.debian.org/u32/performance.php?test=binarytrees for a fun memory-heavy benchmark.

Jdforrester-WMF added a comment.Via ConduitAug 6 2012, 7:25 PM

Mass-moving bugs into the new 'Parsoid' product.

GWicke added a comment.Via ConduitJan 28 2013, 10:25 PM

See https://www.mediawiki.org/wiki/Parsoid/Roadmap for our latest plans on this. Our plan is to support HTML-only wikis with VisualEditor without any dependency on Parsoid.

Add Comment