Extension talk:VisualEditor/2013

Error contacting the Parsoid server

Hi,

when I click on the WYSIWYG button, I only get an error:

{"error":{"code":"parsoidserver","info":"Error contacting the Parsoid server"}}

My config is as following:

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

define( 'NS_VISUALEDITOR', 2500 );

define( 'NS_VISUALEDITOR_TALK', 2501 );

$wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor';

$wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk';

$wgVisualEditorNamespaces = array( NS_MAIN );

$wgVisualEditorNamespaces = array();

$wgVisualEditorNamespaces[] = NS_VISUALEDITOR;

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

$wgHiddenPrefs[] = 'visualeditor-enable';

$wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/';

I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).

I would apreciate any help! 217.111.66.226 14:29, 24 January 2013 (UTC)

I have met the same problem too.

anybody could help us solve this problem? 121.14.96.125 11:11, 23 May 2013 (UTC)

Same problem! Zoglun (talk) 02:40, 6 June 2013 (UTC)

Same here! 2605:EB00:100:1:0:0:2085:29B0 14:36, 29 August 2013 (UTC)

same here 65.49.68.174 09:44, 7 January 2014 (UTC)

I'm sure there are many people who, like me, are happy to help, but you have to give more information. Have you followed all instructions for installing the parsoid, have you checked that parsoid is running correctly (it has some test scripts..), and have you checked error logs? Stephan Matthiesen (talk) 11:22, 8 January 2014 (UTC)

Can't save page.

set in the localsettings.js as: parsoidConfig.setInterwiki( 'localhost', 'http://moewiki.org/121test/api.php' );

LocalSettings.php as: $wgVisualEditorParsoidURL = 'http://moewiki.org:8000'; $wgVisualEditorParsoidPrefix = 'localhost';

I DO can visit the visualedit page, I can't save the change. It show:"unsuccessful request:eoor."

MW 1.21.1

VisualEditor 1.20 stable from here:http://www.mediawiki.org/wiki/Special:ExtensionDistributor/VisualEditor

and Parsoid from git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/Parsoid.git at June 6th, 2013 Zoglun (talk) 09:00, 6 June 2013 (UTC)

Hey! First off, you shouldn't use that version of VisualEditor ("VisualEditor 1.20 stable" is a fiction created by a script; it's not remotely appropriate to use - I'll get that removed).

If you git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git it is much more likely to work. In particular, Parsoid and VisualEditor make major changes to integrate with each other quite regularly, and they won't be able to talk to one another if you use such an old version of VisualEditor alongside a modern one of Parsoid.

Once you've done that, if you have any issues please ask again and I'll help you with them. Sorry for the confusion! Jdforrester (WMF) (talk) 20:33, 6 June 2013 (UTC)

Parity in versions with Parsoid (and node.js)

Could someone help clarify the dependency and versioning between VisualEditor and Parsoid? If a new build of VisualEditor is available (such as the release on June 6) does it require an updated build of Parsoid as well? Do these two inter-related projects require a lock-step update process? The requirements are a little fuzzy to me. (I could be looking in the wrong location as well). Ckoerner (talk) 17:26, 7 June 2013 (UTC)

