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
On Thu, Mar 15, 2018 at 10:22 PM, support@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_i...
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
On 2018-03-16 13:47, Greg Rundlett (freephile) wrote:
On Thu, Mar 15, 2018 at 10:22 PM, support@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_i...
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 _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Hi Greg,
I have actually already tried adding the REMOTE_ADDR snippet. I have used both 127.0.0.1 and the IP Address of the remote server (I ping the app address to get the IP). But still getting the same result.
I am from Australia so giving you a call might be difficult lol
Happy to chat over email.
Thanks Matthew
Hi Greg,
I have actually already tried adding the REMOTE_ADDR snippet. I have used both 127.0.0.1 and the IP Address of the remote server (I ping the app address to get the IP). But still getting the same result.
So, where is Parsoid running in relation to the new wiki server? Is
Parsoid on 'localhost'? Is it running on the original server?
I am from Australia so giving you a call might be difficult lol
Happy to chat over email.
Thanks, I'll follow up.
On 2018-03-16 14:03, Greg Rundlett (freephile) wrote:
Hi Greg,
I have actually already tried adding the REMOTE_ADDR snippet. I have used both 127.0.0.1 and the IP Address of the remote server (I ping the app address to get the IP). But still getting the same result.
So, where is Parsoid running in relation to the new wiki server? Is Parsoid on 'localhost'? Is it running on the original server?
Parsoid is running via a heroku nodejs app instance. Cannot run Parsoid local as the wiki is running on a shared hosting environment.
I am from Australia so giving you a call might be difficult lol
Happy to chat over email.
Thanks, I'll follow up.
Thanks Matthew
Did you update the parsoid config? It will need to know where to find the wiki.
On Fri, 16 Mar 2018, 04:41 , support@comprofix.com wrote:
On 2018-03-16 14:03, Greg Rundlett (freephile) wrote:
Hi Greg,
I have actually already tried adding the REMOTE_ADDR snippet. I have
used both 127.0.0.1 and the IP Address of the remote server (I ping the app address to get the IP). But still getting the same result.
So, where is Parsoid running in relation to the new wiki server? Is
Parsoid on 'localhost'? Is it running on the original server?
Parsoid is running via a heroku nodejs app instance. Cannot run Parsoid local as the wiki is running on a shared hosting environment.
I am from Australia so giving you a call might be difficult lol
Happy to chat over email.
Thanks, I'll follow up.
Thanks Matthew _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l@lists.wikimedia.org