Extension talk:VisualEditor/2018

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.

Cant access wiki when add visual editor

I'm very new to all this. I'm installing mediawiki on my raspberry pi and trying to add the visual editor extension to it. I have installed wiki and parsoid, and they both seem to work fine. when i add the configuration to LocalSettings in media wiki however, specifically the extension line for visual editor I am no longer able to access the wiki as it wont load when i try and get onto it.

Has anyone got any suggestion or can help me on what could be causing this? 86.22.162.83 (talk) 23:53, 10 January 2018 (UTC)

HTML meta tags corrupting wiki pages when saved with VisualEditor

I recently upgraded PHP from 5.6.32 to 5.6.33 on Windows Server. This seems to have broken the VisualEditor or Parsoid. For SOME wiki pages only, when I save them with the VisualEditor, the content is cut off, and there is text such as the following:

<meta charset="utf-8" /> <meta property="mw:articleNamespace" content="0" /> [ ] <meta property="dc:modified" content="2018-01-12T18:05:44.000Z" /> <meta property="mw:revisionSHA1" content="27d6cb96b2749fa12625bff4fe0181947d5d61e4" /> <meta property="mw:html:version" content="1.2.1" /> <meta property="mw:data-parsoid:version" content="0.0.2" />

Basically I am losing chunks of my pages. But this does not happen on all pages. There doesn't seem to be anything special about these pages.

This occurred on mediawiki 1.29.2, but I have now upgraded mediawiki to 1.30.0 and the VisualEditor extension as well. The same problem is happening to the same pages.

Any help with this problem would be appreciated. I have turned off the VisualEditor for now.

Thanks. GnomeSkull (talk) 18:47, 12 January 2018 (UTC)

Do you by any chance have the 2017 wikitext editor installed and enabled? Whatamidoing (WMF) (talk) 19:03, 12 January 2018 (UTC)

According to my Special:Version page I have extension WikiEditor 0.5.1. Is that what you mean or what else should I look for? GnomeSkull (talk) 19:16, 12 January 2018 (UTC)

Extra info: I have upgraded node.js to v8.9.4. NPM is version 5.6.0. After upgrading those, I reinstalled parsoid from git, doing a fresh install, creating a new config.yaml. So everything is current now. The same problem with the meta tags is still happening as shown above. GnomeSkull (talk) 18:05, 15 January 2018 (UTC)

I am also experiencing this issue. Clean and up-to-date 1.30 install on a dedicated Windows 2016 Server Machine. Components installed are: node.js x64 8.94, Git x64 2.15.1.2, PHP 7.1, MySQL 5.7.

When saving a page, the bottom (whatever it may be) will be replaced by HTML meta tags the same way as GnomeSkull described. I've tried with the WikiEditor extension both enabled and disabled (no change).

This is what shows on the page revision (What it was is on the right-side, what it was changed to is on the left-side - this is from the undo page):

−	* [[Exchange:Create a New Distribution Group|Ex <meta charset="utf-8" /> <meta property="mw:pageNamespace" content="0" /> <meta property="mw:pageId" content="1" />  <meta property="dc:modified" content="2018-01-16T20:35:06.000Z" /> <meta property="mw:revisionSHA1" content="048709d3822257e25fa0a57f9796f0e70b2f015d" /> <meta property="isMainPage" content="true" /> ]]	+	* [[Exchange:Create a New Distribution Group|Exchange: Create a New Distribution Group]]
		+	* [[Office365: OneDrive]]

I suspect that the link title syntax is what may be causing the substitution 'somehow'. I moved the page to a new name (instead of using wrong titles with redirects), added a "buffer" chunk of text on the bottom of the page, and begun moving things around again. Seems stable but I know I'm speaking way too soon! Camxct (talk) 20:49, 16 January 2018 (UTC)

GnomeSkull, are you using any Wikipedia templates? I have a couple and it looks like some were attempting to call CSS styles from Wikipedia's MediaWiki:Common.css. Once I copied Wikipedia's MediaWiki:Common.css to mine, this issue went away. Camxct (talk) 15:24, 18 January 2018 (UTC)

Hi Camxct - thanks for the reply. I don't think I am using any such templates but how can I tell for sure? Some extra details would be helpful. Thanks again. GnomeSkull (talk) 22:05, 18 January 2018 (UTC)

Sure! Copy the source of the page: https://en.wikipedia.org/wiki/MediaWiki:Common.css and then paste that into MediaWiki:Common.css on your installation. Camxct (talk) 16:10, 22 January 2018 (UTC)

Hi Team,

I am also experiencing the same issue of meta property being added at the end of the page, if the page content is long.

I am running a clean Mediawiki 1.30 on Windows Server 2012 with PHP7.2, node.js 8.94.

I have copied source of MediaWiki:Common.css to muy installation, but it did not help

Thanks Kapil.bolli (talk) 15:34, 23 January 2018 (UTC)

Hi Camxct, thanks for the extra info. I copied the contents of Common.css to my own, but it made no difference. GnomeSkull (talk) 20:35, 23 January 2018 (UTC)

GnomeSkull, there are screenshots of the common editing environments at Editor.

What do the "Exchange:" and "Office365:" namespaces do, and are you having problems only if links like those are present? Whatamidoing (WMF) (talk) 22:59, 27 January 2018 (UTC)

They are not real namespaces, just regular pages. Perhaps that's something I completely overlooked and the copying of MediaWiki:Common.css was a coincidence! Welllllllp....... Camxct (talk) 09:18, 28 January 2018 (UTC)

I wonder if VisualEditor is failing to cope with "fake" namespaces. Does the problem always appear with such links? Whatamidoing (WMF) (talk) 16:30, 29 January 2018 (UTC)

Hi Guys, I am using the regular "Extension:WikiEditor" and then trying to use "VisualEditor"... not the "2017 wikitext editor". I don't have the problem appearing with "fake" namespaces. But what would you consider a fake namespace? Anything with a colon (:)? This doesn't seem to be my case. I even went through the trouble of stripping all the colons (:) from a problem page by editing the source (even URLs) and then editing with VisualEditor to test. The problem still occurred. For me it seems to be random. It does seem to happen on longer pages. GnomeSkull (talk) 16:46, 30 January 2018 (UTC)

Same result, I corrected the "fake" namespace issue and the parsing error with VisualEditor persists. Other WYSIWYG editors such as TinyMCE do not have this problem. I'm speculating that the issue may lay with Parsoid and/or the node.js installation(s). Camxct (talk) 03:31, 1 February 2018 (UTC)

I upgraded Parsoid and Node after I started having problems and it didn't help. I also upgraded PHP from 5.6.32 to 5.6.33 just prior to this problem appearing. Could this be a factor? I am thinking not as I see others are using PHP 7.1 and 7.2 and also having the same problem. GnomeSkull (talk) 14:13, 1 February 2018 (UTC)

Do you use your database in Binary or UTF-8 mode? I'm using UTF-8 currently so I wonder if that plus the length of the page has something to do with it. Camxct (talk) 18:53, 1 February 2018 (UTC)

In MySQL, the mediawiki database collation shows as 'utf8_general_ci'. If I look at the tables themselves, the majority show with collation as 'binary'. There are a 4 (comment, image_comment_temp, ip_changes, revision_comment_temp) showing as 'utf8_general_ci' though. And searchindex table is 'latin1_swedish_ci'. Don't know if any of that matters. GnomeSkull (talk) 18:39, 2 February 2018 (UTC)

This issue can be fixed by upgrading your PHP to 7.1.13 as it is a bug with the curl library. Curl library comes with PHP for Windows which requires you to update PHP instead of just the library.

More information: https://phabricator.wikimedia.org/T183356 204.40.130.136 (talk) 15:59, 6 February 2018 (UTC)

Ah, so it was the upgrade to PHP 5.6.33 that broke it after all. Presumably it will be fixed in a version 5.6.34. I will have to live without the Visual Editor until then. Unfortunately I am still supporting some legacy apps on the same server and can not upgrade to version 7 yet. Thank you for the info! GnomeSkull (talk) 18:55, 6 February 2018 (UTC)

For me it was a combination of the "fake namespaces" by using "index.php?page=FakeNamespace:Article_Title" formatting AND my PHP version to 7.2. I actually wound up rebuilding the installation completely using 1.31wmf.20 instead of 1.30, used a forward slash instead of a colon, and now everything works flawlessly! :) Camxct (talk) 01:12, 22 February 2018 (UTC)

I just upgraded PHP to version 5.6.34 and everything seems to be working fine now! GnomeSkull (talk) 16:46, 2 March 2018 (UTC)

VE exposes template parameters of sub-template

When creating an article page X from a template A and template A uses template B then the template arguments for B are shown in the VE of article page X.

Is this intended? The other editors do not expose sub-template parameters.

When changing a value of a sub-template B in article page X the change takes effect in the preview/visual editor window. However, after applying the change does not show on the resulting page!

Suggested behaviour: VE should not expose parameters of sub-templates. 92.230.128.148 (talk) 20:11, 16 January 2018 (UTC)

Can you please give a specific example, with links to the templates? It would help me write a simple list of steps to reproduce for the devs to test. Whatamidoing (WMF) (talk) 23:58, 27 January 2018 (UTC)

VisualEditor worked once.

After installing Mediawiki 1.30 using the tar.gz and VisualEditor using -b REL1_30 and Parsoid with APT;

I saw the VisualEditor popup and was able to switch once and use the editor once, after that I haven't been able to switch to the Visual Editor anymore

I've reinstalled VisualEditor and again was able to see the editor once but not any longer.

I see the following warning in the console 7 times each time I click Edit;

'Use of "mw.toolbar" is deprecated.'

I've looked around but don't see what mw.toolbar is replaced with instead.

I'm using Mediawiki 1.30 in combination with VisualEditor REL1_30, why is it trying to use deprecated functions?

Any help would be appreciated,

Thanks 70.66.150.29 (talk) 08:28, 20 January 2018 (UTC)

I've updated to the latest master branch for both Wikimedia and VisualEditor and after following the Visualeditor installation guide and editing LocalSettings.php I still do not see the VisualEditor

What settings does MediaWiki use to make the editor work like that.? 70.66.150.29 (talk) 09:09, 20 January 2018 (UTC)

$wgDefaultUserOptions['visualeditor-enable'] = 1; may have fixed it

I'm not sure at this point, there are conflicting articles and LocalSettings examples. 70.66.150.29 (talk) 11:37, 20 January 2018 (UTC)

How does e.g. $wgVisualEditorAvailableNamespaces work?

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 set the following to my "LocalSettings.php"

$wgVisualEditorAvailableNamespaces = [
        NS_MAIN => true,
        NS_USER => true,
        NS_EXTRA => true
        ];

What I expected was that VisualEditor is only available for the namespaces MAIN, USER and EXTRA. What is happening is that also the namespaces CATEGORY and FILE are available for editing with VisualEditor.

Changing the setting to the following does not change the set of available namespaces:

$wgVisualEditorAvailableNamespaces = [
        NS_MAIN => true,
        NS_USER => true,
        NS_EXTRA => true,
        '_merge_strategy' => 'array_plus'
        ];

So my question is: Which values are available to "_merge_strategy"? or What do I have to add to get VisualEditor only for the namespaces MAIN, USER and EXTRA?

Thanks for some insights. [[kgh]] (talk) 23:09, 20 January 2018 (UTC)

Doing something like the following does not change anything either:

$wgVisualEditorAvailableNamespaces = [
        NS_MAIN => true,
        NS_USER => true,
        NS_FILE => false,
        NS_CATEGORY => false,
        NS_EXTRA => true
        ];

Adding something like 'array_replace' to '_merge_strategy' does not work either. Currently I just do not get it. [[kgh]] (talk) 23:23, 20 January 2018 (UTC)

I believe the merge strategies are only available on extension.json. For the available values see Manual:Extension.json/Schema#Merge strategies.

Have you tried manipulating the value in an "extension function"? e.g.

$wgExtensionFunctions[] = function() {

unset( $GLOBALS['wgVisualEditorAvailableNamespaces'][NS_CATEGORY] );

};

(Code not tested) Osnard (talk) 12:36, 26 January 2018 (UTC)

Thanks for you info. @Tgr: came up with the decisive hint for easy configuring. This was probably too obvious. Current docu is pretty bad so I will improve that. The info about the merge strategies was very interesting too. So this is nothing for use in "LocalSettings.php".

That's how to enable and disable namespaces:

$wgVisualEditorAvailableNamespaces = [
        "File" => false, 
        "Category" => false, 
        "Extra" => true
        ];

[[kgh]] (talk) 22:01, 26 January 2018 (UTC)

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

curl error: 7

Dear All,
I have installed this extension and now I am getting the following error report when I try to open a nonempty page with the VisualEditor:

Fehler beim Laden der Daten vom Server: apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server. Soll der Vorgang erneut durchgeführt werden?

I can open nonempty pages vith the VE, but then I get this error report when I am trying to save the edit:

Etwas ist schief gelaufen

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

Parsoid/Troubleshooting doesn't help me a lot until now: e.g., what would be the positive result of

curl http://your-mediawiki-server/api.php

(http://localhost/mediawiki/api.php in my case)
and what the negative? and why should I set this URL in [my] /etc/mediawiki/parsoid/settings.js if I'm supposed not to have that file, but configure parsoid via /etc/mediawiki/parsoid/config.yaml (where I have set that URI btw)?
Thank you in advance!
Ciciban (talk) 16:03, 21 January 2018 (UTC)

uninstall and purge parsoid

install parsoid again 46.219.43.18 (talk) 12:44, 22 January 2018 (UTC)

Thanks for your answer.
It did not change anything :(
Yours, Ciciban (talk) 13:28, 22 January 2018 (UTC)

So, let's start from scratch with Parsoid/Troubleshooting.

My api.php is http://localhost/mediawiki/api.php, which is linked to /var/lib/mediawiki-1.30.0/api.php.
Consequently, I changed /etc/mediawiki/parsoid/config.yaml (btw, locate delivers two other files with this name: /usr/lib/parsoid/node_modules/service-runner/config.yaml and /usr/lib/parsoid/src/tests/mocha/test.config.yaml):
# uri: 'http://localhost/w/api.php'
uri: 'http://localhost/mediawiki/api.php'

curl -L http://localhost:8142/localhost/v3/page/

html/Hauptseite>curl.htm
leaves a html-page similar to my main page in curl.htm, plus it returns

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
Current 
                                 Dload  Upload   Total   Spent    Left  
Speed 
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--
100    62  100    62    0     0     79      0 --:--:-- --:--:-- --:--:--
100    62  100    62    0     0     79      0 --:--:-- --:--:-- --:--:--
    79 
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--
100  6140  100  6140    0     0   2970      0  0:00:02  0:00:02 --:--:--
 21928

to my console.

Is this, in the sense of Parsoid/Troubleshooting, the positive or the negative result, resp., what does this exactly mean?

Thank you in advance for your answers.
Yours, Ciciban (talk) 10:11, 24 January 2018 (UTC)

I am also having this trouble @Ciciban Did you ever find a fix? AslanFrench (talk) 20:32, 18 October 2018 (UTC)

@user:Thedonquixotic
Nope :(
Yours, Ciciban (talk) 09:29, 19 October 2018 (UTC)

I had this problem under Win10 as log as I haven't startet manually the parsoid server:

C:\Users\User\node_modules\parsoid> node bin/server.js

After that it worked. Mariuszjluther (talk) 20:53, 8 April 2020 (UTC)

O.k., Maybe I have just found a lead:

curl http://localhost/mediawiki/api.php

returns the source of api.php

curl https://localhost/mediawiki/api.php

returns: curl: (7) Failed to connect to localhost port 443: Verbindungsaufbau abgelehnt

So, how can I contact my localhost via https (and, could this solve my problem)?

Thank you in advance for your help.
Yours, Ciciban (talk) 11:38, 13 April 2020 (UTC)

I hoped I could solve the issue with mkcert localhost, but I still cannot reach api.php via https, neither via curl nor in the browser, whereas it does work both ways via http.
Any hints?
Yours, Ciciban (talk) 15:46, 13 April 2020 (UTC)

I got some steps ahead: I produced certificates with mkcert and activated https in Apache according to https://wiki.ubuntuusers.de/Apache/mod_ssl

Interestingly enough I got troubles with short urls:

curl https://localhost/mediawiki/index.php/Hallo

curl http://localhost/mediawiki/index.php/Hallo

curl http://localhost/wiki/Hallo

all deliver the source of my wiki page Hallo.

curl https://localhost/wiki/Hallo

delivers a 404 page. Ciciban (talk) 09:04, 14 April 2020 (UTC)

Is the extension TemplateData required

MW 1.27, I have a few templates in my new instance. When creating/editing a page, I go to Insert->Template, then I start typing in the text box but nothing is returned. When using the network inspector in developers tools, I see a call to a templatedata function which returns an error - of course, since TemplateData is not installed. Did i miss an option somewhere that says "Use templatedata"?

BTW, the reason why I picked MW 1.27 instead of the newer version is because it is the long term support version. Ti infotrad (talk) 12:30, 2 February 2018 (UTC)

I believe that it does not hurt installing this too and as it looks from your report it is even a hard requirement to avoid errors. This should be documented after confirmation. [[kgh]] (talk) 12:37, 2 February 2018 (UTC)

We've merged a fix for that particular broken-functionality. In the next release, it should no longer break that autocomplete to not have TemplateData installed. DLynch (WMF) (talk) 17:56, 22 February 2018 (UTC)

oldidnotfound: There is no revision with ID 4

New MW installation (1..30 stable) with only VE extension

VE is fully fuctional, no problems. before doing the below for the first time on a new installation.

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

localsettings:

wfLoadExtension( 'WikiEditor' );

$wgDefaultUserOptions['usebetatoolbar'] = 1;

$wgHiddenPrefs[] = 'usebetatoolbar';

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

$wgHiddenPrefs[] = 'wikieditor-preview';

wfLoadExtension( 'VisualEditor' );

// 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;

#$wgVisualEditorTabPosition = 'before';

$wgVisualEditorUseSingleEditTab = true;

$wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

$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'

);

//$wgVisualEditorParsoidForwardCookies = true;

$wgVisualEditorRestbaseURL = 'http://localhost:7231/localhost/v1/page/html/';

$wgVisualEditorFullRestbaseURL = 'http://localhost:7231/localhost/';

$wgVirtualRestConfig['modules']['restbase'] = [

  'url' => "http://localhost:7231",

  'domain' => 'localhost',

  'parsoidCompat' => false

];

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

Steps to recreate:

Create page and add content

take a backup in mysql of --all-databases

create new page or edit and existing page

restore mysql backup

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

now some pages wont work when you try to edit them (and VE is the editor which is loading)

here is the error:

Error loading data from server: oldidnotfound: There is no revision with ID 4.. Would you like to try again?

https://imgur.com/a/jLYSE

The ID seems to stay the same when the error appears even when edit different pages,

Also some pages now load blank when trying to edit them even though there is content to load into VE...

---

if I edit a page and switch to the wikieditor, then copy the contents, delete thhe page and recreate, it fixes the problem but I cannot do this for 100's of pages everytime I want to restore a MySQL backup!

--

I have also tried running update.php and some of the rebuild scripts but this didn't help

---

Please help me fix this, i've been trying to for a week and I cant backup or restore my real wiki otherwise all the pages break like this! Darknite999 (talk) 01:31, 4 February 2018 (UTC)

Change Parsoid port

Hi,

Alright, i just wanted to know, is there a way to change the port that parsoid uses? My host supports node.js apps but it has restrictions on what ports are open and the ports used by parsoid (8000,8142) are blocked and because they cannot unblock them (for security reasons) i am unable to complete the parsoid installation and have it be used with my mediawiki installation.

Any help is GREATLY appreciated.

Thank you! Tormentium (talk) 20:22, 5 February 2018 (UTC)

Hi Tormentium,

I think you need to talk to your network administrator about exactly what those "security reasons" are. https://isc.sans.edu/port.html?port=8142 doesn't give me any obvious reasons to be concerned. AIUI, the most typical approach that would result in both of those ports being blocked is a blanket blacklist of all ports except those few that the network administrator has been told are needed. (This is particularly popular when the IT staff has limited resources.) If that's the case, then you should be able to get these two added to the whitelist by explaining why you need them open.

That said, the software is open source, so theoretically you could change the numbers to whatever you wanted. Whatamidoing (WMF) (talk) 20:26, 22 February 2018 (UTC)

Hi

I also want to know the same thing. How can I change the port?

Because my server has 8000 and 8142 ports closed, so I have to use different port.

Maybe I can use,,,,

【web】

・http(80)

・https(443)

【FTP】

・ftp(21)

・ftp over ssl(21)

・ftp-data

【SSH】

・SSH(10022)

【mail】

・smtp (25、587)

・smtp over ssl(465)

・pop(110)

・pop over ssl(995)

・imap(143)

・imap over ssl(993)

Is it available on these ports?

Please help me..................... 41.222.180.180 (talk) 21:04, 27 February 2018 (UTC)

@Tormentium @Whatamidoing (WMF)

this is my experience regarding the port for Parsoid.:

I had to say that I am not expert in JSON nor parsoid, but I changed the port here:

FIle: \parsoid\lib\api\ParsoidService.js (folder where Parsoid is installed)

LINE: || parsoidConfig.serverPort || process.env.PORT || 8142;

My value was 8000 (I followed developer setup) and I changed to 8142 > worked

I changed to 8150 > worked

once you run the server with command node /bin/server.js from windows cmd, you should see the port:

read on: <port you wrote>

{"name":"lib/index.js","hostname":"<the name of your web host, apache>","pid":14548,"level":30,"levelPath":"info","msg":"ready on :8150","time":"2020-04-11T14:03:03.304Z","v":0}

I did not widely test, but only with curl and opening with browser

both success.

I hope this help MarcoFerra1979 (talk) 14:31, 11 April 2020 (UTC)

VisualEditor Error: Could not connect to the server

I've just installed MediaWiki 1.30 on Ubuntu 16.04 32-bit, and I've successfully installed Parsoid and RESTbase. The 8000 port for Parsoid and 7231 port for RESTbase are all accessible and can return the correct pages. But when I try to edit or create pages using Visual Editor, the message shows up: Error loading data from server: Could not connect to the server. I've read through the docs in MediaWiki and googled my problem, but it seems that no one has met this problem before.

Do anyone know how to solve this problem? Thanks for your help. 65.49.133.47 (talk) 12:17, 8 February 2018 (UTC)

I have the same problem... My MediaWiki is on Debian Server. 143.107.126.144 (talk) 16:51, 20 February 2018 (UTC)

How to enable the 2017 wikitext editor on a wiki (cross posted)

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.

---

How do I activate the so called "2017 wikitext editor" feature? [[kgh]] (talk) 15:00, 8 February 2018 (UTC)

At Special:Preferences#mw-prefsection-betafeatures on the wiki you want it enabled at. TerraCodes (talk) 16:12, 8 February 2018 (UTC)

Thanks for you reply, but this is about activating it on a wiki providing this mode. However I do not know what to set or even install to get there. Is there a configuration parameter, a software dependency (probably BetaFeatures?), etc. ... I am asking since I did not find the docu. [[kgh]] (talk) 17:13, 8 February 2018 (UTC)

Hi there,

If you want all users to have the 2017 wikitext editor available as a beta feature, install the BetaFeatures extension and add the following to your LocalSettings.php:

$wgVisualEditorEnableWikitext = true;

If you want all users to have the 2017 wikitext editor all the time, add the following to your LocalSettings.php:

$wgVisualEditorEnableWikitext = true;
$wgDefaultUserOptions['visualeditor-newwikitext'] = 1;
$wgHiddenPrefs[] = 'visualeditor-newwikitext';

There's not currently a proper preference for this, as we were waiting for the run of the beta feature before moving ahead with that, so it's not possible to configure it to be on by default but removable, sorry. Jdforrester (WMF) (talk) 18:33, 8 February 2018 (UTC)

Thanks for the info. This helps. Also found out in the meantime that installing the CodeMirror extension allows for wikitext syntaxhighlighting. Will document both on the extensions docu soon. [[kgh]] (talk) 23:37, 8 February 2018 (UTC)

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

the height and width of images is set in float (not integer) so, size i set doesn't apply

As you know, "You can resize an existing image by clicking, then moving the resize icon (the two-headed arrow on one or both bottom corners)."

However, when i resize image with visual editor, the height and width of images is set in float (not integer) so, size i set doesn't apply.

ex> after i moved resize icon, size was set in 400.32x300.54px.

but the image is shown in full size. (probably because size data type is float type?)

could you help me, please? Tgds003 (talk) 11:18, 9 February 2018 (UTC)

I can't reproduce this. When I drag to re-size, I only get whole numbers. I can't put decimals into the dialog box. When I edit the pixel size manually, it gets ignored or treated like a caption.

Can you tell me more about your setup? It'd be helpful to know about your browser/OS/skin/zoom, if you think it's about editing, or MediaWiki versions/installation details if you think it's about your wiki's configuration. Whatamidoing (WMF) (talk) 18:57, 2 March 2018 (UTC)

Drag and drop any other file extension (not just image)

My apologies if this has been eventually already discussed (I was not able to find any specific thread on this). Is there any support (or is eventually plan for implementation) in order to allow drag and drop in Visual Editor of files which are not Images? Thanks mik Michele.Fella (talk) 08:57, 15 February 2018 (UTC)

VisualEditor supports drag-and-drop of CSV files. I don't think any others (e.g., .txt files) are currently planned. Is there something you'd particularly like to have supported? Whatamidoing (WMF) (talk) 18:52, 2 March 2018 (UTC)

Why to have a limit to particular extension. I think all extension declared in wgFileExtensions should be accepted, where possible handling them as image or simply adding them as generic file. Michele.Fella (talk) 22:45, 17 August 2018 (UTC)

Install MediaWiki with VisualEditor

Hello,

I'm trying to install Mediawiki on a Windows Server 2012 R2 running Xampp. It workds fine, but I don't manage to install Visual Editor. When I try to edit a page, I get the message

Erreur lors du chargement des données du serveur : apierror-visualeditor-docserver-http: HTTP 404.

Can anyone help me please ? Shaihulud1979 (talk) 13:40, 18 February 2018 (UTC)

You may need to correct your API URL setting in Parsoid. Edit Parsoid's config.yaml to include the correct API URL setting. https://www.mediawiki.org/wiki/Parsoid/Setup#Configuration . If this does not work please write back. Gryllida 06:01, 9 March 2018 (UTC)

I think this is a place, where I can ask some installation questions:

1. I miss a usable step-by-step installation to install the rest server/visualeditor correctly with the related details in the config files - all what I found tells me more about, that the visual editor is running in some environments only, depending stable or not on versions of visual editor and the rest proxy/parsoid
2. I see some installation hints for the restbase server and/or parsoid - are both installations required?
3. I'd like to install the rest proxy on an additional server - is that possible, if yes, how I have to configure that

I'm using the version 1.30 - thanks all in advance to help in this case ! Newin-ve (talk) 06:45, 22 May 2018 (UTC)

Install VisualEditor in Windows Using WAMPServer

Hello, i'm new in this world of coding.

Can you guys guide me how to install this VE Extension in MediaWiki that I installed in my computer using WAMPServer.

Because I find it hard to install the part of Parsoid. Thank you. 203.130.235.26 (talk) 04:23, 21 February 2018 (UTC)

i need this help too 80.25.201.181 (talk) 18:29, 31 March 2018 (UTC)

No screenshot?

Would be a good thing to have a screenshot of the tool on this page. Nikerabbit (talk) 12:57, 5 March 2018 (UTC)

There are 103 of them on Help:VisualEditor/User guide – which one would we pick? :-) Jdforrester (WMF) (talk) 17:33, 5 March 2018 (UTC)

Ideally one which shows the editor toolbar with some content. I only saw close-ups of different panels on that page :/ Nikerabbit (talk) 15:08, 6 March 2018 (UTC)

Showing what the editor feels like at 200px across is going to be a mess. Jdforrester (WMF) (talk) 15:23, 6 March 2018 (UTC)

300px then? Or a thumbnail? Nikerabbit (talk) 16:03, 6 March 2018 (UTC)

Remove jumpiness in the layout when activating and deactivating Visual Editor

When I open visual editor the page contents is pushed about 50 pixels down to create space for the visual editor toolbar. This looks and feels inconvenient.

The requirements are that:

• When the page is not being edited, there is some empty space where the VisualEditor toolbar would be located.
• While VisualEditor is activating, layout of the page does not change. The first heading of the page content stays exactly on the same place where it was.
• While VisualEditor is deactivating, layout of the page does not change. The first heading of the page content stays exactly on the same place where it was.
• When VisualEditor is activated, the first heading of the page contents stays exactly where it was before VisualEditor was opened.

I tried to write a CSS for this, but things are still jumpy.

/*.ve-available #content{	padding-top:36px;}
.ve-loading  #content {	padding-top:0px !important;}
.ve-active #content{	padding-top: 0px !important;}
*/
#content{	padding-top:36px !important;}
.ve-ui-toolbar {   margin: -48px -2em 0;}
.ve-deactivating #content{	padding-top: 84px !important;}

Do you have suggestions for this? Thank you! Gryllida 05:52, 9 March 2018 (UTC)

We've had a lot of complaints in the opposite direction: despite not being WYSIWYG anyway (e.g., with added blank lines in a few places, to make it easy to insert new elements), most people want more difference between editing mode and reading mode. I therefore thing that the team isn't going to move in the direction that you want.

In particular, I think those blank lines (called "slugs") are going to make your goal impossible, because any page that begins with templates and pictures will see the first line of text move down as one or more slugs is added. You might be able to work it out for pages with a set number of slugs (0, 1, 2...) but I don't think you'll be able to work it out for all pages. Whatamidoing (WMF) (talk) 16:24, 9 March 2018 (UTC)

Insert Media (and other) doesn't work

I installed mediawiki 1.30 with visuael editor. The editor starts, edit works: I can add text.

But when I choose "Insert -> Media" nothing happens. The same when I click on the "link" Button or when I choose "bold" for a selected text - there is just no reaction.

Can anyone give me a hint on how to fix this problem? 2003:C0:BBD9:CB00:FE70:9E8:9183:F663 (talk) 12:13, 24 March 2018 (UTC)

VE could not save the page.

when I access my wikisite use IP address throug outside of subnetwork, user read pages is OK ,but,I could not save modifing page in VE . Appears error like:" curl error：28 Timeout was reached". sametime ,I could not switch from VE to resouceeditor. Appears error :"apierror-visualeditor-docserver-http-error"

when I access my wikisite use IP address throug inner of subnetwork. Every function is OK.

access restbase server so good in anywhere.

would anyone like help me ?Thank you . Flame qi (talk) 15:20, 24 March 2018 (UTC)

httpResponse 406 from Parsoid

When trying to edit using the extension Parsoid is throwing a 406.

Is this a known response? Gwsampo (talk) 01:02, 27 March 2018 (UTC)

I am seeing the same pattern. I am able to create a new page using VisualEditor without problem but if I try to edit it gives a 406 error. If I check the log file on the Parsoid server it has the error message "Not acceptable". In checking the code for Parsoid in its Git repository, it looks like the error is produced by a check of the content version. 216.248.100.66 (talk) 15:55, 27 March 2018 (UTC)

I am also getting a 406 error. I was trying to set up parsoid on another server and getting this. I thought it was me configuring wrong but now I wonder. @Gwsampo, was this already working on your server and now it is giving 406 error? Dbummy (talk) 20:44, 27 March 2018 (UTC)

I'm a new install but wouldn't say I'm a battler at this kind of thing...

My setup (IP_ADRESS/index.php?title=Special:Version)

== Installed software ==

Product	Version
MediaWiki	1.30.0
PHP	7.0.28-0ubuntu0.16.04.1 (apache2handler)
MySQL	5.7.21-0ubuntu0.16.04.1
Parsoid	0.9.0all
Curl	7.47.0

== Installed extensions ==

Other
Extension	Version	License	Description	Authors
VisualEditor	0.1.0 (61f161a)05:07, 3 October 2017	MIT	Visual editor for MediaWiki	Alex Monk, Bartosz Dziewoński, Christian Williams, Ed Sanders, Inez Korczyński, James D. Forrester, Moriel Schottlender, Roan Kattouw, Rob Moen, Timo Tijhof, Trevor Parscal, C. Scott Ananian and others

Gwsampo (talk) 22:11, 27 March 2018 (UTC)

I also has the same problem, I got apierror-visualeditor-docserver-http: HTTP 406. when editing any already exists wiki pages , but when I create a new wiki page no problem appear and everything goes fine the and page created with the visual editor.

any one know how to solve this? Mshannaq (talk) 23:02, 27 March 2018 (UTC)

When using postman to GET

http://IP_ADDRESS/mediawiki/api.php?action=visualeditor&format=json&paction=parse&page=Main_Page&uselang=en

{

    "error": {

        "code": "apierror-visualeditor-docserver-http",

        "info": "HTTP 406",

        "*": "See http://IP_ADDRESS/mediawiki/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce&gt; for notice of API deprecations and breaking changes."

    }

} Gwsampo (talk) 23:53, 27 March 2018 (UTC)

Yes I got the same also when I use post man

http://IP/api.php?action=visualeditor&format=json&paction=parse&page=REST_API_using_PHP&uselang=en

{

    "error": {

        "code": "apierror-visualeditor-docserver-http",

        "info": "HTTP 406",

        "*": "See https://IP/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce&gt; for notice of API deprecations and breaking changes."

    }

}

but when I try to request the same url for a non exists content I got

http://IP/api.php?action=visualeditor&format=json&paction=parse&page=not_exists_topic&uselang=en

{

    "visualeditor": {

        "result": "success",

        "notices": [

            "<p><strong>Warning:</strong> You are not logged in. Your IP address will be publicly visible if you make any edits. If you <strong><a rel=\"nofollow\" class=\"external text\" href=\"https://IP/index.php?title=%D8%AE%D8%A7%D8%B5:UserLogin&returnto=Not_exists_topic\">log in</a></strong> or <strong><a rel=\"nofollow\" class=\"external text\" href=\"https:/IP/index.php?title=%D8%AE%D8%A7%D8%B5:UserLogin/signup&amp;returnto=Not_exists_topic\">create an account</a></strong>, your edits will be attributed to your username, along with other benefits.\n</p>",

            "<p>You have followed a link to a page that does not exist yet.\nTo create the page, start typing in the box below (see the <a class=\"external text\" href=\"https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents\">help page</a> for more info).\nIf you are here by mistake, click your browser's <strong>back</strong> button.\n</p>"

        ],

        "checkboxesDef": [],

        "checkboxesMessages": [],

        "templates": "<div class=\"templatesUsed\"></div>",

        "links": {

            "missing": [

                "Not exists topic"

            ],

            "known": []

        },

        "protectedClasses": "",

        "basetimestamp": "20180328002134",

        "starttimestamp": "20180328002134",

        "oldid": 0,

        "content": ""

    }

}

any advices? Mshannaq (talk) 00:23, 28 March 2018 (UTC)

So frustrating but try in LocalSettings.php

Enabled skins (commenting out the other ones)

wfLoadSkin( 'MonoBook' );

wfLoadSkin( 'Vector' ); Gwsampo (talk) 02:12, 28 March 2018 (UTC)

Sorry that didn't work Gwsampo (talk) 02:14, 28 March 2018 (UTC)

Maybe a bug in 1.30.0 mediawiki

Working in 1.31.0-alpha mediawiki

Steps to resolve was completing removing old mediwiki and installing latest development version from github and latest development version of visualeditor from git

Something like this

cd /var/lib/mediawiki

mv /var/lib/mediawiki /var/lib/mediawikiold

git clone https://gerrit.wikimedia.org/r/p/mediawiki/core.git

mv /var/lib/core /var/lib/mediawiki

Installed composer globallly (https://getcomposer.org/)

/var/lib/mediawiki composer update --no-dev

test mediawiki config page working

copied old skins

copied old extensions (excluding visual editor)

cd extensions

git clodn https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git

cd VisualEditor

git submodule update --init

completed wiki setup

worked

== Installed software ==

Product	Version
MediaWiki	1.31.0-alpha (6f9c30c) 09:38, 28 March 2018
PHP	7.0.28-0ubuntu0.16.04.1 (apache2handler)
MySQL	5.7.21-0ubuntu0.16.04.1
ICU	55.1

== Installed extensions ==

Other
Extension	Version	License	Description	Authors
VisualEditor	0.1.0 (476a590)07:29, 28 March 2018	MIT	Visual editor for MediaWiki	Alex Monk, Bartosz Dziewoński, Christian Williams, David Lynch, Ed Sanders, Inez Korczyński, James D. Forrester, Moriel Schottlender, Roan Kattouw, Rob Moen, Timo Tijhof, Trevor Parscal, C. Scott Ananian and others:

Gwsampo (talk) 02:30, 28 March 2018 (UTC)

I'm having the same problem .. 96.23.48.169 (talk) 03:45, 28 March 2018 (UTC)

Hi same problem here. Media Wiki 1.30, Visual Editor 1.30 93.39.230.4 (talk) 07:23, 28 March 2018 (UTC)

Seems that MW1.30 works with Parsoid 0.8.0all but NOT with Parsoid 0.9.0all. if you run "dpkg -s parsoid" it will show you Parsoid version. I have mirrored setups (Ubuntu Server 16.04) with each of the versions of Parsoid and one is working and the other is giving 406 error. Trying to downgrade now. Dbummy (talk) 14:04, 28 March 2018 (UTC)

Was able to get mine working (MW 1.30 / Parsoid 0.9.0all) by downgrading Parsoid to 0.8.0all.

--Ubuntu Server 16.04--

apt-get purge parsoid

wget https://people.wikimedia.org/~ssastry/parsoid/debs/parsoid_0.8.0all_all.deb

dpkg -i parsoid_0.8.0all_all.deb

apt-mark hold parsoid Dbummy (talk) 14:25, 28 March 2018 (UTC)

Worked for me, I couldn't find 0.8.0 via apt before so thanks for these steps

Don't forget to check your configs too! 82.204.2.90 (talk) 15:28, 29 March 2018 (UTC)

This worked for me! 185.154.146.37 (talk) 11:26, 7 June 2018 (UTC)

For me, changing the version of Parsoid to 0.8.0 was the solution. While it is noted in Parsoid's documentation that you need to be careful to use the right version of Parsoid for the version of VisualEditor you have, I didn't see any mention in the VE documentation as to which version was appropriate. 216.248.100.66 (talk) 15:34, 28 March 2018 (UTC)

I am on Centos 7 and I am not able to install the .deb file in the download page for the 0.8.0

I have tried:

dpkg -i parsoid_0.8.0all_all.deb

but I receive these errors:

parsoid depends on nodejs (>= 4.0.0); however:

  Package nodejs is not installed.

parsoid depends on logrotate; however:

  Package logrotate is not installed.

parsoid depends on adduser; however:

  Package adduser is not installed.

But I have installed node: v6.13.1 and npm: 3.10.10

Do you have any suggestion?

Thanks 93.39.230.4 (talk) 15:56, 28 March 2018 (UTC)

The "deb" file is for Ubuntu or Debian based systems. I think with CentOS you would have to find the "rpm" file or compile from source. If using the rpm file, You would use "yum" instead of "apt-get". You may even be able to install the old version using yum. I know you can with apt-get in Ubuntu if the package is still available but it wasn't in my case. Dbummy (talk) 17:03, 28 March 2018 (UTC)

Already tried, in the repo there is only the last version.

I think I am stucked until they update the Visual Editor.... 217.148.121.13 (talk) 12:46, 29 March 2018 (UTC)

Edit the file ParsoidConfig.js.

Its in ----> lib/config/ParsoidConfig.js

Change the following line from TRUE to FALSE:

ParsoidConfig.prototype.strictAcceptCheck = false;

Full Article is here

Greets,

Chris 77.118.171.223 (talk) 06:38, 2 April 2018 (UTC)

This "fixed" the issu for my setup. 217.18.193.124 (talk) 10:24, 3 April 2018 (UTC)

Thanks,It's work.Looks good. 60.11.42.35 (talk) 01:10, 4 April 2018 (UTC)

Googled for hours until i found this solution...works for me, a fresh installation of mediawiki & parsoid 62.2.90.162 (talk) 14:05, 5 April 2018 (UTC)

Thanks so much. Worked for me as well. 12.118.115.198 (talk) 16:19, 5 April 2018 (UTC)

Thank you that fixed it!

Just for documentation purposes the error I had on the parsoid.log file was:

Error:

{"name":"parsoid","hostname":"wiki","pid":1453,"level":60,"logType":"fatal/request","wiki":"wiki$1","title":"Ejemplo","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.30.0","msg":"Not acceptable.\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/1.6.1\"\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/2.0.0\"\n","stack":"","httpStatus":406,"longMsg":"Not acceptable.\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/1.6.1\"\ntext/html; charset=utf-8; profile=\"https://www.mediawiki.org/wiki/Specs/HTML/2.0.0\"\n","levelPath":"fatal/request","time": ""}

Solution:

Edit the file ParsoidConfig.js.

Its in ----> lib/config/ParsoidConfig.js

Change the following line from TRUE to FALSE:

ParsoidConfig.prototype.strictAcceptCheck = false;

Thanks! 186.46.139.226 (talk) 20:33, 12 April 2018 (UTC)

Yep that did it ! Solved.

• sudo vim /usr/lib/parsoid/src/lib/config/ParsoidConfig.js
• ParsoidConfig.prototype.strictSSL = false;
• sudo service parsoid restart
• Done Compumatter (talk) 17:53, 11 June 2018 (UTC)

Wait, what should i do if there is no such line in my config file?

There is only a "strict check for ssl", but setting that to false didn't solve the problem.

Is there something missing from my files? Oleolsenkjhølkølk (talk) 07:40, 24 October 2018 (UTC)

Posting to let everyone know that the post above exposes a solution that doesn't involve manually downloading the previous version of parsoid and freezing it on Ubuntu via apt mark. Be sure to restart the parsoid service after making the change. 185.125.207.249 (talk) 19:48, 2 April 2018 (UTC)

You can also change the config file instead of Parsoid code: edit /etc/mediawiki/parsoid/config.yaml and add strictAcceptCheck: false at the same level as "userAgent" in the beginning, i.e. just under "conf". Example:

services:

- module: lib/index.js

entrypoint: apiServiceWorker

conf:

# For backwards compatibility, and to continue to support non-static

# configs for the time being, optionally provide a path to a

# localsettings.js file. See localsettings.example.js

#localsettings: ./localsettings.js

# Set your own user-agent string

# Otherwise, defaults to:

# 'Parsoid/<current-version-defined-in-package.json>'

#userAgent: 'My-User-Agent-String'

# /!\ COMPATIBILITY for Parsoid 0.9.0 with MediaWiki before 1.31

strictAcceptCheck: false

# Configure Parsoid to point to your MediaWiki instances.

mwApis:

...

PS: this is just an improvement over the above solution, all merits are due to [1]. ~ Seb35 [^_^] 10:31, 7 April 2018 (UTC)

Don't forget to restart Parsoid with `service parsoid restart` after changing the configuration! This is the cleanest solution to get Parsoid 0.9.0all working with Mediawiki 1.30! 213.33.64.46 (talk) 08:42, 16 April 2018 (UTC)

Thank you too much, my friends!

I spend hours to search in baidu and google, it really frustrated me.

Thanks! All my friends!

真的非常感谢，前辈们！ 117.136.45.110 (talk) 03:45, 21 April 2018 (UTC)

I am still getting error "apierror-visualeditor-docserver-http","info":"HTTP 406"

Using these configs:

OS : GNU bash, version 4.2.46(2)-release (x86_64-redhat-linux-gnu)

NAME="Red Hat Enterprise Linux Server"

VERSION="7.6 (Maipo)"

MediaWiki 1.31.1

VisualEditor 0.1.0 (6854ea0)22:33, 5 November 2018

"parsoid" : 0.10.0+git

Parso log:

"name": "parsoid",

"hostname": "ashsd.xxx.com",

"pid": 19229,

"level": 60,

"logType": "fatal/request",

"wiki": "Wiki2",

"title": "Bot",

"oldId": null,

"reqId": null,

"userAgent": "VisualEditor-MediaWiki/1.31.1",

"msg": "Not acceptable.\ntext/html; charset=utf-8; profile=\"\"\ntext/html; charset=utf-8; profile=\"/HTML/999.0.0\"\n",

"stack": "",

"httpStatus": 406,

"longMsg": "Not acceptable.\ntext/html; charset=utf-8; profile=\""\ntext/html; charset=utf-8; profile=\"/HTML/999.0.0\"\n",

"levelPath": "fatal/request",

"time": "2019-06-19T09:00:58.714Z",

"v": 0

Rajeshrajesh.35 (talk) 09:19, 19 June 2019 (UTC)

same error with you 116.232.53.1 (talk) 08:51, 15 July 2019 (UTC)

I have solved this error, there was missing domain name in these files, i would suggest all of you to check the domains in these files.

[Root]/config.yaml,

[Root]/sys/mathoid.js,

[Root]/v1/mathoid.yaml Rajeshrajesh.35 (talk) 06:16, 16 July 2019 (UTC)

These errors are related to restbase. Rajeshrajesh.35 (talk) 06:17, 16 July 2019 (UTC)

@Rajeshrajesh.35

Hi,

I have the same error but it seems that I have no problem with domain names.

Have you change anything else ? 192.196.142.91 (talk) 13:45, 5 August 2019 (UTC)

No, is individual services running as

Parsoid?

Restbase?

Method?

Also, check port is enabled so that API connect internally, still you have problem drop me email [my user name] @ gmail.com Rajeshrajesh.35 (talk) 06:35, 28 August 2019 (UTC)

If people are getting this with MediaWiki version 1.31.x on Ubuntu 18.04, parsoid had updated to version 0.11.all for me.

You can downgrade to 0.10.0all which is supported by 1.31.x here: https://releases.wikimedia.org/parsoid/

Pin it with `apt-mark hold parsoid` 213.133.67.162 (talk) 09:27, 19 February 2020 (UTC)

Для установленной на WINDOWS

php 5.6

apache 2.4

Mediawiki 1.30.2

помогла решить проблему установка версий Parsoid 0.9.0, NodeJS 10.21

С parsoid версии 0.11.0 не работало с указанной в теме ошибкой.

Новые страницы создавались, а при редактировании существующих было: apierror-visualeditor-docserver-http: HTTP 406 93.188.122.139 (talk) 14:54, 8 July 2020 (UTC)

"Unknown error, HTTP status 500"

When I attempt to save a page using VisualEditor, the normal "Save your changes" box comes up. When I click on Save page in the upper right-hand corner of that box, the box receives a modal overlay with the message "Unknown error, HTTP status 500".

Here's my set up: Ubuntu 16.04, Apache 2.4.18, PHP 7.0.28, MySQL 5.7.21, MediaWiki 1.30.0, VisualEditor 0.1.0, Node.js 8.10.0, Parsoid 0.9.0. My wiki is using Let's Encrypt.

The first thing I want to do is find out more about this 500 error. I cannot find it in the following log files:

• The error_log for the virtual host (/home/wiki/logs/error_log).
• The error_log for Apache as a whole (/var/log/apache/error.log).
• The log for the Parsoid service (/var/log/parsoid/parsoid.log).

Where else may I look? I'm not savvy about Node.js or applications built on it, and I couldn't find any places by googling "parsoid error log location". 216.114.117.77 (talk) 06:38, 27 March 2018 (UTC)

Solution: Turns out the php-curl extension wasn't installed. Installing this extension fixed this issue. 216.114.117.77 (talk) 07:51, 31 March 2018 (UTC)

How exactly did you solve this issue? I have the same problem, and i got cURL enabled from my provider, but the issue still exist. Oleolsenkjhølkølk (talk) 23:33, 1 March 2019 (UTC)

unable to save the edit page in visual editor

@Christian .R;

i am able save and edit the first level pages but not the child pages. Arshiyakhanam013 (talk) 09:43, 5 April 2018 (UTC)

Please don't post e-mail addresses in plain text.

Can you give me a link to the page that you are able to save, and another that you can't save? Whatamidoing (WMF) (talk) 16:14, 5 April 2018 (UTC)

Edited by @Whatamidoing (WMF)

mediawiki/Main_Page = able to save

mediawiki/Main_Page/subpage = failing with 404

the child page not able to save or tiltle having slash in it .

thank you in advance Arshiya1234 (talk) 09:57, 16 April 2018 (UTC)

mediawiki/Main_Page = able to save

mediawiki/Main_Page/subpage = failing with 404

thank you in advance Arshiya1234 (talk) 09:55, 16 April 2018 (UTC)

Ubuntu server + Parsoid errors

Looks like im not alone in getting 406 error, happend on all servers i have Visualeditor on at the same time. But on two servers the parsoid service is dead refuses to start and throws this error: https://pastebin.com/BCuKEE3h

Only thing that has happend on these servers is ubuntu security patches auto updating, else I have only used the frontends no other changes has occured.

Tried to reinstall parsoid on one more critical server but fails to get it working no matter what I do, throws same error as above.

Regards, Jberg83 (talk) 14:25, 10 April 2018 (UTC)

Just found this: Talk:Parsoid/2018#h-VisualEditor_stopped_working_after_upgrade_to_parsoid_0.9.0all-2018-03-24T10:16:00.000Z

Will look in to if it will work. Jberg83 (talk) 14:29, 10 April 2018 (UTC)

Now parsoid starts, tried to downgrade but whatever I do i get (:..)Error: ETIMEDOUT\ so upgraded mediawiki to 1.30 and VE to latest for 1.30 but same problem. The api is reachable via curl and even remotely and parsoid is running on port 8142,

However, on one wiki I use MW1.27.2 because of lack of support of intraACL on newer versions, but on this installation it was sufficient to downgrade parsoid only! Jberg83 (talk) 20:21, 10 April 2018 (UTC)

Got it running again, on most servers it was to wget from here https://people.wikimedia.org/~ssastry/parsoid/debs/

apt-get pruge parsoid

dpkg -i <package>

Update the /etc/mediawiki/parsoid/config.yaml file accordingly and restart parsoid service.

In two cases regarding MW1.28 it was needed to upgrade to 1.30 and matching VE then still using the 0.8.0 parsoid deb package those machines are running Ubuntu server 16.04. Edit: Problem was API timeout errors, but never found what was the cause.

Problem solved but remember to apt-mark hold parsoid so it wont break again.

Br Jberg83 (talk) 06:04, 11 April 2018 (UTC)

Problem saving , gives a messy page

Hi , First I really gone mad installing this extension , it's very very difficult , but somehow I managed to get the Editor work.

But , when I save a modification , just a tiny text to see if the editor is working , he gives me a big tall page with html coding and MediaWiki API help page instead of what I modified !

It really really gave me a hard pain. 41.109.228.37 (talk) 18:52, 15 April 2018 (UTC)

I'm having the same issues, can you give me some explanation about your configuration in hopes we can find a common denominator? 12.227.180.130 (talk) 18:36, 16 April 2018 (UTC)

Umm I don't know how to explain my configuration , but I installed nodejs , parsoid and composer , curl php5 , npm , I configured the yaml file to point to the wiki api link , I am having both shared hosting and VPS , I tried on shared host didn't work , on vps at least the editor is loading without any errors popups , I installed ubuntu on the VPS. and I think that's all. 41.109.170.112 (talk) 13:24, 18 April 2018 (UTC)

Did the mess look more or less like the mess that I made here? Whatamidoing (WMF) (talk) 21:55, 19 April 2018 (UTC)

I think it's a little bit less in volume , the mess is exactly begins with some html messy tags , then the api page and ends with html messy tags 41.109.129.122 (talk) 08:40, 20 April 2018 (UTC)

Is VisualEditor configured to work in that namespace? Also, do you have the 2017 wikitext editor installed? (That's how I created that mess.) Whatamidoing (WMF) (talk) 16:54, 20 April 2018 (UTC)

Color editor

Hey,

I'm using the visual editor for one of my wikis, and there seems to be too much blue space in the wikitext visual editor page. I was wondering which file I could go to to change this to decrease this blue space. 131.179.59.99 (talk) 21:30, 16 April 2018 (UTC)

Can you tell me more about this? There shouldn't really be any blue space (unless you select something). Whatamidoing (WMF) (talk) 21:53, 19 April 2018 (UTC)

VisualEditor loads with empty page

Parsoid and RESTbase needed to be configured to get VisualEditor working.

I have a wiki setup with VisualEditor, Apache, HTTPS, Parsiod, and RestBase. Everything works except when loading VisualEditor, the page becomes empty when it finishes loading. TheROFL98 (talk) 01:01, 18 April 2018 (UTC)

I just posted a new topic, starting with essentially the same problem. Did you figure it out? What was wrong? Baxterz (talk) 10:05, 10 February 2019 (UTC)

This was over 10 months ago. I apologize, as I now have got it working. Thanks. TheROFL98 (talk) 22:33, 10 February 2019 (UTC)

That is great that you got it working. What did you have to fix in your configuration files to stop getting the empty page? There are 3 files I am working with: config.yaml for parsoid, config.yaml for restbase, and LocalSettings.php for mediawiki. Can you post what you fixed that made it start displaying the next that was already on the page? Baxterz (talk) 11:16, 11 February 2019 (UTC)

Image search not working

Hi,

I've got VisualEditor to work with both parsoid and mediawiki using SSL. However, image search in the "insert image" box is not working. If I add the images via the "edit source" , I can edit its properties with VisualEditor without problems

Any hints on debugging or making the search to work?

This is my configuration:

MediaWiki	1.30.0
PHP	5.6.29-1+deb.sury.org~xenial+1 (apache2handler)
MySQL	5.7.22-0ubuntu0.16.04.1

VisualEditor: REL1_30, 2017-10-02T19:13:54 Cascosoft (talk) 19:20, 24 April 2018 (UTC)

Upload files and display them via VE works for me but image search is not possible.

Also it the file/image description is not saved. 217.83.25.72 (talk) 15:04, 7 August 2018 (UTC)

New Categories Not Recognized

After creating a couple categories by creating their Category:[NAME] pages, VisualEditor doesn't recognize them as existing categories. The same occurs if it's not a new category but it is empty. If I enter the name of the category as a "new category" in VE it links up fine with the existing new category, though. Mrbmi513 (talk) 19:14, 26 April 2018 (UTC)

I understand that there's something odd about how MediaWiki handles categories. They don't technically exist if there has never been a page in the category, even if you have created a page for the category. If these empty categories have always been empty, then that may be the source of the disconnect. Whatamidoing (WMF) (talk) 07:25, 28 May 2018 (UTC)

HTTP 404 when I [Save Changes] via VisualEditor

Hi All,

I'am trying to deploy VisualEditor from my Mediawiki site. After I successfuly set up Parsoid and RESTBase service, VisualEditor can be actived successfully, but when I try to save changes, the page informs me that "Something went wrong" with a "HTTP 404" warning.

When I check code of this page in chrome internet explorer. I find that it gives 1 warnings "JQMIGRATE: jQuery.fn.offset() requires an element connected to a document" when I click the "Editor" bar.

Can anyone help me or does someone ever met this issue before?

Below is my Env:

OS: Ubuntu Server 18.04

Mediawiki Version: 1.30

below is the detailed warning info:

JQMIGRATE: jQuery.fn.offset() requires an element connected to a document

	migrateWarn	@	load.php?debug=false…version=0f3njs5:140
	jQuery.fn.offset	@	load.php?debug=false…version=0f3njs5:148
	OO.ui.PopupWidget.computePosition	@	load.php?debug=false…version=0czp4ko:854
	OO.ui.mixin.FloatableElement.position	@	load.php?debug=false…version=0czp4ko:837
	OO.ui.mixin.FloatableElement.togglePositioning	@	load.php?debug=false…version=0czp4ko:835
	OO.ui.PopupWidget.toggle	@	load.php?debug=false…version=0czp4ko:851
	(anonymous)	@	VM321:1073
	fire	@	load.php?debug=false…&version=0f3njs5:46
	add	@	load.php?debug=false…&version=0f3njs5:47
	always	@	load.php?debug=false…&version=0f3njs5:48
	ve.init.mw.DesktopArticleTarget.maybeShowMetaDialog	@	VM321:1073
	ve.init.mw.DesktopArticleTarget.surfaceReady	@	VM321:1060

59.63.207.115 (talk) 16:48, 23 May 2018 (UTC)

Replacing TextInputWidget with TargetWidget

I am trying to replace the TextInputWidget on line 284 of the ve.ui.MWParameterPage.js with a TargetWidget to allow rich text editing. I have looked all over to find info on how to do this, and the only reference I've seen is here, which is pretty vague:

VisualEditor/Feedback/Archive/2016/06#h-Allow_formatting_in_TextInputWidget?-2016-06-16T10:08:00.000Z

What I specifically want to know is what .js file do I need to add the targetwidget constructor to for the ParameterPage.js to be able to use it, and where if possible. Cbarnard 76 (talk) 17:35, 29 May 2018 (UTC)

@Jskurat, did you ever figure that out? Whatamidoing (WMF) (talk) 00:33, 5 June 2018 (UTC)

@ESanders (WMF), @Whatamidoing (WMF)

Here is what I have figured out so far. I've copied 7 references to the captionTarget and captionFieldset from the ve.ui.MWMediaDialog.js to the ve.ui.MWTemplateDialog.js to replace the functionality of the TextInputWidget with the TargetWidget on the ve.ui.MWParameterPage.js.

I've been debugging the code and have hit a roadblock with a "cannot read property 'childnodes' of undefined" error when it attempts to create the TargetWidget. This is a timing error, and I'd usually solve it by putting the function calling the targetwidget inside the (document).ready function for the JS creating the dialog. It seems that Mediawiki and the Visual Editor don't have a document ready, though, so I'm trying to figure out where else I should put it. Cbarnard 76 (talk) 16:02, 10 July 2018 (UTC)

I meant calling the function within document ready, not putting the whole function in there. Cbarnard 76 (talk) 16:04, 10 July 2018 (UTC)

If you push your code to gerrit we'll be able to provide more detailed feedback. ESanders (WMF) (talk) 16:59, 10 July 2018 (UTC)

I'm trying to clone the correct repository to cut a branch and add my updated JS code to. I've tried "VisualEditor" and "VisualEditor/VisualEditor", but neither one is the same code as the version I'm working on. Can you point me in the right direction? 172.221.150.69 (talk) 03:21, 15 July 2018 (UTC)

Everything inside /lib/ve is the core editor, which is the "VisualEditor/VisualEditor" repo, everything else is the MediaWiki integration and is the "VisualEditor" repo. TargetWidget is initially defined in core VE, but MWParameterPage is from the MediaWiki integration (as the filename suggests). ESanders (WMF) (talk) 13:49, 16 July 2018 (UTC)

I am trying to create a branch in the VisualEditor repo but I am getting a 403 error. What should I create the branch under? Cbarnard 76 (talk) 17:59, 23 July 2018 (UTC)

Just push your code as a commit on master (git review will do that by default); pushing new branches to the server is a highly restricted operation on gerrit. Jdforrester (WMF) (talk) 20:46, 25 July 2018 (UTC)

@ESanders (WMF), @Jdforrester (WMF) - I have committed my changes to the VisualEditor repo. Can you please check them out for me and point me in the right direction on what needs to be changed for the TargetWidget to work on the Parameter Page? Cbarnard 76 (talk) 16:38, 7 August 2018 (UTC)

I see it at https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/451020 – I've pinged people to have a look. Thanks! Jdforrester (WMF) (talk) 22:40, 8 August 2018 (UTC)

Has anyone had a chance to look at this yet? Cbarnard 76 (talk) 16:07, 22 August 2018 (UTC)

There are three comments on it, at https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/VisualEditor/+/451020/ Whatamidoing (WMF) (talk) 17:57, 22 August 2018 (UTC)

If I could get feedback on the MWTemplateDialog.js changes, that would be more helpful. Cbarnard 76 (talk) 21:49, 22 August 2018 (UTC)

Is the login for the Gerritt the same as for the Mediawiki? Cbarnard 76 (talk) 19:56, 10 July 2018 (UTC)

I don't think so. https://wikitech.wikimedia.org/w/index.php?title=Special:CreateAccount&returnto=Gerrit/NewUser seems to be the place to create an account. Whatamidoing (WMF) (talk) 01:55, 12 July 2018 (UTC)

VisualEditor change a PDFHandler Seite 1

The VisualEditor 1.30 change a PDFHandler shown PDF file in a wrong way.

without the , that is only for this view: That is the source: <nowiki> [[File:TestPDF.pdf|page=1|600px|Seite 1]] [[File:TestPDF.pdf|page=2|600px|Seite 2]]

after next edit with VisualEditor the Editor change it into this: <figure-inline>[[File:TestPDF.pdf|919x919px]]</figure-inline> <figure-inline>[[File:TestPDF.pdf|919x919px]]</figure-inline> 213.61.254.67 (talk) 10:43, 25 June 2018 (UTC)

I have the same Problem with Images. I open an existing page with VisualEditor 1.30 and change some text. After saving all inline images received a <figure-inline> tag like this:

<figure-inline>[[Datei:test2.png|644x644px]]</figure-inline>

When I save a second time, another one will be added.

<figure-inline><figure-inline>[[Datei:test.png|644x644px]]</figure-inline></figure-inline>

88.217.159.242 (talk) 11:17, 28 June 2018 (UTC)

I updated parsoid from 0.6.0 to 0.9.0. After doing that I had no more problems with this tag. 94.217.10.240 (talk) 05:21, 13 July 2018 (UTC)

Cannot edit subpages

Tracked in Phabricator
Task T201628

I have VisualEditor generally working correctly on my site. However, when I attempt to edit a subpage VisualEditor presents me with a blank page instead of the contents of the page. Looking at the Parsoid log I can see no evidence of any calls to Parsoid relating to the subpage so it appears that it fails to get that far. Looking at my Apache log I can see:

"GET /api/rest_v1/page/html/Page%2FSubpage?redirect=false HTTP/1.1" 404 602 "https://www.mysite.org/wiki/Page/Subpage?action=edit" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134"

All other items relating to this page return success and editing the page (rather than the subpage) returns a similar result but with a success code so I'm guessing this is the problem. Any idea why I'm getting a 404 error here and how I fix it?

Thanks in advance for any assistance. Prh47bridge (talk) 12:28, 25 June 2018 (UTC)

A bit more information...

Having tried the request to /api/rest_v1/page/html/... from a browser, I find the response is as follows:

Page - the contents of the page as expected

Page/Subpage - the response "{"type":"https://mediawiki.org/wiki/HyperSwitch/errors/bad_request","title":"Invalid parameters","method":"get","detail":"data.params.revision should be an integer","uri":"/www.mysite.org/v1/page/html/Page/Subpage"}"

Page%2FSubpage - "The requested URL /api/rest_v1/page/html/Page/Subpage was not found on this server."

I'm running MediaWiki 1.31, the VisualEditor version tagged for 1.31, Parsoid 0.9.0all and Restbase 0.18.1. My Apache config includes the directive "ProxyPass /api/rest_v1/ http://localhost:7231/www.mysite.org/v1/"

I am unclear why Page/Subpage and Page%2FSubpage produce different results but neither response is correct. Prh47bridge (talk) 13:54, 26 June 2018 (UTC)

There have been some problems with subpages in the past (e.g., https://phabricator.wikimedia.org/T110413 ) but I can't find any bugs that sound like what you're experiencing. Whatamidoing (WMF) (talk) 19:56, 13 July 2018 (UTC)

I've investigated a bit further.

If I use curl to go straight to localhost:7231 I get the following:

Page - the contents of the page as expected

Page/Subpage - the response "{"type":"https://mediawiki.org/wiki/HyperSwitch/errors/bad_request","title":"Invalid parameters","method":"get","detail":"data.params.revision should be an integer","uri":"/www.mysite.org/v1/page/html/Page/Subpage"}"

Page%2FSubpage - the contents of the subpage

This seems to mean that the Page%2FSubpage case is not being handed off correctly to Restbase by Apache. Having checked, it seems VE is using the Page%2FSubpage version. So my guess is that there is a URL-encoding issue here. Any thoughts? Prh47bridge (talk) 15:45, 6 August 2018 (UTC)

My thought is that I love all the details you've posted, and that it's time to file a bug report. It's up at phab:T201628. You can login (look for the button to login using your MediaWiki.org account) and edit the bug report or add extra information there. Whatamidoing (WMF) (talk) 16:48, 9 August 2018 (UTC)

This does sound like an Apache rewrite rule problem. @Prh47bridge could you please subscribe to the ticket above and include your apache config there? Mobrovac-WMF (talk) 17:25, 9 August 2018 (UTC)

I've been on holiday for a couple of weeks. My apache config has now been added to the bug report. Prh47bridge (talk) 16:45, 25 August 2018 (UTC)

Hi, I'm getting similar problems as this user. I was looking if there was an update to this problem? TheROFL98 (talk) 22:20, 14 February 2019 (UTC)

While the visual editor is active, it does not have any activity

Hello

While everything is right, it worked well even yesterday, but now, although it does not seem to be a problem, but I'm going to click on the VisualEditor button, nothing happens.

wfLoadExtension( 'VisualEditor' );

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

$wgHiddenPrefs[] = 'visualeditor-enable';

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

   // Use port 8142 if you use the Debian package

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

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

   'domain' => 'localhost',

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

   'prefix' => 'localhost'

);

$wgVisualEditorAvailableNamespaces = [

   NS_MAIN => true,

   NS_USER => true,

   102 => true,

   "_merge_strategy" => "array_plus"

];

#options = Enabled for all to opt-out

#Visual mode

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

#Wikitext mode + Beta Features opt-in state

$wgVisualEditorEnableWikitextBetaFeature = true;

#Single edit tab

$wgVisualEditorUseSingleEditTab = true;

$wgDefaultUserOptions['visualeditor-tabs'] = 'multi-tab';

#Visual diffs on history pages + Beta Features opt-in state

$wgVisualEditorEnableDiffPageBetaFeature = true;

#end options

#other options

#Table Of Contents widget  (Beta)

$wgVisualEditorVisualEditorEnableTocWidget = true;

#URL to use to access the experimental rebaser technology (Beta)

$wgVisualEditorVisualEditorRebaserURL = true; Sokote zaman (talk) 11:46, 2 July 2018 (UTC)

I think you should provide MW version, Parsoid version and your OS and its version. Spas.Z.Spasov (talk) 16:30, 2 July 2018 (UTC)

MediaWiki 1.31.0 (e9afac4)

PHP 7.2.5-0ubuntu0.18.04.1 (fpm-fcgi)

MariaDB 10.1.29-MariaDB-6

ICU 60.2

Lua 5.1.5

ubuntu 18.04

localhost

parsoid version (0.9.0all)

VisualEditor 0.1.0 (13a585a)

tanks Sokote zaman (talk) 18:40, 2 July 2018 (UTC)

Can you remove tools/gadgets from the toolbar?

Replies are at Talk:VisualEditor/2018#h-Can_you_remove_tools/gadgets_from_the_toolbar?-2018-07-08T11:31:00.000Z

I would like to remove unneeded tools from the toolbar to simplify the editing experience on my wiki, is this possible? Also is it possible to remove items from the dropdown menus in the toolbar? Josh Harry (talk) 12:06, 8 July 2018 (UTC)

Hiding comments in VE edition mode

Hi Friends, Is there a way to hide comments on VE edition mode?

I would like the comments (ie:

<!-- Exemple of comment -->

) to be seen only on wiki-text edition mode and not in VE edition mode.

Thank you. ClemFlip (talk) 14:14, 19 July 2018 (UTC)

No, there isn't currently a way to do this. From the big public wikis, the request is usually the opposite (to make them more visible). I think that Wikipedia editors may be more likely to use these comments to post information about content, which everyone needs to see, rather than, say, wikitext formatting, which would only be relevant for people using one of the wikitext editors. Whatamidoing (WMF) (talk) 15:59, 20 July 2018 (UTC)

Private wiki fowarding cookie to parsoid error

Good Afternoon,

Im trying to foward cookies to my parsoid 0.9.0 on a docker (hub.docker.com/r/thenets/parsoid/) on my private wiki , who is also a docker stable version, to be able to use VisualEditor.

But when i add the below code to my LocalSettings.php doesn't run:

$wgSessionInObjectCache = true;

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

    'url' => 'http://172.18.0.1:3308',

    'domain' => 'localhost',

    'fowardCookies' => true

);

I get this error: on loading visualeditor:

Error loading data from server: apierror-visualeditor-docserver-http: HTTP 401. Would you like to retry?

I readed on Extension:VisualEditor#Forwarding Cookies to Parsoid :

This feature requires a non-locking session store. The default session store will not work and // will cause deadlocks (connection timeouts from Parsoid) when trying to use this feature.

But i have passed a few days searching how to do a non-locking session store, but since i don't know php, i've failed every try.

What am i missing or doing wrong?

Also, The solutions: Extension:VisualEditor#Parsoid Authentication Without Forwarding Cookies and Extension:VisualEditor#2) Adapt how permissions are set does not work because my nginx, parsoid and mediawiki are on the same server, so requests sent over nginx are reaching my mediawiki with the host ip. 177.200.199.82 (talk) 18:33, 3 August 2018 (UTC)

Same problem here 46.36.64.114 (talk) 05:18, 6 October 2020 (UTC)

Can't edit existing text/content on existing pages: "Sorry, this element can only be edited in source mode for now."

Tracked in Phabricator
Task T202931

I have MediaWiki 1.27.3 with the VisualEditor extension and Parsoid 0.9.0 compat (with strictAcceptCheck: false in my Parsoid config) running on Nginx on Ubuntu 18.04.1 LTS. Parsoid and MediaWiki seem to be communicating fine, but whenever I try to edit a page with the VisualEditor, I can't change any of the existing content. The editor loads alright, but I can only add new text. When I hover over the existing content, I just see the message, "Sorry, this element can only be edited in source mode for now."

Does anyone have an idea what could be causing this, or where to look to troubleshoot the problem? The Parsoid log file doesn't have any obvious errors in it, and in fact seems to indicate that the wikitext to HTML conversion is occurring successfully:

{"name":"parsoid","hostname":"XXX","pid":13560,"level":30,"logType":"info","wiki":"wiki$0","title":"XXX","oldId":16409,"reqId":null,"userAgent":"wikimedia/multi-http-client v1.0","msg":"completed wt2html in 719ms","longMsg":"completed wt2html in 719ms","levelPath":"info","time":"2018-08-03T21:07:49.225Z","v":0}

Screenshot: https://i.imgur.com/kV35WpX.png Ejs1234 (talk) 21:18, 3 August 2018 (UTC)

Is there anything odd or unusual about these pages? Any templates at the top, or other content that might not be valid HTML? Any unusual or specialized tags on the page? Whatamidoing (WMF) (talk) 06:40, 7 August 2018 (UTC)

If you add new text, save the page, and open it up again, can you edit the content that you just added? Or is it blocked out as well? Whatamidoing (WMF) (talk) 06:41, 7 August 2018 (UTC)

I don't think there's any odd elements. When I created a new page (which worked fine using the VisualEditor) with just some text. After saving the page with VisualEditor, I can no longer edit it. The Dump Model button shows that the existing content is being classified as alienBlock. Ejs1234 (talk) 16:41, 8 August 2018 (UTC)

I filed a bug at phab:T202931. The Wikimedia Foundation does not provide support to third-party sites, but I've filed the bug report so the Editing team can take a look at it and determine whether they think there might be a more fundamental problem behind the very annoying symptoms. Whatamidoing (WMF) (talk) 20:09, 27 August 2018 (UTC)

I can't tell for sure without being able to access your wiki, but this is almost certainly caused by mismatched versions of Parsoid and VisualEditor. Parsoid 0.9.0 was released on 23 March 2018 (Parsoid/Releases). MediaWiki 1.27 was released on 28 June 2016 (MediaWiki 1.27) and I assume you've got VisualEditor from the 1.27.3 release tarball.

I suspect that old VisualEditor can't deal with the <section> tags, which are being output by your new Parsoid.

Try downgrading your Parsoid, or upgrading your MediaWiki and VisualEditor. If you have a good reason to run MW 1.27 instead of a newer version, try Parsoid 0.5.1 (I'm recommending this per Parsoid/Releases#0.5.1 (released Jun 3, 2016)). Matma Rex (talk) 01:06, 29 August 2018 (UTC)

Thanks, that's very helpful and matches some of my own suspicions.

I'd also like to note that the version compatibility matrix on the Visual Editor extension page lists multiple versions of Parsoid higher than 0.5.1 as compatible with MediaWiki 1.27. However, it seems like that's not the case, so perhaps the table is incorrect? Ejs1234 (talk) 01:34, 24 September 2018 (UTC)

I changed the compatibility matrix according to this discussion. When I created initially this compatibility matrix I checked if basic features worked, but it seems here that some advanced features don’t work sometimes.

Possibly this compatibility matrix should be re-checked with more extensive tests and/or put some warning saying this table is non-official. ~ Seb35 [^_^] 16:34, 24 September 2018 (UTC)

VisualEditor works in debug mode only

VisualEditor+Parsoid works fine in debug mode, but progressbar stops at 70% in normal mode. It's all the same with new pages and existing pages.

$wgResourceLoaderDebug = true; /* works with this option */

I've also tried $wgParserCacheType = CACHE_NONE. It doesn't help.

System: MediaWiki 1.31, WAMPServer (PHP 7.2.8 + php_apcu, Apache 2.4.34), Windows 10 (32bit)

UPD: chrome performance recording w/ and w/o debug mode: https://yadi.sk/d/0Hn4f0JG3a2BAb Winand (talk) 07:03, 7 August 2018 (UTC)

Installation error

Hi,

I install the VisualEditor extension. It works front-end side but it doesn't work backend side. It gives me that error when i click edit button:

apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server

Here is my configuration for Visual Editor:

LocalSettings.php

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' => 'https://viki.gameofthronestr.com:8142',
// Parsoid "domain", see below (optional)
'domain' => 'viki.gameofthronestr.com',
// Parsoid "prefix", see below (optional)
'prefix' => 'mediawiki'
);

etc/mediawiki/parsoid/settings.js

parsoidConfig.setMwApi({ uri: 'https://viki.gameofthronestr.com/api.php', domain: 'viki.gameofthronestr.com', prefix: 'mediawiki' });

How can i fix that problem? Any ideas? Bekircem (talk) 09:48, 8 August 2018 (UTC)

If you have a single server it is easier to set Parsoid locally, listening on 127.0.0.1 and port 8142, and use this as configuration for VisualEditor. Also, it is also easier not to use 'domain' and 'prefix', which are old or for specific configurations. These both comments would result in:

LocalSettings.php:

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://127.0.0.1:8142',

);

/etc/mediawiki/parsoid/settings.js:

parsoidConfig.setMwApi({ uri: 'https://viki.gameofthronestr.com/api.php' }); ~ Seb35 [^_^] 07:26, 24 September 2018 (UTC)

where are Visual Editor Plugin Modules?

Where I can get Graph module or any other modules within Visual Editor as Plugin Module as you can see on the below link that's available on wikipedia Visual Editor?

Insert Options in Wikimedia Aravind2905 (talk) 06:51, 13 August 2018 (UTC)

The Graph extension provides the chart option. The Score extension provides the sheet music option. The Kartographer extension provides the map option. Note that several of these require a fair bit of server set up, not least the last of these. Jdforrester (WMF) (talk) 15:58, 13 August 2018 (UTC)

Thank you @Jdforrester!

I was wondering if there is docker images available to replicate all the functionality that Wikipedia uses on the production along with all beta features, gadgets, extensions, live updates instead of manually doing one by one on my own.

That would be really helpful and less pain to configure one by one and trust able features provided by source. Aravind2905 (talk) 22:59, 21 August 2018 (UTC)

No. We run Wikipedia directly on the bare metal with a (large) number of bespoke set-ups, mostly managed via puppet. Moving to a proper virtualised set of images is… a nice idea, but it's very far off. :-(

There's MediaWiki-Vagrant which allows you to run quite a lot of the code we use in production, but some things (like the different pools of app servers dedicated to API requests, or media pools) don't scale down sanely. Sorry. Jdforrester (WMF) (talk) 16:59, 22 August 2018 (UTC)

Can this be any more difficult?

I have a Raspberry PI. It runs Raspbian Jessie. This system is a house of cards and I don't dare run a dist upgrade on it. MediaWiki 1.27 runs beautifully. I decided to try installing this extension to help unskilled users find it easier to edit my open wiki.

Oh hell no... What are the steps? The installation instructions are scattered all over the damn place. I have no interest in diving in the depths of JavaScript just because of an extension - that would take a lot of money or a Groundhog Day infinite time warp to motivate me. This Parsoid acts as a webserver on port 8000, and unencrypted at that? Surely there must have been an easier and more direct way with less resource overhead...

I'm almost certainly not going to do this in 2018. I'll maybe come back in a year and see if it's better. In the meantime, those of you who know how this Rube Goldberg machine works, please fix it and make this page clear and concise. I love to write and by messaging me, I can maybe be talked into it, but overall, this is a crushing and disappointing experience and I'm off to seek out competing choices. Timothylegg (talk) 01:00, 31 August 2018 (UTC)

I think that everyone would love to have clear instructions. I'm sorry to say that I'm not aware of any plans to fix them this year. I hope that you find something that will work for you. Whatamidoing (WMF) (talk) 23:28, 16 October 2018 (UTC)

I agree, Timothy. I have never seen such a ridiculous kluge. This editor should be a self-contained plugin to mediawiki, and installation should be completely managed by clicking something in the admin UI of mediawiki. It is absurd that one is expected to open two special purpose ports (8000 or 8142 for parsoid + 7231 for restbase). Why should someone have to figure that out and deal with changes to their firewall config? They shouldn't. I have spent over 12 hours RTFMing and googling error messages trying to get visualeditor to work and it still doesn't work for me (in a sub-account on a CentOS 7 server where I have root access). You can see some of my posts here that have gone unanswered as well.... :/ End-of-Flame Baxterz (talk) 11:34, 12 February 2019 (UTC)

Creating "sublines"

https://phabricator.wikimedia.org/T190474

Hi - a "subline" (maybe there's another term for it, but that's the one I know) is an indented line within a bulleted or numbered list - in wikitext it's defined by starting a line with "*:" or "#:". VisualEditor handles the round-tripping for these fine. The problem is creating a new subline within the VE interface. Hitting Shift+Enter when on one line of a list seems like it does that - it creates a new line within the list, that's indented - but the resulting wikitext has that new line as just additional text on the line above it. In other words, instead of:

# Item one
#: Comment about item one
# Item two

...the resulting wikitext is:

# Item one  Comment about item one
# Item two

Is this a bug? Or is there another way to create sublines? Yaron Koren (talk) 14:38, 4 October 2018 (UTC)

You are trying to combine ordered-list formatting with definition-list formatting, which is bad HTML. The visual editor does not fully support definition-list formatting yet, but this is the sort of thing that shouldn't be done (that way) anyway.

If you want a visual indentation, then you might consider trying w:en:Template:Pb. The wikitext would then be:

# Item one {{pb}} Comment about item one
# Item two

and the results would be what you seem to be looking for. Whatamidoing (WMF) (talk) 23:26, 16 October 2018 (UTC)

Whatamidoing - thanks for responding. I'm very surprised that you say that the first snippet of wikitext I provided is bad. Whatever HTML it corresponds to (I have no idea, actually), the wikitext itself displays fine and looks quite logical. Are you sure that it's not recommended? What's the point of notation like "#:", if not for cases like this? Yaron Koren (talk) 03:39, 17 October 2018 (UTC)

See Wikipedia:Manual of Style/Accessibility#Lists. Whatamidoing (WMF) (talk) 16:39, 17 October 2018 (UTC)

Sorry, I don't understand - what should I look at there? Yaron Koren (talk) 04:37, 18 October 2018 (UTC)

Whatamidoing - thanks for responding. I'm very surprised that you say that the first snippet of wikitext I provided is bad. Whatever HTML it corresponds to (I have no idea, actually), the wikitext itself displays fine and looks quite logical. Are you sure that it's not recommended? What's the point of notation like "#:", if not for cases like this?

In the #Indentation section said: "A colon (:) at the start of a line marks that line in the MediaWiki parser as the ‎<dd>...‎</dd> part of an HTML description list (‎<dl>...‎</dl>). The visual effect in most Web browsers is to indent the line. This is used, for example, to indicate replies in a threaded discussion on talk pages. However, this markup alone is missing the required ‎<dt> (term) element of a description list, to which the ‎<dd> (description/definition) pertains. As can be seen by inspecting the code sent to the browser, this results in broken HTML (i.e. it fails validation). The result is that assistive technology, such as screen readers, will announce a description list that does not exist, which is confusing for any visitor unused to Wikipedia's broken markup. This is not ideal for accessibility, semantics, or reuse, but is currently commonly used, despite the problems it causes for users of screen readers."

Anyway why hitting Shift+Enter within a list seems like it make a line break, but actually just double spaces  ? Lens0021 (talk) 04:57, 18 October 2018 (UTC)

@Lorentz21 - right, but this doesn't involve a colon at the start of the line - I'm talking about the notation "#:" (or "*:"). That "Accessibility" page says that "*:" is "acceptable practice" - I assume it's the same for "#:". So why not have VE generate that?

You're right, though, that the current approach of just putting in spaces is not ideal by any standard. Yaron Koren (talk) 15:24, 18 October 2018 (UTC)

Under some circumstances, a colon does not have to be the very first character for it to be interpreted as the second part of an HTML description list. Whatamidoing (WMF) (talk) 18:12, 18 October 2018 (UTC)

@Whatamidoing - I just don't understand. The Accessibility page you linked to says that "*:" is acceptable - is that incorrect? Or is there some difference between that and what I'm talking about? Yaron Koren (talk) 19:00, 18 October 2018 (UTC)

Editors at the English Wikipedia accept it. AIUI it does not produce valid HTML. Whatamidoing (WMF) (talk) 16:38, 19 October 2018 (UTC)

Oh, okay. Has been there any discussion about the lack of desirability of "#:" and "*:"? Is it documented anywhere?

In any case, I think just putting in a <br />, instead of spaces, would be fine also - as @Lorentz21 also said. Yaron Koren (talk) 18:21, 19 October 2018 (UTC)

VisualEditor manipulating whitespace?

Recently, the wiki I'm an administrator of forked away from Wikia to its own independent site with a fully up-to-date MediaWiki version. This includes this new version of the Visual Editor which is great (and better than Wikia's) for newbies and IPs, however every time anyone uses the VisualEditor it removes empty lines from one place, adds empty lines in other places and also removes spaces between the asterisk character and the content that follows.e.g. " * Content" becomes "*Content". Is there a way to stop VE from doing that? I've been manually reverting all those changes while also keeping the actual edits that the editors who were using VisualEditor made. There must be some way to stop VE from forceably altering the whitespace on pages? I looked through the complete list of configuration options and I couldn't find an option that might be related. Teysz Kamieński (talk) 12:33, 12 October 2018 (UTC)