Yes, in general you need to run master from VE and Parsoid at the same point (there are occasional times where there's incompatibility between masters, but we try our hardest to reduce these). This is what we mean by "it's not generally ready for real-world applications yet". Sorry for the confusion. Jdforrester (WMF) (talk) 18:47, 7 June 2013 (UTC)

Great, thank you for the clarification. Ckoerner (talk) 15:35, 11 June 2013 (UTC)

This was very helpful!

We installed the latest git masters of the VE and Parsoid and eventually got it working on the wmf alpha 'master' as of June 15. I'm not a programmer but my hosting provider has been quite helpful.

One question: If I am going to follow the development progress the next few months (exciting) by upgrading every week or so, should I get the Git VE and Parsoid + the Master WMF, or use the wmf10, wmf11, wmf12 etc.. are those releases more 'put together' then the master wmf dump I can select?

Thanks! MJurgens 18:24, 16 July 2013 (UTC)

It's probably best to take the wmf* branches of MW core, yes; this will avoid the (very occasional) times where we might be broken against master but not branches. Jdforrester (WMF) (talk) 15:52, 18 July 2013 (UTC)

Enable VisualEditor for 'create' page

Any suggestions for turning on the visual editor for as the default for creating a page?

It still defaults to the old editor.

Still experimenting. Great work everyone. MarkJurgens (talk) 04:24, 11 June 2013 (UTC)

If you have VisualEditor switched on, you should get "Create" and "Create source". The first takes you into VisualEditor, the second to the wikitext editor. Does this not show up for you? Jdforrester (WMF) (talk) 15:30, 12 June 2013 (UTC)

Almost, the visual editor is available as an option, and works when I click on the tab. However it defaults to the edit source.

Here's my localsettings:

require_once("$IP/extensions/VisualEditor/VisualEditor.php");
## Visual Editor Settings:
// Create VisualEditor namespace
define( 'NS_VISUALEDITOR', 2500 );
define( 'NS_VISUALEDITOR_TALK', 2501 );
$wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor';
$wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk';
// Allow using VisualEditor in the main namespace only (default)
$wgVisualEditorNamespaces ['*'];
// $wgVisualEditorNamespaces = array( NS_MAIN, NS_TALK, NS_USER, NS_USER_TALK );
// Restrict VisualEditor to the VisualEditor namespace
//$wgVisualEditorNamespaces = array();
//$wgVisualEditorNamespaces[] = NS_VISUALEDITOR;
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';

MarkJurgens (talk) 21:12, 18 June 2013 (UTC)

I have the same request. Creating pages through a link or through the search box always loads the markup editor, and you have to change to VE manually with the "create" tab. This behaviour is very confusing for my users. By the way, preloading a template also doesn't work with VE. 129.215.139.112 16:24, 17 March 2014 (UTC)

Hello, I also work on this issue.

I developed a special page extension for creating an article. The user has to type the name of article, then after a search (checking if already exists) user select a template and click create. Behind "create" there's this link 'http://yourmedia.wiki/index.php?title=[ARTICLE_NAME]&veaction=edit&redlink=1'. So, the visual editor will start and the user can create content.

But the preloading of templates also doesn't work. With the standard eitor this was easy by using NewArticleTemplate extension. But the used hook 'EditPage::showEditForm:initial' doesn't work with VE. Can anyone help? Otherwise I implement an work-around (some 'Javascript magic'). 139.30.7.108 12:14, 14 April 2014 (UTC)

If you have a workaround, that would be great. I have the same issue, and it would be enough if an extension just creates and saves a new page by copying the template, and the user then can click on "edit" to actually modify it. This would solve both problems (that VE isn't default, and it doesn't handle templates). Is it possible to copy a page using URL parameters? Stephan Matthiesen (talk) 07:28, 15 April 2014 (UTC)

I implement an extension for this issue. Actually, it's based on MediaWiki WriteAPI which is not a good solution because it makes it easy for automatic editing by bots. But it works. The user chooses a name and a template from a list and click create. In background AJAX is used to get MediaWiki text from choosen template and then creates the page by using the WriteAPI (where you give template text as a parameter). Finaly, the user is automatically forwarded to the new page with opened visual editor. 139.30.7.108 14:19, 25 April 2014 (UTC)

Is this extension available somewhere? Sounds useful and I'd like to test it. Stephan Matthiesen (talk) 05:51, 6 May 2014 (UTC)

I would also like to test this extension... Noti1234 (talk) 11:47, 31 May 2014 (UTC)

I have implemented the following crude hack into the top of my index.php:

if($_GET['redlink']==1 && $_GET['action']=='edit') {
	header('Location: index.php?title='.$_GET['title'].'&veaction=edit&redlink=1'); 
	die();
}

Hope this helps someone. 86.21.250.65 11:43, 14 August 2014 (UTC)

Thanks for your workaround. It works well! 118.69.216.234 04:13, 22 August 2014 (UTC)

Thanks for that, it's a great workaround! Noboddy (talk) 09:25, 13 April 2015 (UTC)

Hi - is this suppose to be placed in the index.php of the wiki folder? I did that and got all kinds of errors. 65.60.117.82 22:57, 12 May 2015 (UTC)

Nevermind I figured out how to do it. You can't simply use that code, you have to modify it to first check if the page even has those tags in the url.

this works

if(isset($_GET["redlink"]) && isset($_GET["action"])){

$clicked_edit_link = ($_GET["redlink"]);

$action_doing_now = ($_GET["action"]);

if($clicked_edit_link==1 && $action_doing_now=='edit')

{ header('Location: index.php?title='.$_GET['title'].'&veaction=edit&redlink=1');

die();

}} 65.60.117.82 00:04, 13 May 2015 (UTC)

All you need is to modify (noarticletext) message at Special:Allmessages - just replace action=edit by veaction=edit Vedmaka★ 11:41, 29 May 2015 (UTC)

Thanks! That works great for creating pages based on what you type in the URL (ie: www.example.com/wiki/newpage123). But it does not work if you type "newpage123" in the search box. If you want to be able to create pages from the search box using Visual Editor, you would also have to edit the special message MediaWiki:Searchmenu-new

Here is what I came up with for that:

<nowiki><strong>[{{fullurl:$1|veaction=edit}} Create the page "$1"] on this wiki!</strong> </nowiki>&lt;/pre&gt; [[User:Potrod|Potrod]] ([[User talk:Potrod|talk]]) 06:06, 5 June 2015 (UTC)
:::{{FlowMention|Vedmaka}} & {{FlowMention|Potrod}}'s suggestions worked well for me. I recommend this method. [[User:Ianmelchior|Ianmelchior]] ([[User talk:Ianmelchior|talk]]) 20:14, 28 March 2016 (UTC)
:::for me too!!! S2 [[Special:Contributions/177.69.223.132|177.69.223.132]] ([[User talk:177.69.223.132|talk]]) 13:28, 9 March 2018 (UTC)
::{{FlowMention|Vedmaka}}{{FlowMention|Potrod}} any idea how to also make VisualEditor the default when clicking on a red link to create a new article? [[User:Ianmelchior|Ianmelchior]] ([[User talk:Ianmelchior|talk]]) 19:48, 4 April 2016 (UTC)
::There was an [https://www.mediawiki.org/w/index.php?title=Extension%20talk%3AVisualEditor/2013#c-86.21.250.65-2014-08-14T11%3A43%3A00.000Z-Noti1234-2014-05-31T11%3A47%3A00.000Z idea above] that seemed to work for some people. [[User:Potrod|Potrod]] ([[User talk:Potrod|talk]]) 20:17, 5 April 2016 (UTC)
:::@Vedmaka's tip and the code above worked for me and seems to cover all bases (page creation via a redlink, search or URL). The code above works fine when placed in the LocalSettings.php (instead of index) but you need to check for the existence of all $_GET parameters with <code>isset($_GET['var'])</code>. Here is the final result:
:::<syntaxhighlight lang='text'>
# A hack that redirects users to the visual editor when clicking a redlink rather that to the wikicode editor.
if(isset($_GET['redlink']) && isset($_GET['action']) && isset($_GET['title']) && $_GET['redlink'] == 1 && $_GET['action']=='edit') 
{
	header('Location: index.php?title='.$_GET['title'].'&veaction=edit&redlink=1'); 
	die();
}

Tinss (talk) 19:17, 20 April 2017 (UTC)

Thanks Tinss. Your solution solved my problem too.

Kevin 163.8.84.67 (talk) 04:00, 11 September 2018 (UTC)

Note that this is now supported in VisualEditor-MediaWiki master (as will come out for compatibility with MW 1.27.0). Jdforrester (WMF) (talk) 23:26, 7 April 2016 (UTC)

How is it supported? Quinnj09 (talk) 17:59, 22 March 2017 (UTC)

@Ianmelchior Maybe a little late to the party. I am using Mediawiki 1.27.1 stable and to set visual editor as default for redlink I write a hook on LinkBegin. Hope it helps someone.

public static function onLinkBegin( $dummy, $target, &$html, &$customAttribs,

&$query, &$options, &$ret ) {

if ( in_array( 'broken', $options, true ) && empty( $query['action'] )

&& $target->getNamespace() !== NS_SPECIAL ) {

$ret = Html::rawElement ('a', ['href' => $target->getFullURL('veaction=edit&redlink=1'), 'class' => 'new'], $target->getPrefixedDBKey());

return false;

}

return true;

} Baongoc124 (talk) 09:38, 27 October 2016 (UTC)

Great idea @Baongoc124! But your code as is does not quite work as it needs to be hooked to the event ($wgHooks['LinkBegin'][] = 'onLinkBegin';) and would not display the correct link text. Here is an improved and simplified version:

# A hack that redirects users to the visual editor when clicking a redlink rather that to the wikicode editor.
function onLinkBegin( $dummy, $target, &$html, &$customAttribs, &$query, &$options, &$ret ) 
{
	if ( in_array( 'broken', $options, true ) && empty( $query['action'] ) && $target->getNamespace() !== NS_SPECIAL ) 
	{
		$query['veaction'] = 'edit';
		$query['action'] = 'view'; // Important! Otherwise MediaWiki will override veaction.
		$query['redlink'] = '1';
	}
	return true;
}
$wgHooks['LinkBegin'][] = 'onLinkBegin'; // WARNING! Will be superseded by HtmlPageLinkRendererBegin in MediaWiki 1.28.

Note: to cover all bases, you still need to modify the noarticletext message as @Vedmaka suggested. Tinss (talk) 19:21, 20 April 2017 (UTC)

I have done this job with a little java script placed in page MediaWiki:Common.js

if ( wgArticleId === 0 && wgAction === 'edit' )

{

window.location = 'index.php?title=' + wgPageName + '&veaction=edit&redlink=1'; }

It works for me. Hope it helps! 213.33.71.5 (talk) 10:47, 8 February 2017 (UTC)

Based on @Tinss answer, here is a hook using HtmlPageLinkRendererBegin that can be added to LocalSettings.php:

# Default to VisualEditor for red links
class MyHooks {
	public static function onHtmlPageLinkRendererBegin($linkRenderer, $target, &$text, &$extraAttribs, &$query, &$ret) {
		$title = Title::newFromLinkTarget($target);
		$isKnown = $title->isKnown();
		if (!$isKnown) {
			$query['veaction'] = 'edit';
			$query['action'] = 'view'; // prevent MediaWiki from overriding veaction
		}
	}
}
$wgHooks['HtmlPageLinkRendererBegin'][] = 'MyHooks::onHtmlPageLinkRendererBegin';

RobertoTH (talk) 14:24, 30 November 2017 (UTC)

Excellent work guys! This thread solved all my redlink problems XD Here is a shortened version of the snippet for those like me who don't like any fat in their code.

$wgHooks['HtmlPageLinkRendererBegin'][] = function ( $linkRenderer, $target, &$text, &$extraAttribs, &$query, &$ret ) {
	$title = Title::newFromLinkTarget( $target );
	if ( !$title->isKnown() ) {
		$query['veaction'] = 'edit';
		$query['action'] = 'view'; // Prevent MediaWiki from overriding veaction
	}
};

Sophivorus (talk) 22:00, 28 June 2018 (UTC)

Thanks to @Beatlicker from the post Enable All Name space see this --> Project:Support desk/Flow/2015/09#h-Enable_all_namespaces_for_VisualEditor-2015-09-25T10:57:00.000Z

Add blow lines to your LocalSettings.php page

$wgVisualEditorNamespaces = array_merge( $wgContentNamespaces, array( NS_USER, NS_CATEGORY ) );

$wgVisualEditorAvailableNamespaces = [

    NS_MAIN => true,

    NS_USER => true,

NS_HELP => true,

    "_merge_strategy" => "array_plus"

];

If you need other standard namespace see Help:Namespaces to added standard that enable VisualEditor all the pages. Hope this Helps. Aravind2905 (talk) 06:15, 13 August 2018 (UTC)

This did not work, is there more to the instructions?@Aravind2905 2001:4641:F835:0:5CFB:CDD6:6C21:37BA (talk) 20:13, 27 February 2019 (UTC)

What are you trying to achieve? If it's enabling the Visual Editor for the create page, put Sophivorus' code at the bottom of LocalSettings.php. Tinss (talk) 23:48, 27 February 2019 (UTC)

Installation difficulties

I've installed VisualEditor, however, at the moment cannot install Parsoid as I don't have internet access on said computer. However, when I install it nothing different happens. Nothing new shows up, etc. I've edited localsettings with the requireonce and such, but can't for the life of me get it to work. Any help? 169.252.4.21 05:30, 18 June 2013 (UTC)

The most common reason is if you're running a version of MediaWiki core that's too old; for browser support, we made a change to core MediaWiki's Javascript library that deals with browser feature detection. Currently VE fails silently if that code isn't available, which we should fix. Sorry for this. :-( Jdforrester (WMF) (talk) 16:14, 18 June 2013 (UTC)

Thanks for the response! However, I don't think that's the issue, I'm running MediaWiki 1.21. 114.6.22.11 06:23, 19 June 2013 (UTC)

Sorry, I should have been more specific; you need MediaWiki 1.22 alpha wmf 3 (or later) to use VisualEditor right now. Jdforrester (WMF) (talk) 15:43, 19 June 2013 (UTC)

I think it would be a good idea to add that as a notice to the installation instructions.

I was looking for a solution to the problem for a while now. Mastergalen (talk) 22:23, 3 July 2013 (UTC)

Sorry about that - done. Jdforrester (WMF) (talk) 15:43, 5 July 2013 (UTC)

parsoidserver-http-bad-status: 500

I'm using 1.22wmf9.

And my VisualEditor and Parsoid are downloaded from GIT, but my wiki keeps going into ERROR 'parsoidserver-http-bad-status: 500'.

The error from the server says "TypeError: Cannot set property '0' of null at Object.WikiConfig (……\Parsoid\js\lib\mediawiki.WikiConfig.js:52:29)"

In addition, my wiki and Parsoid don't share a same server.

Wiki (Linux) is on http://thwiki.cc/api.php

Parsoid (Windows) is on http://mc.bibi.im:8000/ JoesSR (talk) 05:14, 30 June 2013 (UTC)

I'm also getting this error after upgrading from wmf4 to wmf9. I also updated the parsoid and visual editor.

The editor worked great up until that point. I was trying to upgrade the editor to use see the 'insert media' option. Are all the git repositories updated properly?

Error loading data from server: parsoidserver-http-bad-status: 404. Would you

like to retry?

However when I create a NEW page, the visual editor works initially (without the insert media option, and but throws an error when I try and save "Error Loading data from server: Unsuccessful request, error contacting the Parsoid server.

Can we check that the release tarballs are okay?

Could this be page caching related? Is it possible to purge the system in someway? This is a new install. MarkJurgens (talk) 14:03, 9 July 2013 (UTC)

I installed the latest alpha of wmf-master (July 9)

Latest Visual editor master

I'm still getting this error when editing:

Error loading data from server: parsoidserver-http-bad-status

However, when I create a new page, the editor loads, but does not let me save the page.

Error: Error contacting the Parsoid server

Is there anything wrong with the way I'm linking to parsoid?

$wgVisualEditorParsoidURL = 'http://www.sitename.com:8000/';

$wgVisualEditorParsoidPrefix = 'sitename.com';

The actual wiki is in /wiki directory www.sitename.com/wiki/

So close!

Any help? MarkJurgens (talk) 17:32, 9 July 2013 (UTC)

the same problem I have met too, hope it be solved as soon as possible. Andytao (talk) 12:52, 15 July 2013 (UTC)

I have same trouble.

After installing node ver 0.8.22 problem was solved 62.168.240.26 07:54, 31 July 2013 (UTC)

mine cannot be fixed after installing node v0.8.22. any more suggestion? 115.220.94.123 02:26, 4 August 2013 (UTC)

I have the same error, in the npm i see the next error log:

PS C:\xampp\htdocs\extensions\parsoid\js\api> node server.js
 master loading...
 - master ready
 - worker(3564) loading...
 - worker(4364) loading...
 - worker(6076) loading...
 - worker(3564) ready
 - worker(3124) loading...
 - worker(4364) ready
 - worker(6076) ready
 - worker(5756) loading...
 - worker(3124) ready
 - worker(5756) ready
non-200 response: 404
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>Object not found!</title>
<link rev="made" href="mailto:postmaster@localhost" />
<style type="text/css"><!--/*--><![CDATA[/*><!--*/
    body { color: #000000; background-color: #FFFFFF; }
    a:link { color: #0000CC; }
    p, address {margin-left: 3em;}
    span {font-size: smaller;}
/*]]>*/--></style>
</head>
<body>
<h1>Object not found!</h1>
<p>
The requested URL was not found on this server.
If you entered the URL manually please check your
spelling and try again.
</p>
<p>
If you think this is a server error, please contact
the <a href="mailto:postmaster@localhost">webmaster</a>.
</p>
<h2>Error 404</h2>
<address>
  <a href="/">localhost</a><br />
  <span>Apache/2.4.4 (Win32) OpenSSL/0.9.8y PHP/5.4.16</span>
</address>
</body>
</html>
ERROR in localhost:Parsoid:
Page Fetch failure for null
Stack trace: DoesNotExistError: Page Fetch failure for null
worker 5756 died (1), restarting.
 - worker(4632) loading...
 - worker(4632) ready

200.14.107.2 16:03, 30 September 2013 (UTC)

¿Did you fix this? I've the same error. 201.231.129.71 15:06, 28 February 2014 (UTC)

I have the same error. And when I retry as suggested, I alternatively get this error :

parsoidserver-http-bad-status: 401

Thanks for any help. Dieudo (talk) 06:34, 3 March 2014 (UTC)

i have the same error 186.87.73.221 16:12, 3 March 2014 (UTC)

I fixed 404 parsoid error by editing parsoid\api\localsettings.js parsoid config file. I run mediawiki under webmatrix so I changed url to mediawiki api:

parsoidConfig.setInterwiki( 'localhost', 'http://localhost:49136/api.php' ); GeorgeRu (talk) 13:29, 9 March 2014 (UTC)

I have the same issue. Error loading data from server: parsoidserver-http-bad-status: 500. Would you like to retry?

I think everything is setup as it should. Server on port 8000 works in browser. api.php is accessable... Tried different versions of mediawiki and VisualEditor. Running on Windows server.

Any suggestions? Can I find some log data somewhere? From node?

LocalSettings.php

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

$wgVisualEditorParsoidPrefix = 'localhost';

LocalSettings.js for Parsoid

parsoidConfig.setInterwiki( 'localhost', 'http://mydomain.com/wiki/core/api.php' ); 81.91.3.6 14:15, 1 July 2014 (UTC)

Make sure these files are configured correctly, I fixed my error 404 with these settings

/etc/mediawiki/parsoid/settings.js

exports.setup = function( parsoidConfig )

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

parsoidConfig.serverPort = 8000;

};

/var/www/html/LocalSettings.php

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

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

$wgHiddenPrefs[] = 'visualeditor-enable';

$wgVisualEditorParsoidURL = 'http://127.0.0.1:8000'; Londonx (talk) 08:40, 10 February 2016 (UTC)

Beta on Wikipedia

Wikipedia has this up. Looking forward to it getting nailed down!

Is this eventually going to become standard on Mediawiki? Varkman (talk) 21:55, 2 July 2013 (UTC)

Yes, we hope that it will be standard, though right now it requires a nodeJS service as well to work (Parsoid), so we're looking at what options we can offer general MediaWiki users. Jdforrester (WMF) (talk) 15:29, 3 July 2013 (UTC)

Is picture search in VE wikicommons only?

No.

I've installed VisualEditor and Parsoid on my CentOS 6.x-server and everything is up and running quite nicely. When I try to add pictures it seems that the picture search automatic searches wikicommons and not my own uploaded pictures in my local mediawiki installation. And when I add pictures it only reefers to the file name, as it should do with wikicommons - if I where editing on wikipedia.

Can I change this anywhere in the VE beta?

MyOnlyEye Myonlyeye (talk) 06:53, 3 July 2013 (UTC)

I found something that worked in:

modules/ve/init/mw/ve.init.mw.Platform.js: { 'url': '//commons.wikimedia.org/w/api.php' }

I changed the URL to my own wiki (and path to api.php) and then it worked quite well.

I _love_ this editor! Thanx! MyOnlyEye (talk) 10:01, 3 July 2013 (UTC)

Sorry, you're right, we need to factor that out of our code - I've created a bug about this. Glad you like it generally! Jdforrester (WMF) (talk) 15:28, 3 July 2013 (UTC)

Now it doesn't search in commons, but it doesn't find images in the local directory either. Do I have to set anything, besides the usual image upload enable stuff ($wgUploadDirectory, $wgUploadPath)? This is 1.23wmf10. Stephan Matthiesen (talk) 12:05, 11 January 2014 (UTC)

Hi, i try to do the same.

i'm in local wiki, i found this line of code in VisualEditor/modules/ve-mw/init/ve.init.mw.Platform.js,

but not understand how to modify it to work for me.

My local media are in http:localhost/media directory

the api for my wiki are in http:localhost/wiki/api.php

this is right?

this.mediaSources = [

{ 'url': mw.util.wikiScript( 'api' ) },

{ 'url': '//localhost/wiki/api.php' }

];

and then what i do?

thank's for help and sorry for my poor english! 81.208.38.27 09:56, 19 September 2013 (UTC)

Extension talk:VisualEditor/2013#c-81.208.38.27-2013-09-19T09:56:00.000Z-Myonlyeye-2013-07-03T10:01:00.000Z

test 81.208.38.27 15:14, 19 September 2013 (UTC)

VisualEditor now no longer hardcodes the reference to Wikimedia Commons. Instead it uses whatever media repositories your wiki server is configured to use.

Make sure you have InstantCommons / $wgUseInstantCommons set up in your LocalSettings. You needed this step already (previously VisualEditor would let you search Commons, but it would break while saving if you don't actually have it configured on the server-side in LocalSettings).

Now VisualEditor detects this configuration automatically and searches any and all media repositories you have configured. Krinkle (talk) 19:12, 16 January 2014 (UTC)

User:Krinkle is correct. For clarification you can have $wgUseInstantCommons set to false if you choose not to use Wikimedia Commons in your wiki. Ckoerner (talk) 19:56, 16 January 2014 (UTC)

My problem is that it doesn't search the local media directory. Uploading is enabled; $wgUploadDirectory and $wgUploadPath are set. Do I also have to define the local directory as a media repository somehow? Stephan Matthiesen (talk) 16:58, 18 January 2014 (UTC)

User:Stephan Matthiesen - Id start here Manual:Configuring_file_uploads if you haven't already. Make sure the w/images/ directory is writable and that $wgEnableUploads is set to true. Ckoerner (talk) 14:56, 20 January 2014 (UTC)

Yes, well, as I said, uploading is enabled, the directory writeable etc and I have absolutely no problem uploading files or including them with Wiki markup. The only problem is that the Visual Editor (1.23wmf11) doesn't find them through the media dialogue. Stephan Matthiesen (talk) 15:45, 20 January 2014 (UTC)

I have the exact same problem, it only works with the commons files, and not the local files located in /var/www/mediawiki/images/, doesnt search, unable to add picture (media) to the articles through VisualEditor 131.116.254.197 14:50, 28 January 2014 (UTC)

Has this problem been identified as a bug anywhere? Or fixed?

I'd like to try and install it again soon with a 1.23x, but that little bug makes it unusable on us little 3rd party sites.. :( MarkJurgens (talk) 03:10, 18 February 2014 (UTC)

I'm running 1.23wmf11 and the latest build of VisualEditor. I can confirm that the "Insert Media" dialog in VisualEditor does return local w/images results out-of-the box. Ckoerner (talk) 22:40, 18 February 2014 (UTC)

I am running 1.23wmf14 mediawiki and visual editor and it does kind of search local images, but for some reason doesn't return what expected. For instance, I have an image called "Caisson Platform II.jpeg" and another "Caisson Platform.jpg". If I search for platform, only "Caisson Platform II.jpeg" is returned. If I search for caisson, both are returned! I have no idea why. Could it be something to do with the database indexing the files? I'm not sure if it's related but the special pages "Gallery of new files" and "File List" searches never retrieve anything whatever I put in.

Also, it would be great to show the top 50 images or so by upload date by default. And of course to have uploading integrated in the visual editor. Plectrum20 (talk) 16:40, 20 February 2014 (UTC)

Something to do with file extension, type the exact name including extension "Caisson Platform.jpg", or "Platform.jpg". I think it's a bug. Alacn1 12:26, 28 November 2014 (UTC)

@Plectrum @Alacn

I set up a wiki in our intranet and have the same problem. But the name or file extension has nothing to do with this bug.

The reason "platform" works fine in "Caisson Platform II.jpeg" is the space between "platform" and "II.jpeg".

The other file has only the space between "Caisson" and "Platform".

The same problem occurred when I added some logos of our customers. Everytime I named the pictures "logo xyz.jpg" I found them by searching for "logo" but not when a searched for "xyz". Vice versa, when I named the file "xyz logo.jpg" I found the file searching for "xyz".

I don't know why this function works correct when you search Commons. With 2 letters you find results with the searched value inside of a word.

But for local files this functions don't work.

Is this bug (and method) already known and possibly fixed? 217.91.231.179 15:45, 8 January 2015 (UTC)

Bug 61151 was filed about this, but was a false report based on the search API being un-intuitive. I'm pretty sure it should work out-of-the-box with InstantCommons off, as it does for me. Jdforrester (WMF) (talk) 01:47, 19 February 2014 (UTC)

More details: The problem occurs on a private wiki. It works fine when $wgGroupPermissions['*']['read'] = true; but when it is set to false then images are not found in the media selector.

My relevant permissions settings are:

$wgGroupPermissions['*']['read'] = false; # works for true

$wgGroupPermissions['*']['edit'] = false;

if ( $_SERVER['REMOTE_ADDR'] == "127.0.0.1") {

$wgGroupPermissions['*']['read'] = true;

$wgGroupPermissions['*']['edit'] = true;

}

The if condition allows VE local access (I also tried cookie forwarding with same results).

When I set the first line to true, it works. Two questions:

• Why does the VE image selector not use the permissions for local access from inside the if statement?
• Is there any setting that gives VE specifically access to the images without opening the whole Wiki?

Thanks Stephan Matthiesen (talk) 12:55, 21 March 2014 (UTC)

I created a bug about this. Stephan Matthiesen (talk) 08:50, 31 March 2014 (UTC)

Editor does not always search local images "out of the box", both my installations (local and webserver) have no integration of local search. The webserver one is private, the local one is public, and both VE's have no access.

Even more interesting in this is that the VE on the private wiki can't even see the already linked files, meaning when I edit a page that has a file linked in it, it disappears within the editor. Checking some logs states that the parsoid service produces API Errors, but everythin else works, including creating, deleting and editing articles with the VE. Permission checks on the images-floder have been run, owner is set correctly, parsoid is installed as a service that works nicely and cookies are being forwarded correctly, but still - nothing.

Don't know if this is still the same bug, but it seems to be something very similar. 46.237.215.30 10:09, 30 October 2014 (UTC)

Any updates regarding this topic? I too am having issues getting graphics to show up on a local wiki. Thanks. 221.241.135.146 03:38, 20 May 2015 (UTC)

I just realized that the media dialog is only looking for images with more than 4 characters. The user are looking for the images and do not find anyone.

I changed the title in ../iki/extentions/VisualEditor/modules/ve-mw/i18n/??.json - ?? (means your laguage) the visualeditor-dialog-media-title term so that user are aware of typing 4 chars and * to fin the images:

f.e foopicsfisrt.jpg, foopicssecond.jpg foopicthird.jpg

can be found with foof*

It would be fine if the editor could start with * and also accept search with one character without the * Knut Krüger (talk) 15:49, 14 September 2015 (UTC)

The three-characters-or-more config I think is done by the search system you're using, not by VisualEditor itself? Jdforrester (WMF) (talk) 15:54, 14 September 2015 (UTC)

I believe this issue is due to HOW visual editor is searching for the local images. In my case, while I have all instances of my settings correctly set up - images fail when I load visual editor (and work again when I close visual editor) Java console reports this is due to searching for these images at 127.0.0.1, so something somewhere is telling visual editor to search for local images at the loopback Ehartman2 (talk) 21:29, 12 October 2016 (UTC)

Installed but not displaying

I have installed the extension, and can see that it is installed if I go to: Special:Version; however, it just shows the basic text editor that is included in the MediaWiki. I am using MediaWiki version 1.21.1. Is it currently not compatible with this version? 66.7.112.4 20:27, 11 July 2013 (UTC)

you need to use 1.22 version Alpha 121.121.98.31 08:14, 12 July 2013 (UTC)

I also got same problem use mediawiki 1.19.1 last it works fine but now facing some but some issue, it shows install but not showing to enable enhanced in editing. 117.211.75.8 06:39, 4 November 2013 (UTC)

Stable Version - When?

Can you guys estimate when the extion will be stable? --Unsigned 93.184.128.25 09:38, 12 July 2013 (UTC)

We estimate that we will have a reasonably-solid version of VisualEditor available for people to re-use in a few months' time (certainly, by the end of the calendar year). Jdforrester (WMF) (talk) 15:29, 12 July 2013 (UTC)

Thanks! --Unsigned 93.184.128.25 09:19, 15 July 2013 (UTC)

Is the plan to continue the requirement for a Parsoid server, or do you intend to roll it all into php so it can be just hosted like older versions of MediaWiki (web server + database) ? Dangrec (talk) 23:32, 5 August 2013 (UTC)

We do not plan to make a PHP version of Parsoid (for language design reasons - PHP would be ridiculously slow to run Parsoid), no, sorry. However, we are hoping to eventually (probably next year) be able to provide a version of MediaWiki that does not need to store its contents in wikitext at all, which would mean that VisualEditor could edit "natively" without the need for Parsoid. Jdforrester (WMF) (talk) 10:16, 6 August 2013 (UTC)

Cool. Thanks for the info. Will there be a way to convert existing MediaWiki installs from wikitext to whatever the new standard is?

Is there a development blog or roadmap or something where I can follow these developments? Thanks again! Dangrec (talk) 18:07, 9 August 2013 (UTC)

VisualEditor on a private Wiki that requires login to both read and edit

I'm trying to run this on a wiki that requires login to both read and edit. It works if I configure the site to be visible to all users, but this isn't really a viable option for this wiki. Is there any way to let the parsoid service see the site, but deny all others unless logged in? If there was some sort of way to define the parsoid service, or localhost as a special user, group or bot, wouldn't it be possible to allow it to view the site while still shutting out all others who aren't supposed to view it? 193.213.227.242 07:19, 19 July 2013 (UTC)

Hear, Hear. for all those private wiki's.

like on the Collection extension, they solved it with $wgCollectionMWServeCredentials. 213.224.16.158 10:49, 23 July 2013 (UTC)

Could you please expand on this? 82.110.141.241 15:40, 24 July 2013 (UTC)

http://www.mediawiki.org/wiki/Talk:Parsoid#Running_Parsoid_on_a_.22private.22_wiki_-_AccessDeniedError 88.79.71.204 08:06, 12 August 2013 (UTC)

It seems to be solved today. (6 nov 2013).

I synced, but i have no clue how to set it up.

It doesn't work by just having the Master. Do i need to do something in LocalSettings?

Thumbs up for the entire project! 84.196.230.204 09:58, 6 November 2013 (UTC)

Will VisualEditor run on hosted servers?

Hi there,

as VisualEditor seems to rely on this Parsoid and node.js, it seems unlikely that I would be able to install it on my hosted environment (where I have no rights to install new binaries).

Is a solution in the making for such scenarios?

Would a remotely hosted public Parsoid be an option? Detlefs (talk) 14:15, 22 July 2013 (UTC)

VisualEditor itself does not depend on any hosted services. For application within MediaWiki it requires an HTML DOM. As long as we are storing wikitext as the canonical format and needing to convert it to an HTML DOM for VisualEditor, it will require a Parsoid service running. If a wiki would store HTML instead of wikitext, Parsoid would not be required. Depending on whether you want to allow people to edit in wikitext still, you'd still need Parsoid for the other way around, naturally. But I imagine it will be possible in the future to set up a new wiki (or convert an existing wiki) to only store and edit the HTML, so VisualEditor would not need a Parsoid service in that case.

VisualEditor nor Parsoid require the MediaWiki service to be on the same server, so yes a remotely hosted service is totally possible. However you'd need to find someone to run that. Krinkle (talk) 12:32, 23 July 2013 (UTC)

MyWikis now offers a Hosted Parsoid service that starts at $1/month. https://www.mywikis.com/hostedparsoid Grapetheratclerk (talk) 18:56, 9 December 2015 (UTC)

Why VisualEditor cann't contact to Parsoid correctly on windows?

I have deploy the latest MediaWiki 1.22 WMF 11 on windows test environment, the install process follow the install instructions completely, the edit and edit source button display correct, but cann't contact Parsoid, Why? anybody have solved this problem? 14.17.22.31 02:00, 26 July 2013 (UTC)

Have you installed and started Parsoid on an Linux server? Without Parsoid VisualEditor can not parse the Wikicode to a Visual Text. Florianschmidtwelzow (talk) 23:32, 27 July 2013 (UTC)

Custom Skin

Hello, on my private Wiki running MediaWiki 1.22/wmf12 i want to use (better provide) this great Extension to my users. The Wiki has a Custom Design very basically based on Vector, but edited :). Now the "problem" is, that VisualEditor for now only supports vector, monobook and apex. I gave it a try and added my Skins name to the $supportedskin in extensions hook file. The Extension is activated then on this skin, too. But it doesn't work good, the Main "Edit" Link in head is not shown (the Edit source isn't shown, too), but in the sections i can choose Edit or Edit Sourcecode, but by clicking "Edit" the site is loading (Parsoid parsed the site) and then the Site is shown normaly, without any VisualEditor Features.

I know, that VisualEditor is an experimental build, but know someone, which are the requirements to the skin, that VE is working correctly? Thanks! Kind regards Florianschmidtwelzow (talk) 15:40, 27 July 2013 (UTC)

In a newer Development version all function now :) Florianschmidtwelzow (talk) 15:19, 3 August 2013 (UTC)

VisualEditor not loading on 1.22/wmf11

I try to run VisualEditor on a 1.22/wmf11 Mediawiki site. Parsoid is running fine and shows that articles are parsed, but the Editor does not load, instead I just see the "K.I.T.T. bar". Any hint where to start debugging? 88.79.71.204 14:15, 9 August 2013 (UTC)

Preload

Is it possible to get the VisualEditor to observe the '&preload=Template' parameter in the url? Stefanclark (talk) 15:40, 19 August 2013 (UTC)

No, not currently; bug 49622 tracks us getting this done, however (and also for editintro). Jdforrester (WMF) (talk) 18:10, 20 August 2013 (UTC)

Code to enable in IE and Ipad (despite the temporary shut down on the main Wikipedia?)

Where in the code can I turn the editor back on for IE, and possibly mobile devices?

I know it might be buggy, but I'd like to experiment!

Thanks! MarkJurgens (talk) 13:57, 20 August 2013 (UTC)

If you append ?vewhitelist=true to the query URL, VisualEditor should load regardless of your browser (even if it fails our fundamental technology tests). However, there are reasons behind each of the blacklist-ings, so be careful - for example:

• Firefox 13 and 14 causes links to be turned from [[Foo]] to [[./Foo]], corrupting pages;
• Internet Explorer's security model means that the cross-server requests used to save the page don't work, so users can never save their work; and
• Android 2.x claims that it supports contentEditable, but then doesn't give you a keyboard, so users can't enter or interact with any content.

We only blacklist browsers that are known to break, and whitelist those that are known to work; other browsers, assuming they pass the feature tests, should "just work", with a note explaining that they may exhibit broken behaviour. Mobile browsers are generally in this last group, and so should be usable - though we've heard a few reports of issues (we've not been focussing on mobile and tablet users yet). If it's not working for you, some details would help me figure out why and see if we can fix it. Jdforrester (WMF) (talk) 16:13, 20 August 2013 (UTC)

Button configuration / site notice

On private wikis is there a configuration option, (or a part of the code to comment out) that will remove the 'beta' sign?

.. and possibly the LaTex button and Hieroglyphics.

Too many options too soon will be a bit much for my users. :) MarkJurgens (talk) 13:59, 20 August 2013 (UTC)

There isn't an option to remove the "beta" notice menu (though we may change that soon anyway, now that we have the welcome message), no. You could hack it out or over-ride the message.

The various extra buttons in the toolbar will (eventually) only appear if you have those extensions installed, and (soon) they will only appear in the "insert" menu in the toolbar rather than over-loading users with too many buttons. Jdforrester (WMF) (talk) 20:39, 20 August 2013 (UTC)

Opposite I wonder how to enable Latex option in the toolbar menu. How those extensions could be installed? 193.200.33.20 18:43, 13 October 2013 (UTC)

Uploading files?

I am using the latest master branch of Visual Editor incl. Parsoid server. Everything works fine except the handling of files like images. Using $wgVisualEditorEnableExperimentalCode = true; did not take any positive or negative effect.

Is it in general possible, to add files by drag&drop? Also, in the wiki, there are a lot of pictures, but I could not select any of them with the media browser.

Do you have any hints how to get them to work? 85.236.204.26 11:49, 21 August 2013 (UTC)

It is not yet possible to upload files inside VisualEditor; we are interested in building this, including drag-and-drop support, but it's not likely to be a priority for the next few months.

When you say that you "could not select any of [the images on your wiki] with the media browser", what do you mean? Did the images show up but selecting one did not insert it? Some of them didn't show up? None of them appeared? Jdforrester (WMF) (talk) 21:36, 26 August 2013 (UTC)

I'm not the original poster, but I'm experiencing the same issue, and when trying to insert an image, only images from wikimedia commons are shown – not files uploaded directly to the local wiki. 82.196.215.178 10:02, 9 December 2013 (UTC)

VisualEditor doesn't show: Error setting curl options

Hi there, thanks in advance for your attention and thanks for your amazing work on VisualEditor!

I'm trying to get VisualEditor to work with my MediaWiki but instead I get the following error via a popup in my browser:

internal_api_error_MWException: Exception Caught: Error setting curl options.

My configuration is:

MediaWiki 1.22wmf14

PHP 5.3.2 (apache2handler)

MySQL 5.1.46

VisualEditor (Version 0.1.0) (bdd1a73) 01:07, 30. Aug. 2013

curl 7.21.4

Any clue why curl or the api could be a problem here? MichaelD 12:11, 30 August 2013 (UTC)

I have the same message with 1.22wmf16 and trunk version (latest commit 29/8 17:42u). How can I find out what the problem is? 77.175.89.221 19:46, 8 September 2013 (UTC)

I have this problem too. 91.204.24.253 04:52, 23 September 2013 (UTC)

+1

PHP 5.3.27

Curl 7.15.5

with both MediaWiki 1.22wmf21 and current HEAD(708528039d0c3aeb6353f25fee9ba8af69dafddf) 77.255.58.181 17:23, 23 October 2013 (UTC)

As of this moment VisualEditor requires MediaWiki 1.22wmf21 and newer. Also make sure you keep Parsoid updated with the latest master as well - the two need to be updated at the same time. Ckoerner (talk) 16:16, 28 October 2013 (UTC)

Can't get the VisualEditor to start

I'm using 1.22wmf17 on Windows 2003/IIS6 w/ PHP 5.3.27. My database and Parsoid are set up on a separate Linux machine; I've verified that the wiki host can access Parsoid and that Parsoid can grab pages from my wiki. Other modules installed: SMW, Cite, MsUpload, ParserFunctions, SyntaxHighlight, MWSearch, TitleKey, Validator and WikiEditor. All are up to date.

My VE configuration matches that recommended by the VE installation guide. Special:VisualEditorSandbox is working.

When I click the 'Edit' tab on an article, I'm taken to WikiEditor. I do not have any other edit tabs, i.e. no 'Edit Source' tab. If I try to access the expected VE url directly, e.g. if I enter this in the address bar:<pre>http://mywiki/wiki/index.php?title=Article&veaction=edit</pre> The Article page loads but the editor does not start. I don't get a loading bar or anything.

What am I missing? This should work, right? 64.88.191.182 20:09, 22 September 2013 (UTC)

I notice that in VisualEditor\VisualEditor.php there is an external cmd section with node stuff. I have node installed on the wiki host, but I can't get all the Parsoid modules installed - contextify issue - which is why it's on a separate host. The documentation reads as if VE should still load and work in a read-only way w/o node or Parsoid though. Is this correct? 64.88.191.182 20:18, 22 September 2013 (UTC)

VisualEditor won't show - Running Mediawiki 1.22alpha (lastest snapshot from 2013-10-01) and latest snapshot of Visual Editor

Hi!

I installed a fresh copy of the latest Mediawiki on a new system and everything works fine. I want to test the new VisualEditor, but after following the installation instructions I can't get the VisualEditor to load. WHen editing any page it only shows the default editor. In Special:Version I can see that Visual Editor is installed (I installed it using git).

Perhaps I did something wrong in the config? I added the settings to localsettings.php exactly as specifed in the installation intstructions. perhaps something there needs to be changed?

require_once("$IP/extensions/VisualEditor/VisualEditor.php");
 
// OPTIONAL: Enable VisualEditor in other namespaces
// By default, VE is only enabled in NS_MAIN
//$wgVisualEditorNamespaces[] = NS_PROJECT;
 
// 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
//$wgVisualEditorEnableExperimentalCode = true;

Would be greatful for any tips! 82.196.205.190 13:28, 1 October 2013 (UTC)

By the original author:

After 12 hours of trying and failing to make the VisualEditor appear, I finally managed to do so. This was accomplished by changing the "server" variable in localsettings.php from a LAN-IP (192.168.1.6) to a valid internet domain and then by accessing the server from the internet.. So no the VisualEditor works. Downside, I cannot access the site locally anymore, but that might be that my (NAT) router, uses port 80 locally on the LAN for the router web-interface.. So trying to access the same domain name locally, just opens the router web-page, so whenever I try ot open the Mediawiki on my LAN, i just a 404 not found, coming from my Inteno Broadband router.. 82.196.205.190 13:57, 2 October 2013 (UTC)

Your wiki requires a logged-in account to access the API. Parsoid will not work for this wiki!

How can I use VisualEditor with Parsoid when I have a private wiki? 24.134.219.86 14:25, 21 October 2013 (UTC)

You can't yet, sorry. Jdforrester (WMF) (talk) 16:07, 21 October 2013 (UTC)

What is Parsoid and why is it incompadible with VisualEditor on a private wiki? Myrtonos (talk) 23:15, 27 October 2013 (UTC)

I can only answer half your question, but Parsoid is the backend system that allows VisualEditor to transform HTML markup to wikitext and vice versa. It is required for VisualEditor to function.

My guess as to why is doesn't work on a private wiki? I believe that Parsoid does not have any authentication schema in place. It can't access the wiki because it can not authenticate as a user - something required in a private wiki. Ckoerner (talk) 16:13, 28 October 2013 (UTC)

This works now: Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis 2602:306:C5E1:EA50:D5AA:D9C:26A3:BF0C 17:05, 19 February 2014 (UTC)

Visual editor and templates

I've noticed that it is possible to transclude pages with visual editor, but either I have not figured out how to Substitute them, or it is still only possible with source editor. Myrtonos (talk) 23:19, 27 October 2013 (UTC)

This feature was requested on bugzilla:49904. Helder 16:20, 31 October 2013 (UTC)

Email notifications

What about email notifications and hooking? Hot to catch onArticleSaveComplete hook from another extension, e.g. 213.232.243.233 12:06, 13 November 2013 (UTC)

MediaWiki Required Version

Is there a reason VisualEditor now requires 1.23wmf2? I didn't see anything in the status updates stating what was changed in core that causes it to require the alpha development version. I would like to start testing on MediaWiki 1.22 with the idea of allowing my production users to try it, but it currently throws an exception stating "MediaWiki 1.23wmf2 required--this is only 1.22.0rc2". Jlemley (talk) 19:29, 2 December 2013 (UTC)

VisualEditor now uses mw.util.getUrl instead of the newly-deprecated mw.util.wikiGetlink as of this change, sorry. Jdforrester (WMF) (talk) 19:43, 2 December 2013 (UTC)

So does this also mean that the stable version will not be published before the end of the year, as it depends on a mediawiki version that won't be released before May? Or do you plan to release a branch that works with 1.22? That would be greatly appreciated. Stephan Matthiesen (talk) 17:09, 13 December 2013 (UTC)

One of the things we're going to talk about with the MediaWiki release managers when they come to San Francisco later this month for the Architecture Summit 2014 is how to proceed in back-porting non-security issues to older versions of MediaWiki; hopefully this will mean we can have VisualEditor work with a 1.22.x branch. Jdforrester (WMF) (talk) 09:08, 7 January 2014 (UTC)

No action when I clicked the 'edit' link

Parsoid is running, I'm able to parse the page by going to http://localhost:8000/localhost. When I'm on the Main Page of my wiki, nothing happens when I clicked on the edit link. Tommyheyser (talk) 20:37, 22 December 2013 (UTC)

Are you using the latest git? I had the same. I don't really understand it enough, but there was a commit a few days ago in which a lot of libraries were removed. As I understand it, they are supposed to be somewhere else now, but I haven't been able to figure out where they are and how to get them back. Anyway, the only thing that worked for me was to revert to the last working version with:

cd extensions/VisualEditor

git checkout c41b600 Stephan Matthiesen (talk) 13:07, 24 December 2013 (UTC)

I tried to move to the current wmf/1.22wmf9 branch. Still not working. Works fine on wmf8, even with MW on wmf9 but VE on wmf8. Standard MW installation, no other problems. Can some expert please explain what Commit: use submodel for VE core means, if we have to install/enable an additional module or what is needed to make it work again? Thank you. Stephan Matthiesen (talk) 09:22, 3 January 2014 (UTC)

Ok, I think I found out how to get the submodule:

cd extensions/VisualEditor

git submodule update --init

It would be good to add this information to the download instructions, but I'm not really sure what I'm doing here and don't know what else is implied, so it would be better if this is explained by somebody who understands the plugin system. Stephan Matthiesen (talk) 14:31, 3 January 2014 (UTC)

Thanks for the reminder – I've added this to the instructions. Sorry for not mentioning it earlier! Jdforrester (WMF) (talk) 08:46, 7 January 2014 (UTC)

When I click edit I get the progress picture but then nothing. Parsoid is working when I use it directly and I can see that Parsoid completed parsing. Any idea?

MediaWiki 1.22.2 (upgraded from 1.21.1) Windows 2008 R2 server, Chrome Kayvee (talk) 16:34, 13 February 2014 (UTC)

UPDATE: Found that when I remove my MediaWiki:Common.js it works. Not sure what is in there but at least I know where to look. Kayvee (talk) 10:40, 14 February 2014 (UTC)

Yes, if there's a fatal JS error in Common.js (or a user's gadgets/etc.) then VisualEditor won't load, because JS interpretation will have been aborted by the user's browser. Jdforrester (WMF) (talk) 01:43, 19 February 2014 (UTC)

