Extension talk:VisualEditor/2015

Please note that the Wikimedia Foundation does not provide support for installing VisualEditor on third party wikis. However, if you have a question we may try to help.

Node.js vs io.js

This post by Jdforrester (WMF) was moved on 2015-01-22. You can find it at Extension talk:Parsoid#c-Temptuousinsolence-2015-01-14T09:07:00.000Z-Node.js_vs_io.js. Jdforrester (WMF) (talk) 17:59, 22 January 2015 (UTC)

How i install Visual Editor extension?

Hi.

I want to install Visual Editor extension, but i can't. Because i guess Visual Editor extension require Parsoid. How i install Visual Editor excatly? Please help.

Thank you. 78.166.94.88 16:40, 24 January 2015 (UTC)

VisualEditor can't work without Parsoid, all other installation steps are identical like other Extensions, and documented here: Extension:VisualEditor. Which specific step is failing? :) Florianschmidtwelzow (talk) 18:38, 24 January 2015 (UTC)

Make sure you go into the Preferences and select the editing tab. From the editing tab, check the option that says "Enable enhanced editing toolbar" Jregan2015 (talk) 21:54, 24 January 2015 (UTC)

I should install it http://www.mediawiki.org/wiki/Extension:Parsoid and after VE? 83.27.43.89 13:45, 8 February 2015 (UTC)

No, this extension isn't needed to run VisualEditor, it's optional. You need the Parsoid Service, which you need to host on a Linux system, but you should really read the complete installation instructions on the extension page of VisualEditor and the links to the requirements :) Florianschmidtwelzow (talk) 22:38, 8 February 2015 (UTC)

Not working on MW 1.25alpha (51ca723)

I just created a VM with an Ubuntu 14.04.1 LTS on an AMD64 to install MW 1.25alpha (51ca723). Parsoid extension is version 0.2.0 (f2bb6c9) and VisualEditor extension si version 0.1.0 (fd6a2c0). Parsion service is working on port 8142 and although I setup MW extensions (I believe in the right way) VisualEditor is not working. When click on the edit link it stays loading for ever. Eventually I got a popup error message which is none of the erros messages shown on the troubleshooting section. Firebug says 500 internal server error on the api.php call. Any ideas what's going on?

Thank you.

robert Robertgarrigos (talk) 00:39, 27 January 2015 (UTC)

Fixed: needed the php5-curl library oops. (there is nothing like getting some sleep...) Robertgarrigos (talk) 09:02, 27 January 2015 (UTC)

Error: Unknown dependency: schema.Edit

I'm using MW 1.25alpha (51ca723) and VisualEditor. I manage to get it work but it does something stupid: it only works when I reload the page but not when clicking on the "edit" link. This is: whenever I click on the edit link, the VisualEditor tries to load itself but nothing happens, other than adding "?veaction=edit" to the url in the url field of the browser. Then I click the reload button of the browser, so it goes to the url with "?veaction=edit" at the end and only then VisualEditor loads it self.

Firebug shows an error:

"Error: Unknown dependency: schema.Edit
Error: Unknown dependency: schema.Edit"

Yes, it shows it twice:

https://www.evernote.com/shard/s4/sh/2e0c8b84-2122-4037-8508-0fd91f5e2660/7c0473d1fca8eab2009854a9ea62f63e

Then, when I reload, as I said, VisualEditor works fine, even Firebug shows the same error, but now only once:

https://www.evernote.com/shard/s4/sh/762d2896-6e67-4f05-82e5-42e78772b6a7/ac868f21b6b903e6bc173be4507fb6fd

Any idea of what's going on??

Thanks.

Robert Robertgarrigos (talk) 13:21, 1 February 2015 (UTC)

Do you by any chance have the EventLogging extension installed, but not the WikimediaEvents extension? Catrope (talk) 22:00, 2 February 2015 (UTC)

Thanks! That was the problem. it works, now. :-) Robertgarrigos (talk) 14:50, 4 February 2015 (UTC)

no templates edition

After having fixed last error (Error: Unknown dependency: schema.Edit), now it's the template edition which doesn't work, and it did before. This is the error I'm having:

Uncaught TypeError: Cannot read property 'layout' of undefined

Any ideas?

thanks.

Robert Robertgarrigos (talk) 15:30, 4 February 2015 (UTC)

It looks like phab:T88471 (a bug in the UI library used by VisualEditor), but Jdforrester (WMF) should have a more accurate answer. Ricordisamoa 02:36, 5 February 2015 (UTC)

Yes, this is now fixed in development, but not yet deployed. Jdforrester (WMF) (talk) 16:44, 5 February 2015 (UTC)

No edit link anymore, just edit wiki text

Hi, i installed and activated VisualEditor (shown in special page Version). Parsoid is running. I have only "modify wikitext" button, but no "modify" one..

I don't understand what's going on..

Sorry for my poor english.

Thanks for your help. 82.250.227.128 23:31, 5 February 2015 (UTC)

Same thing happened on my installation after I added some custom namespaces.

Then I found that custom namespaces (an maybe other configuration directives in LocalSettings.php) should be declared AFTER VisualEditor inclusion.

You should try to remove/move configuration elements until the Edit button is shown... 37.1.253.18 16:07, 4 March 2015 (UTC)

doesn't work with erudite skin

Hello,

I'm unable to make it work with erudite skin. I have this js error :

"TypeError: $container[0] is undefined" TypeError: $container[0] is undefined

Works great with Vector and Monobook.

Any idea ?

Thanks 82.254.44.152 23:15, 6 February 2015 (UTC)

Digital Ocean Droplet: Ubuntu 14.04 x64 with MediaWiki 1.24.0

I thought I'd put this here, because the instructions were not extremely clear in my case. Though they were thorough enough to troubleshoot.

Install Visual Editor

Note the -b REL1_24

cd extensions
git clone -b REL1_24 https://github.com/wikimedia/mediawiki-extensions-VisualEditor.git
cd VisualEditor ***CHANGE THE NAME OF THE FOLDER***
git submodule update —init

Modify LocalSettings.php

require_once "$IP/extensions/VisualEditor/VisualEditor.php";
$wgDefaultUserOptions['visualeditor-enable'] = 1;
$wgHiddenPrefs[] = 'visualeditor-enable';
$wgVisualEditorParsoidURL = 'http://localhost:8142';
$wgVisualEditorParsoidPrefix = 'localhost';

Check that VisualEditor is not throwing the error Fatal exception of type MWException

Install Parsoid

gpg --keyserver keys.gnupg.net --recv-keys 5C927F7C
gpg -a --export 5C927F7C | sudo apt-key add -

Open /etc/apt/sources.list and add the follow at the end:

deb [arch=amd64] http://parsoid.wmflabs.org:8080/deb wmf-production main

Run:

sudo apt-get update && sudo apt-get install parsoid

Modify /usr/lib/parsoid/src/api/localsettings.js

// parsoidConfig.setInterwiki( 'localhost', 'http://localhost/wiki/api.php', 'http://localhost/' );
parsoidConfig.setInterwiki( 'localhost', 'http://yoursite.com/api.php' );

Modify /etc/mediawiki/parsoid/settings.js

// parsoidConfig.setInterwiki( 'localhost', 'http://localhost/w/api.php' );
parsoidConfig.setInterwiki( 'localhost', 'http://localhost/api.php' );

DrLulzMD (talk) 02:07, 8 February 2015 (UTC)

I can confirm that installing this on Ubuntu 14LTS and MW 1.24 is possible. I also confirm that Apache localhost URLs don't work out of the box and that using the wikis (virtual) hostname is the solution. Finally make sure that the Apache virtual host config file is correct. Since I was moving the wiki to a new machine, I had <VirtualHost wrong.name.here> and that was enough to make the edit button insensitive to any clicking :(

If you like to read longer text, my full installation notes are here Daniel K. Schneider (talk) 21:04, 29 April 2015 (UTC)

Selecting 'Edit' button produces no observable result.

I am running with MediaWiki 1.25. The Parsoid service is active, and I can demonstrate that it can parse a page at $url/$prefix/$pagename. When I attempt to invoke "Edit," the result is indistinguishable from just viewing a page -- in fact, when I select "Edit Source," then "Edit," I am returned to an uneditable page that shows no apparent difference from simply viewing the page. The generated URL contains "&veaction=edit," so it is trying to invoke Visual Editor. These events do register in the HTTPD access_log, but the error_log is silent.

VisualEditor does in fact appear in Special:Version.

Is it possible that I have made a simple error in configuration? These are pertinent entries (IP address fictionalized to 99.99.99.99):

o LocalSettings.php:
require_once "$IP/extensions/VisualEditor/VisualEditor.php";
$wgVisualEditorParsoidURL = 'http://99.99.99.99:8000';
$wgDefaultUserOptions['visualeditor-enable'] = 1;
$wgHiddenPrefs[] = 'visualeditor-enable';
$wgVisualEditorParsoidPrefix = 'localhost';

o parsoid/api/localsettings.js:
parsoidConfig.setInterwiki( 'localhost', 'http://99.99.99.99/mediawiki/api.php' );

I appreciate any insights that would help me to move further along toward resolution. Thank you! Pickle-san (talk) 20:18, 13 February 2015 (UTC)

I had exactly the same problem and the cause was that I forgot to run git submodule update --init as mentioned in the installation instructions. LFS (talk) 23:31, 15 February 2015 (UTC)

Thank you! I just re-confirmed that I had followed this step of the instructions, and I have even repeated the step several times throughout my investigations. Unfortunately, the situation remains unchanged.

I do think it is fascinating that the same behavior occurs when the git command is omitted. What is it about running the git command that fixes the problem -- what does it actually change? I wonder whether I might have the same underlying issue but have arrived at it in a different way. Pickle-san (talk) 19:24, 17 February 2015 (UTC)

The command downloads the actual VisualEditor, which is stored in a subfolder of the VisualEditor folder. LFS (talk) 14:14, 18 February 2015 (UTC)

Using VisualEditor on shared hosting

As you will know, Parsoid can't be installed on shared hosting, which is something that made MediaWiki great.

Is there any option to install the VisualEditor on a shared hosting, thus, without Parsoid, at least installing Parsoid on my own server?

Thanks! A2323545 (talk) 11:07, 17 February 2015 (UTC)

What a great question, and one I am trying to figure out now, I have asked this same question and have not received and answer. I am currently scouring the internet now to see if I can catch any glimpse of anyone successfully setting up the Visual Editor on shared hosting. John Morris (talk) 15:49, 13 March 2015 (UTC)

It's highly unlikely you'd be successful getting VisualEditor to work on shared hosting. The biggest reason isn't VE itself, but the parsoid service that's needed to parse the wikitext/HTML.

Parsoid requires that you have node.js running in the background at all times. Most shared-hosting companies (HostGator, Bluehost, Dreamhost, etc.) don't allow you to do that. You are better served, for performance and security reasons, to use a dedicated hosting solution such as a VPS. Ckoerner (talk) 15:41, 16 March 2015 (UTC)

@Ckoerner thanks that's useful to see explicitly stated. I've copied your reply into extension VE's installation instructions. Rob Kam (talk) 19:41, 16 March 2015 (UTC)

Thank you completely Ckoerner for the final answer. It's been a bone of contention of me as I set up our wiki. VPS is something I have been checking into, is seems like it is the proper way to set up a successful wiki, and more secure as you stated. Thanks again! John Morris (talk) 22:29, 16 March 2015 (UTC)

There is no need for parsoid to run on the same server, and therefor you can install it on another available cloud platform which supports node.js, such as Heroko, and you can even so it for free if your needs are not of a wide scale. Actually this is what I am doing, and by deploying one instance of parsoid on Heroku I can support VE on many small wikis. Wess (talk) 12:44, 20 March 2015 (UTC)

BTW Node.js page at Heroku. Thanks, this is interesting!

@SSastry (WMF): It would be nice to have a walk through for implementing it this way, and to have some idea of the security risks please. Rob Kam (talk) 17:17, 20 March 2015 (UTC)

@Wess: Please could you update the extension document page to explain how to do this? Rob Kam (talk) 18:25, 25 March 2015 (UTC)

Wess, I have checked into Heroko, and it seems Apache is not supported for the node.js app. Have you found this to be the case, or did you find a way around this?

Thanks Wess John Morris (talk) 20:03, 25 March 2015 (UTC)

While exploring different web hosting companies I am discovering that some do offer node.js installers for their shared hosting plans, I don't know if I am breaking protocol here by mentioning a hosting company, but A2 Hosting does provide node.js for their shared hosting clients, and they have an installer as well. I spoke with A2 customer service last night and they confirmed they do allow this to run on their shared hosting accounts. That may be good news for some to be able to keep a node.js service on the same account as their shared hosting. John Morris (talk) 20:05, 25 March 2015 (UTC)

I have started new page VisualEditor on a shared host. If you figure this out, please edit it to help explain in clear simple to follow steps. Rob Kam (talk) 21:21, 25 March 2015 (UTC)

I started the process last night Rob Kam, it's involved for me, at my skill level. But I am working through it, if I can implement this successfully I'll be glad to create detailed instructions with screen shots. John Morris (talk) 11:43, 26 March 2015 (UTC)

That'd be good work on your part. I've not got the spare time to get stuck in at the moment. Watch out, step 4 "using a custom Buildpack" could well be incorrect.

This lack of documentation makes hard work out of something that ought to be trivial for the average user. Spending time over seemingly arcane applications instead of working on wiki content. Rob Kam (talk) 18:23, 26 March 2015 (UTC)

Being as I have no wiki content yet, this is a good time for someone like me to get their elbows dirty. I did contact Heroku Support in regards to the (for me) confusing instructions on how to deploy the node.js (which I successfully did) but not much beyond that. And I also asked them about parsoid and this was their answer.

"In order to install a custom library like this, you need to create a custom buildpack.

Unfortunately, while we provide an open API, we can't provide support in the development of those.

From the setup instructions of parsoid, it looks like you can use an apt-get install to install that library.

There is an open-source APT buildpack that you can find here: https://github.com/ddollar/heroku-buildpack-apt

Using that buildpack might let you install parsoid on your machine here."

So into the world we go! John Morris (talk) 19:41, 26 March 2015 (UTC)

Thanks, I've altered step 4. Good luck :-) Rob Kam (talk) 20:03, 26 March 2015 (UTC)

I'd like to get some feedback from Wess as well, since he has actually completed the process. Thanks all so far for jumping in. John Morris (talk) 23:17, 26 March 2015 (UTC)