Whitespace changes are usually (but not always) a Parsoid thing. Are you running the correct version of Parsoid?

There has been some whitespace preservation work in the past (e.g., T45543) but I haven't seen recent complaints about this. Whatamidoing (WMF) (talk) 23:23, 16 October 2018 (UTC)

I've been told by a sysadmin that we're using the latest version of Parsoid, 0.9.0. Teysz Kamieński (talk) 10:22, 17 October 2018 (UTC)

I think you need to be using RESTBase as well as Parsoid so that you get selective serialization, which prevents some of these normalizations from causing dirty diffs. 2601:19B:A00:C0CC:0:0:0:843F (talk) 22:23, 9 November 2018 (UTC)

Problem is solved now. I believe the sysadmins did indeed turn on selective serialization. Teysz Kamieński (talk) 15:20, 11 November 2018 (UTC)

VisualEditor and shared uploads

I've got shared uploads configured on my wiki and it works fine, but VisualEditor doesn't seem to take it into account. Searching for files returns nothing because there are none of the local wiki, and the upload tab returns the disabled uploads message.

Is there any way for VisualEditor to search for images on the shared uploads wiki rather than the local ones?

Thanks! Synonymshawfinch (talk) 11:02, 16 October 2018 (UTC)

I have the same problem, somebody help me! :) Ivan Mudrik (talk) 12:20, 27 August 2019 (UTC)