Where is the common.js file in the directory tree?

We just installed the latest 1.23 master of everything and the edit button doesn't do anything. Parsoid service is running... 74.15.111.103 12:41, 7 March 2014 (UTC)

It is a page of your wiki, MediaWiki:Common.js.

HTH,

David Kayvee (talk) 13:07, 7 March 2014 (UTC)

Still nothing. Not even an attempt to refresh the page.

common.js wasn't created since it's a clean install, so I created the page and deleted the content. No effect (cache was cleared)

I'm still not sure I'm getting the right install. Using the git Master of everything? Instead of wmf16, wmf17 etc..?

To get Parsoid I'm going here:

https://git.wikimedia.org/log/mediawiki%2Fservices%2Fparsoid/f6f820f617878a0a360d6da15a925ed59d2b375c

The clicking the 'tree' at the right side of the last commit, and downloading that.

My hosting guys are tying valiantly to install it for me. I don't know what to tell them next. :(

We had it 'working' a few months ago under 1.22, it just didn't place local images properly so we couldn't use it yet. MarkJurgens (talk) 13:28, 7 March 2014 (UTC)

I'm having the same issue, and even moved to 1.23 Rel 1 to make sure I have the most up-to-date code. No javascript errors appear in the console (and I cleared common.js to be sure).

I traced the javascript with Chrome and found that the init is running, a bunch of .js and jquery sources load, and then... nothing. When I compared this same process with the MediaWiki site, I found that there were more sources loaded there. Perhaps there is another dependency that we are missing? Jlemley (talk) 02:55, 15 May 2014 (UTC)

Hi,

I see this post is 2 years old, I have the same issue now with 1,26 version. Is anythin clear with this?

Thanks 213.4.35.99 (talk) 15:29, 17 December 2015 (UTC)

Hi,

The same here, seems to be ramdom, not always happens.

Thanks in advance. 95.121.247.36 (talk) 10:50, 11 January 2016 (UTC)

Hello ,

I have a similar issue here as well, the edit link loads VE randomly after a few clicks and when it does I can work on VE and save the wiki article via Parsoid without a problem.

I used firebug to see what's going on when the VE doesn't load and I get the following error in the console:

TypeError: mv.libs.ve.targetLoader is undefined.   load.php (line 178)

I'm using version 1.26.

Thank you Jankarloz (talk) 16:03, 19 January 2016 (UTC)

I have this issue as well with mediawiki 1.37.1

It was working with error and today I can't even open the edit section. Idris, the wise (talk) 12:37, 23 February 2022 (UTC)