I edited the Page VisualEditor on a shared host according to the steps I made to get it working. I hope I didn't miss a step, but I'm no pro at all. I'm glad I got it working and it took me forever to figure out all of the problems ;) Noboddy (talk) 12:20, 27 March 2015 (UTC)

Hi.

The manual is correct (I've deleted the last line which is not necessary). I also added a link to Heroku's getting started manual which is quite simple.

Some of the content in the new manual was not necessary for my deployment (7.3-10). Wess (talk) 12:38, 27 March 2015 (UTC)

Thank you Wess and Noboddy, this is great. You've saved anyone else trying to figure this out from scratch, (and maybe without the know-how) a lot of hassle. Rob Kam (talk) 15:17, 27 March 2015 (UTC)

Cheesycow5 (talk) 00:23, 28 August 2022 (UTC)

Hello Rob,

In the page "VisualEditor on a shared host", there is a step that I couldn't understand that says:

15. Now copy your files from the parsoid folder in folder 1 to folder2. Note that you have to copy the files inside the parsoid folder into folder2 and not the parsoid folder itself.

Can you please clarify what does this exactly mean? 37.186.34.188 (talk) 11:18, 19 January 2017 (UTC)

Progress bar keeps on forever when "Edit"

Hi! I have migrated my wiki from a shared hosting to VPS in order to enable VisualEditor (this is the future of the wikis!) but I am not able to make it work.

Firstly, I have installed Parsoid, and I think it is working, as I can see http://example.com:8000 and I can render a page from http://example.com:8000/localhost/PageName.

Secondly, I have installed VisualEditor for MediaWiki 1.24, as I have upgraded to MediaWiki 1.24.1, and I have configured it to connect to http://example.com:8000 and "localhost".

I think that the setup is right because when I click on "edit", from the shell, I see that the rendering starts and finishes. However, the only thing I see is the progress bar indicating that the VisualEditor interface is loading and it doesn't change.

From what I see, I think that Parsoid is properly installed but I don't know if the problem is with the VisualEditor extension or some other extension/configuration/whatever is preventing the VisualEditor interface from loading. I have tried to disable all other extensions and the situation is the same. With a previous installation (MediaWiki 1.23.6 and the VisualEditor for 1.23 with Parsoid extension was the same).

Please, I do really want to make this work

Thanks! A2323545 (talk) 10:29, 24 February 2015 (UTC)

Cannot edit existing or create new

MediaWiki 1.23.8
PHP 5.6.5 (cgi-fcgi)
MySQL 5.6.22-log
VisualEditor 0.1.0
Parsoid 0.2.0
I am having an inexplicable issue with VisualEditor in my WIMP environment. Everything seemed to be going fine up until this I try to actually edit a page. I keep getting MWHttpRequest errors when trying to edit existing pages, and when I try to create new pages I get the Save Page dialog open but when I go to save the page, I get an unknown error 209.252.234.128 21:05, 26 February 2015 (UTC)

Check out whether server.js is running or not. 198.45.23.25 06:57, 23 April 2015 (UTC)

VE and inline queries

We have an issue with the VE and inline queries. Once the VE is activated for an edit, the properties assigned to the query do not work any more and the result of the query on the pager differs from what had been shown originally. Furthermore, some of the queries break altogether and present merely some Wikitext and not a query.

• MediaWiki 1.24.1 (1eb9951)17:04, 18. Feb. 2015
• PHP 5.4.36-0+deb7u3 (apache2handler)
• VisualEditor 0.1.0 (af11aa1) 22:25, 11. Okt. 2014 Temptuousinsolence (talk) 09:11, 11 March 2015 (UTC)

By 'inline queries' are you referring to Semantic MediaWiki's #ask or #show queries? Ckoerner (talk) 16:08, 13 March 2015 (UTC)

Yes he is. Most notably the SMW::off and -on tags are visible, partially also the source code of #ask queries. The CURRENTUSER magic word is rendered by some IP adress. Upon saving the page everything looks ok again. Hans Oleander (talk) 11:04, 16 March 2015 (UTC)

Ah, I thought so. In that case is this something that the VE team would work to solve or the SMW folks? Ckoerner (talk) 15:50, 16 March 2015 (UTC)

It sounds like SMW isn't using parser tags correctly (which is what is causing Parsoid not to treat them correctly); this is the same issue from which the Translate extension suffers. Fixing this is the responsibility of the extension author (but this is a serious piece of work, apparently). Jdforrester (WMF) (talk) 16:27, 16 March 2015 (UTC)

Is this by any chance an issue that is already known to the folks behind the SMW extension? Should it be brought to attention at the github entry? Temptuousinsolence (talk) 16:38, 16 March 2015 (UTC)

I did a quick search over on GitHub and didn't see anything. I'd encourage you to submit an issue. Even if they are aware we should be tracking it! Ckoerner (talk) 17:21, 20 March 2015 (UTC)

ничего не происходит

установил VisualEditor появились кнопки править, и править как вики.при нажатии на править ничего не происходит. версия 1.23. 94.77.173.172 20:11, 14 March 2015 (UTC)

Nadhani itakuwa bora kwa kuacha ujumbe katika lugha ya Kiingereza. [[kgh]] (talk) 22:47, 15 March 2015 (UTC)

cannot creat new pages because of JS error

I am using VE successfully in the last months (on MW 1.25alpha), however - after updating MW and VE, VE cannot create new pages, because of this JS error:

Exception in load-callback in module ext.visualEditor.mwreference:
load.php:175 TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.

Wess (talk) 12:59, 20 March 2015 (UTC)

This error seems to be a skin related problem (using skin:foreground with the necessary VE requirements). Any ideas in helping debugging this error will be very useful. Wess (talk) 23:01, 21 March 2015 (UTC)

Not able to see the Edit button, only the Edit Source button

I am using MW 1.24 and have the appropriate stable VE installed for that version, and I am able to parse pages using parsoid's local host function. What could be causing this? I am preparing the wiki for launch on a virtual machine on my home network. Does that matter? What determines whether or not the edit link is displayed? Thanks in advance! Studentwikicorey (talk) 05:18, 22 March 2015 (UTC)

Duplicate of Visual Editor not displaying 'Edit' links (displays 'Edit Source' link fine). Ricordisamoa 05:20, 23 March 2015 (UTC)

Solved - VE only works with certain skins. BootstrapSkin is not its friend. Studentwikicorey (talk) 00:51, 25 March 2015 (UTC)

It is not very difficult to adapt a skin to work with VE: VisualEditor/Skin requirements Wess (talk) 22:20, 28 March 2015 (UTC)

new VisualEditor Version not working proberly

hey there,

i tried to setup the new visual editor to use the column feature. To get it working i updated the media wiki to version 1.25wmf22 , php 5.4.4-14+deb7u14 (apache2handler), mysql 5.5.38-0+wheezy1 . Then i deleted the VisualEdior directory under /var/www/extensions/ and did the following :

root@wiki:/var/www/extensions# git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git Cloning into 'VisualEditor'... remote: Counting objects: 1414, done remote: Finding sources: 100% (611/611) remote: Getting sizes: 100% (311/311) remote: Compressing objects: 100% (2169515/2169515) Receiving objects: 100% (79071/79071), 30.22 MiB | 392 KiB/s, done. remote: Total 79071 (delta 231), reused 78816 (delta 216) Resolving deltas: 100% (53291/53291), done. [11:02][root@wiki:/var/www/extensions]# cd VisualEditor/ [11:03][root@wiki:/var/www/extensions/VisualEditor]# ös -bash: $'\303\266s': Kommando nicht gefunden. [11:03][root@wiki:/var/www/extensions/VisualEditor]# ls ApiVisualEditorEdit.php betafeatures-icon-VisualEditor-ltr.svg build extension.json Gruntfile.js LICENSE.txt README.md VisualEditor.php ApiVisualEditor.php betafeatures-icon-VisualEditor-rtl.svg composer.json Gemfile jsduck.json modules VisualEditorDataModule.php VisualEditorViewPageTargetInitModule.php AUTHORS.txt bin CONTRIBUTING.md Gemfile.lock lib package.json VisualEditor.hooks.php [11:03][root@wiki:/var/www/extensions/VisualEditor]# git submodule update --init Submodule 'lib/ve' (https://gerrit.wikimedia.org/r/p/VisualEditor/VisualEditor.git) registered for path 'lib/ve' Cloning into 'lib/ve'... remote: Counting objects: 2433, done remote: Finding sources: 100% (991/991) remote: Getting sizes: 100% (475/475) remote: Compressing objects: 100% (4302517/4302517) remote: Total 74950 (delta 492), reused 74557 (delta 400) Receiving objects: 100% (74950/74950), 29.57 MiB | 266 KiB/s, done. Resolving deltas: 100% (51875/51875), done. Submodule path 'lib/ve': checked out '731b3ad852d3e6cf55d0a2f0f054478b03519f55'

Then i restarted the Server and checked if everything was working as expected. Currently i can see the "EDIT" Tab and i can click on it. As i do so i am getting a loading screen and shortly after that an http error 500. The page gets greyed out, and i can not do anything until i click on another website. Funny thing is, that the Visual Editor Tab itself folds out , so i can see the typical VisualEditor tab, but its inaccessible 213.172.115.21 10:22, 26 March 2015 (UTC)

any ideas on this? 213.172.115.21 12:29, 27 March 2015 (UTC)

I needed to install php5-curl.

It took me days to figure out, then I posted it here, for people like you. Hope this does it for you!

VE also needs UniversalLanguageSelector (loaded before VE?), but that is at least documented. 195.243.184.114 11:43, 30 March 2015 (UTC)

Thanks, that really did fix the problem, But now i can not save pages, that were edited with visual editor. The save function via source code is working as expected. Any Ideas on this? 213.172.115.21 08:58, 31 March 2015 (UTC)

Update: I figured out that saving itself is working fine, but as soon as i got a filled table on the webpage , i am not able to save the page. Probably a bug right? 213.172.115.21 09:16, 31 March 2015 (UTC)

When upgrading from 1.24 to 1.25 I needed to install php5-curl

...and then restart the parsoid service. Documentation on dependencies of VisualEditor could be improved. In the worst case you end up with server error 500, which can be anything. 195.243.184.114 11:40, 30 March 2015 (UTC)

Session ends after some idle time and cant save

so it seems to happen that when i edit a page and idle in the editor while doing some research after a period of time (20-30mins) i cant save the proress anymore and it loggs me out... it seems to be a specific problem with the editor cuz i dont get timeout on the normal wiki - the token in the php ini file is also set to 0 so it shouldnt happen. anyone an idea? 178.201.150.120 14:20, 7 April 2015 (UTC)

media location

Where is media location for VE ? I have tried to use /images, extension/plugin/images, root dir, but VE does not found images 87.229.231.234 11:04, 10 April 2015 (UTC)

file ve.init.mv.platform.js has not line like "mediaSources" ... 87.229.231.234 12:06, 10 April 2015 (UTC)

Can't edit source tags

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I'm using the buildly nights for MediaWiki, VisualEditor and have GeSHi extension installed. The visual editor is working pretty well, but I am not able to edit source blocks. A message like "sorry, this can only be edited in source code mode" appears when the mouse is over the source block.

I have one more question. How can I insert a source block? 201.26.61.1 03:03, 24 April 2015 (UTC)

I found that:

$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

It enables the 'edit' button for 'source' tags.

But still I didn't find a way to insert a new source tag using VisualEditor. 200.205.195.3 11:35, 26 April 2015 (UTC)

Sorry, proper editing of <syntaxhighlight> is not yet created, but we're working on it. See https://phabricator.wikimedia.org/T45126 for progress. Jdforrester (WMF) (talk) 03:00, 10 June 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Hide cite-menu in main menu

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Is there a way to hide the cite-menu in the main toolbar with javascript? The only way to do this I have found so far is by hacking the visibility after the editor is loaded

Like this

//hide cite-menu in main-toolbar
  $( ".oo-ui-toolbar-tools" ).children().get(4).remove();

This is an ugly hack. I would rather be able to get a reference to the main bar, and then remove the cite-menu itself. Is there a way to do this? Antonbil (talk) 12:25, 28 April 2015 (UTC)

Hi there,

Sorry for this ugliness; you're right that this is the only way to do this right now. This is because the code for coping with the Cite extension is in VisualEditor-MediaWiki itself, rather than in the Cite extension – this is [1].

More generally, this is blocked on a ground-up re-write of OOjs UI's toolbar system to allow more flexible registration, de-registration and dynamic display; I've created [2] to track this. Jdforrester (WMF) (talk) 15:07, 10 June 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Parsoid Error - Failed to parse the JSON response

error: Failed to parse the JSON response for Config Request path: /kb/Main_page

 ParserError: Failed to parse the JSON response for Config Request
   at ApiRequest._handleBody (c:\xampp\apps\mediawiki\htdocs\extensions\parsoid\lib\mediawiki.ApiRequest.js:249:11)
   at ApiRequest._requestCB (c:\xampp\apps\mediawiki\htdocs\extensions\parsoid\lib\mediawiki.ApiRequest.js:214:8)
   at Request.self.callback (c:\xampp\apps\mediawiki\htdocs\extensions\parsoid\node_modules\request\request.js:123:22)
   at Request.emit (events.js:110:17)
   at Request.<anonymous> (c:\xampp\apps\mediawiki\htdocs\extensions\parsoid\node_modules\request\request.js:1047:14)
   at Request.emit (events.js:129:20)
   at IncomingMessage.<anonymous> (c:\xampp\apps\mediawiki\htdocs\extensions\parsoid\node_modules\request\request.js:998:12)
   at IncomingMessage.emit (events.js:129:20)
   at _stream_readable.js:908:16
   at process._tickCallback (node.js:355:11)

Here are the details:

http://www.mediawiki.org/w/index.php?title=Talk:Parsoid&redirect=no#Parsoid_working_but_getting_JSON_error 158.106.76.130 16:02, 20 May 2015 (UTC)

I got the same error after I installed the 'php.ini-development' config file provided with my PHP 5.6.29 install dir (renamed 'php.ini').

Before this, I was running without config (using the built-in defaults) and everything was working fine.

I binary searched the faulting key and found that the 'error_reporting' key under section '[PHP]' was causing the problem.

Commenting the key in 'php.ini' worked for me:

[PHP]

;error_reporting = E_ALL Guista (talk) 09

47, 23 December 2016 (UTC)

Media / Image searching problem with search

I can't find any media/images at all in the VE.

I can manually add a [ [file:thing.png] ] to source and it all works, but VE doesn't find the images while editing or while searching to add new images.

After a poke around I found in my http access log :

GET /api.php?format=json&uselang=en&action=query&generator=search&gsrsearch=sat.png&gsrnamespace=6&gsrlimit=20&gsroffset=0&prop=imageinfo&iiprop=dimensions%7Curl%7Cmediatype&iiurlheight=150

So, pasted that as the URL and get :

{"error":{"code":"gsrsearch-text-disabled","info":"text search is disabled"}}

We use Lucene search, so I'm guessing that has disabled the standard API search somehow. I added :

$wgDisableInternalSearch = false;

$wgDisableTextSearch = false;

To my LocalSettings but still no joy.

Am I going to be able to get Lucene and API searching working? Is there something else I need to add for API search(variables, includes, etc...)?

(I couldn't find any sensible references to variables to control it. Searching for "search" and "API" type phrases tend to give me either lots too many hits or nothing relevant at all.)

And if both search types are not compatible, does that mean VE and Lucene will never play together? Max.allan (talk) 11:02, 22 May 2015 (UTC)

OK, I removed all search/Lucene related lines from LocalSettings and then did a rebuildall.php and a rebuildimages.php and I can search for images successfully.

However, when editing a page, existing images still show as a broken link. If I add a new image to a page, it shows up fine, save page and edit again and it's a broken link... I can sort of live with that. Be nice if it could be fixed... Max.allan (talk) 11:50, 22 May 2015 (UTC)

I am having the exact same issue. VE only shows the images if I provide it will the name of the file. If anyone has some insight into why this is occurring it would be appreciated 108.13.218.111 04:19, 2 June 2015 (UTC)

Disregard, gif image do not show up in the Media Sector, but other file types do 108.13.218.111 09:18, 2 June 2015 (UTC)

128.71.125.211 22:22, 9 June 2015 (UTC)

Parsoid SSL error

I have a problem with parsoid running on an Ubuntu 14.04 LTS Apache 2.2 PHP 5.5.

When clicking "Edit" on a page, I get the error parsoidserver-http-cjurl-error: Unknown SSL protocl error in connection <FQDN>:8142

My configuration - It is an https only host, that means that I have configured my apache2.conf this way:

<Directory /var/www>

Options Indexes FollowSymLink

AllowOverride None

Require all granted

<IfModule mod_pam.c>

AuthPAM_Enabled on

AuthPAM_FallThrough off

</IfMOdule>

<IfModule mod_authnx_external.c>

AuthBasicProvider external

AuthExternal pwauth

</IfModule>

</Directory>

my ports.conf this way:

Listen 80

<IfModule ssl_module>

Listen 443 https

</IfModule>

and my sites-available/ssl.conf this way:

<VirtualHost _default_:443>

SSLEngine on

SSLCertificateFile /etc/ssl/certs/apache.crt

SSLCertificateKeyFile /etc/ssl/private/apache.key

SSLRequireSSL

<IfModule mod_authnz_external.c>

AddExternalAuth pwauth /usr/sbin/pwauth

SetExternalAuthMethod pwauth pipe

</IfModule>

DocumentRoot /var/www

</VirtualHost>

Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"

Here is the history of how I setup visualeditor:

So I setup mediawiki 1.24 stable in /var/www/mediawiki, I copied VisualEditor from here http://www.mediawiki.org/wiki/Special:ExtensionDistributor/VisualEditor and added my LocalSettings.php, at the bottom I added

require_once "$IP/extensions/UniversalLanguageSelector/UniversalLanguageSelector.php";

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

// Enable by default for everybody

$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Don't allow users to disable it

$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features

1. $wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

Then I setup parsoid. I added the rquired line to m sources.list and installed with apt-get install parsoid.

At /etc/mediawiki/parsoid/settings.js, i added

parsoidConfig.setInterwiki( 'localhost', 'https://<FQDN>:443/mediawiki/api.php' );

and at the bottom of LocalSettings.php, It doesnt matter if I try:

$wgVisualEditorParsoidURL = 'http://localhost:8142';''

or

$wgVisualEditorParsoidURL = 'http://<FQDN>:8142';

I even forwarded Port 8142 in my Router, still doesnt work.

I restarted parsoid via service parsoid restart.

The command lsof -i:8142 shows

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

nodejs 12273 parsoid 14u IPv4 71435 0t0 TCP *:8142 (LISTEN)

nodejs 12275 parsoid 11u IPv4 71435 0t0 TCP *:8142 (LISTEN)

nodejs 12276 parsoid 11u IPv4 71435 0t0 TCP *:8142 (LISTEN)

nodejs 12278 parsoid 11u IPv4 71435 0t0 TCP *:8142 (LISTEN)

nodejs 12279 parsoid 11u IPv4 71435 0t0 TCP *:8142 (LISTEN)

The command curl https://<FQDN>:443/mediawiki/api.php shows:

curl: (51) SSL: certificate subject name 'Ubuntu' does not match target host name '<FQDN>'

That's strange, because Ubuntu is the standard-hostname of the machine after installation, but I edited the hostname of the machine matching it's FQDN-Hostname-Part and set the FQDN as ServerName in apache2.conf. I approved that the hostname is changed via cat /etc/hostname and by pinging it. I even regenerated the apache.key/apache.crt pair to make sure that the FQDN is set at generation time of the certificate.

Any suggestions? Dafrk (talk) 12:26, 26 May 2015 (UTC)

I find that the problem might be that nodejs doesnt accept self signed certificates. I find that a rather problem because the wiki is for a small non-commercial community without a 2nd level domain behind it (server is running behind a DynDNS hostname), so we really cant afford an SSL certificate. I consider this a major deal because all the other services of our community are running SSL-protected and mediawiki would now force me to allow non-secure traffic just for using VisualEditor. Is there any way around this? Otherwise I would consider installing a Wiki Plugin for wordpress which then allows me to still use SSL-protection next to being able to use a visual WYSIWYG editor. Dafrk (talk) 13:39, 26 May 2015 (UTC)

Hi, I don't know anything about VisualEditor's SSL config, but you can get an SSL certificate for free at StartSSL. I use that service myself. To clarify: I'm *not* affiliated with them in any way. FFS ^Talk 12:32, 27 May 2015 (UTC)

I got parsoid working with SSL using Letsencrypt certificates and setting up a VHost in apache to redirect 8000 to the local 8142 port Tansaku (talk) 11:57, 5 May 2017 (UTC)

I still can't get this to work - I opened a ticket

https://phabricator.wikimedia.org/T178778 PlanetKrypton (talk) 18:14, 22 October 2017 (UTC)

Broken after upgrade to 1.25

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

UPDATE: Fixed by changing localhost to 127.0.0.1 in $wgVisualEditorParsoidURL to avoid conflict with IPv6.

I just upgraded my mediawiki install to 1.25, and I downloaded the 1.25 version of VisualEditor using the mediawiki.org Extension Distributor (here).

It starts to load fine; it loads the toolbar (greyed out) and the progress bar goes to the end, but is no longer talking to my Parsoid service (this is a Windows server, btw). I get a parsoid error:

Error loading data from server: 0: parsoidserver-http: HTTP 0. Would you like to retry?

This is not like other parsoid errors I have seen. I tried restarting parsoid and it didn't help. I can reach http://localhost:8000 where the parsoid runs and it works just fine there.

Any help would be greatly appreciated.

Edit: I should also mention that if I go to create a new page, the VisualEditor does work, and I can use it for tables and all that fancy new stuff. But it won't save or preview because that also requires Parsoid. So it is just that something has changed in the way it talks to the Parsoid server. The Parsoid server itself has not changed, though. Thanks. GnomeSkull (talk) 18:11, 26 May 2015 (UTC)

Having the same issue.

When I go to localhost:8000 I get the Parsoid page

localhost:8000/localhost/wiki/api.php gives me:

[fatal/request][localhost/wiki/api.php] Did not find page revisions for Wiki1_25/api.php

from my Parsoid service

Trying to edit the Main_Page gives me:

Error loading data from server: 0: parsoidserver-http: HTTP 0. Would you like to retry?

Trying to create a page gives a similar parsoidserver-http: HTTP 0 error 106.186.104.137 06:22, 28 May 2015 (UTC)

Same problem here.

Anyone got a solution? Lilis2nd (talk) 23:55, 31 May 2015 (UTC)

I had this issue on a fresh install of mediawiki 1.25, set up to be a private wiki. It was fixed by setting this variable in LocalSettings.php:

$wgSessionsInObjectCache = true;

Note I already had this enabled:

$wgVisualEditorParsoidForwardCookies = true; Reinventionadverse (talk) 20:01, 1 June 2015 (UTC)

arrgh..

Doesn't do the trick. Wonder what I'm missing. Lilis2nd (talk) 23:39, 1 June 2015 (UTC)

Did some digging and it seems the mediawiki install page hasn't been updated for version 1.25. The version of php required now looks to be 5.4

Compatibility#Software_required_to_run_MediaWiki 106.186.104.137 07:29, 4 June 2015 (UTC)

I'm running on PHP 5.5.9 so I don't think that's it.

Thanks anyway. :) LILIS (talk) 04:41, 5 June 2015 (UTC)

Mind posting your working parsoid localsettings.js and mediawiki LocalSettings.php so we can see if we're missing something else? 106.186.104.137 02:26, 2 June 2015 (UTC)

My LocalSettings.php settings:

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

$wgDefaultUserOptions['visualeditor-enable'] = 1; // Enable by default for everybody

$wgHiddenPrefs[] = 'visualeditor-enable'; // Don't allow users to disable it

$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1; // OPTIONAL: experimental features

$wgVisualEditorParsoidURL = 'http://localhost:8000'; // URL to Parsoid service (must not end in slash)

$wgVisualEditorParsoidPrefix = 'localhost';

$wgSessionsInObjectCache = true;

$wgVisualEditorParsoidForwardCookies = true;

Like I said, the Parsoid server was working in 1.24, so I just kept the same settings.

I wonder if something has changed with the API? GnomeSkull (talk) 13:42, 2 June 2015 (UTC)

I was asking Reinventionadverse for theirs ;)