Answering my own question (see Manual:$wgForeignFileRepos):

$wgLBFactoryConf = array(

'class' => 'LBFactoryMulti',

'sectionsByDB' => array(

'dewiki' => 's1',

'enwiki' => 's1',

'eswiki' => 's1',

'frwiki' => 's1',

'hiwiki' => 's1',

'itwiki' => 's1',

'jawiki' => 's1',

'plwiki' => 's1',

'ptwiki' => 's1',

'ruwiki' => 's1',

'svwiki' => 's1',

'zhwiki' => 's1',

),

'sectionLoads' => array(

's1' => array(

'localhost'  => 0, // All on section s1, which has single master, at localhost.

),

),

'serverTemplate' => array(

'dbname'        => $wgDBname,

'user'          => $wgDBuser,

'password'      => $wgDBpassword,

'type'          => 'mysql',

'flags'         => DBO_DEFAULT,

'max lag'       => 30,

),

);

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'dewiki',

'name' => 'dewiki', # displayname (eg. the vector-skin-tab “View on OtherWiki“) may be set at wiki-specific MediaWiki:Shared-repo-name-<otherwiki>

'url' => 'https://de.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2, # This must be the same for the other family member

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://de.companypedia.net/w', # has effect whether description can be fetched

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'enwiki',

