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.

404: docserver-http: HTTP 404.

Similar error perhaps to the parsoidserver-http: HTTP 404 error. Parsoid and VE don't seem able to talk to eachother. Curl is working, I've removed both the extra # and the - from the line "# This is the only required parameter,"

The only line in config.yaml is "uri: '[mydomain].co/mediawiki/api.php'

When I try to edit a page on the wiki it gives me a "Error loading data from server: 404: docserver-http: HTTP 404. Would you like to try again?" error and the parsoid log throws a:

{"name":"parsoid","hostname":"li1778-46","pid":9678,"level":60,"err":{"message":"Invalid domain: [mydomain].co","name":"../src/lib/index.js","stack":"../src/lib/index.js: Invalid domain: [mydomain].co\n    at errOut (/usr/lib/parsoid/src/lib/api/routes.js:31:13)\n    at routes.v3Middle (/usr/lib/parsoid/src/lib/api/routes.js:106:11)\n    at Layer.handle [as handle_request] (/usr/lib/parsoid/node_modules/express/lib/router/layer.js:95:5)\n    at next (/usr/lib/parsoid/node_modules/express/lib/router/route.js:137:13)\n    at Route.dispatch (/usr/lib/parsoid/node_modules/express/lib/router/route.js:112:3)\n    at Layer.handle [as handle_request] (/usr/lib/parsoid/node_modules/express/lib/router/layer.js:95:5)\n    at /usr/lib/parsoid/node_modules/express/lib/router/index.js:281:22\n    at param (/usr/lib/parsoid/node_modules/express/lib/router/index.js:354:14)\n    at param (/usr/lib/parsoid/node_modules/express/lib/router/index.js:365:14)\n    at param (/usr/lib/parsoid/node_modules/express/lib/router/index.js:365:14)\n    at param (/usr/lib/parsoid/node_modules/express/lib/router/index.js:365:14)\n    at param (/usr/lib/parsoid/node_modules/express/lib/router/index.js:365:14)\n    at Function.process_params (/usr/lib/parsoid/node_modules/express/lib/router/index.js:410:3)\n    at next (/usr/lib/parsoid/node_modules/express/lib/router/index.js:275:10)\n    at /usr/lib/parsoid/src/lib/api/ParsoidService.js:170:3\n    at Layer.handle [as handle_request] (/usr/lib/parsoid/node_modules/express/lib/router/layer.js:95:5)","httpStatus":404,"suppressLoggingStack":true,"levelPath":"fatal/request"},"msg":"Invalid domain: [mydomain].co","time":"2019-01-28T14:56:57.237Z","v":0}

I'm on:

parsoid 0.8

MediaWiki 1.27.5

VE 0.1.0

MediaWiki is on Debian 9.6

and the Parsoid server is on Ubuntu 18

thoughts? Thanks! :)

Treebytron (talk) 15:04, 28 January 2019 (UTC)

Replace your config.yaml with below lines and try again.

worker_heartbeat_timeout: 300000
logging:
    level: info
services:
  - module: lib/index.js
    entrypoint: apiServiceWorker
    conf:
      uri: '[mydomain].co/mediawiki/api.php'
      domain: '[mydomain].co'

And I would like to ask you whether your domain is really [mydomain].co. If is not, you replace it too with your real hosted domain or IP address in some cases. Lens0021 (talk) 15:27, 28 January 2019 (UTC)

hey thanks for quick response. Not sure exactly why I hid the domain haha. I tried your config, parsoid wouldn't run I think because the module is in a different place, but I tried this one,

worker_heartbeat_timeout: 300000

logging:

    level: info

services:

  - module: ../src/lib/index.js

    entrypoint: apiServiceWorker

    conf:

      uri: 'wiki.spacebase.co/mediawiki/api.php'

      domain: 'wiki.spacebase.co'

and parsoid runs but I get the same error on edit, "Error loading data from server: 404: docserver-http: HTTP 404. Would you like to try again?" Treebytron (talk) 15:59, 28 January 2019 (UTC)

The log you wrote above includes "Invalid domain: [mydomain].co", how is it now? Lens0021 (talk) 16:05, 28 January 2019 (UTC)

same log output, ends with "msg":"Invalid domain: wiki.spacebase.co","time":"2019-01-28T16:13:39.102Z","v":0}

visual editor section of localsettings.php on the mediawiki machine is,

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

    // URL to the Parsoid instance

    // Use port 8142 if you use the Debian package

    'url' => '172.104.187.46:8142',

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

    //'domain' => 'http://wiki.spacebase.co/mediawiki/',

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

    //'prefix' => 'localhost'

);

I read that 'domain' must match between localsettings.php and config.yaml, is that true? Treebytron (talk) 16:19, 28 January 2019 (UTC)

Yes, that is. So you need to uncomment 'domain' => 'http://wiki.spacebase.co/mediawiki/', and rewrite it. Finally whole code could be:

$wgVirtualRestConfig['modules']['parsoid'] = array(
    'url' => '172.104.187.46:8142',
    'domain' => 'wiki.spacebase.co',
);

Lens0021 (talk) 16:25, 28 January 2019 (UTC)

ah, ok, made the change. Also, I should have noted, the parsoid log only throws that error after trying to open the visual editor on the web. Just after freshly rebooting parsoid the log ends with a line with "msg":"Startup finished"

Made the change to localsettings.php and still getting "Invalid domain: wiki.spacebase.co" in the parsoid log.

Is there anything that needs to be rebooted after making changes to localsettings.php? No, right?

I guess another datapoint is that when I try hitting http://172.104.187.46:8142/wiki.spacebase.co/mediawiki/index.php/Main_Page in the browser it returns Cannot GET /wiki.spacebase.co/mediawiki/index.php/Main_Page Treebytron (talk) 16:35, 28 January 2019 (UTC)

Is there anything that needs to be rebooted after making changes to localsettings.php? No, right?

No, sudo service parsoid restart is enough I think.

