$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;
$PARSOID_INSTALL_DIR = 'vendor/wikimedia/parsoid'; # bundled copy#$PARSOID_INSTALL_DIR = '/my/path/to/git/checkout/of/Parsoid';
// For developers: ensure Parsoid is executed from $PARSOID_INSTALL_DIR,// (not the version included in mediawiki-core by default)// Must occur *before* wfLoadExtension()if ( $PARSOID_INSTALL_DIR !== 'vendor/wikimedia/parsoid' ) {AutoLoader::$psr4Namespaces += [// Keep this in sync with the "autoload" clause in// $PARSOID_INSTALL_DIR/composer.json'Wikimedia\\Parsoid\\' => "$PARSOID_INSTALL_DIR/src",];}
wfLoadExtension( 'Parsoid', "$PARSOID_INSTALL_DIR/extension.json" );
# Manually configure Parsoid$wgVisualEditorParsoidAutoConfig = false;$wgParsoidSettings = ['useSelser' => true,'rtTestMode' => false,'linting' => false,];$wgVirtualRestConfig['modules']['parsoid'] = [];
Yours truly,
For private instances, it won't work out of the box. You need to manually configure your LocalSettings.php.
See https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis
-Subbu.
Thanks for the reply.
I had purchased the domain/hosting purely to test MW before I do a demo for a company to install a private instance.
Hence, the setup is as basic as it could be. Nothing has been modified beyond the defaults.
Yours truly,
From: MediaWiki-l <mediawiki-l-bounces@lists.wikimedia.org> on behalf of Bartosz Dziewoński <matma.rex@gmail.com>
Sent: 14 October 2020 18:14
To: mediawiki-l@lists.wikimedia.org <mediawiki-l@lists.wikimedia.org>
Subject: Re: [MediaWiki-l] Issue with VisualEditor on MediaWiki 1.35On 2020-10-14 13:56, Rehman Abubakr wrote:
>
> A number of users have complained about VisualEditor not working
> out-of-the-box for MW 1.35.0 (even on fresh install). [1][2][3]
>
> Is this a known issue (i.e. actually a bug)? And has a solution been
> shared yet?
>
> Sorry if this is the wrong place. It just seems (to me) like it is not
> accepted as an actual bug yet, despite a number of feedbacks. Feel free
> to reply to the onsite pages.
My impression has been that if you have the simplest possible setup,
then everything does work out-of-the-box.
But if you have configured any of many reasonable things (e.g. you have
some hardened security settings, or you're running multiple wikis, or
you have a caching proxy in front of your site), then you might also
need to configure VisualEditor with that in mind.
Unfortunately our documentation for configuring VisualEditor is lacking.
You could probably consider that a bug, even if most of the issues being
reported don't actually require any code changes on our side to fix.
--
Bartosz Dziewoński
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
_______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l