Open main menu

Extension talk:VisualEditor

About this board

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.

Gwsampo (talkcontribs)

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

Is this a known response?

216.248.100.66 (talkcontribs)

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.

Dbummy (talkcontribs)

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?

Gwsampo (talkcontribs)

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
Mshannaq (talkcontribs)

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?

Gwsampo (talkcontribs)

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> for notice of API deprecations and breaking changes."

    }

}

Mshannaq (talkcontribs)

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> 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&amp;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?

Gwsampo (talkcontribs)

So frustrating but try in LocalSettings.php

Enabled skins (commenting out the other ones)

wfLoadSkin( 'MonoBook' );

wfLoadSkin( 'Vector' );

Gwsampo (talkcontribs)

Sorry that didn't work

Gwsampo (talkcontribs)

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
96.23.48.169 (talkcontribs)

I'm having the same problem ..

93.39.230.4 (talkcontribs)

Hi same problem here. Media Wiki 1.30, Visual Editor 1.30

Dbummy (talkcontribs)

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 (talkcontribs)

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

82.204.2.90 (talkcontribs)

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!

185.154.146.37 (talkcontribs)

This worked for me!

216.248.100.66 (talkcontribs)

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.

93.39.230.4 (talkcontribs)

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

Dbummy (talkcontribs)

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.

217.148.121.13 (talkcontribs)

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

I think I am stucked until they update the Visual Editor....

77.118.171.223 (talkcontribs)

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

217.18.193.124 (talkcontribs)

This "fixed" the issu for my setup.

60.11.42.35 (talkcontribs)

Thanks,It's work.Looks good.

62.2.90.162 (talkcontribs)

Googled for hours until i found this solution...works for me, a fresh installation of mediawiki & parsoid

12.118.115.198 (talkcontribs)

Thanks so much. Worked for me as well.

186.46.139.226 (talkcontribs)

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!

Compumatter (talkcontribs)

Yep that did it ! Solved.

  • sudo vim /usr/lib/parsoid/src/lib/config/ParsoidConfig.js
  • ParsoidConfig.prototype.strictSSL = false;
  • sudo service parsoid restart
  • Done
Oleolsenkjhølkølk (talkcontribs)

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?

185.125.207.249 (talkcontribs)

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.

Seb35 (talkcontribs)

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 .

213.33.64.46 (talkcontribs)

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!

117.136.45.110 (talkcontribs)

Thank you too much, my friends!

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

Thanks! All my friends!

真的非常感谢,前辈们!

Rajeshrajesh.35 (talkcontribs)

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


This post was hidden by Rajeshrajesh.35 (history)
Reply to "httpResponse 406 from Parsoid"

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

1
185.39.141.50 (talkcontribs)

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 ?

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

Is VE designed to help users resolve expired sessions?

7
Revansx (talkcontribs)

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:
ooui-dialog-process-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.

Beriksson187 (talkcontribs)

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.

Revansx (talkcontribs)

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.

Osnard (talkcontribs)

What kind of SSO are you using? I have some experience with a network based authentication using the kerberos protocol, if that helps.

Revansx (talkcontribs)
Osnard (talkcontribs)

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.

Revansx (talkcontribs)

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.

Reply to "Is VE designed to help users resolve expired sessions?"
Revansx (talkcontribs)
ooui-dialog-process-error

Hi. I have a SAML-based SSO that times out every 15 mins.

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

The following is a summary of the way edits are saved with respect to the SAML expiration.

  1. FORM EDIT - No Problem - User attempts to save edits to a page using Form Edit after SAML has timed-out --> SAML just renews and the pending edits are saved. Nothing lost.
  2. SOURCE EDIT - No Problem - User attempts to save edits to a page using Source Edit after SAML has timed-out --> SAML just renews and the pending edits are saved. Nothing lost.
  3. VE - PROBLEM - User attempts to save edits to a page using VE after SAML has timed-out --> VE crashes with error as shown in thumbnail. USER HAS NO CLEAR OPTIONS

To the savvy user the solution is simple - just renew the session using a new tab and come back to the edit screen, click "Resume editing", and then SAVE again (with the session renewed), but the non-savvy user (rightly) does not know what to do.

How to fix this scenario so the normal user has a clear intuitive option to renew session and save their edits?

Can I alter the Mediawiki message "ooui-dialog-process-error" to maybe provide a link to a page on my server that will renew the session?

ESanders (WMF) (talkcontribs)

ooui-dialog-process-error is a very generic message for failures within a dialog. It also probably isn't parsed so you couldn't put a link in there. You might be able to modify ApiVisualEditor to send back a more descriptive error message, which is displayed in the red box.