The parsoid log says that it sent data from the server but does not know included domain name "wiki.spacebase.co". Therefore there is a something wrong in your config.yaml. But I have no more idea... :( Lens0021 (talk) 16:47, 28 January 2019 (UTC)

I guess another datapoint is that when I try hitting http://172.104.187.46:8142/wiki.spacebase.co/mediawiki/index.php/Main_Page in the browser it returns Cannot GET /wiki.spacebase.co/mediawiki/index.php/Main_Page

Sorry, I was missing: uri: 'wiki.spacebase.co/mediawiki/api.php' in config.yaml would be uri: 'http://wiki.spacebase.co/mediawiki/api.php'. Lens0021 (talk) 16:55, 28 January 2019 (UTC)

Could you try replace all "wiki.spacebase.co" with "spacebase.co"? I have noticed I had same problem when I put two or more dots in domain. Lens0021 (talk) 17:12, 28 January 2019 (UTC)

thanks so much for your help Lorentz21. I replaced wiki.spacebase.co in localsettings (so now it's     'url' => '172.104.187.46:8142',   'domain' => 'spacebase.co') and in config.yaml and made the http change (so config.yaml is now  uri: 'http://wiki.spacebase.co/mediawiki/api.php' domain: 'spacebase.co')

Still 404 error. Now though the parsoid log indicates Invalid domain: spacebase.co, so now I know where it's pulling that domain from...

maybe I'll play around with that domain setting....

Treebytron (talk) 21:52, 28 January 2019 (UTC)

Usually the script path and the article path are different, so test in a browser whether http://wiki.example.com/api.php works. If yes, put it in the parsoid's config.yaml. Spas.Z.Spasov (talk) 01:14, 29 January 2019 (UTC)

Oh, I am apologizing I made a mistake, try this:

1. Fix your config.yaml like below: (I forgot mwApis: last time)

   worker_heartbeat_timeout: 300000
   logging:
       level: info
   services:
     - module: ../src/lib/index.js
       entrypoint: apiServiceWorker
       conf:
         mwApis:
           - uri: 'wiki.spacebase.co/mediawiki/api.php'
             domain: 'wiki.spacebase.co'
   

2. Reboot parsoid.
3. Test http://172.104.187.46:8142/spacebase.co/v3/page/html/Main_Page Lens0021 (talk) 02:06, 29 January 2019 (UTC)

thanks Spas.Z.Spasov, I've tested and api.php is at http://wiki.spacebase.co/mediawiki/api.php, wiki.spacebase.co/apt.php doesn't resolve.

good catch Lorentz21! Thanks! Parsoid failed to launch now due to indentation issues with that exact config.yaml. Parsoid log gave me,

Error while reading config file: YAMLException: bad indentation of a mapping entry at line 4, column 3:

      services:

But I messed around with indentation so that it now runs, but when I tried to edit a page I get

Error loading data from server: 500: docserver-http: HTTP 500. Would you like to try again?

in the browser and http://172.104.187.46:8142/spacebase.co/v3/page/html/Main_Page returnsInvalid domain: spacebase.co

parsoid log gives me an Error: Invalid URI \"wiki.spacebase.co/mediawiki/api.php\" error.

So... perhaps some more fiddling with indentation is in order. Thanks for all your help! :)

Treebytron (talk) 20:29, 30 January 2019 (UTC)

Cannot get Citations Enabled

I have gotten VisualEditor to successfully work on my WikiMedia installation, but cannot get the Citation button to work. I have looked at the instructions here Help:VisualEditor/User guide/Citations-Full and here VisualEditor/Citation tool but there is simply no citation button in my VisualEditor. I suspect the fact that I am using MW version 1.27 and compatibility with wikipedia's citation templates is part of the problem. Does anybody know where I could find citation templates compatible with my version or how to begin to debug why the citation button is not showing up? The wiki is here: https://foia.wiki Mitchell.kotler (talk) 20:26, 28 January 2019 (UTC)

Canonical namespace for

In Changing active namespaces it is stated that "There are many ways to do this but it is recommended to use the canonical names defined for the respective namespaces".

Q1: How can one find the canonical namespace of an extra namespace defined in a non-Latin script. I just used the namespace as defined but it was not excluded. Should it, for example, be escaped in a certain way?

Q2: What are the other many ways to do this? Does any of them include using the ID of the namespace? Ahmad Gharbeia أحمد غربية (talk) 14:11, 7 February 2019 (UTC)

No text after installation

I have been trying to install mediawiki with visualeditor on a CentOS 7 server. I installed v1.32.0 no problem and it runs fine (with the regular text-based editor). I then installed visualeditor VisualEditor: v0.1.0 (21d40ce) REL1_32 2018-11-05T23:22:00, parsoid version 0.10.0 and a working freshly installed version of RESTbase. I opened the ports on my firewall and can get to the webpages by going to http://myserver.com:8000 for parsiod and http://myserver.com:7231 for RESTbase. Then I start parsoid and restbase with the node commands.

When I on any page, such as Main_page or any page that I create, I can click the "Edit" tab, and visual editor loads without a problem, and I can "edit". However, the first problem is that the text that already exists on the page (put in with the text editor) is not in the edit window. The edit window is blank! And, if I type stuff in there and try to Save, I get a HTTP 404 error displayed.

Can someone clue me in on what issue(s) to fix? Thanks in advance for helping a mediawiki virgin!!! Baxterz (talk) 22:10, 9 February 2019 (UTC)

*Really* exclude VisualEditor from namespace

By default, VisualEditor is excluded from the Template namespace, that is good. But it is not *really* excluded : if someone replaces, in the url, "&action=edit" with "&veaction=edit", VisuaEditor is activated. Is there a possibility to avoid that ?

In my case, the problem is that when you click on a red link (template page not existing yet), the url contains "&veaction=edit", therefore VisualEditor is automatically launched if I create a Template this way. Varlin (talk) 22:05, 19 February 2019 (UTC)

Caught exception of type Error when saving changes in VisualEditor

Any ideas about what would cause "Error loading data from server: apierror-visualeditor-docserver-http-error: http-request-error. Would you like to retry?"

Thanks, ~ Setian~mw (talk) 07:05, 22 February 2019 (UTC)

Not logged in?

I have installed VisualEditor and it seems to be properly linked to parsoid service. However, when I try to edit a page I get a message warning that I am not loggedin to the wiki, even if I am. I cannot edit the text (I can add new text but I see the paragraphs and photos in green boxes non editable) and when I finally try to save changes I am asked to confirm my e-mail. Everything so strange. How can I fix that? 85.84.142.59 (talk) 14:18, 23 February 2019 (UTC)

Mediawiki 1.32

We just upgraded to mediawiki 1.32. We have visual editor working fine with mediawiki 1.31, but with 1.32 the visual editor fails to even start loading and has this warning/error in the js console in the browser:

> VisualEditor failed to load: Error: One or more dependencies failed to load

Has anyone else experienced similar?

More details here: https://github.com/AgileVentures/SocialPrescribingWiki/issues/76 Tansaku (talk) 13:48, 1 March 2019 (UTC)

Bump, pretty frustrating... Ryanjjjj (talk) 04:19, 4 March 2019 (UTC)

Same problem here. MW 1.32 (Docker image), linking to a Parsoid service that is also running in a Docker container (and is up and running). Bovender (talk) 10:10, 28 April 2019 (UTC)

For me worked after I saw this:

From : Extension:VisualEditor#Basic configuration for MediaWiki-VisualEditor

For the General User: If you're using the latest stable version of MediaWiki you will need to download the VisualEditor-MediaWiki extension from the ExtensionDistributor page. Bozomal (talk) 14:15, 23 May 2019 (UTC)

I fought with this issue for a while and ended up going through and disabling all of my extensions one-by-one. In my case it was the UserPageViewTracker extension that was causing this error somehow. As soon as I disabled it, this error was resolved. Dstoeltz (talk) 18:56, 21 November 2019 (UTC)

Have similar issue. Mine seems to be linked to Chameleon skin 205.200.97.2 (talk) 16:04, 6 December 2019 (UTC)

I have now upgraded to MW 1.34, updated the VisualEditor extension, and it works! Using the Chameleon skin, btw. Bovender (talk) 12:45, 5 January 2020 (UTC)

mediawiki 1.32.1 apierror-visualeditor-docserver-http-error: (curl error: 6)

MsCatSelect like category management

Hi,

MsCatSelect extension provides an easy and intuitive way of managing categories in MediaWiki. On our wiki, we recently switched to Visual editor due to it's better features but now we lost the ability to use MsCatSelect extension to manage categories. We miss the feature of drop down lists and that It can automatically detect/create new subcategories.

I've tried to hack it around but with no lock, I could display the extension on the edit page but I have no clue how I can also use it for saving the new category lists/settings.

I'd like to ask whether somebody has successfully connected MsCatSelect with VisualEditor or if there are any plans on implementing such a feature into VisualEditor.

Thank you!

213.81.164.217 (talk) 14:55, 6 March 2019 (UTC)

Visual Editor + Flagged Rev issue on MW 1.31

Since I have upgraded the MW from 1.27 to 1.31, clicking the "Edit" now shows "Warning: You are editing an out-of-date revision of this page. If you save it, any changes made since this revision will be lost." if you try to edit a page with the accepted revision (from Flagged Rev)

Back in 1.27, clicking the "Edit" button always displayed the latest (unapproved) version... How can we force Visual Editor to show the latest version? 64.251.40.246 (talk) 21:20, 7 March 2019 (UTC)

As far as I can tell, the VE dev team introduced an (not very well documented ) autosave feature. I was experiencing the same issue as you so I disabled it (sessionStore=false at line 354 in \modules\ve-mw\init\targets\ve.init.mw.DesktopArticleTarget.init.js) and it seems to have fixed it. Ti infotrad (talk) 10:59, 18 March 2019 (UTC)

Thank you for the response - I have disabled the session store but the problem still persists. Do you remember any other changes that you've made along with the line 354 change? 64.251.40.248 (talk) 20:42, 18 March 2019 (UTC)

It worked for me. Did you hard clear your browser cache? Ti infotrad (talk) 11:39, 19 March 2019 (UTC)

Tried in both IE and Chrome with cache cleared - no go. I will try to download fresh copy of the extension and try again 64.251.40.242 (talk) 14:21, 19 March 2019 (UTC)

Unfortunately changing the sessionstore didn't help my issue. Note that my "Edit" button has the oldid paramter that is forcing the visual editor to display the "approved" version and not the "latest version"

URL Example - *wiki address*/index.php?title=Test&oldid=52301&veaction=edit 64.251.40.242 (talk) 14:36, 19 March 2019 (UTC)

Hmmm, it does not sound like the problem I was experiencing. You would have to look at the code to check why the oldid is tacked to the vedit action in the VE code... Ti infotrad (talk) 17:13, 19 March 2019 (UTC)

I have intentionally broke the extension by commenting out the line 356 (//oldId: oldId,)of the same file (\modules\ve-mw\init\targets\ve.init.mw.DesktopArticleTarget.init.js)

The problem is that editing old revision no longer works which it may present another issue down the road.

@Ti infotrad - Do you use Flagged Revision with Stable version set to default? (See https://www.mediawiki.org/w/index.php?title=Extension%20talk%3AFlaggedRevs/archive%204/Flow%20export#c-Dadai12-2013-07-12T11%3A49%3A00.000Z-84.253.4.90-2011-08-22T11%3A57%3A00.000Z) 64.251.40.242 (talk) 20:10, 19 March 2019 (UTC)

No, I do not use this extension. I would try disabling it to see if you still run into the issue. Ti infotrad (talk) 11:24, 20 March 2019 (UTC)

I've fixed the problem by looking at the MW 1.32 codes for both Visual Editor and Flagged Rev.

For others who are encountering this problem - please see below

1. Download Visual Editor and Flagged Rev extension for MW 1.32
2. Copy the following files to your MW 1.31 environment
   1. FlaggedRevs\frontend\FlaggablePageView.php
   2. VisualEditor\modules\ve-mw\int\targets\ve.init.mw.DesktopArticleTarget.init.js

Explanation

• FlaggedRevision added "wgFlaggedRevsEditLatestRevision" config variable to check if the page you are looking at the is stable or latest version
  • Please see line 1383 and 1384 in the FlaggablePageView.php from MW 1.32
• Using the newly added "wgFlaggedRevsEditLatestRevision" variable, Visual Editor can now determine if you are looking at the stable or the latest version
  • Please see the line 491 in the ve.init.mw.DesktopArticleTarget.init.js from MW 1.32

I didn't read the entire script and have cause problem. If I find it, I will come back here to mention it.

Also, I will create a simple DL link that fixes both revision and media link issue later today when I get back home 64.251.40.248 (talk) 16:40, 20 March 2019 (UTC)

Visual Editor converting [[Media:]] tags to Protocol-relative external link

Anyone having the issue where the Visual Editor is converting Media tags ([[Media:file.pdf|example]] to protocol-relative external link ([\\sitename\path\file.pdf example])? 64.251.40.244 (talk) 14:18, 8 March 2019 (UTC)

I am having the same issue with MW 1.31. I think it is related to https://phabricator.wikimedia.org/T198511 Ti infotrad (talk) 10:54, 18 March 2019 (UTC)

Thank you for the response - i have manually updated the modules/ve-mw/dm/annotations/ve.dm.MWInternalLinkAnnotation.js file using the https://gerrit.wikimedia.org/r/454860

It looks like Media link is back but would like your feedback before implementing the change in the live wiki 64.251.40.248 (talk) 21:06, 18 March 2019 (UTC)

That sounds reasonable (though note that it will require a reasonably-recent version of Parsoid, too). To make things easier, I've cherry-picked it into the 1.32.x-compatable branch so you can use it directly there. Hope this helps! Jdforrester (WMF) (talk) 21:43, 18 March 2019 (UTC)

To me the change did nothing, the [[Media: ]] link still gets replaced by [[\\localhost\...]]. 83.243.48.54 (talk) 06:01, 11 July 2019 (UTC)

Hello, just an update to my last post: After having rebooted the wiki-server, everything went swell, the [[Media:...]] links remained, and I can now edit pages just like that. Thank you everyone for your support. 83.243.48.54 (talk) 11:49, 12 July 2019 (UTC)

Update Parsoid/MediaWiki compatibility table

Because

• I am particularly interested in the fix for the direct file links (https://phabricator.wikimedia.org/T151277);
• I noticed WikiPedia does not exhibit this issue and it runs MW 1.33 and VisualEditor 0.1.1;
• there are no corresponding entries in the Parsoid/MediaWiki compatibility table,

Would it be possible to update the table to include these versions?

Subsidiary question: is it possible to run newer versions of VE and Parsoid with an older version of MW? Ti infotrad (talk) 18:35, 18 March 2019 (UTC)

https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/325341 was merged in May 2017 and released in Parsoid v0.8.0.

Note that VisualEditor is not versioned independently of MediaWiki. "0.1.1" is a prototype artefact, not a real version number, and has been this way for most of the decade.

Finally, in general, no, running old versions of MediaWiki is impossible with new Parsoid and VisualEditor, as we have to add new core functionality for them to work. Jdforrester (WMF) (talk) 21:36, 18 March 2019 (UTC)

Hello,

Thank you for your help. Note that, with respect to this thread and https://www.mediawiki.org/wiki/Extension%20talk%3AVisualEditor/2019#h-Visual_Editor_converting_%5B%5BMedia%3A%5D%5D_tags_to_Protocol-relative_external_link-2019-03-08T14%3A18%3A00.000Z, the reason why I am using MW 1.31 is because it is the Long Term Support version, hence my question above. Since 1.31 is supposed to be maintained up to June 2021, is there any chance/possibility the fix can be backported? Ti infotrad (talk) 11:55, 19 March 2019 (UTC)

No. "LTS" refers to security updates for the core of MediaWiki and bundled extensions, not other extensions, sorry. Note that any security issues with VisualEditor would not be back-ported (though, in the eight years to date, the project has not had to release any). Jdforrester (WMF) (talk) 15:25, 19 March 2019 (UTC)

Can't search for pictures in Media Tab

Hello,

i noticed a problem with my companys Mediawiki.

In the Mediatab from VE no pictures are found with any input, even exact filenames.

We have Mediawiki-1.30.0 and VisualEditor-REL1_30 installed.

Uploading pictures work fine and they are also displayed.

They also exist as a File and are in the images folder.

If i enable $wgUseInstantCommons, pictures are found.

This seems strange. Does anyone know what the problem could be?

Thanks 87.148.76.3 (talk) 17:03, 20 March 2019 (UTC)

Parsoid vs. private wiki over HTTPS

Hello,

I'm having problems setting up Parsoid on a private Wiki.

It works fine in public mode but I want to restrict even reading the wiki to authenticated users.

The wiki is served by Apache 2.4 with SSL enabled and HTTP redirected to HTTPS, so it's strictly HTTPS.

I did the following configurations:

LocalSettings.php

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

        'url' => 'https://myhost:8001',

        'forwardCookies' => true

);

$wgSessionsInObjectCache = true;

config.yaml (parsoid)

uri: 'https://myhost/mediawiki/api.php'

domain: 'myhost'

stunnel.conf

cert = /etc/apache2/ssl.crt/myhost.crt

key = /etc/apache2/ssl.key/myhost.key

CAfile = /etc/apache2/ssl.crt/CA.crt

[parsoid]

accept  = 8001

connect = 8000

With this I get the error:

"httpStatus":401,"levelPath":"fatal/request","msg":"Your wiki requires a logged-in account to access the API."

I fail to see what I'm missing. LocalSettings is pointing at the accept port and should forward cookies, the tunnel connects the accept port to the parsoid port and parsoid is configured to the MediaWiki API. And I still get the error. Do I lose the cookies somewhere?

I will try to route the parsoid-wiki communication through localhost as they are on the same server, but I would like to know why the above configuration isn't working.

edit: Using localhost fails with invalid domain error and http 401.

apache config

<VirtualHost localhost:80>

   ServerName localhost

   DocumentRoot /srv/www/htdocs

</VirtualHost>

LocalSettings.php

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

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

        'domain' => 'localhost',

        'forwardCookies' => true

);

$wgSessionsInObjectCache = true;

config.yaml (parsoid)

uri: 'http://localhost/mediawiki/api.php'

domain: 'localhost'

Errors:

"levelPath":"fatal/request","msg":"Invalid domain: myhost"

"httpStatus":401,"levelPath":"fatal/request","msg":"Your wiki requires a logged-in account to access the API." BAtira (talk) 12:04, 28 March 2019 (UTC)

Disallow Visual Editor by Page ID?

Is it possible to hide VE's edit button by page ID? I'd like to disallow editing for example my homepage (page id 1) with the Visual Editor... 217.110.67.35 (talk) 07:06, 3 April 2019 (UTC)

custom link with the save error pop-up

MW 1.30 - VE 0.1.0

Hi. I have an urgent situation that I think there is a simple solution for from a sufficiently savvy person.. my system's session times out after 15 minutes and VE users get an error when trying to save because parsoid can't talk to the server anymore. My organization then requires the browser to revalidate them against some other site on the company network.. which then sends them back to the wiki without a new session and logs them in newly as well loosing all the edits.. I have 2 requests:

1. how to get the wiki to stay in communication with the server while the user is editing a page, and
2. how to modify the VE error message upon save to include a "click 'here' to re-new your session" message with a link to another page on the wiki that would be re-directed to the remote identity provider? Revansx (talk) 19:45, 10 May 2019 (UTC)

Changed System Message "Visualeditor-dialog-error" change does not occur

VisualEditor rewrites media: links to external URL links

MW 1.31.1, VE 0.1.0 (6854ea0)

We use

$wgUploadPath = "$wgScriptPath/img_auth.php";

With this every single edit of a page containing something like

[[media:foo.pdf]]

becomes

[//wiki.example.org/img_auth.php/1/1d/foo.pdf media:foo.pdf]

This is not what I expected, because this explicitly codes the hostname, img_auth.php and the hash dirs into the database. Any idea how to get rid of this? Rrosenfeld (talk) 12:55, 16 May 2019 (UTC)

I have tre same problem. I also would like to get rid of it.

I am a (though enthusiast) totally unprofessional editor of my comnpany wiki, and these things are annoying for non IT people... 62.97.59.238 (talk) 08:00, 24 May 2019 (UTC)

I've got that problem, too. Is there no one at MediaWiki who could take care of that? 83.243.48.54 (talk) 05:47, 10 July 2019 (UTC)

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

Setting up Visual Editor for a private wiki, but keep getting errors as stated in the topic, when I hit edit on pages. How can I fix this problem?

Settings in Localhost.php

# Disable reading by anonymous users

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

# Disable anonymous editing

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

# Prevent new user registrations except by sysops

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

# Linking with Parsoid

$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

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

    // URL to the Parsoid instance

    // Use port 8142 if you use the Debian package

    'url' => 'server's ip address:8000',

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

    'domain' => 'localhost',

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

    'prefix' => 'localhost'

);

# Basic configuration for MediaWiki-VisualEditor

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

// OPTIONAL: Enable VisualEditor's experimental code features

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

Settings in config.yaml

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'

        # Configure Parsoid to point to your MediaWiki instances.

        mwApis:

        - # This is the only required parameter,

          # the URL of you MediaWiki API endpoint.

          uri: 'server's IP address/wiki/api.php'

          # The "domain" is used for communication with Visual Editor

          # and RESTBase.  It defaults to the hostname portion of

          # the `uri` property above, but you can manually set it

          # to an arbitrary string. It must match the "domain" set

          # in $wgVirtualRestConfig.

          domain: 'localhost'  # optional

          # To specify a proxy (or proxy headers) specific to this prefix

          # (which overrides defaultAPIProxyURI). Alternatively, set `proxy`

          # to `null` to override and force no proxying when a default proxy

          # has been set. Weinberg1992 (talk) 17:38, 17 May 2019 (UTC)

I got this running by using the following work around:

if ( !isset( $_SERVER['REMOTE_ADDR'] ) OR $_SERVER['REMOTE_ADDR'] == '127.0.0.1') {
    $wgGroupPermissions['*']['read'] = true;
    $wgGroupPermissions['*']['edit'] = true;
}

And using uri: 'http://localhost/api.php' in config.yaml.

In addition I added an apache site on localhost:80, which only allows access from 127.0.0.1 without SSL, since parsoid doesn't support SSL and I don't like the workaround with stunnel.

This setup seems to work without problems for two weeks in our production setup now. Rrosenfeld (talk) 12:18, 27 May 2019 (UTC)

Hi Rrosenfeld,

thanks for that workaround! But, to be honest, I have no idea how to realize the second part of your suggestion. How did you manage to add localhost:80 with 127.0.0.1 without SSL in apache? Could you share the configuration? That really would be appreciating!

Thanks a lot in advance!

YW Yrwyddfa (talk) 18:45, 3 June 2019 (UTC)

<VirtualHost localhost:80>
        ServerName localhost
        DocumentRoot /srv/www/wiki/htdocs
        ErrorLog ${APACHE_LOG_DIR}/localhost80.error.log
        CustomLog ${APACHE_LOG_DIR}/localhost80.access.log combined
        <Directory />
                Options None
                AllowOverride None
                Require all denied
        </Directory>
        <Directory /srv/www/wiki>
                Options FollowSymLinks
                AllowOverride All
                Require ip 127.0.0.1
        </Directory>
</VirtualHost>

should do the job. Rrosenfeld (talk) 09:23, 5 June 2019 (UTC)

Thanks a lot! Maybe some others will benefit, unfortunately it didn't solve my issue. It seems that a bunch of many, many different problems can lead to the error above. Guess I'll have to dig deeper and hopefully find the problem which causes my troubles. That really is kind of frustrating. Yrwyddfa (talk) 20:47, 7 June 2019 (UTC)

How do I perform search only into the local base when using "Insert > Media"?

ooui-dialog-process-error

MediaWiki 1.31.1 (a4c8065)
VisualEditor 0.1.0 (3db9a0a)12:41, 3 June 2019

Is VE designed to help users resolve expired sessions?

RESOLVED

Issue is a symptom of: https://www.mediawiki.org/wiki/Extension%20talk%3AVisualEditor/2019#h-VE_blocked_by_CORS_policy_of_SSO-2019-07-02T14%3A24%3A00.000Z

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

---

Is VE designed to help users in the situation where the MW application is using an SSO auth with an time-out? This scenario creates two situations:

1. timeout prior to launching VE edit
2. timeout prior to work being saved in VE

In Case 1 - I see this VE error:
In Case 2 - I see this VE error:

So the question is - Is VE designed to help users resolve the scenario where the underlying auth has expired and they need to renew it in order for VE to work. Revansx (talk) 14:45, 11 June 2019 (UTC)

I get a very similar error when trying to use the VisualEditor:

Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 28) Timeout was reached. Would you like to retry? (Sorry, I don't know how to attach images.)

My wiki is https enabled and hosted on a Debian machine on Google Cloud. I have installed all packages that are suggested such as curl, openssl, parsoid, nodejs, etc, and have configured them as directed by the VisualEditor page, and set up all of the firewall rules suggested. Beriksson187 (talk) 21:58, 11 June 2019 (UTC)

For me the problem is clear, after the session times-out, the page is no longer able to communicate with the parsoid service on the server. If only I could add a custom link to the VE system message. Revansx (talk) 22:38, 11 June 2019 (UTC)

What kind of SSO are you using? I have some experience with a network based authentication using the kerberos protocol, if that helps. Osnard (talk) 05:49, 12 June 2019 (UTC)

It's a SAML-based auth. Implemented with Meza [1]

[1] https://www.mediawiki.org/wiki/Meza Revansx (talk) 13:21, 12 June 2019 (UTC)

I don't think there is a way to inject a link into the error message. Maybe you could write a Gadget that detects a session loss (by pulling the web API every few seconds) and displays a modal dialog / overlay that asks the user to re-login. Osnard (talk) 12:41, 13 June 2019 (UTC)

so, my basic question is, "Is VE designed to 'help' users work through a session loss scenario?" .. I'd like to hear a definitive answer on that from one of the VE project folks (Is that you?).

Base MW is fine wrt my SSO session loss. MW source edits renew well, form page edits renew well.. it seems that VE simply doesn't know what do do when the session needs renewed and it's frustrating because the solution is so simple. Ideally VE would just have a button that says, "renew session?" that does a silent and benign call to load.php and if successful, retrys the save.

But before I go down the rabbit hole of trying to implement a work-around, I'd like to know if my basic scenario is one that the VE project team has considered. Revansx (talk) 13:22, 13 June 2019 (UTC)

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

No results for search internal pages with link

When I create a link the search pages tab won't populate with other pages in my wiki. It will only display an exact match of what I type in. 108.4.158.54 (talk) 16:30, 12 June 2019 (UTC)

VE edit button appear and disappear in a new namespace when the page is loaded. MW 1.32.2

Hi !

I've created a new namespace in my wiki and I would like to use VE in it but when i use the configuration to add a new namespace in VE :

$wgVisualEditorAvailableNamespaces = [

    "NewNamespace" => true,

];

It works but the button disappear instantly after the page is loaded :/

I use Lockdown extension on this namespace to lock it to a range of groups. But I tried to set in comment that part and Lockdown too and the problem is still there.

Someone has an idea ? 185.39.141.50 (talk) 23:52, 15 June 2019 (UTC)

VE blocked by CORS policy of SSO

Running VE on MW (1.31) with remote SSO (SAML) authentication seeing the following problem when session expires and needs to be revalidated by the remote SSO:

• VE fails to revalidate with remote SSO
  (standard source edit revalidates no problem)

From the Developers console of the browser I can see that VE is trying to use JS to contact the server via the API and is getting redirected to the SSO (as it should). The SSO, however, is refusing the process the request (causing the VE client JS to fail) with the message:

[client request] blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."

I have no ability to alter the CORS policy of my SSO. The only hope for resolving this issue is to update VE to meet the requirements of the SSO.

Curious if this is this something the VE developers could implement easily? .. or is this something way more complicated than I'm aware of. Revansx (talk) 14:24, 2 July 2019 (UTC)

Further insights here: Extension talk:VisualEditor/2017/03#h-RestBase_Configuration-2017-03-03T14:08:00.000Z

and here: https://javascript.info/fetch-crossorigin Revansx (talk) 20:35, 4 July 2019 (UTC)

ref:

• https://phabricator.wikimedia.org/T227329
• https://phabricator.wikimedia.org/T227325 Revansx (talk) 13:50, 5 July 2019 (UTC)

Options for a template parameter

Hi all, is there an option to set options for template parameters in TemplateData, so users can pick from pre-written options? A user gave me some feedback and said this would be helpful for him. I find the parameter info is often missed as it's hidden behind the "i" icon.

Thanks Garuda3 (talk) 15:44, 2 July 2019 (UTC)

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

Recently, I installed the mediawiki 1.33.0 and parsoid 0.8.0 on my win10 under the environment xampp. But I meed this problem all the time, how to fix this problem? Iszhi (talk) 09:12, 7 July 2019 (UTC)

Problemas para copiar en tablas en el editor visual

Hola, buenas comunidad, hace un tiempo escribí en busca de ayuda sobre mi problema con el editor visual y las tablas, pero no recibí respuesta. Siempre que he usado el editor visual me ha funcionado de maravilla y copiar contenido de una celda a otra no ha sido un problema, pero desde ya un tiempo me pasa lo siguiente:

¿Alguien me puede ayudar a resolverlo por favor?, he probado en otras computadoras e incluso fuera de mi cuenta pero el resultado es el mismo con Google Chrome, cuando lo probé en Microsoft Edge funcionó de maravilla, pero su entorno no me parece tan cómodo, me gustaría seguir editando desde Google Chrome. Barú Sanchezpérez (talk) 17:54, 14 July 2019 (UTC)

Parsoid worker failing on startup

Hi, I am unsure if I am posting this in the correct space but I am having issues with Parsoid starting up. Basically whenever I try to start Parsoid I cannot get any workers to start.

Here is the output from when I start up:

\node_modules\parsoid>node bin\server.js

{"name":"parsoid","hostname":"SonicWiki","pid":6760,"level":30,"levelPath":"info/service-runner","msg":"master(6760) initializing 8 workers","time":"2019-07-19T14:43:38.612Z","v":0}

{"name":"lib/index.js","hostname":"SonicWiki","pid":2388,"level":30,"levelPath":"info","msg":"loading ...","time":"2019-07-19T14:43:39.796Z","v":0}

here

{"name":"parsoid","hostname":"SonicWiki","pid":2388,"level":60,"errno":"EACCES","code":"EACCES","syscall":"bind","address":"127.0.0.1","port":8000,"levelPath":"fatal/service-runner/unhandled","msg":"bind EACCES 127.0.0.1:8000","time":"2019-07-19T14:43:39.814Z","v":0}

{"name":"parsoid","hostname":"SonicWiki","pid":2388,"level":60,"errno":"EACCES","code":"EACCES","syscall":"bind","address":"127.0.0.1","port":8000,"levelPath":"fatal/service-runner/unhandled","msg":"bind EACCES 127.0.0.1:8000","time":"2019-07-19T14:43:39.815Z","v":0}

{"name":"parsoid","hostname":"SonicWiki","pid":6760,"level":40,"message":"first worker died during startup, continue startup","worker_pid":2388,"exit_code":1,"startup_attempt":1,"levelPath":"warn/service-runner/master","msg":"first worker died during startup, continue startup","time":"2019-07-19T14:43:39.933Z","v":0}

{"name":"parsoid","hostname":"SonicWiki","pid":6760,"level":30,"levelPath":"info/service-runner/master","msg":"master shutting down, killing workers","time":"2019-07-19T14:43:45.839Z","v":0}

{"name":"parsoid","hostname":"SonicWiki","pid":6760,"level":30,"levelPath":"info/service-runner/master","msg":"Exiting master","time":"2019-07-19T14:43:45.844Z","v":0}

Here in the information about the environment that I am using:

- Windows 10 environment.

- node version 10.16.0

- parsoid version 0.10.0

If there is any other information that could be helpful please let me know. Thank you very much for whatever help you can give WanderingUser (talk) 14:50, 19 July 2019 (UTC)

Got VE working with workaround '$wgUser' - unclear why

We got the following configuration to work

This is the activation of VE in LocalSettings.php

# ----------------------------------------------------------------------
# VisualEditor                              
# ----------------------------------------------------------------------
wfLoadExtension( 'VisualEditor' );
$wgDefaultUserOptions['visualeditor-enable']	= 1;
$wgDefaultUserOptions['visualeditor-editor']	= 'visualeditor';
$wgHiddenPrefs[]				= 'visualeditor-enable';
$wgVirtualRestConfig['modules']['parsoid']	= array(
							'url' => 'http://localhost:8142',
							'domain' => 'mediawikitest');

// this workaround is needed for the functioning of VE - unclear why

function workaround_for_ve() {
	global $wgUser;
	$wgUser->getID();
	return true;
}

$wgHooks['SpecialPage_initList'][]='workaround_for_ve';

The corresponding entry in /etc/mediawiki/parsoid/config.yaml is

services:
  - module: ../src/lib/index.js
    entrypoint: apiServiceWorker
    conf:
        # Configure Parsoid to point to your MediaWiki instances.
        mwApis:
        - # Editorsettings for mediawikitest
          uri: 'http://localhost/mediawikitest/api.php'
          domain: 'mediawikitest'

Before adding this workaround our wiki had the following behaviour: Upon clicking the 'edit' tab the loading bar of VE shortly flashed up, disappeared and left the browser address '..mediawikitest/index.php/mainpage?veaction=edit'

The strange thing is the workaround we needed, and we would like to know if someone has an explanation, why this workaround works, and whether there is a direct solution for achieving the same result. MW Kappa (talk) 16:32, 22 July 2019 (UTC)

Hello. As I know MediaWiki doesnt't support PHP 7.3 yet, but I can't say whether this is the reason of your issue. I'm using the same MW, Parsoid and VE versions, but PHP on my server is 7.2 - and there is no such issue. Probably it will be usefull here to post also the Rewrite rules of your MediaWiki virtual host (or .htaccess) configuration. Spas.Z.Spasov (talk) 06:49, 23 July 2019 (UTC)

Thank you very much for your quick reply. I have not tested going back to PHP 7.2. MW 1.32.2 and lots of extensions are running well with PHP 7.3. But my question is: are there special requirements for rewrite rules for Parsoid? MW Kappa (talk) 15:46, 24 July 2019 (UTC)

Yes, most of the extensions and MW itself behave well with PHP 7.3, but I found that, some of the CLI scripts doesn't work with PHP 7.3, so probably and the web interface could experience some issues. Also recently, on the support desk, I found a discussion, where was described that MW 1.32 doesn't support officially PHP 7.3.

Actually I've used PHP 7.3 with my wiki for few weeks, before switch back to 7.2, and can't remember such issue as yours, so probably the cause of the issue is elsewhere, but who knows :)

I think there are not special requirements for rewrite rules for Parsoid. I meant that, if you already have some (incomplete) rules they could cause some problems.

This is not related to the issue, but I would like to edit the server's hosts file in order to access the wiki via FDQN instead of localhost or IP address, an example configuration is shown in the bottom of this post of mine. Spas.Z.Spasov (talk) 17:17, 24 July 2019 (UTC)

Hello

I have also a MediaWiki (Bluespice) and running it with PHP 7.3. Im also having this issue that a blank site opens if i want to edit. Im running my MediaWiki with XAMPP on a Shared Host. Thats why i have to run Parsoid with Heroku. Unfortunately your workaround dont work with Heroku :/

Any help please 84.254.96.125 (talk) 12:55, 25 July 2019 (UTC)

Feasibility check on a few possible features

The WikiJournals are looking to form a possibly new WMF sister project. As part of this, there are a number of new features that'd be useful (WikiJournal technical wishlist), some of which are related to VisualEditor.

We don't really have the technical expertise to assess which are trivial and which are difficult/impossible so any feedback from more knowledgeable people is welcomed (either direct-editing the page, or leaving a talkpage comment). Thanks! T.Shafee(Evo﹠Evo)^talk 05:04, 5 August 2019 (UTC)

Troubleshooting HTTP 500 error

Troubleshooting HTTP 404 and http 500

total two 404 error appear :

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

2. something went wrong http 404 when save the modify page

i dont know how to resolve the problem, why not upload image? KermitLiu (talk) 11:25, 23 August 2019 (UTC)

Every template on a page displayed as puzzle icon

On https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/User_guide#Editing_templates it is said that "hidden templates" on a page are displayed as a puzzle icon. Yet every template that I've created is displayed this way and I've not "hide" them or anything. How do I make a template display properly in VisualEditor like that example on a said page with "International health organisations"? 2001:1AB8:2:0:B489:945B:6110:2041 (talk) 12:29, 6 September 2019 (UTC)

For anyone dealing with this : parsoid logs were filled with "non-200 response: 302" "Error: Template Expansion failure". It was because of HTTP to HTTPS redirect settings of the site. A fix was to alter apache config to not redirect on localhost. More on this problem here : https://phabricator.wikimedia.org/T65613 2001:1AB8:2:0:34BF:7FF0:3654:7947 (talk) 11:39, 10 September 2019 (UTC)

Thanks for the tip! It wasn't obvious since I never looked at the parsoid logs. 184.64.117.27 (talk) 21:44, 14 June 2020 (UTC)

[Yes, I read other topic]Error loading data from server: apierror-visualeditor-docserver-http: HTTP 404

But other topics not help me with fixing this error

UPD-1: ⧼abusefilter-warning-linkspam⧽, I change some parts of "links" for not this posting warning

I have this error, parsoid installed on C:/Users/_PROFILE_NAME_/node_modules

MediaWiki on local server - OpenServer

Config.Yaml :

mwApis:

uri: 'http : // *** .net/w/api.php'

domain: 'localhost' ( and I have try domain: '*** .net' )

serverPort: 8000

LocalSettings.PHP :

variant 1:

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

  'url' => 'http: // *** .net',

);

variant 2:

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

   'url' => 'http : // *** .net',

   'domain' => 'localhost',

   'prefix' => 'localhost'

);