But I was thinking something is different with the API as well. Or some other minor configuration. 106.186.104.137 08:41, 3 June 2015 (UTC)

Try removing the Port 8000 from the URL and run mw-config again, just to be sure. That worked for me Noboddy (talk) 08:57, 8 June 2015 (UTC)

Have same issue. Fix by remove curl_exec_multi from disable_functions in php.ini 128.71.125.211 22:40, 9 June 2015 (UTC)

Anyone got a solution for parsoidserver-http: HTTP 0 in mediawiki 1.25.1 ? Beginneruser (talk) 08:23, 11 June 2015 (UTC)

So has anyone figured this out yet? Still pretty lost. 98.235.236.5 (talk) 17:32, 11 June 2015 (UTC)

i have the same error with new installation of 1.25.1. The VE loading bar stopped when Edit is selected and the chrome says parsoidserver-http: HTTP 0. 199.64.6.150 (talk) 18:50, 23 June 2015 (UTC)

same problem 91.47.241.88 (talk) 22:25, 6 July 2015 (UTC)

If you are having trouble with this, try setting:

$wgVisualEditorParsoidURL = 'http://127.0.0.1:8000';

Ike Hecht 20:18, 13 July 2015 (UTC)

This worked for me!

Changed localhost to 127.0.0.1 in $wgVisualEditorParsoidURL (but don't change it in $wgVisualEditorParsoidPrefix). GnomeSkull (talk) 13:06, 15 July 2015 (UTC)

This don't work for me...

My LocalSettings.php settings:

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

$wgDefaultUserOptions['visualeditor-enable'] = 1;

$wgHiddenPrefs[] = 'visualeditor-enable';

$wgVisualEditorParsoidPrefix = 'localhost';

$wgVisualEditorParsoidURL = 'http://127.0.0.1:8142';

$wgSessionsInObjectCache = true;

$wgVisualEditorParsoidForwardCookies = true;

require_once "$IP/extensions/UniversalLanguageSelector/UniversalLanguageSelector.php"; 93.108.216.27 (talk) 18:29, 28 August 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Installing VisualEditor on MediaWiki 1.25.1 and 1.26.0 on Debian 7

This is an overview of what it took for me to get VisualEditor working with MediaWiki 1.25.1, I hope this helps other people that might be experiencing issues in the setup.

Requirements (This is what My System is currently using)

• MediaWiki 1.25.1
• VisualEditor REL1_25
• UniversalLanguageSelector REL1_25
• parsoid 2.2.0
• nodejs 0.10.38-1chl1
• php5-curl 5.4.39-0+deb7u

Installing/Update parsoid'

apt-get install parsoid
apt-get install nodejs
apt-get install php5-curl

Testing parsoid to make sure it works

cd /usr/lib/parsoid/src/tests
./runtests.sh

The test should run and complete, there will be warning and possibly errors for parsoid bugs. The full results can be viewed in the folder /usr/lib/parsoid/src/tests/results/all.txt

Update the following files with the correct parsoidConfig settings (I seems like you need both for it to work in a Debian Environment) Also you MUST restart the parsoid service every time you change either file for the changes to take effect.

/etc/mediawiki/parsoid/settings.js
/usr/lib/parsoid/src/api/localsettings.js

i.e. parsoidConfig.setInterwiki( 'mediawiki', 'http: //localhost/mediawiki/api.php'); <- Remove the space between http: //localhost

Installing MediaWiki 1.25.1 and VisualEditor

• MediaWiki 1.25.1 http://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.1.tar.gz - stable
• VisualEditor REL1_25 http://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_25-c1ed854.tar.gz - stable
• UniversalLanguageSelector REL1_25 http://extdist.wmflabs.org/dist/extensions/UniversalLanguageSelector-REL1_25-7661826.tar.gz - stable

Instructions on configuring the LocalSettings.php (More or less copy and paste)

• http://www.mediawiki.org/wiki/Extension:VisualEditor
• http://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector

Notes: Multiple MediaWiki Instances on Single Host I can confirm that I am able to run multiple MediaWiki instances on a single host and VisualEditor works fine. Parse the Link below for how I am doing it on my site.

http: //sharkysoft.com/wiki/how_to_configure_multiple_MediaWiki_instances_on_a_single_host

Slowness with parsoid Still have not quite figured this one out, but after stopping restarting apache and parsoid the parser times have stabilized for me. MKruer (talk) 19:08, 31 May 2015 (UTC)

Thank you. Jdforrester (WMF) (talk) 17:46, 10 June 2015 (UTC)

Thanks for the help this worked, I have been trying to get this running for a week now!! 5.35.186.135 (talk) 08:17, 7 August 2015 (UTC)

Update for the New Media Wiki 1.26.0

You should be able to do a upgrade "sudo apt-get update && sudo apt-get upgrade"

• MediaWiki 1.26.0
• VisualEditor REL1_26
• UniversalLanguageSelector REL1_26
• parsoid 0.4.1all (Parsoid/Setup)
• nodejs 0.10.41-1nodesource1~wheezy1
• php5-curl 5.4.45-0+deb7u2

After the upgrade you will need to update the two following files as the syntax has changes between versions.

/etc/mediawiki/parsoid/settings.js

/usr/lib/parsoid/src/api/localsettings.js < localsettings.js.example

You also need to update the LocalSettings.php as the VisualEditor syntax has also changed.

Finally It appears that the Multiple MediaWiki Instances on Single Host is no longer working. The Parsoid only seems to recognize the last site setting from the /usr/lib/parsoid/src/api/localsettings.js

What I mean by this is that if you have two or more sites defined in Parsoid, VisualEditor will only work on the last site defined. If you try to user VisualEditor on the First Sites pages, the editor will load correctly but the Parsoid instance used is for the second site (last site defined) This cause the entire editor to render a new page. The Parsoid Log also show this same behavior. MKruer (talk) 08:04, 7 December 2015 (UTC)

Hi, i am trying to install MediaWiki on a mac on XAMPP.

I have tried to do it with the latest version as well as with version 1.25.

I am always getting the error message:

"Uncaught exception 'Exception' with message 'VisualEditor is not compatible with the current MediaWiki core (version 1.26.0), it requires: >= 1.27.0.' " Niamb001 (talk) 10:27, 27 April 2016 (UTC)

You need to use the relevant version of VisualEditor for that version of MediaWiki. Master/latest of MediaWiki requires master/latest of MediaWiki, not the latest release version (which is seven months old at this point). Jdforrester (WMF) (talk) 18:22, 27 April 2016 (UTC)

MKruer, you saved me! The required version of parsoid for VisualEditor really ought to be officially documented. 139.169.194.112 (talk) 16:12, 21 July 2017 (UTC)

what is the required version of parsoid for VisualEditor REL1_27? 71.93.58.162 (talk) 17:16, 26 July 2017 (UTC)

I am trying to install Visual Editor REL1_27 on MediaWiki V27

I get this error when trying to edit: Warning Parameter 1 to VisualEditorHooks::onBeforePageDisplay() expected to be a reference, value given in C:\xampp\htdocs\mediawiki\includes\Hooks.php on line 195

does it matter that I am using php version 7.1? 71.93.58.162 (talk) 17:16, 26 July 2017 (UTC)

nevermind. downgraded to xampp with php 5.6.3 and everything's working. 71.93.58.162 (talk) 15:28, 27 July 2017 (UTC)

Fonctionnal with Snapshot version but not with the git version

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

My configuration for this statement is :

• OS X (10.10.3)
• MAMP and XAMPP
• MW 1.25.1
• VisualEditor : 0.1.0 (a83a826) Dieudo (talk) 16:04, 1 June 2015 (UTC)

Correct. a83a826 is 187 commits ahead of the REL1_25 snapshot version (and 35 commits behind master as of writing this). You should not use pre-release git master except with pre-release versions of MediaWiki. Jdforrester (WMF) (talk) 17:45, 10 June 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

VisualEditor won't open on live site when using Refreshed skin

I'm copying this message from a friend, User:MtMNC, who tried to post it here but it wouldn't go through (don't know why). The following is his message:

---

Hi! I help develop Skin:Refreshed and we're trying to make it compatible with VisualEditor. I have a copy of MediaWiki 1.24.2 on my localhost with Refreshed and the appropriate version of VisualEditor (0.1.0) installed, and VisualEditor works as expected. VisualEditor is also installed on a live development wiki here with the same versions of Refreshed and MediaWiki as my localhost. When you use VisualEditor on the live wiki, it opens as expected if you use Vector (see here), but it doesn't open if you use Refreshed (see here). VisualEditor seems to be installed correctly since it works as expected on Vector. It also doesn't seem to be an issue with $wgVisualEditorSupportedSkins as both the "edit" and "edit source" buttons appear on Refreshed, which seems to suggest Refreshed has VisualEditor enabled. I've noticed there's a load.php script present when you view the page in Vector that isn't there when you view it in Refreshed--maybe that's the issue? In which case, why would that script be loaded in one skin and not another, and why would VisualEditor work fine on my localhost but not on the live site?

If it helps, here's the LocalSettings.php file for the live site (VisualEditor is set up at the very bottom).

Any insights greatly appreciated! GeorgeBarnick (talk) 04:52, 2 June 2015 (UTC)

How to set the VisualEditor bar size ?

On a local wiki with this configuration :

• MW 1.25.1
• VisualEditor-REL1_25-c1ed854.tar.gz

The bar looks like this :

On the present MediaWiki it looks smaller. Like this :

How do we set this size ?

Thanks for your help. Dieudo (talk) 08:02, 2 June 2015 (UTC)

I got the same problem after updating to MW 1.25.1 and the latest VisualEditor Version. Would be great if somebody could help Noboddy (talk) 09:01, 8 June 2015 (UTC)

I have the same problem, the only thing I managed to do was to add in MediaWiki:Vector.css

.oo-ui-toolbar-bar {

font-size: 0.75em;

}

.oo-ui-window-frame {

font-size: 0.75em;

}

It's better with this but I don't understand what happened in 1.25 release. SeanFoe 15:10, 12 July 2015 (UTC)

Thanks — it's not perfect, but it fixed the problem for me. Daphne Preston-Kendal (talk) 19:32, 7 October 2015 (UTC)

Does anybody have any idea how to fix that? It's not just the bar size - which I could accept - but also the popup menu for example if you change image properties. The buttons are way too big and won't even fit into the layout, so it is really annoying to work with it. Noboddy (talk) 09:07, 7 July 2015 (UTC)

The same issue. Have no idea how to fix. 109.188.127.7 (talk) 13:38, 13 July 2015 (UTC)

Just to be sure: You all use the latest 1.25 release of Vector, yes? Florianschmidtwelzow (talk) 13:46, 13 July 2015 (UTC)

Yes, MediaWiki 1.25.1, Visual Editor Extension REL1_25, Vector Skin from 1.25.1  Wizo4ka (talk) 16:55, 13 July 2015 (UTC)

Yes, I'm using the latest version of Vector. Are you using the snapshot of VisualEditor or the Git master? I got REL1_25 and it doesn't work with that. Noboddy (talk) 15:44, 13 July 2015 (UTC)

same issue after upgrading from 1.24.2

toolbar isn't the real problem for me, but the option pop-up is -> need to scrool sideways everytime The clemiiiii (talk) 12:54, 16 July 2015 (UTC)

Does anybody have a fix for that problem? Noboddy (talk) 15:04, 5 October 2015 (UTC)

VisualEditor and Parsoid are installed but nothing happened in the site

Hi

I have updated my wiki to 1.25.1 version and installed visualeditor and parsoid which can successfully show up in specifal/version. But, the visualeditor is not enabled also wikieditor disappear as well.

what I have done were all follow with Parsoid page: http://www.mediawiki.org/wiki/Extension:Parsoid and VisualEditor page: http://www.mediawiki.org/wiki/Extension:VisualEditor

In addition, I read the page regarding Parsoid Setup (https://www.mediawiki.org/wiki/Parsoid/Setup) that said setting.js and localsettings.js files all might need to be configured accordingly. However, I did not find such files in my downloaded Parsoid folder.

Anyone could share some thoughts?

Thanks Xiongyu1988 (talk) 10:02, 4 June 2015 (UTC)

a 91.233.163.1 (talk) 17:58, 19 June 2015 (UTC)

Tutorial how to install on Ubuntu

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I am no expert what so ever but wanted to share the tutorial I made for installing Visual Editor on Ubuntu server. Hopefully this may help someone.

www.planet4.se/?p=185 Planet-four (talk) 08:55, 5 June 2015 (UTC)

Thank you. I hope this is helpful for others. Jdforrester (WMF) (talk) 15:42, 10 June 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Error when committing change

Hi Guys

Just upgraded my MW instance from 1.24.1 to 1.25.1 (which required an upgrade of VisualEditor), but now whenever I click "save changes" using VE the pop-up box hangs and in the chrome console I get an error:

TypeError:Cannot read property 'replace' of undefined

I made sure UniversalLanguageSelector was installed, parsoid is installed and running and the VE I am using came from the REL1_25 branch to be compatible with 1.25.1.

Been bashing my head against this for a few hours but no luck, any ideas? CGP92 (talk) 11:56, 18 June 2015 (UTC)

I'm having the same problem, including the TypeError in the chrome console. I have updated all dependancies to VisualEditor (Parsoid, nodejs, UniversalLanguageSelector, php5-curl). Don't have any ideas about how to go forward with this at the moment. Dave3110 (talk) 21:27, 28 September 2015 (UTC)

Visual Editor not working after Database import

Hey guys,

we tried to setup mediawiki 1.25.1 with Visual Editor 1.25REL. Everything works as expected until we import our database from our running wiki (1.24a). As soon as the data is imported VisualEditor loads forever when you click the edit button. Strange thing is that you can still edit pages when you log in as the root user. It seems that only the anonymous user is unable to edit pages with the VisualEditor. We tried a database xml-import as well as a sql import but the same outcome on both variations.

Any ideas on this? Lacp1337 (talk) 06:07, 29 June 2015 (UTC)

Visual Editor edit second time not showing image

After I have created a page with VE and with images, everything works fine. But on the second time of my edit, all my images does not show. It only show the "image with a broken icon on bottom left."

Here is the image: [3] 206.51.148.2 (talk) 22:12, 1 July 2015 (UTC)

I just started to have this problem as well! Adroit (talk) 05:43, 17 July 2015 (UTC)

List of Extensions with VE modules

At Wikimania someone asked if there was a list of MediaWiki extensions that have modules for integration within VE. Does anyone have a rough list?

• Math
• Cite
• Flow Ckoerner (talk) 21:36, 17 July 2015 (UTC)

*Hieroglyphics

*MobileFrontend Ckoerner (talk) 21:43, 17 July 2015 (UTC)

Hey, we should have a category here on MediaWiki.org that lists all extensions with VE modules. Maybe "Category:Extensions with VisualEditor Modules"? Ckoerner (talk) 21:47, 17 July 2015 (UTC)

did such a category ever get created? Tinschel (talk) 23:10, 18 July 2016 (UTC)

Error loading data from server: 0: parsoidserver-http: HTTP 0

Setting '''$wgVisualEditorParsoidURL''' to http://127.0.0.1:8142 doesn't appear to work for me; I still get the following message

"Error loading data from server: 0: parsoidserver-http: HTTP 0"

Parsoid itself seems to work just fine (I can use curl to pull multiple pages with it via the command line), it just isn't working with VisualEditor.

This is a publicly viewable wiki (though not publicly editable).

There's no curl_exec_multi in my php.ini to remove.

The Parsoid log itself doesn't seem to have anything useful in it, beyond the last time I pulled a page successfully with curl. Same goes for the Apache (both overall and site-specific) and MediaWiki logs

Software versions are as follows:

OS: Ubuntu Linux 14.04 LTS

Web server: Apache 2.4.7

PHP: 5.5.9-1ubuntu4.11

NodeJS: v0.10.37

MediaWiki: 1.25.1<div>Parsoid: 0.3.0
  VisualEditor: REL1_25-c947b49
  </div>And here's the relevant settings from my LocalSettings.php:

''# VisualEditor''
  
  ''## Loading Parsoid and ULS first just in case''
  
  ''wfLoadExtension( 'Parsoid' );''
  
  ''require_once "$IP/extensions/UniversalLanguageSelector/UniversalLanguageSelector.php";''
  
  ''// URL to the Parsoid instance''
  
  ''// MUST NOT end in a slash due to Parsoid bug''
  
  ''// Use port 8142 if you use the Debian package''
  
  ''$wgVisualEditorParsoidURL = 'http://127.0.0.1:8142';''
  
  ''// Interwiki prefix to pass to the Parsoid instance''
  
  ''// Parsoid will be called as $url/$prefix/$pagename''
  
  ''$wgVisualEditorParsoidPrefix = 'egwiki';''
  
  ''require_once "$IP/extensions/VisualEditor/VisualEditor.php";''
  
  ''<br>
  ''
  
  ''// Let's not turn this on by default for now.''
  
  ''$wgDefaultUserOptions['visualeditor-enable'] = 0;''<div><br>
  </div><div><br>
  </div> 76.10.197.253 (talk) 18:35, 29 July 2015 (UTC)

Ignore the Wiki markup syntax in there (all the bold/italic indicators), I guess; accidentally posted the source of my comment, and it won't let me post after putting it in the source editor instead. Apologies! 76.10.197.253 (talk) 18:37, 29 July 2015 (UTC)

Using version 1.0.8.12 of SyntaxHighlight_GeSHi as well 76.10.197.253 (talk) 20:57, 29 July 2015 (UTC)

Okay, got VisualEditor to let me edit and save by loading it with "wfLoadExtension( 'VisualEditor' );" instead of the require_once line listed on the extension's page here. So far so good, although it seems like the edit summary box (when saving) may not work all the time, but I don't have any concrete results there yet.

I also had to explicitly set $wgVisualEditorNamespaces after loading the extension in order to enable it (even for NS_MAIN), though that may just be a consequence of my setup. Still, I thought it worth noting in case someone else had the same issue.

24.208.225.167 (talk) 05:25, 30 July 2015 (UTC)

I am having the same problem. The edit summary box plays up from time to time. When I make changes and click on the save button, the box pops-up normally but text cursor stays on the page. So, if I were to type edit summary, it gets typed on the actual page rather than the edit summary box. Surprisingly, it functions properly in IE 11 203.55.211.53 (talk) 05:10, 5 August 2015 (UTC)

I am having the same problem. The edit summary box plays up from time to time. When I make changes and click on the save button, the box pops-up normally but text cursor stays on the page. So, if I were to type edit summary, it gets typed on the actual page rather than the edit summary box. Surprisingly, it functions properly in IE 11 lol 203.55.211.53 (talk) 05:08, 5 August 2015 (UTC)

No VE

I installed VE but it doesn't show on my edit page.

wiki.westeros.pl TraaBBIT (talk) 17:12, 30 July 2015 (UTC)

Which Browser are you using?

for me, didn't show on IE, but did on Chrome. Wesleysousalacerda (talk) 16:54, 3 August 2015 (UTC)

I used Chrome and I don't see VE TraaBBIT (talk) 16:56, 3 August 2015 (UTC)

Did you resolve this? Jdforrester (WMF) (talk) 18:02, 8 September 2015 (UTC)

No Wikimedia Commons?

After upgrading to 1.25.1 the Insert Media dialogue now only returns search results for images within our own wiki, and not Wikimedia commons as previously Stuartbman (talk) 10:50, 18 August 2015 (UTC)

VisualEditor user guide link

I have just installed VE on a local test wiki, and it seems to work. In VE clicking on the ? (help) and then "read the user guide" takes me to a local link where the user guide isn't.

How can I change the link to an officially hosted user guide, or (less preferred) locally host the user guide? 79.86.113.37 (talk) 09:18, 19 August 2015 (UTC)

After installation, 'Revision ID mismatch'

I keep getting an error telling me that the 'Revision IDs (doc=0,api=2) returned by the server do not match'. What's happening? Can anyone help me? 2.99.174.78 (talk) 17:54, 21 August 2015 (UTC)

you need to install Pasoid first.how to install it ,you can see this,Parsoid/Developer Setup#Installation from source on Linux or Mac OS X Zoucong87 (talk) 02:31, 27 August 2015 (UTC)

No results found when trying to insert media in VisualEditor

I have Mediawiki running VisualEditor version 1.25.2. I have been unable to insert media from commons or from local repos. The Images folder has 777 permissions, any suggestions on where I should look first? Matthebu (talk) 06:17, 27 August 2015 (UTC)

I have the same problem - do we have to install anything like commons?

Inserting is possible if you know the filename and add it my keyboard Knut Krüger (talk) 08:34, 10 September 2015 (UTC)

Same issue as above after upgrading to 1.25 and associated VE. I can insert media using the source editor, e.g.:

[[File:Baby eating baby food.jpg|thumb|Baby eating baby food]]

so I don't think it's an issue with Commons. Stuartbman (talk) 15:26, 13 September 2015 (UTC)

Same problem here. Usign MediaWiki 1.24.1 Andreufsc (talk) 18:02, 17 December 2015 (UTC)

I'm running mediawiki 1.26alpha and visual editor 0.1.0 (latest stable). VE searches Commons, although it's disabled in Localsettings. Local media is found but not displayed. Gallery works. Alvaro Ortiz Troncoso (talk) 09:44, 18 December 2015 (UTC)

Anybody have any luck with this? I just installed 1.26.2 with VisualEditor on my own wiki, and the "Insert>Media" dialog only displays "No results found." Is there some configuration variable that needs to be set to point to my standard images location (/w/images)? Maiden taiwan (talk) 21:35, 14 January 2016 (UTC)

check, if access to your Wiki's API is allowed/enabled. Use e.g. Firebug for debugging. Planetenxin (talk) 16:31, 3 February 2016 (UTC)

Some solution to this problem?

I Have installed 1.27.1 VE 0.1.0 and the media search only shows something when I type the whole file name. Bty0808 (talk) 14:08, 10 March 2017 (UTC)

Same problem here. No search results except when using full name of the file and the file type is an image. We have lot's of pdf's in our wiki. And adding links to them is a pain. Rammer (talk) 10:51, 21 November 2017 (UTC)

This is because of the jobs queue. See $wgJobRunRate 46.140.125.126 (talk) 15:24, 12 December 2017 (UTC)

46.140.125.126 could you please elaborate? i'm having this issue on 1.30

Just installed the VE and when trying to search for media, it doesn't show anything 185.82.52.225 (talk) 12:39, 21 December 2017 (UTC)

Enable VisualEditor for all namespaces

I just installed successfullly the VisualEditor for our own Mediawiki. I just got one question: How can I enable the VisualEditor for every Namespace? The parameter "$wgVisualEditorNamespaces[]", which is mentioned in some threads seems not to work anymore. 217.150.249.140 (talk) 14:06, 8 September 2015 (UTC)

Which version of VE are you using? $wgVisualEditorNamespaces was replaced with $wgVisualEditorAvailableNamespaces a few months ago in master, but it's not been in a release yet. Jdforrester (WMF) (talk) 18:14, 8 September 2015 (UTC)

I'm using the last stable version for Mediawiki 1.25, called snapshot no. "c947b49". (replied previously to the false thread). 217.150.249.140 (talk) 09:03, 14 September 2015 (UTC)

I'm using the last stable version for Mediawiki 1.25, called snapshot no. "c947b49". 217.150.249.140 (talk) 05:17, 9 September 2015 (UTC)

Strange characters in edit text

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Its far to difficult to post an image, so I'll just have to describe this... When I use the visual editor I see the edit text contains many instances of a "down and to the left arrow", commonly used to indicate a carriage return (or CRLF for those Windows users reading this). Yet these are in places that clearly are not CR's.

If you would like to see an example, edit the en.wiki article on AI winter and look for the term "technologies developed by". This paragraph has a number of links to other articles, and a number of these CR characters.

I think they are being used to indicate links to other Wiki articles or links in. If this is the case, bad programmer, no donut! I think these need to be changed, whatever the meaning is supposed to be.

p.s. Normally I would link to the article I mention, but I can't - this editor does not appear to allow links to other Wikis. Maury Markowitz (talk) 14:27, 14 September 2015 (UTC)

If you take a look at the wikitext, you'll see that the those links are indeed on separate lines. Elitre (WMF) (talk) 14:32, 14 September 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

"Unknown Error" when trying to save page, parsoid not serializing

Using the newest git master versions of parsoid, visual editor and mediawiki (v1.26alpha) in freebsd. Everything appears to work okay, until I hit the "save" button. When I do, it brings up the confirmation screen. I hit "save changes" I get a message saying "unknown error". The only information I can seem to have that will help debug is that parsoid is failing to serialize the page when I click the "save" button. It is not a parsoid problem however, because I can use the same parsoid server on an older VM with VE and it will work just fine.

So on that VM with an older & working version of mediawiki, parsoid & VE, I notice that when I hit "save" there, I see a request to serialize the page in my parsoid server. I am not seeing that on the new version.

Has anyone ran into this before, and any idea on how I can troubleshoot it? I have tried everything, even went as far as install a completely clean freebsd jail & only install mediawiki. I still get this error. Putting MW in debug mode & running the debug console gives me no useful information. What sort of lack of dependencies or issues will cause VE to fail to send the request to serialize the page to parsoid? 2601:2C6:4600:87B3:219D:250A:153E:C1F1 (talk) 03:34, 16 September 2015 (UTC)

I received the "Unknown Error" when attempting to save as well. I haven't been able to resolve this issue but was able to get a different error by installing php5-curl. Still working on the issue. The error now shown is "Error

loading data from server: 0: parsoidserver-http: HTTP 0". Maybe you'll be able to get further than I have in solving the issue. 169.241.63.90 (talk) 19:03, 25 September 2015 (UTC)

Well I was actually using php56, and I already had php56-curl installed. But your post got me thinking I could try removing php56 and switching to php5. In the end, that didn't work (still the same error), but I did notice that the page does parse quicker on php5.

I appreciate the response since it got me to try something that I haven't attempted yet. If you or anyone else with this issues has any other ideas I'm open. I honestly think this is not a visual editor specific issue, something in my VM isn't playing nice w/ VE.

But using all the built-in debugging tools in chrome & mediawiki hasn't given me anything good to work with.

VE calls the serialize function to parsoid from the "ve.init.mw.Target.js" file stored in "./VisualEditor/modules/ve-mw/init" folder. If I knew more about js I'd play around w/ that file to figure out why VE isn't using that method properly. But I would have no idea where to start. 2601:2C6:4600:87B3:F050:8131:189C:3685 (talk) 01:32, 27 September 2015 (UTC)

I'm having the exact same problem (Unknown Error) .

were you able to find a solution to this ? Fidicterms (talk) 21:57, 14 November 2015 (UTC)

Nope, no solution. Very frustrating. Almost no diagnostic ability to troubleshoot. "unknown error" gives nothing to go off of. Clearly the devs don't know what to do either. 2601:2C6:4600:87B3:3185:D678:7514:FD91 (talk) 02:00, 23 November 2015 (UTC)

I have the same issue, when I check the apache error log it says fatal call to gzinflate(). Now I at least have a direction to follow. 50.253.122.193 (talk) 17:02, 9 March 2016 (UTC)

Fixed by adding zlib module to php. 50.253.122.193 (talk) 17:51, 9 March 2016 (UTC)

holy crap dude. I have been having this problem for over 7 months. I gave up on it a long time ago. Adding zlib to php fixed it!!! 75.148.205.5 (talk) 17:13, 1 April 2016 (UTC)

for me works ./maintanance/update.php 78.46.213.11 (talk) 11:35, 2 December 2016 (UTC)

Activate VisualEditor in certain namespaces.

Hello :)

First I have to say that i'm not familiar with PHP. I'm using Mediawiki 1.25 with the lastest snapshot of VisualEditor from git. So I think it looks pretty cool, but I'm struggling with the configuration. My parsoid service and the editing of existing pages in the main namespace works fine, but how can I activate the plugin in other namespaces?

got two in which I would need this feature: ID 10000 called Appliances and ID 20000 called Customers.

Thank you for your help. Coffeejumper (talk) 12:14, 23 September 2015 (UTC)

worng "paction" on url

I updated my MW to 1.26 and VE stopped working. I found that the url it calls has a "paction" parameter with a value of "parse", which fails with a 404 answer. Intstead, if a change manually that value to "metadata" everything seems to work. How can I fix this within the code? What's wrong with my installation? Robertgarrigos (talk) 15:19, 24 September 2015 (UTC)

MediaWiki 1.26 isn't released yet. Which version of MediaWiki exactly did you update to? Have you updated VisualEditor to the corresponding version? Jdforrester (WMF) (talk) 19:14, 24 September 2015 (UTC)

I'm using mw1.26alpha and master for visualeditor as it says in the download section of the VisualEditor extension page: "The master branch requires alpha builds of MediaWiki" Robertgarrigos (talk) 09:45, 25 September 2015 (UTC)

OK, good. Which versions exactly? Do you have the git hashes? Jdforrester (WMF) (talk) 10:24, 25 September 2015 (UTC)

MediaWiki     1.26alpha (ae90226)

VisualEditor 0.1.0 (a5d3a4d) Robertgarrigos (talk) 12:12, 25 September 2015 (UTC)

Still having this error, even I upgraded to latest master code for VE, MW and ParsoidBAtchAPI

MediaWiki     1.27alpha (4b23e62) 07:10, 1 oct 2015

VisualEditor    0.1.0 (207f55d) 08:50, 24 set 2015

ParsoidBatchAPI    1.0.0 (360ca5a) 19:03, 28 set 2015 Robertgarrigos (talk) 14:08, 1 October 2015 (UTC)

Any idea why my visualeditor is calling paction with parse instead of metadata? Robertgarrigos (talk) 09:05, 19 October 2015 (UTC)

This is the url that visualeditor uses to buildup the editor which gives an error

http://lied.cat/api.php?action=visualeditor&format=json&paction=parse&page=P%C3%A0gina_principal&uselang=ca

this is teh same url with paction=metadata so you can see that my server is working fine

http://lied.cat/api.php?action=visualeditor&format=json&paction=parse&page=P%C3%A0gina_principal&uselang=ca

Any idea what's wrong? Robertgarrigos (talk) 09:08, 19 October 2015 (UTC)

sorry, i pasted the wrong url with the paction=metadata. This is the correct one

http://lied.cat/api.php?action=visualeditor&format=json&paction=metadata&page=P%C3%A0gina_principal&uselang=ca Robertgarrigos (talk) 09:09, 19 October 2015 (UTC)

Any chances to get this solved? Robertgarrigos (talk) 17:52, 19 October 2015 (UTC)

Is it really that no one came across this same problem? 83.41.71.130 (talk) 13:38, 24 November 2015 (UTC)

Download for 1.23LTS is broken

https://extdist.wmflabs.org/dist/extensions/VisualEditor-REL1_23-9883566.tar.gz is 404. 95.210.108.183 (talk) 14:33, 26 September 2015 (UTC)

Hmm, that's odd. I thought that we disabled VE in ExtensionDistributor for MediaWiki 1.22 and 1.23, but it's still listed there? I don't think a working build of VE for 1.23 exists through that system, though a git checkout should work (but be exceedingly old). @Legoktm, any ideas?

Please note that we don't provide support to third parties for VisualEditor, and "LTS" is a misnomer at best. Jdforrester (WMF) (talk) 16:33, 2 December 2015 (UTC)

Filed as Phab:T121748. We currently don't have a way an extension can hide itself in ExtensionDistributor, short of deleting git branches :(. If we want/need that kind of functionality, please file a bug for it. Legoktm (talk) 07:42, 17 December 2015 (UTC)

VisualEditor-REL1_23-9883566.tar.gz is broken 189.212.99.170 (talk) 20:53, 8 May 2017 (UTC)

Error: Unknown dependency: mediawiki.widgets

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I setup MediaWiki with VisualEditor. I followed instruction on the extention wiki page, cloned the git, installed Parsoid, added the necessary lines to get Parsoid to talk to the wiki even if its private :

$local_ip = '127.0.0.1';
if ( $_SERVER['REMOTE_ADDR'] == $local_ip ) {
   $wgGroupPermissions['*']['read'] = true;
   $wgGroupPermissions['*']['edit'] = true;
}else{
   # Disable reading by anonymous users
   $wgGroupPermissions['*']['read'] = false;
   $wgWhitelistRead = array ("Special:Userlogin", "MediaWiki:Common.css",
   "MediaWiki:Common.js", "MediaWiki:Monobook.css","MediaWiki:Monobook.js", "-");
   # Disable anonymous editing
   $wgGroupPermissions['*']['edit'] = false;
}

and now I can talk to the API:

$> curl -L http://localhost:8142/localhost/v3/page/html/Main_Page

<!DOCTYPE html>
<html prefix="dc: http://purl.org/dc/terms/ mw: http://mediawiki.org/rdf/" about="http://localhost/wiki/index.php/Special:Redirect/revision/1"><head prefix="mwr: http://localhost/wiki/index.php/Special:Redirect/"><meta property="mw:articleNamespace" content="0"/><link rel="dc:replaces" resource="mwr:revision/0"/><meta property="dc:modified" content="2015-09-29T22:45:43.000Z"/><meta about="mwr:user/0" property="dc:title" content="MediaWiki default"/><link rel="dc:contributor" resource="mwr:user/0"/><meta property="mw:revisionSHA1" content="8e0aa2f2a7829587801db67d0424d9b447e09867"/><meta property="dc:description" content=""/><meta property="mw:parsoidVersion" content="0"/><link rel="dc:isVersionOf" href="http://localhost/wiki/index.php/Main_Page"/><title>Main_Page</title><base href="http://localhost/wiki/index.php/"/><link rel="stylesheet" href="//localhost/wiki/load.php?modules=mediawiki.legacy.commonPrint,shared|mediawiki.skinning.elements|mediawiki.skinning.content|mediawiki.skinning.interface|skins.vector.styles|site|mediawiki.skinning.content.parsoid|ext.cite.style&amp;only=styles&amp;skin=vector"/></head><body data-parsoid='{"dsr":[0,592,0,0]}' lang="en" class="mw-content-ltr sitedir-ltr ltr mw-body mw-body-content mediawiki" dir="ltr"><p data-parsoid='{"dsr":[0,59,0,0]}'><strong data-parsoid='{"stx":"html","dsr":[0,59,8,9]}'>MediaWiki has been successfully installed.</strong></p>

<p data-parsoid='{"dsr":[61,171,0,0]}'>Consult the <a rel="mw:ExtLink" href="//meta.wikimedia.org/wiki/Help:Contents" data-parsoid='{"targetOff":114,"contentOffsets":[114,126],"dsr":[73,127,41,1]}'>User's Guide</a> for information on using the wiki software.</p>

<h2 data-parsoid='{"dsr":[173,194,2,2]}'> Getting started </h2>
<ul data-parsoid='{"dsr":[195,592,0,0]}'><li data-parsoid='{"dsr":[195,300,1,0]}'> <a rel="mw:ExtLink" href="//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings" data-parsoid='{"targetOff":272,"contentOffsets":[272,299],"dsr":[197,300,75,1]}'>Configuration settings list</a></li>
<li data-parsoid='{"dsr":[301,373,1,0]}'> <a rel="mw:ExtLink" href="//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ" data-parsoid='{"targetOff":359,"contentOffsets":[359,372],"dsr":[303,373,56,1]}'>MediaWiki FAQ</a></li>
<li data-parsoid='{"dsr":[374,472,1,0]}'> <a rel="mw:ExtLink" href="https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce" data-parsoid='{"targetOff":441,"contentOffsets":[441,471],"dsr":[376,472,65,1]}'>MediaWiki release mailing list</a></li>
<li data-parsoid='{"dsr":[473,592,1,0]}'> <a rel="mw:ExtLink" href="//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources" data-parsoid='{"targetOff":555,"contentOffsets":[555,591],"dsr":[475,592,80,1]}'>Localise MediaWiki for your language</a></li></ul></body></html>%    

And I can see in the Parsoid log that it worked

[info][localhost/Main_Page?oldid=1] redirecting to revision 1
[info][localhost/Main_Page?oldid=1] started parsing
[info][localhost/Main_Page?oldid=1] completed parsing in 364 ms

Yet when I try to click the Edit button on the wiki page, it stays stuck with the blue bar loading (and no log or any output to help me debug ...)

I am kinda stuck anyone knows what to do next to check what's wrong ? What log can I check ? Or do you have an idea ?

Thanks !

140.247.90.106 (talk) 22:10, 30 September 2015 (UTC)

Hey,

mediawiki.widgets is provided by a newer version of MediaWiki than it looks like you have installed. If you want to use versions of VisualEditor you need to match them to the same version of MediaWiki. Jdforrester (WMF) (talk) 23:10, 30 September 2015 (UTC)

I install lastest version of mediawiki today and I get this error message as same as you.

When I type mw.widgets in console it say undefined. Chomtana (talk) 10:14, 23 October 2015 (UTC)

By "latest version" do you mean MediaWiki 1.25.3? This is only available in MediaWiki 1.26.0 and later, which is not out yet. Please use the MediaWiki 1.25-compatible version of VisualEditor. Jdforrester (WMF) (talk) 15:38, 23 October 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Visual Editor is freezing at startup

In my closed Mediawiki the Visual Editor ist freezing at start of the editing. I can not reproduce that behavior each time, but it happened at 1 of 10 startups. The Console of my firebug shows the following:

TypeError: origin is null ....cloneObject=function(origin){var key,r;r=createObject( origin.constructor.protot... 194.31.198.71 (talk) 04:47, 6 October 2015 (UTC)

{{VE Bug2

 | description = Visual Editor is freezing at startup

 | intention = Fix the problem at startup of the VE

 | steps =

#Open a random page

#start the VE

#In one of ten startups the loading bar is standing still.

 | results = The loading bar is standing still.

 | expectations = Java - Script error with the following Errormessage in firebug: TypeError: origin is null ....cloneObject=function(origin){var key,r;r=createObject(origin.constructor.protot... 

 | site = my local mediawiki

 | browser = In Firefox 40.0.3 and IE11

 | OS = Windows 7

 | skin = Vector

 | notes = The Mediawiki Version is 1.26wmf21 and Parsoid Version is 0.4.0. I'm using a Linux server.

 | workaround = Reaload the page and try again

}} 194.31.198.71 (talk) 05:03, 6 October 2015 (UTC)

That looks like some code not related to VisualEditor has a race condition and sometimes fails, breaking VisualEditor. Can't help you much more than that, sorry. Jdforrester (WMF) (talk) 16:28, 2 December 2015 (UTC)

Does VE support Page Locking and Auto Save?

Hello, as titled, I wonder if VE supports:

- Page Locking to avoid conflicts for multiple editing instances (i.e. by different people on the same page)

- Auto Save for any accidental situation during editing

As I'm using 1.25, I don't see these features active. Anyone can confirm this to me?

Thanks. Netnetjoe (talk) 09:38, 6 October 2015 (UTC)

We do not have either of those features right now, no. Page Locking would need to be provided in MediaWiki itself (and I'm doubtful it would be accepted as a feature for MediaWiki core; it'd probably need to be done as an extension). Auto-Save is something on the roadmap, but we're not going to start very soon. Jdforrester (WMF) (talk) 15:50, 6 October 2015 (UTC)

Loading bar freeze at 20%

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I have installed Mediawiki and want use VisualEditor. Unfortunately the program freeze after the click on edit.

VisualEditor is installed like this:

cd /var/lib/mediawiki/extensions
git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git
cd VisualEditor
git submodule update --init

git checkout -b REL1_25

git submodule update --init

-----------------------------------------------------------------------------------

This are my LocalSettings.php settings:

#UniversalLanguageSelector - HTML Parser

require_once "$IP/extensions/UniversalLanguageSelector/UniversalLanguageSelector.php";

#VisualEditor (requires HTML Parser)

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

// Enable by default for everybody

$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Don't allow users to disable it

$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features

#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

$wgVirtualRestConfig['modules']['parsoid'] = array(

  // URL to the Parsoid instance

  // Use port 8142 if you use the Debian package

  'url' => 'http://localhost:8000',

  // Parsoid "domain", see below (optional)

  'domain' => 'localhost',

  // Parsoid "prefix", see below (optional)

  'prefix' => 'localhost'

);

#WikiEditor enable

wfLoadExtension( 'WikiEditor' );

$wgDefaultUserOptions['usebetatoolbar'] = 1;

$wgDefaultUserOptions['usebetatoolbar-cgd'] = 1;

$wgDefaultUserOptions['wikieditor-preview'] = 1;

$wgDefaultUserOptions['wikieditor-publish'] = 1;

$wgDefaultUserOptions['usenavigabletoc'] = 1;

wfLoadExtension( 'Parsoid' );

--------------------------------------------------------------------------------

This is my version

MediaWiki	1.25.2
PHP	5.5.9-1ubuntu4.11 (apache2handler)
MySQL	5.5.44-0ubuntu0.14.04.1

Parsoid	0.2.0	GPL-2.0+	Stellt die Laufzeitumgebung Parsoid bereit	Gabriel Wicke, Subramanya Sastry, Mark Holmquist, Adam Wight, C. Scott Ananian, Marc Ordinas i Llopis, Arlo Breault und andere
UniversalLanguageSelector	2015-06-08 (0d5c69f)20:21, 8. Sep. 2015	GPL-2.0+	Bietet verschiedene Möglichkeiten eine Sprache auszuwählen sowie Spracheinstellungen anzupassen	Alolita Sharma, Amir Aharoni, Arun Ganesh, Brandon Harris, Niklas Laxström, Pau Giner, Santhosh Thottingal, Siebrand Mazeland und andere
VisualEditor	0.1.0 (df2c17b)09:49, 9. Okt. 2015	MIT	Stellt den WYSIWYG-Editor „VisualEditor“ bereit	Alex Monk, Bartosz Dziewoński, Christian Williams, David Chan, Ed Sanders, Inez Korczyński, James D. Forrester, Moriel Schottlender, Roan Kattouw, Rob Moen, Sucheta Ghoshal, Timo Tijhof, Trevor Parscal und andere
WikiEditor	0.4.0	Lizenz	Ermöglicht eine erweiterbare Oberfläche zur Wikitext-Bearbeitung sowie viele weitere neue Funktionen	Trevor Parscal, Roan Kattouw, Nimish Gautam und Adam Miller

Any ideas? I use Chrome as web browser. Bernhardsmw (talk) 13:47, 9 October 2015 (UTC)

Same problem with IE. Nice extension... Bernhardsmw (talk) 11:15, 12 October 2015 (UTC)

As it says in bold characters in the instructions:

The master branch requires alpha builds of MediaWiki (currently, 1.25wmf16) and will not work with the older, official releases of MediaWiki like 1.25.1, for that use the REL1_25 branch (command: git clone -b REL1_25

The version of VisualEditor you have downloaded is about 14 months too new to use with MediaWiki 1.25.X. Jdforrester (WMF) (talk) 16:21, 2 December 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Enable VE in custom namespace?

Maybe I'm misunderstanding something, but is VE limited to some list of default namespaces? I have a custom namespace in which I'd like to enable it, and I've added it to the Namespaces line in VisualEditor.php, but for whatever reason I can't get it to work.

This is what I have:

array_merge( $wgContentNamespaces, array( NS_USER, NS_STANDBY ));

NS_STANDBY obviously being the custom namespace. Is this not the correct syntax? No errors or anything, the "Edit" tab simply won't load in that namespace. 66.125.97.2 (talk) 17:37, 4 November 2015 (UTC)

Additional information: MW 1.25.3, VE 0.1.0 66.125.97.2 (talk) 17:38, 4 November 2015 (UTC)

VisaulEditor can be enabled for any namespace. However, I don't know the exact method for doing that, so I'll see if we can get someone more knowledgeable to provide the details. Whatamidoing (WMF) (talk) 18:15, 6 November 2015 (UTC)

$wgVisualEditorAvailableNamespaces = array(

NS_MAIN     => true,

NS_USER     => true,

NS_HELP     => true,

NS_PROJECT  => true,

NS_STANDBY => true

); Divinorum ari (talk) 20:39, 14 June 2016 (UTC)

Multiple instances on IIS 7

Hi all- We have two wikis sharing the same Windows 2008/IIS 7 server. For performance's sake, we have Parsoid running on another 2008/IIS 7 server, and everything works well when we only invoke the VE extension on one installation. When I try to do it on both, I keep getting the 'Error loading data from server: parsoidserver-http-bad-status: 404: No pages were returned from the API request for ____. Would you like to retry?' error.

I've tried various configuration settings with our localsettings.js file (e.g., changing the prefix and domain on both instances and in the LocalSettings), but it only seems to work when I use localhost:

parsoidConfig.setMwApi({
uri: 'http://site1.mywiki.com/api.php',
domain: 'localhost',
prefix: 'localhost',});

Other wiki looks like this:
parsoidConfig.setMwApi({
uri: 'http://site2.mywiki.com/api.php"'
domain: 'site2',
prefix: 'site2', });

Have also tried using site2.mywiki.com as domain/prefix to no avail. Right now I only have the extension available on one site since enabling it on both seems to break one or the other (or both). Have also tried putting one site on a port (e.g. localhost and localhost:81), but that didn't seem to work, either. It appears the only documentation for this type of issue is for Apache2.

Any suggestions? Kchurch05 (talk) 20:59, 5 November 2015 (UTC)

Okay, I've tried some additional troubleshooting steps and here are my findings:

I installed clones of both wikis on another server. They're not resolved to a DNS name, so right now they're set on the IP with a port (e.g., http://10.12.34.567 and http://10.12.34.567:81).

When I used the exact same parsoid server that's being used on our production sites (listed above), I have zero issues running one of the production sites and the two clones (e.g. site1.mywiki.com and the clones).

localsettings.js then looks like this:

parsoidConfig.setMwApi({

uri: 'http://site1.mywiki.com/api.php',

domain: 'localhost',

prefix: 'localhost',

});

parsoidConfig.setMwApi({

uri: 'http://10.12.34.567/api.php',

domain: 'clone',

prefix: 'clone',

});

parsoidConfig.setMwApi({

uri: 'http://10.12.34.567:81/api.php',

domain: 'otherclone',

prefix: 'otherclone',

});

And the Localsettings.php files are corresponding to the domains/prefixes listed above, e.g.

$wgVirtualRestConfig['modules']['parsoid'] = array(

'url' => 'http://parsoidserver:8000',

// Parsoid "domain", see below (optional)

'domain' => 'localhost',

// Parsoid "prefix", see below (optional)

'prefix' => 'localhost',

);

for site1.mywiki.com, and so on.

However, when I add site2.wiki.com and change the localsettings.js to adapt for site2, it goes all awry. Additionally, if I change site1.wiki.com's domain and prefix to anything BUT localhost, it won't work (e.g. if I put "foo" in as both and yes, also changing the appropriate lines in LocalSettings.php).

I tried using the numerical IPs for site1 and site2 (putting site2 on a :81 port since they live on the same server), but no go.

What's the deal here? Why is my parsoid server so in love with localhost?! Kchurch05 (talk) 22:02, 9 November 2015 (UTC)

After updating to the latest version of MediaWiki and Parsoid and NodeJS on a Debian setup I have the a very similar issue. Only one site of my wikis in a multi wiki setup on the same server and can be active. NodeJS nor parsoid gives are error when restarting the service. MKruer (talk) 07:36, 7 December 2015 (UTC)

Missing picture during Visual Editing.

When i tried to edit, i noticed the pictures that are included tend to be not shown but still there.

The size of the graphic is there, but no picture with a broken link icon on the top left.

Sample

When editing is done, the pictures are shown again. All these pictures are uploaded into the mediawiki, AmazingTrans (talk) 13:35, 30 November 2015 (UTC)

Looks like the URLs that Parsoid are generating are pointing to the wrong place (which doesn't exist, so fails). Is your image directory path set to an odd value? Parsoid should pick it up, but maybe it doesn't work in some cases. What URL is being used in the Parsoid DOM (i.e., what URL does VisualEditor attempt to fetch) and how does it differ from the MediaWiki DOM (the URL that the read page successfully fetches)? Jdforrester (WMF) (talk) 16:25, 2 December 2015 (UTC)

My image directory resides in /mediawiki/htdocs/images ; and there is a lot of otehr folder 0-9, a-f et.

From the developer tools, i see it says failed to load resource: net:: ERR_ADDRESS_UNREACHABLE

it gave this http://localhost/images/thumb/5/51/01_picture1-D.jpg/243px-01_picture-D.jpg

but it is suppose to be this: http://localhost/images/thumb/5/51/01_picture-D.jpg

Not sure why it append the size then image file again.

But, other images is at the correct path and still not showing picture:

Failed to load resource: net::ERR_ADDRESS_UNREACHABLE  : http://localhost/images/1/11/02_Siemens-Sinamics_S120.JPG AmazingTrans (talk) 18:05, 4 December 2015 (UTC)

Aha, i figured out that it is displaying localhost rather than  AmazingDomain during visualedit mode.

http://AmazingDomain/images/thumb/5/51/01_picture1-D.jpg/243px-01_picture-D.jpg

and when it is read mode, it display the proper domain.

What should i edit so that it points to the proper domain during edit mode? AmazingTrans (talk) 18:15, 4 December 2015 (UTC)

Did you manage to solve your problem? I have a similar problem: Extension talk:VisualEditor/2017/02#h-Images_(edit-mode)_not_shown_with_https-wiki-2017-02-16T19:19:00.000Z. Maybe your solution gives me a clue.

Thanks in advance, regards, Jethro Waanders (talk) 13:05, 22 February 2017 (UTC)

My issue is fixed: Extension talk:VisualEditor/2017/02#h-Images_(edit-mode)_not_shown_with_https-wiki-2017-02-16T19:19:00.000Z Waanders (talk) 11:29, 5 April 2017 (UTC)

Hey, I just wanted to point out that someone started VisualEditor/Recipes to list solutions for third-party wiki installations, so if you have information that might help other people, then please add it there. Whatamidoing (WMF) (talk) 16:53, 14 April 2017 (UTC)

Stopped working after 125.1 to 1.25.3 upgrade

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi

I recently installed this extension and everything was working fine, but after upgrading to 1.25.3 the editor has stopped working. You click the button and it starts to load but then just stops, with no clear errors. What is the best way to debug, this ? I have tried the latest version of the Editor and the one indicated for 1.25 and they both have the same issue.

Very few errors; no errors in javascript, html or parsoid (and the direct test for parsoid are fine). There are also no consistent apache2 errors, though I have seen some related to "class 'MWNamespace' does not have a method 'wantSignatures'" I have checked the defualt log files but can not find a problem.

Any ideas about how to proceed would be most welcome, Thanks Jpadfield (talk) 15:49, 1 December 2015 (UTC)

it looks like you accidentally upgraded VisualEditor in the process. The only code in VisualEditor that references MWNamespace::wantSignatures was added to master a couple of weeks ago, and will only be compatible with MediaWiki 1.27.0+. Jdforrester (WMF) (talk) 16:27, 2 December 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How to disable VE for a content namespace

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I need to disable VisualEditor on a namespace using semanticforms. The doc shows Namespaces as the configuration option, and I think this has been replaced with AvailableNamespaces as an array.

If I just give it the list to enable, my NS_TEMPPROJECTS isn't disabled, I presume it's already in the array because it's defined as a content namespace.

$wgVisualEditorAvailableNamespaces = array( 

NS_MAIN     => true,

NS_USER     => true,

NS_HELP     => true,

NS_PROJECT  => true,

);

I had to add it and specifically disable it with false, like this.

$wgVisualEditorAvailableNamespaces = array( 

NS_MAIN     => true,

NS_USER     => true,

NS_HELP     => true,

NS_PROJECT  => true,

NS_TEMPPROJECTS => false

);

I temporarily ended up with 2 Edit Source links in the toolbar, the first actually still pointed to veaction=edit, and then a popup says it's disabled for the namespace. But after refreshing everything it went away. Kc5vcx (talk) 17:36, 5 December 2015 (UTC)

Thank you for these instructions. I hope they are useful for others. Jdforrester (WMF) (talk) 17:53, 7 December 2015 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Couldn't connect to server: parsoidserver-http-error: (curl error: 7)

Hello, I have reinstalled MediaWiki recently since I wanted to update from 1.25.3 to 1.26.0. I had VisualEditor installed and working properly on my previous install of MediaWiki, but after updating (read: Full re-install of MediaWiki) it does not seem to work anymore.

When I click on Edit the VisualEditor loading bar appears but at around 25% it stops and gives me the following error:

"Error loading data from server: (curl error: 7) Couldn't connect to server: parsoidserver-http-error: (curl error: 7) Couldn't connect to server. Would you like to retry?"

I updated both the VisualEditor extension and did a full reinstall of Parsoid (to my knowledge) after VisualEditor stopped working but I still get the same error.

In my LocalSettings.php I have the following:

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

// Enable by default for everybody

$wgDefaultUserOptions['visualeditor-enable'] = 1;

// Don't allow users to disable it

$wgHiddenPrefs[] = 'visualeditor-enable';

// OPTIONAL: Enable VisualEditor's experimental code features

$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;</pre>

In my /etc/mediawiki/parsoid/settings.js I have the following:

parsoidConfig.setMwApi({ prefix: 'localhost', uri: 'http://mydomain.com/w/api.php', domain: 'mydomain.com'});</pre>

My log located at /var/log/parsoid/parsoid.log does not update when this error is created.

I run Ubuntu 14.04 and have Node.js installed. Swennet (talk) 00:47, 7 December 2015 (UTC)
:I have the same issue and configuration, trying to install 1.26.0 from scratch. Sorenweber (talk) 13:54, 14 December 2015 (UTC)
:@Sorenweber
:Did you manage to get it working? Swennet (talk) 13:03, 23 December 2015 (UTC)
:@Swennet, I can't see in your snippet where you're telling VisualEditor the URL of your Parsoid instance...
:Check this section to make sure your setting is correct: Extension:VisualEditor#Linking with Parsoid using $wgVirtualRestConfig 88.109.25.153 (talk) 00:17, 10 January 2016 (UTC)
:@88.109.25.153
:I did not include that snippet since I have 5 of them, each for a separate Wiki database. I am certain that it was set up correctly since it worked perfectly fine on 1.25.3. So far I have not yet found a solution and ended up simply restoring my 1.25.3 installation. I will re-try sometime in the future since I do not want to update MediaWiki once my website is completed. 92.110.165.206 (talk) 16:24, 14 January 2016 (UTC)
:Has anyone found a solution to this? I am having the same problem:
:1.25.3 Visual Editor works fine
:1.26.2 Visual Editor loads 75% then fails with this message in the log:
:[caches] LocalisationCache: using store LCStoreDB
:[MessageCache] MessageCache::load: Loading en... local cache is empty, global cache is expired/volatile, loading from database
:[gitinfo] Computed cacheFile= for /var/lib/mediawiki-1.26.2/extensions/VisualEditor-1.26
:[gitinfo] Cache incomplete for /var/lib/mediawiki-1.26.2/extensions/VisualEditor-1.26
:[GlobalTitleFail] MessageCache::parse called by VisualEditorDataModule::getScript/Message::parse/Message::toString/Message::parseText/MessageCache::parse with no title set.
:[GlobalTitleFail] MessageCache::parse called by VisualEditorDataModule::getScript/Message::parse/Message::toString/Message::parseText/MessageCache::parse with no title set. 173.13.64.171 (talk) 02:20, 30 January 2016 (UTC)
:It's working for me using MediaWiki 1.26.2 and these settings in LocalSettings.php:
:require_once "$IP/extensions/VisualEditor/VisualEditor.php";
:$wgDefaultUserOptions['visualeditor-enable'] = 1;
:$wgDefaultUserOptions['minordefault'] = 1;
:$wgHiddenPrefs[] = 'visualeditor-enable';
:$wgVisualEditorParsoidURL = 'http://localhost:8000';
:$wgVirtualRestConfig['modules']['parsoid'] = array(
:  'url' => 'http://localhost:8000',
:  'domain' => 'localhost',
:  'prefix' => 'core_wiki'
:);
:And these settings in Parsoid localsettings.js:
:parsoidConfig.setMwApi({
:                prefix: 'core_wiki', // optional
:                domain: 'localhost', // optional
:                uri: 'http://localhost/api.php',
:        }); Mpconnick (talk) 22:39, 1 February 2016 (UTC)
:for version 0.3.0. change options format for setMwApi
:Your cmd : parsoidConfig.setMwApi({prefix: 'core_wiki', domain: 'localhost', uri: 'http://localhost/api.php' });
:new cmd : parsoidConfig.setMwApi( 'core_wiki', {domain: 'localhost', uri: 'http://localhost/api.php' });
:...
:see line 377 in file "/usr/lib/parsoid/src/lib/mediawiki.ParsoidConfig.js", method ParsoidConfig.prototype.setMwApi,... 77.154.204.235 (talk) 14:06, 7 March 2016 (UTC)
:Hi everyone, it's working fine on 1.26.2 now. Not entirely sure what I did wrong, maybe it was a bug in 1.26.0...
:My format right now is:
:
:parsoidConfig.setMwApi({ prefix: 'main', uri: 'http://domain.com/w/api.php' });
:parsoidConfig.setMwApi({ prefix: 'secondary', uri: 'http://secondary.domain.com/w/api.php' });
:
:Thank you to everyone that helped :) Swennet (talk) 14:27, 7 March 2016 (UTC)
:Hi everyone,
:I have follow the instruction on 
:Parsoid/Developer Setup#Quick start
:My Environment is
:1.Windows server 2012 
:2.xampp-win32-5.6.19-0-VC11
:3.Media-Wiki 1.26.2
:4.VisualEditor 1.26
:5.git
:6.Curl 7.47.1
:7.VS2010
:8.node-v4.4.0-x64
:9.python-2.7.11
:10. parsoid 
:When I want to active VisualEditor , It pop's up the error 
:(curl error:28)Timeout was reached:parsoidserver-http-error: (curl error:28) Timeout was reached,
:Do you want to retry?
:After retry many times still fail to active VisualEditor. Nita1577 (talk) 09:59, 23 March 2016 (UTC)
:Hi Nita,
:I think you shouldn't follow the developer instructions for Parsoid unless you intent to help develop the software itself.
:As stated on the Extension:VisualEditor page:
:<syntaxhighlight lang='text'>The master branch requires alpha builds of MediaWiki (currently, 1.27.0-wmf8) and will not work with the older, official releases of MediaWiki like 1.26.2; for that, use the REL1_26 branch (command: git clone -b REL1_26 https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git).</pre>
Basically, if you want to install Parsoid the "Developer" way, then you need to work with the latest development builds of MediaWiki and VisualEditor. Swennet (talk) 15:16, 25 March 2016 (UTC)
:Hi
:I’m having a similar problem “Couldn’t connect to server: parsoidserver-http-error: (curl error: 7)”
:Firstly I’m new to using MediaWiki, VisualEditor and Parsoid although I’m very familiar with Linux OS over many years.  I’ve installed the above on to Linux workstation running Centos 6.5 as follow: 
:# MediaWiki from mediawiki-1.26.2.tar
:# VisualEditor from VisualEditor-REL1_26-a733545.tar 
:#Parsoid from https://gerrit.wikimedia.org/r/p/mediawiki/services/parsoid
:This Linux workstation is known to our LAN as “carme”
:URL to my wiki is              http://carme/w 
:Path to my wiki is             /var/www/html/w
:After configured Localsetting.js I started the parsoid service as follows:
:cd /opt/parsoid
:node bin/server.js
:I get the following message:
:[info][master][6165] initializing 5 workers
:[info][worker][6167] loading ...
:[info][worker][6170] loading ...
:[info][worker][6169] loading ...
:[info][worker][6172] loading ...
:[info][worker][6167] ready on :8000
:[info][worker][6174] loading ...
:[info][worker][6170] ready on :8000
:[info][worker][6169] ready on :8000
:[info][worker][6172] ready on :8000
:[info][worker][6174] ready on :8000
:So it looks like parsoid service is functioning and in a Chrome browser on window pc within the same LAN if I enter:
:http://carme:8000
:I get the following page (between ==== ) displayed:
:====
:=== Welcome to the Parsoid web service. ===
:See the API documentation on mediawiki.org.
:There are also some convenient tools for experiments. These are not part of the public API.
:* Round-trip test pages, for example: /_rt/mediawiki/Parsoid
:* WikiText     -> HTML DOM -> WikiText round-trip form
:* WikiText     -> HTML DOM form
:* HTML     DOM -> WikiText form
:====
:And if I click these links and follow the instructions it all appears to work as expected.
:On my wiki I can see the default main page http://carme/w/index.php/Main_Page with both the “Edit” and “Edit source” tabs displayed.  So it looks like my mediawiki is using the VisualEditor extension.  If on this page I click the “Edit” tab I get a progress bar but before it completes I get an error message box displaying:
:carme says: 
:Error loading data from server: (curl error: 7) parsoidserver-http-error: (curl error: 7). Would you like to retry.
:Also if I try to create a new page by entering: http://carme/w/index.php/New_test I get a “Create” and “Create source” tab. If I click “Create” tab then I get VisualEditor interface allowing me to create my new test page.  The VisualEditor appears to work as expected.  However when I do to Save page I get message box saying:
:Something went wrong
:Parsoidserver-http-error: (curl error: 7)
:I think the problem is something to do with the configuration between Mediawiki, VisualEditor and Parsoid but I can’t seem to work it out.  I can provide configuration for Localsetting.php and localsettings.js if that would help. 
:I would be very grateful for any help that offered. Flyingadrian (talk) 17:04, 5 April 2016 (UTC)
:@Flyingadrian
:Parsoid and VisualEditor runs on port 8142 on Debian servers. Did you intentionally change this port or did you enter it incorrectly? Try using port 8142 and see if it works :) Swennet (talk) 21:21, 5 April 2016 (UTC)
:Thanks Swennet for your input.
:My Mediawiki, Parsoid and VisualEditor is installed on a Workstation running Cento 6.5 not Debian.  I understand that for a Centos installation the default port is 8000.  I can get Parsoid to work on port 8000 by entering http://carme:8000.  I can also get VisualEditor to work on a new wiki page by entering http://carme/w/New_page.   However, I can't get seem to get VisualEditor to communicate with Parsoid. Flyingadrian (talk) 09:13, 6 April 2016 (UTC)
:@Flyingadrian
:Sorry, I was under the impression that they were one and the same. Providing us with your Localsettings.php and Localsettings.js would definitely help troubleshooting the problem. Swennet (talk) 13:34, 6 April 2016 (UTC)
:Thanks for your help.  I'm sure it is a configuration problem somewhere.  Anyway here is the code I've added to my wiki LocalSetting.php file relating to VisualEditor and Parsoid: 
:  # =======================================================================
:  # This VisualEditor extension block has been added by ALB 31 Mar 2016 from code snippet found in:
:  # https://www.mediawiki.org/wiki/Extension:VisualEditor
:  #
:  #
:  require_once "$IP/extensions/VisualEditor/VisualEditor.php";
:  // Enable by default for everybody
:  $wgDefaultUserOptions['visualeditor-enable'] = 1;
:  // Don't allow users to disable it
:  $wgHiddenPrefs[] = 'visualeditor-enable';
:  // OPTIONAL: Enable VisualEditor's experimental code features
:  $wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
:  $wgVisualEditorParsoidURL = 'http://carme:8000';
:  // if you have a private wiki you will need these lines to enable parsoid to access
:  // the mediawiki api (these settings must follow all other group permission settings)
:  if ( $_SERVER['REMOTE_ADDR'] == 'carme' ) {
:  $wgGroupPermissions['*']['read'] = true;
:  $wgGroupPermissions['*']['edit'] = true;
:  }
:  # VisualEditor extension block end
:  # ========================================================================
:  # =======================================================================
:  # This block has been added to get VisualEditor to talk to Parsoid has been added by ALB 01 Apr 2016 from
:  # code snippet found in:
:  # https://www.mediawiki.org/wiki/Extension:VisualEditor
:  #
:  $wgVirtualRestConfig['modules']['parsoid'] = array(
:  // URL to the Parsoid instance
:  // Use port 8142 if you use the Debian package
:  // 'url' => 'http://localhost:8000',
:  'url' => 'http://carme:8000',
:  // Parsoid "domain", see below (optional)
:  'domain' => 'carme',
:  // Parsoid "prefix", see below (optional)
:  'prefix' => 'carme'
:  );
:  # End Linking VisualEditor to talk to Parsoid
:  # ========================================================================
:Below is the code I've added to my localsetting.js file
: /*
: * This is a sample configuration file.
: *
: * Copy this file to localsettings.js and edit that file to fit your needs.
: *
: * Also see:
: * - api/server.js for more information about passing config files via
: *   the commandline.
: * - lib/mediawiki.ParsoidConfig.js all the properties
: *   that you can configure here. Not all properties are
: *   documented here.
: */
: 'use strict';
: exports.setup = function(parsoidConfig) {
: // Set your own user-agent string
: // Otherwise, defaults to "Parsoid/<current-version-defined-in-package.json>"
: //parsoidConfig.userAgent = "My-User-Agent-String";
: // Configure Parsoid to point to your MediaWiki instance.
: parsoidConfig.setMwApi({uri: 'http://carme/w/api.php', domain: 'carme', prefix: 'main' } );
:I feel sure it is something simple as independently my mediawiki, VisualEditor and Parsoid are working.  Anyway thanks again for any help you can offer. Flyingadrian (talk) 17:26, 6 April 2016 (UTC)
:@Flyingadrian
:No problem, sharing the knowledge what it's all about!
:I don't know 100% sure if this is this issue, but I'd like you to try something which worked for me.
:In your LocalSettings.php:
:Comment out the parsoid domain line 'domain' => 'carme',.
:Then in your LocalSettings.js:
:Edit your parsoidConfig.setMwApi setting to so that the prefix value comes before the url, and delete the domain setting altogether.
:parsoidConfig.setMwApi({prefix: 'main', uri: 'http://carme/w/api.php' } );
:Now see if it works for you (don't forget to restart the Parsoid service on your server!)
:I'm not sure if the problem is with the location of the prefix setting in LocalSettings.js, or if the issue is with the domain setting, but it worked for me. Note that the domain setting doesn't actually do anything (as far as I know), so omitting it shouldn't affect you in any way.
:Let me know if that worked for you :) Swennet (talk) 22:47, 6 April 2016 (UTC)
:@Flyingadrian it work for me on centos 7 with this config :
:/opt/parsoid/localsettings.js
: 'use strict'; exports.setup = function(parsoidConfig) { parsoidConfig.setMwApi('core_wiki', { uri: 'http://localhost/api.php' }); };
:===== /var/www/html/LocalSettings.php =====
: require_once "$IP/extensions/VisualEditor/VisualEditor.php"; // Enable by default for everybody $wgDefaultUserOptions['visualeditor-enable'] = 1; // Don't allow users to disable it $wgHiddenPrefs[] = 'visualeditor-enable'; // OPTIONAL: Enable VisualEditor's experimental code features $wgDefaultUserOptions['visualeditor-enable-experimental'] = 1; # Linking with Parsoid $wgVirtualRestConfig['modules']['parsoid'] = array(  // URL to the Parsoid instance  // Use port 8142 if you use the Debian package  'url' => 'http://localhost:8000',  // Parsoid "domain", see below (optional)  'domain' => 'localhost',  // Parsoid "prefix", see below (optional)  'prefix' => 'core_wiki' );
:when I start parsoid i just get deprecated warning but visual editor work 
:/usr/bin/node /opt/parsoid/bin/server.js 
:String arguments to ParsoidConfig#setMwApi are deprecated: core_wiki
:[info][master][17699] initializing 11 workers
:String arguments to ParsoidConfig#setMwApi are deprecated: core_wiki
:[info][worker][17708] loading ...
:[info][worker][17712] loading ...
:[info][worker][17708] ready on :8000
:unfortunately I have to run parsoid in terminal every time before starting visual editor to prevent parsoidserver-http-error: (curl error: 7)
:I think I probably make an error in the /etc/systemd/system/parsoid.service file but I have put ExecStart=/usr/bin/node /opt/parsoid/bin/server.js and I dont understand where is the problem here. Cirselrac (talk) 09:29, 7 April 2016 (UTC)
:I found the solution : I forgot to enable the Parsoid-daemon to start on boot time:
:systemctl enable parsoid.service
:now visual editor work well for me in centos7 Cirselrac (talk) 07:43, 13 April 2016 (UTC)
:Sorry I haven't responded for several days but I had to drop trying to resolve my problem here to attend to other business matters.
:Anyway, I've managed to solve my problem, well at least get around it.  I'm running Centos 6.5 and SELinux was set to enforcing.  This is an internal server and we don't really need enhanced security.  Anyway, if I modify my /etc/selinux/config file to set SELINUX=permissive my curl error: 7 problem goes away and I can now get VisualEditor to work with my wiki.  There is probably another way to stop SELinux from blocking port 8000 connections but I've spent too much time on this problem already so happy to live with my solution.
:I would like to thank everyone for all the help and in particular the suggestions from @Swennet and @Cirselrac.  Much appreciated. Flyingadrian (talk) 19:14, 19 April 2016 (UTC)
:In my case also, i checked the boot process and found that while it was configured to start on boot, it was not running at the moment. I also could not start it, but for somer reason first stopping, then starting worked. NitaiDas (talk) 10:45, 15 May 2017 (UTC)
:I cannot use the visual editor on the rest of miraheze, because it keep on stopping, so i will be moving to a new account next day.
:Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 52) Server returned nothing (no headers, no data). Would you like to retry? Chebbycraft34 (talk) 03:59, 10 September 2020 (UTC)
:Worked for me downloading and installing another visual editor (mediawiki version 1.35.1) called TinyMCE, and disabling VisualEditor on LocalSettings.php; just deleting or commenting line wfLoadExtension ( 'VisualEditor' ); 93.188.143.2 (talk) 14:50, 14 April 2021 (UTC)

500 error on VisualEditor

Hello,

I've been trying to install VisualEditor on a Windows machine and Ubuntu. Both tries returns me 500 error when trying to edit pages, or Unkown Error when trying to create a new page. Parsoid is up and running but I can't confirm it's linked with VisualEditor.

What am I doing wrong? Any suggestion?

Thanks. 200.198.121.123 (talk) 21:00, 11 December 2015 (UTC)
:For a 500 error on the visual editor end you should be getting an error in your web server logs, if you haven't set a special vhost configuration for apache then the log should be in /var/log somewhere. 88.109.25.153 (talk) 00:19, 10 January 2016 (UTC)
:I got the same error when i start editing a page. BUT: I create a new site = the Editor works perfectly..
:My persoid.log (the error section):
:[info][wiki$0/Hauptseite?oldid=8] started parsing
:[fatal/request][wiki$0/Hauptseite?oldid=8] Cannot assign to read only property 'lastIndex' of object '[object RegExp]'
:TypeError: Cannot assign to read only property 'lastIndex' of object '[object RegExp]'
:at RegExp.exec (native)
:at RegExp.test (native)
:at /usr/lib/parsoid/src/lib/wt2html/HTML5TreeBuilder.js:128:45
:at Array.map (native)
:at TreeBuilder._att (/usr/lib/parsoid/src/lib/wt2html/HTML5TreeBuilder.js:123:22)
:at TreeBuilder.processToken (/usr/lib/parsoid/src/lib/wt2html/HTML5TreeBuilder.js:212:66)
:at TreeBuilder.resetState (/usr/lib/parsoid/src/lib/wt2html/HTML5TreeBuilder.js:101:7)
:at new TreeBuilder (/usr/lib/parsoid/src/lib/wt2html/HTML5TreeBuilder.js:34:7)
:at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/wt2html/parser.js:233:17)
:at ParserPipelineFactory.makePipeline (/usr/lib/parsoid/src/lib/wt2html/parser.js:229:17)
:Content of my persoid settings.js-File:
:'use strict';
:exports.setup = function(parsoidConfig) {
:parsoidConfig.setMwApi({ uri: 'http://sub.domain.tld/api.php', domain: 'sub.domain.tld' });
:parsoidConfig.debug = true;
:parsoidConfig.useSelser = true;
:};
:Content of my LocalSettings.php:
:$wgVirtualRestConfig['modules']['parsoid'] = array(
:'url' => 'http://sub.domain.tld:8142',
:'domain' => 'sub.domain.tld'
:);
:By the way: sub = my Subdomain (help), domain = my Domainname, tld = de Keegan1120 (talk) 20:01, 23 September 2016 (UTC)
:I don't know if you still have this problem, but I was having the same problem (13 july  2017) and manage to solve it by installing php5-curl (or "php7.0-curl" if you have newer versions of ubuntu)
:I don't know if I missed a step through the installation guide or got an error that I dind`t notice or maybe It's missing on the mediwiki article.
:anyway, when I installed the php5-curl the Visual Editor started working, the http 500 error was gone
:Extension:VisualEditor#Troubleshooting Bozomal (talk) 17:08, 13 July 2017 (UTC)
:Thank you Bozomal! Installing php7.0-curl fixed the 500 error for me too. 216.243.20.18 (talk) 22:33, 18 October 2017 (UTC)
:hey bro, it fixed my trouble too with curl install 80.74.72.215 (talk) 14:32, 31 January 2018 (UTC)
:Hello,
:I installed VisualEditor 1.30 and Mediawiki 1.30 on Virtual machine Debian 9.It returns me 500 error when trying to edit pages. 
:Here are my configuration files.
:- LocalSettings : 
:wfLoadExtension( 'VisualEditor' );
:// Enable by default for everybody
:$wgDefaultUserOptions['visualeditor-enable'] = 1;
:// Optional: Set VisualEditor as the default for anonymous users
:// otherwise they will have to switch to VE
:// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
:// Don't allow users to disable it
:$wgHiddenPrefs[] = 'visualeditor-enable';
:$wgVirtualRestConfig['modules']['parsoid'] = array(
:   // URL to the Parsoid instance
:   // Use port 8142 if you use the Debian package
:   'url' => 'http://swebprod688.local:8000',
:   // Parsoid "domain", see below (optional)
:   'domain' => 'swebprod688.local',
:   // Parsoid "prefix", see below (optional)
:   'prefix' => 'localhost'
:);
:- Config.yaml
:uri: 'http://swebprod688.local/mediawiki/api.php'
:         # The "domain" is used for communication with Visual Editor
:         # and RESTBase.  It defaults to the hostname portion of
:         # the `uri` property above, but you can manually set it
:         # to an arbitrary string. It must match the "domain" set
:         # in $wgVirtualRestConfig.
:         domain: 'swebprod688.local'  # optional
:Please, help. Thanks. 77.158.24.248 (talk) 09:36, 27 March 2018 (UTC)
:Hi,
:are you using the heroku app?
:1) Make sure that no htpasswd is set up in your /w folder. I realized that the heroku app is not working with a password protected ftp folder.
:2) Be careful where you set your root directory in your website hosting app 2003:C6:4F25:E6E0:285D:1D34:EF27:E455 (talk) 15:11, 28 December 2019 (UTC)
:Hi, same problem with heroku app.
:I've no htpasswd on my /w folder.
:I changed nothing - and it's not working now... hollosch (talk) 15:21, 23 January 2020 (UTC)
:I spent ages on this myself.
:I checked in the web browser's debug console while clicking 'edit' to see what URL was being loaded. Manually loading the 500 URL it in the browser showed me I was getting a "SQLSTATE[HY000]: General error: 5 database is locked".
:I am using SQLITE for the database. It wasn't locked and normal editing worked fine.
:What eventually fixed it was setting $wgMainCacheType = CACHE_ACCEL; (needs the correct php extension install). Previously I also set the journal mode to wal in the sqlite database as advised by the mediawiki docs on sqlite which might have also helped.
:See the mediawiki SQLite manual section under performance tips. [Manual:SQLite#Performance_Tips] 27.32.128.11 (talk) 07:18, 26 February 2023 (UTC)