'name' => 'enwiki',

'url' => 'https://en.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://en.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'eswiki',

'name' => 'eswiki',

'url' => 'https://es.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://es.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'frwiki',

'name' => 'frwiki',

'url' => 'https://fr.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://fr.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'hiwiki',

'name' => 'hiwiki',

'url' => 'https://hi.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://hi.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'itwiki',

'name' => 'itwiki',

'url' => 'https://it.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://it.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'jawiki',

'name' => 'jawiki',

'url' => 'https://ja.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://ja.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'plwiki',

'name' => 'plwiki',

'url' => 'https://pl.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://pl.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'ptwiki',

'name' => 'ptwiki',

'url' => 'https://pt.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://pt.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'ruwiki',

'name' => 'ruwiki',

'url' => 'https://ru.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://ru.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'svwiki',

'name' => 'svwiki',

'url' => 'https://sv.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://sv.companypedia.net/w',

];

$wgForeignFileRepos[] = [

'class' => 'ForeignDBViaLBRepo',

'wiki' => 'zhwiki',

'name' => 'zhwiki',

'url' => 'https://zh.companypedia.net/w/images',

'directory' => '/var/www/mediawiki/wiki/w/images',

'hashLevels' => 2,

'tablePrefix' => '',

'hasSharedCache' => false,

'fetchDescription' => true,

'scriptDirUrl' => 'https://zh.companypedia.net/w',

]; Ivan Mudrik (talk) 07:01, 18 September 2019 (UTC)