F12 console can't help, this not display domains errors for me Demer Nkardaz (talk) 20:20, 15 September 2019 (UTC)

anonymous upload

hi

is it possible to upload images as anonymous user with visualeditor?

thanks 185.24.187.196 (talk) 13:37, 24 September 2019 (UTC)

I am also trying this . Changing LocalSettings only worked in regular upload page. Visual Editor Seems to have a problem and asking for the owner of the file.

Could not store upload in the stash (UploadStashNotLoggedInException): "UploadStash::stashFile No user is logged in, files must belong to users". 8.3.127.189 (talk) 04:14, 17 October 2019 (UTC)

Same. Anonymous file upload can't work with visualeditor apparently... 82.64.12.155 (talk) 20:30, 13 May 2024 (UTC)

Keep h2 / h3 style when pressing Enter

Hi,

When you are using Word or LibreOffice etc., if you are currently focusing the beginning of a line with a "title" style, if you press Enter the line created above will have the same title style by default.

Is it possible to have the same behavior with VisualEditor ?

(I think this is a useful feature when you want to add a new section)

Thanks Varlin (talk) 12:09, 25 September 2019 (UTC)

Replace quotes with guillemets

Hi,

When you are using the french Word or LibreOffice etc., if you press the ' " ' (on Key number 3 !) on your keyboard, this is replaced with the guillement ' «  ' (or ' » ' if at the end of a word). This is useful because guillemets are more commonly used than 'quotes' in french.