Revansx (talkcontribs)

yes. if I could tailor the message to have a custom hyperlink, that would give the user an option. I've tried updating the system message "Mediawiki:ooui-dialog-process-error" to no avail. Is that not the right system message for this situation?

Revansx (talkcontribs)

also getting this error when SAML SSO Auth is expired:

Revansx (talkcontribs)

I think the basic question is this - Is VE designed to help users resolve the scenario where the underlying auth has expired and they need to renew it in order to save their work. Yes. That's the questions. Is VE designed to address that scenario?

ESanders (WMF) (talkcontribs)

We retry if the edit token has expired, but I don't know anything about SAML SSO.

Revansx (talkcontribs)

how do you do the retry?

Reply to "ooui-dialog-process-error"

No results for search internal pages with link

1
108.4.158.54 (talkcontribs)

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.

Reply to "No results for search internal pages with link"

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

3
Summary by Revansx

it does now. I think it just needed its cache flushed

Revansx (talkcontribs)

MW 1.30, VE 0.1.0 (61f161a) 14:07, 2 October 2017

Hi, I've been having an issue with parsoid that causes the following error in mediawiki when I go to save:

Until I get it solved, I wanted to provide a custom message to my users and found the following System Message related to this error of Visual Editor as follows:

However, this modified message does not render when the error occurs. Instead, I just get the original text in the message:

I've tried clearing the page cache before the error is produced with no luck.

Why doesn't this custom system message work?

ESanders (WMF) (talkcontribs)

Use ?uselang=qqx to see which message is being used

Revansx (talkcontribs)

Neat. But how do I make that switch a mw default? Once the error generates, I only have the existing page code that was served from the server to work from. Any new request from the server will renew the session and the message does not appear.

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

5
Weinberg1992 (talkcontribs)

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.

Rrosenfeld (talkcontribs)

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.

Yrwyddfa (talkcontribs)

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

Rrosenfeld (talkcontribs)
<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.

Yrwyddfa (talkcontribs)

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.

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

นาย พิเชษฐ์แสนทวีสุข

2
Wang.carl (talkcontribs)

Dear All:

I already setup VisualEditor successfully,and it work when in anonymous users mode。But when I

add grouppermissions, it hide by itself。even I add this command:

$ wgDefaultUserOptions ['visualeditor-editor'] =“visualeditor”;

Here is my set:

$wgGroupPermissions = array();

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

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

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

$wgWhitelistRead = array ("Main Page","Special:Userlogin","Wikipedia:Help");

$wgGroupPermissions['user']['autocreateaccount']=false;

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

$wgGroupPermissions['user']['userrights']=false;

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

$wgRemoveGroups['bot'] = true;

$wgRemoveGroups['autoconfirmed'] = true;

$wgGroupPermissions['sysop']['userrights']=false;

$wgGroupPermissions['sysop']['upload']= true;

$wgGroupPermissions['sysop']['reupload']= true;

$wgGroupPermissions['sysop']['reupload-shared']= true;

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

$wgGroupPermissions['sysop']['import']=true;

$wgGroupPermissions['sysop']['editprotected']=true;

$wgGroupPermissions['sysop']['createpage'] = true;

$wgGroupPermissions['sysop']['move'] = true;

$wgGroupPermissions['sysop']['delete'] = true;

$wgGroupPermissions['bureaucrat']['userrights']=true;

Here is my VisualEditor set:

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

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

$wgHiddenPrefs[] = 'visualeditor-enable';

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

#// URL to the Parsoid instance

#// Use port 8142 if you use the Debian package

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

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

'domain' => '10.159.246.222',

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

'prefix' => '10.159.246.222'

);

so do i set up wrong command, or If you have solutoin, please help me.

Thanks very much.

Seb35 (talkcontribs)
Reply to "นาย พิเชษฐ์แสนทวีสุข"

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

1
Spas.Z.Spasov (talkcontribs)

Hello, I'm using VisualEditor on MwdiaWiki 1.32.1 and it everything works fine! :)

I just wonder is there any way to force VisualEditor to perform only local search when I'm using the "Insert > Media" feature? It could be perfect If I could restrict this search to the local base via LocalSettings.php.

Reply to "How do I perform search only into the local base when using "Insert > Media"?"
Tansaku (talkcontribs)

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

Ryanjjjj (talkcontribs)

Bump, pretty frustrating...

Bovender (talkcontribs)

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).

Bozomal (talkcontribs)
Reply to "Mediawiki 1.32"
Return to "VisualEditor" page.