On Thu, Mar 15, 2018 at 10:22 PM, <support(a)comprofix.com> wrote:
Hi Guys,
We have been running Private MediaWiki with VisualEditor and using Parsoid
provided by a Heroku instance for some time and this has worked with out an
issue.
We recently needed to move our Wiki to a new host and change the hosting
URL (this part may be important).
So I updated my $wgServer & $wgScriptPath with the new domain and path. I
then spun up a new Heroku Instance for this new url. I also updated the
$wgVirtualRestConfig url for the new Heroku App.
Now when testing and attempting to edit a page checking the log on Heroku
I receive the following error: "Your wiki requires a logged-in account to
access the API."
If I make the wiki public readable the editor,
change $wgGroupPermissions['*']['read'] = false;
to $wgGroupPermissions['*']['read'] = true; the editor works fine.
The only thing that has changed as mentioned is we have moved to a new
host and we moved from a subdomain to a folder.
So we have gone from
wiki.example.net to
www.example.net/wiki.
Any help you can give would be appreciated.
Thanks.
Matthew
Hi Matthew,
Check here
https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_…
There are a few different permutations depending on your exact setup.
You should probably use this snippet if not already using it:
if ( !isset( $_SERVER['REMOTE_ADDR'] ) OR $_SERVER['REMOTE_ADDR'] ==
'127.0.0.1' ) {
$wgGroupPermissions['*']['read'] = true;
$wgGroupPermissions['*']['edit'] = true;}
By the way, I'm interested in hearing about your Heroku experience since a
potential client is comparing platforms. If you have time for a 5 minute
chat, please give me a call. (Boston - 978-225-0471)
Thanks,
Greg Rundlett
https://eQuality-Tech.com <https://equality-tech.com/>
https://freephile.org