Using visual editor on MinervaNeue Desktop mode

I dont have the option to use Visual editor on MinervaNeue desktop mode. Am I missing something? The mobile editor lacks in functionality and I want desktop users to have more options than the ones that are given in the mobile mode.

Thanks! Ztiruam (talk) 10:27, 21 October 2018 (UTC)

Well... On the one hand, this skin isn't technically on the list of supported skins for VisualEditor (if memory serves). On the other hand, that's really, seriously broken. It looks like you can only edit (in any editor) once, and then nothing happens if you click the edit buttons a second time. I'll file a bug today, and I think it's likely to get some attention soon. Whatamidoing (WMF) (talk) 16:23, 25 October 2018 (UTC)

Great! the MinervaNeue skin is pretty buggy and I've spent many hours tinkering with it. I found a solution and posted it here, for those who are interested:Skin talk:Minerva Neue/2018#h-Toggle_desktop_visual_editor_on_Desktop_mode-2018-10-21T10:35:00.000Z Ztiruam (talk) 16:26, 25 October 2018 (UTC)

Tracked in Phabricator
Task T208068

Can you try something for me? Once you open the (wikitext) editor, could you find the pencil icon in the toolbar, and see if it lets you switch to visual mode? Whatamidoing (WMF) (talk) 17:10, 26 October 2018 (UTC)