I'd like to have this behavior in VisualEditor. Has anyone heard of a way to do that ?

Thanks Varlin (talk) 12:14, 25 September 2019 (UTC)

Seeing non-image thumbs in VisualEditor, but not when viewing page.

Hello all,

I hope this is a correct location to post this, or hopefully someone can point me in the right direction.

I'm adding non-image downloadable files (i.e., zip, pdf, etc.) to my Wiki page with custom 120x120px thumbnail images depending on type. I've added these to the /resources/assets/file-type-icons replacing the same-name distributed versions. However, the file thumbnail does NOT display when viewing the page, but if I click on the Edit tab and enter VisualEditor, I am able to see the thumbs and they are formatted correctly (left justified) on the page.

Has anyone any ideas? Womattctc (talk) 16:46, 10 October 2019 (UTC)

VE hangs if page has .webm file embedded

The VE seems to hang (won't load the page for editing) if it has a .webm file embedded. -- Jtneill - Talk 03:55, 17 October 2019 (UTC)

How to accept self-signed certificate? curl error: 60

Hello,

I'm running private wiki with SSL enabled but I'm getting this error:

apierror-visualeditor-docserver-http-error: (curl error: 60) Peer certificate cannot be authenticated with given CA certificates

I have fallowed this Extension:VisualEditor#Parsoid over HTTPS

How can I resolve my problem?

Tadeshug (talk) 10:24, 22 October 2019 (UTC)

Hello,

Is there anybody that can help me with this topic? Or is there something that I can try to make it work? Tadeshug (talk) 05:08, 29 November 2019 (UTC)

BUMP Tadeshug (talk) 10:57, 11 February 2020 (UTC)

We are having the same problem. Since we only want to host a wiki server in our local intranet, we don't really want to use an actually signed certificate. Because of this, we are using a self signed certificate (which is also applied by a nginx - reverse proxy).

Is there any way to disable the certificate check? Thanks. 213.160.6.194 (talk) 10:28, 26 March 2021 (UTC)

BUMP Avin Shum (talk) 10:35, 28 May 2021 (UTC)

There's one config in php.ini to set the trusted certificate info: https://www.php.net/manual/curl.configuration.php#ini.curl.cainfo

You can download a generic one, for example, https://curl.se/docs/caextract.html and then append to that file your own certificates. That pem file is editable with any text editor.

I guess a configuration could be made in MediaWiki to skip this validation altogether. If nobody has requested that already, you can bugreport it Ciencia Al Poder (talk) 11:09, 28 May 2021 (UTC)

Thank you! This workaround is working. 136.159.160.126 (talk) 17:51, 31 August 2022 (UTC)

Hide a template from the template dialog search list

On my wiki, there are both "user usable templates" (like Abbr, Hidden etc.) and "structural templates" used with PageForms : the latter should only be used by sysop. Therefore it is annoying that they appear in the suggestions of VE template dialog. Is there a way to hide them ? Varlin (talk) 13:44, 8 November 2019 (UTC)

I want know that feature too always. In my cases, users see both a template:foo and a template:foo/doc if exists. Lens0021 (talk) 13:52, 8 November 2019 (UTC)

Yes me too. But see here, apparently it will be fixed in the next release of VE. Varlin (talk) 13:55, 8 November 2019 (UTC)

How does wikipedia hide the template redirection in some cases ?

In the VE template dialog, the suggestions hide the redirection in some cases, and I'd like to know how it works. Because in this case it is useful : The template "Boite déroulante" redirects to "Boîte déroulante", but on wikipedia it does not appear twice, which looks better. On my wiki this is not the case : https://imgshare.io/images/2019/11/08/screen.png Varlin (talk) 14:07, 8 November 2019 (UTC)

VisualEditor failed to load: Error: One or more dependencies failed to load

I am unable to get Visual Editor to load in MW 1.33. It looks as if it is about to load (the loading bar shows up momentarily) then I just get a generic error message in my console `VisualEditor failed to load: Error: One or more dependencies failed to load`.

Parsoid is installed and appears to be running. Here is what I have tried so far to fix the issue based on older threads I have found about this issue:

1. Installed VisualEditor via git and updated submodules
2. Installed VisualEditor for MW 1.33 directly via the extension distribution page
3. Updated to the latest version of Semantic Media Wiki

I am also seeing the following error in my console when VIsualEditor is enabled

```

/mw133/load.php?lang=en&modules=startup&only=scripts&skin=arubaskin   BadMethodCallException from line 826 of /var/www/html/mw133/includes/session/SessionManager.php: Sessions are disabled for this entry point

Backtrace:

#0 /var/www/html/mw133/includes/session/SessionManager.php(196): MediaWiki\Session\SessionManager->getSessionFromInfo(MediaWiki\Session\SessionInfo, WebRequest)

#1 /var/www/html/mw133/includes/WebRequest.php(748): MediaWiki\Session\SessionManager->getSessionForRequest(WebRequest)

#2 /var/www/html/mw133/includes/user/User.php(1380): WebRequest->getSession()

#3 /var/www/html/mw133/includes/user/User.php(441): User->loadFromSession()

#4 /var/www/html/mw133/includes/user/User.php(2433): User->load()

#5 /var/www/html/mw133/extensions/UserPageViewTracker/SpecialUserPageViewTracker.php(16): User->getId()

#6 /var/www/html/mw133/includes/Hooks.php(174): SpecialUserPageViewTracker::updateTable(Parser, string)

#7 /var/www/html/mw133/includes/Hooks.php(202): Hooks::callHook(string, array, array, NULL)

#8 /var/www/html/mw133/includes/parser/Parser.php(1487): Hooks::run(string, array)

#9 /var/www/html/mw133/includes/parser/Parser.php(494): Parser->internalParseHalfParsed(string, boolean, boolean)

#10 /var/www/html/mw133/includes/cache/MessageCache.php(1261): Parser->parse(string, Title, ParserOptions, boolean)

#11 /var/www/html/mw133/includes/Message.php(1262): MessageCache->parse(string, Title, boolean, boolean, LanguageEn)

#12 /var/www/html/mw133/includes/Message.php(890): Message->parseText(string)

#13 /var/www/html/mw133/includes/Message.php(943): Message->toString(string)

#14 /var/www/html/mw133/includes/EditPage.php(3639): Message->parse()

#15 /var/www/html/mw133/extensions/VisualEditor/includes/VisualEditorDataModule.php(70): EditPage::getCopyrightWarning(Title, string, string)

#16 /var/www/html/mw133/extensions/VisualEditor/includes/VisualEditorDataModule.php(25): VisualEditorDataModule->getMessageInfo(ResourceLoaderContext)

#17 /var/www/html/mw133/includes/resourceloader/ResourceLoaderModule.php(727): VisualEditorDataModule->getScript(ResourceLoaderContext)

#18 /var/www/html/mw133/includes/resourceloader/ResourceLoaderModule.php(694): ResourceLoaderModule->buildContent(ResourceLoaderContext)

#19 /var/www/html/mw133/includes/resourceloader/ResourceLoaderModule.php(830): ResourceLoaderModule->getModuleContent(ResourceLoaderContext)

#20 /var/www/html/mw133/includes/resourceloader/ResourceLoaderStartUpModule.php(255): ResourceLoaderModule->getVersionHash(ResourceLoaderContext)

#21 /var/www/html/mw133/includes/resourceloader/ResourceLoaderStartUpModule.php(438): ResourceLoaderStartUpModule->getModuleRegistrations(ResourceLoaderContext)

#22 /var/www/html/mw133/includes/resourceloader/ResourceLoaderModule.php(727): ResourceLoaderStartUpModule->getScript(ResourceLoaderContext)

#23 /var/www/html/mw133/includes/resourceloader/ResourceLoaderModule.php(694): ResourceLoaderModule->buildContent(ResourceLoaderContext)

#24 /var/www/html/mw133/includes/resourceloader/ResourceLoaderModule.php(830): ResourceLoaderModule->getModuleContent(ResourceLoaderContext)

#25 /var/www/html/mw133/includes/resourceloader/ResourceLoader.php(656): ResourceLoaderModule->getVersionHash(ResourceLoaderContext)

#26 [internal function]: ResourceLoader->{closure}(string)

#27 /var/www/html/mw133/includes/resourceloader/ResourceLoader.php(668): array_map(Closure, array)

#28 /var/www/html/mw133/includes/resourceloader/ResourceLoader.php(749): ResourceLoader->getCombinedVersion(ResourceLoaderContext, array)

#29 /var/www/html/mw133/load.php(46): ResourceLoader->respond(ResourceLoaderContext)

#30 {main}

``` Dstoeltz (talk) 18:57, 12 November 2019 (UTC)

RESOLVED: Turns out one of my other extensions, UserPageViewTracker, was causing this issue. I figured this out by going through and disabling all other extensions one by one. As soon as I turned off UserPageViewTracker this error went away and I was on to the next error! Dstoeltz (talk) 19:04, 21 November 2019 (UTC)

Is it mandatory restbase, mathoid and parsoid?

In my case i do not want to use these services just want to use Editor?

Kindly confirm. Rajeshrajesh.35 (talk) 04:47, 20 November 2019 (UTC)

Only Parsoid is required, others are optional. Lens0021 (talk) 05:31, 20 November 2019 (UTC)

Sorry, i was forgot to add wiki version. I am using

WIKI 1.31.

VisualEditor 0.1.0

In this version restbase is mandatory if i remove the restbase settings then i gets error 404 while loading editor for edit.

Rajeshrajesh.35 (talk) 06:39, 20 November 2019 (UTC)

RESTBase is not mandatory since I started to use Visual Editor(Up to MW1.27). Could I know if you finished to set up Parsoid or not? If not, Parsoid/Troubleshooting is helpful. Lens0021 (talk) 06:52, 20 November 2019 (UTC)

Yes!, It is working Rajeshrajesh.35 (talk) 07:04, 20 November 2019 (UTC)

Visual Editor every time loads restbase url and restbase return 404.

I check all service is running Rajeshrajesh.35 (talk) 07:06, 20 November 2019 (UTC)

After removing RESTBase settings, you have to clear your browser's cache since Visual Editor's Javascript that includes reference of restbase url is cached in your browser. Lens0021 (talk) 07:12, 20 November 2019 (UTC)

TextColor on VisualEditor

Hi,

I'l need to be able to specify text color in my pages.

Is it planned to integrate this feature soon?

Thank you in advance for your answers!

Patrice 85.31.195.162 (talk) 15:52, 28 November 2019 (UTC)

Not soon, sorry. HTML works, but there's no built-in tool for adding text color. Whatamidoing (WMF) (talk) 20:58, 9 December 2019 (UTC)

Hi,

Thank you.

it's a shame, it's a feature that could be really nice ... 85.31.195.162 (talk) 14:16, 10 December 2019 (UTC)

If you create an account, you can subscribe to phab:T54645 and get an e-mail notification whenever it gets done. Whatamidoing (WMF) (talk) 20:03, 12 December 2019 (UTC)

Cookie Visual Editor

Does not work on Chameleon skin

I am getting this error on MediaWiki 1.32 running Chameleon skin. The Visual Editor starts to load but then fails. I can not figure out what is the issue and where to fix it. I would appreciate any suggestions

VM6687:445 VisualEditor failed to load: Error: inheritClass: Origin is not a function (actually undefined)

Looking at the console code in Chrome

.then(function() {
                    var target, modes = [];
                    if (!active) {
                        targetPromise = null;
                        return $.Deferred().reject().promise();
                    }
                    if (init.isVisualAvailable) {
                        modes.push('visual');
                    }
                    if (init.isWikitextAvailable) {
                        modes.push('source');
                    }
                    target = ve.init.mw.targetFactory.create(conf.contentModels[mw.config.get('wgPageContentModel')], {
                        modes: modes,
                        defaultMode: mode
                    });
                    target.setContainer($('#content'));
                    targetLoaded = !0;
                    return target;
                }, function(e) {
                    mw.log.warn('VisualEditor failed to load: ' + e);
                });

205.200.97.2 (talk) 15:54, 6 December 2019 (UTC)

In addition following messages are displayed

load.php?debug=false&lang=en&modules=ext.bootstrap.scripts|jquery%2Coojs-ui-core%2Coojs-ui-widgets|oojs-ui.styles.icons-editing-advanced&skin=chameleon&version=1nb3fru:166 jQuery.Deferred exception: Cannot set property 'section' of undefined TypeError: Cannot set property 'section' of undefined
load.php?debug=false&lang=en&modules=ext.bootstrap.scripts|jquery%2Coojs-ui-core%2Coojs-ui-widgets|oojs-ui.styles.icons-editing-advanced&skin=chameleon&version=1nb3fru:166 jQuery.Deferred exception: Cannot read property 'on' of undefined TypeError: Cannot read property 'on' of undefined
    at <anonymous>:447:249
load.php?debug=false&lang=en&modules=ext.bootstrap.scripts|jquery%2Coojs-ui-core%2Coojs-ui-widgets|oojs-ui.styles.icons-editing-advanced&skin=chameleon&version=1nb3fru:166 jQuery.Deferred exception: Cannot read property 'on' of undefined TypeError: Cannot read property 'on' of undefined
    at <anonymous>:447:249

> 205.200.97.2 (talk) 15:57, 6 December 2019 (UTC)

Finally made VisualEditor to run. There should be exact match between the mediawiki and VisualEditor release. Mine turned to be 1.33 but I was trying to install visualeditor for version 1.32. VidualEditor was not loading at all. No popup error messages were displayed. The parsoid service is running on the Heroku free hosting and it works wonderfully. Takes a bit of time to open page for the first time. I also needed to hide edit buttons as they get broken. Add this variables to Localsettings.php

$wgVisualEditorTabMessages['editsource'] = null;

$wgVisualEditorTabMessages['createsource 2605:8D80:6A0:B9C:F14D:6ACA:754A:68CB (talk) 17:04, 7 December 2019 (UTC)

In-VE User Guide link - error Bad title

Release notes VisualEditor extension

Hello all,

Where can I find the release notes of the VisualEditor extension? We are migrating from MediaWiki 1.27 to MediaWiki 1.31 and want to inventory the differences (in code) between the versions. We made an extension to the extension. Some things have changed we've noticed.

Regards, Jethro Waanders (talk) 11:08, 18 December 2019 (UTC)

AFAIK, there are no release notes. Maybe you can do a git diff between VisualEditor REL1_27 and REL1_31 branches? Tinss (talk) 06:37, 24 January 2020 (UTC)

Parsoid PHP and VisualEditor