No it doesnt let me :( Ztiruam (talk) 06:45, 27 October 2018 (UTC)

This is supposed to be mostly fixed – at this site, anyway. It won't reach most of the Wikipedias for a couple of days. Would you like to try it out in User:Whatamidoing (WMF)/Sandbox? Whatamidoing (WMF) (talk) 02:55, 7 November 2018 (UTC)

Seems to work in the sandbox... hm... oh well, my fix worked for me : ) Ztiruam (talk) 16:39, 11 November 2018 (UTC)

Does this work with MS Upload or have similar drag and drop image insertion capabilities?

I want to be able to just drag and drop images onto a page I'm editing or be able to paste it from my clipboard. This is possible with the Extension:WikiEditor using the Extension:MsUpload but doesn't appear to work with Visual Editor? Considering Visual Editors focus on bringing a more modern frontend content editing experience to mediawiki, the exclusion of this functionality seem odd. AslanFrench (talk) 22:58, 28 October 2018 (UTC)

There is the feature in the Visual Editor: during edition with VE, click on Insert > Media > tab Upload, and here you can drag and drop the image, then you have to fill some description of the image and it finally upload the image. ~ Seb35 [^_^] 08:11, 31 October 2018 (UTC)

There are less features in this interface than in MsUpload but the basic feature exists. ~ Seb35 [^_^] 08:13, 31 October 2018 (UTC)

It seems that the intended use case for VE actually does include the ability to simply drag and drop or copy paste without having to hit the insert media tab. As per this story here: https://phabricator.wikimedia.org/T39932

I've filed a bug on the topic here for anyone interested: https://phabricator.wikimedia.org/T208631 AslanFrench (talk) 21:18, 2 November 2018 (UTC)

"Just copy" from one page to another needs to vary according to the pages in question. Adding new images to the public wikis (e.g., Wikipedia) requires a separate licensing step, for legal/copyright reasons. Copying an image from one Wikipedia page to another Wikipedia page does not.

You can currently open two Wikipedia pages in the visual editor, copy and image from the first, switch to the other tab, and paste the image into the second. You should not be able to open a Wikipedia article and a news website, copy an image from the website, and "just" paste it into the Wikipedia article. Whatamidoing (WMF) (talk) 17:07, 9 November 2018 (UTC)

@Whatamidoing (WMF) Why not just have the process of copying into Visual Editor paste over the image and trigger the licensing pop up?

Also if you check the bug I filed there is conversation on how things can be copy pasted from MSpaint.exe but not from a page, due to the way that wikitext cannot accept img tags with external resources, so I'm not sure it's an intentional design decision so much as it is a limitation of the implementation as it relates to previously designed systems.

To quote:

Turns out that when you copy an image in the browser, it is stored in the clipboard in two formats: as the actual image, and as HTML like this:

<html>

<body>

<img src="https://apod.nasa.gov/apod/image/1705/Arp273Main_HubblePestana_3079.jpg" alt="Image result for galaxy"/>

</body>

</html>

When this is pasted into VisualEditor, we use the HTML instead of the image (ve.ce.Surface.prototype.handleDataTransfer), because:

// Only look for files if HTML is not available:

// - If a file is pasted/dropped it is unlikely it will have HTML fallback (it will have plain text fallback though)

// - HTML generated from some clients has an image fallback(!) that is a screenshot of the HTML snippet (e.g. LibreOffice Calc)

Then our paste sanitization strips that HTML down to nothing (since <img> tags using external resources are not possible in wikitext), and then nothing is pasted. AslanFrench (talk) 21:32, 13 November 2018 (UTC)

I have only said that "just" pasting an external image alone is not acceptable for Wikimedia wikis.

The sentence in the task that begins "I'd imagine we'd be less likely to accept this for Wikimedia wikis..." is the key one. Not every feature in VisualEditor works in (or is relevant to) Wikipedia. Whatamidoing (WMF) (talk) 00:47, 14 November 2018 (UTC)

VE fails when we have Facebook comments widget on page

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 have installed mw 1.31, VE, restbase and etc. https://l2wiki.com/Special:Version

All works fine, but when I enabled PageDisqus extension or added Facebook comments widget - then on pressing Edit VE fails and not loads.

How we can make VE and Disqus\facebook comments work together? :( StRiANON (talk) 16:43, 29 October 2018 (UTC)

@Seb35 Can you answer please? StRiANON (talk) 00:52, 5 November 2018 (UTC)

It’s difficult to answer since I have no account on your wiki and didn’t test these extensions together. Can you try to activate first PageDisqus, press Ctrl+F5 and Ctrl+R on your browser (depending on your browser, pressing both is harmless), and click on 'Edit VE' (sometimes there are browser cache issues). If this does not work, open the Developer Tools of Firefox (F12), click on the tab Console, press Ctrl+F5, and check if there are errors (in red) or warnings (in yellow), and report here there errors/warnings. ~ Seb35 [^_^] 10:57, 5 November 2018 (UTC)

Replied below. StRiANON (talk) 02:54, 18 November 2018 (UTC)

@Seb35 I still waiting for you, please, check it, because we have a trouble here, with VE and PageDisqus or facebook widget, and I want to know, can we have a fix or not.

The possible fix here is to add something similar to

if ( $wgRequest->getVal( 'action', 'view' ) != 'view' ) {

return true;

}

into PageDisqus onSkinAfterBottomScripts function code, but I don't know, what same we need to write here for VisualEditor. I tried just replace action to veaction, but this doesn't work. StRiANON (talk) 16:15, 21 November 2018 (UTC)

Finally found the problem - it was in a custom resourceloader module, not in the PageDisqus ext or VE. StRiANON (talk) 14:14, 22 November 2018 (UTC)

Ok, I activated PageDisqus and created acc for you on l2wiki.com, login and pass are:

checker

testit

Please, log in and then edit main page - and you will see messages in console, something about "VisualEditor failed to load: Error: Module ext.visualEditor.mwcore has failed dependencies" and etc.

I think it will be better if you can see messages by yourself.

Without enabled PageDisqus or Facebook comments, that inserted as it described in the instruction, all works fine. StRiANON (talk) 14:34, 15 November 2018 (UTC)

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

Is there a way to install this extension on arm debian?

I use raspberry pi to host my media wiki site and this extension would be useful, but parsoid is not available on arm 2601:280:4200:42E6:79D7:341C:8195:4128 (talk) 19:22, 9 November 2018 (UTC)

Parsoid doesn't have any binary dependencies. You can use the released deb on all architectures. Arlolra (talk) 20:25, 9 November 2018 (UTC)

I just installed parsoid using source and it appears to be working. 2601:280:4200:42E6:79D7:341C:8195:4128 (talk) 21:30, 9 November 2018 (UTC)

Visual Editor "Embed Video" Button

Hi, I've just +1'ed the idea to have an "embed video" button in visual editor Extension talk:EmbedVideo#Visual Editor EmbedVideo Button

Is there anyway to get that onto the Visual Editor roadmap?

Many thanks in advance --Tansaku 2A00:23C0:B04:AC01:8CCF:77DA:31F8:7D53 (talk) 18:06, 5 December 2018 (UTC)

That would have to be something the EmbedVideo developers worked on. It should be pretty easy for them to do. Jdforrester (WMF) (talk) 18:09, 5 December 2018 (UTC)

The VirtualRESTService for the document server is not defined

When I installed this extension then click the edit button,it just pop up a window said “no_vrs: The VirtualRESTService for the document server is not defined;”

What’s that mean?screenshot 机智的小鱼君 (talk) 19:02, 5 December 2018 (UTC)

I have the same problem. Have you found a solution? 95.128.148.222 (talk) 11:37, 25 January 2019 (UTC)

Same probleme, i have installed parsoid and nodejs ... but i have this message ... 185.48.255.114 (talk) 08:54, 29 January 2019 (UTC)

parsoid upgrade from 9 to 10broke ve on debian stretch

Hello, I posted to parsoid discussion: https://www.mediawiki.org/wiki/Talk%3AParsoid/2018#h-upgrade_from_9_to_10_resulted_in_curl_error%3A_7-2018-12-09T13%3A36%3A00.000Z

after upgrade clicking edit displated

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

If you may have a solution, or the same issue, please post at https://www.mediawiki.org/wiki/Talk%3AParsoid/2018#h-upgrade_from_9_to_10_resulted_in_curl_error%3A_7-2018-12-09T13%3A36%3A00.000Z RobFantini (talk) 13:40, 9 December 2018 (UTC)

Error when editing a page: Error loading data from server: HTTP 0. Would you like to retry?

System information:

OS: Windows Server 2008

Mediawiki: 1.27.3

PHP: 5.6.30

MySQL: 5.7.18

VisualEditor: 0.1.0

nodejs: v8.9.1

Parsoid: 0.8.0

Symptoms:

• Editing a page with VisualEditor, received the following error:

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

The page itself is not very large (14 KB in wikicode). Using direct corresponding api call in the browser bar (http://xxx/api.php?action=visualeditor&format=json&paction=parse&page=...) returns a result after almost one minute;

• Issue with 30 s ajax timeout in \mediawiki-1.27.3\resources\src\mediawiki\api.js . Changing the timeout to one minutes fixed the issue

Questions:

• There are 200 media links in the test page. Is the parsoid response time I am experiencing (~ 60 seconds) what one would expect?
• Any way of making it faster (e.g., setting ParsoidConfig.prototype.fetchImageInfo to false)?
• Any way to provide better information as to what is happening to the user?

Thanks in advance for any answers. Ti infotrad (talk) 13:15, 13 December 2018 (UTC)

I sometimes having the same issue with timeouts in VisualEditor, just because Parsoid is waiting for API. Czech.Fox (talk) 16:23, 24 January 2019 (UTC)

Same issue for me in mediawiki 1.33.4. The file has changed here. It is now resources/src/mediawiki.api/index.js but the suggested fix still solves the problem. C holtermann (talk) 08:54, 5 December 2020 (UTC)

Exclude /doc from template name search

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.

---

Hello!

I'd like to exclude /doc, /Documentation results from search results in the template tool. Template data is defined in those subpages and then transcluded and they should not show up in the result set.

Thanks! Tinss (talk) 00:15, 27 December 2018 (UTC)

Hey there, you're right that this is an irritation, and has been for a while – it was first reported way back in 2013. Looking at your request it struck me that we now have a way to do this, so it should be fixed very soon. Jdforrester (WMF) (talk) 19:33, 9 January 2019 (UTC)

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

error loading data from server: apierror-visualeditor-docserver-http: http 401

Hello gurus,

I have the following enviornment:

OS (Linux vm-intwiki 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux)

MediaWiki

1.33.0-alpha (84460b0)

VisualEditor

0.1.1 (9cd26f5) 00:52, 27 December 2018

LDAP Authentication Plugin

2.1.0 (662eaaf) 19:37, 15 November 2018

So I installed parsoid, temporary turned off my LDAP and created a user for parsoid for

NetworkAuth

2.1.2 (58ddb5e) 12:12, 9 March 2018

However, I still have the following error

error loading data from server: apierror-visualeditor-docserver-http: http 401

Any ideas how can I fix it?

Regards,

Serge 67.183.134.86 (talk) 01:22, 29 December 2018 (UTC)

hi,

read this

User:Andrujhon/Allow Parsoid Server

its helped me to solve this. 192.116.109.192 (talk) 09:26, 1 March 2020 (UTC)

Problem with FlaggedRevs with MW 1.31

We have recently upgraded the MW v1.29 to v.31 with both FlaggedRevs and VisualEditor extension updated.

The problem I have is with Visual Editor "Edit" button now directs you to the stable (approved) page, instead of showing the latest edit.

This was not an issue in v1.29 but it looks like EDIT button now carries the "OLID" parameter that is causing the issue (see the link example below)

MYSITE/mediawiki/index.php?title=PAGENAME&stable=1&veaction=edit&oldid=48401

Is there a way to remove the OLDID paramater so it directs you to the latest revision to edit, review, and approve the page? 64.251.40.244 (talk) 20:47, 31 December 2018 (UTC)