VisualEditor/Feedback

Post your feedback about using the visual editor.

If you have never provided feedback before, you can learn how to do it effectively. If you are reporting a problem directly on this page, please include your web browser, computer operating system, and wiki skin (usually Vector, sometimes Monobook). The feedback tool within the visual editor will include your user agent details instead.

You can use this page to tell the Wikimedia developers your ideas and issues about using the visual editor: this is the only feedback page actively monitored by WMF staff. The Contributors team welcomes your feedback and ideas, especially on user interface decisions and the priorities for adding new features. All comments are read, in any language, but personal replies are not guaranteed: the team will try and go through reports here at least once a week. Need more attention? Report directly in Phabricator. Please note that the Wikimedia Foundation does not provide support for installing VisualEditor on third-party wikis. Please report bugs involving Parsoid at Talk:Parsoid instead.

You may also want to read a guide to optimize the visual editor's experience on your site, which details work necessary on the community side (such as translating or setting up citation systems).

View open developer tasks – Report a new bug in Phabricator – Join the IRC channel – Test the visual editor! (no account required)

Previous page history was archived for backup purposes at VisualEditor/Feedback/LQT Archive 1 on 2015-07-30.

I just updated to MediaWiki 1.35.0 yesterday.

Whenever I try to edit a page using the visual editor a progress bar starts to load and near the middle of the process the progress bar stops to fill itself and I get the message:

"Error contacting the Parsoid/RESTBase server (HTTP 404)"

I'm on shared hosting and I'm not running a RESTBase server, but from what I get it's not mandatory (https://www.mediawiki.org/wiki/Extension:VisualEditor#Switching_between_Wikitext_Editing_and_VisualEditor). I have set $wgVisualEditorAllowLossySwitching=false, by the way.

The wiki also has $wgGroupPermissions['*']['edit'] = false.

Any ideas?

If you set $wgGroupPermissions['*']['read'] = true, it might work.

I am in the same situation except that I want a to have $wgGroupPermissions['*']['read'] = false

The documentation of VisualEditor sadly is still lacking. I am having the same problem, but there are no hints on how to fix this.

There is a relative bug report in Phabricator: https://phabricator.wikimedia.org/T263928

You can subscribe if you wish.

There is also https://phabricator.wikimedia.org/T261921, which might also be related. I’m using mediawiki via the bitnami docker image and have opened https://github.com/bitnami/bitnami-docker-mediawiki/issues/84 hoping to get a fix upstream.

I always get a 404 error. Not only in pages with special characters. The relative bug report on Phabricator is available here: https://phabricator.wikimedia.org/T263928

I am having the same issue.

Check and if you wish contribute to: https://phabricator.wikimedia.org/T263928

Having the same problem. It seems that the option to make it a private wiki (need to login, University Intranet) causes it to get the error and fail:

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

The fix at the moment is to check via IP address, but that isn't going to work for me. Is there anything which I can add to LocalSettings.php which checks for Logged In user?

When mediawiki 1.35 (from debian buster-backports) is behind reverse proxy, visualeditor does not work correctly because it does not use $wgInternalServer but uses $wgServer to make internal rest requests which is wrong (internal traffic should not travel to external). Please fix visualeditor logic to use $wgInternalServer for internal api calls.

I am having the same isue. With a peculiarity. As I upgraded my wiki to 1.35, the old pages can be edited with VisualEditor, no problem, the new ones give me this 404 error (parsoid etc.).

Report it here: https://phabricator.wikimedia.org/T263928

Any news on this?

I still can't save using VisualEditor, always getting that "Error contacting the Parsoid/RESTBase server (HTTP 404)".

My wiki is private and I need to keep it this way. Any workaround?

Having the same issue, using Mediawiki 1.35.1 on redhat. anyone got any solutions.

same.

Same, I've been searching for 20 hours now without a solid fix for this T_T

I had this same problem. I fixed it by redirecting the default apache virtual site to my wiki directory.

Same problem. I'm using private MediaWiki 1.35.1 with Nginx on Ubuntu server.

Same, Ubuntu and Nginx.

I get this error strictly when editing a page whose name contains a slash or other problematic character.

Me too, I use slashes because of the mediawiki's subpages feature. Pages which have a slash give the error. All other pages work fine.

What worked for me was the change in the Apache settings, as suggested by:

Extension:VisualEditor#Allowing VisualEditor on page titles containing slashes

(for a private wiki, with subpages).

I had hopes it would work, but no.

Clarify I have:

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

$wgNamespacesWithSubpages was not set at all, but I added it "$wgNamespacesWithSubpages[NS_MAIN] = true;" but no difference.

Added:

<VirtualHost ....>

AllowEncodedSlashes NoDecode

Could it be related that wgNamespacesWithSubpages was not set?

Will have another play to double check. Has anyone else got it working?

Cheers

Well, I moved the wiki to another system and it does work so it looks like "AllowEncodedSlashes NoDecode" may solve the problem. Guess my real site has some other coding which is messing it up. I don't think it is in apache.conf files so will have a closer look at any .htaccess files which may be read...

Not seeing anything which could be change the "AllowEncodedSlashes" option. Our web server is behind a load balancer is there any chance that may be it? Is there away of test if AllowEncodedSlashes is working?

Got it working...

I decided to start fro scratch building a new website and after a waste of a day. I spotted the problem. Yes you need "AllowEncodedSlashes NoDecode" but you also need the php "extension=curl.so"

Since I like to keep our external web server as secure I possible I disables curl a long time ago, which is fine except VisualEditor seems to require it..

Thanks for all your help...

[Solved in my case] For those who have still problems with the Parsoid:

I have recognized that the Visual Editor may have problems with short urls. If I set the variable "$wgArticlePath" properly, the Visual Editor didn't work. For this reason I have developed a concept to activate short urls for standard users (read-only) and to use full urls for users which may work with the Visual Editor.

Hope it helps somebody!

Hi, @Asphorm:. That's exactly why I'm here now - short URL's and VE. Could you pls be as kind as to explain your solution more accurately? Thanx in advance! Pawel Niemczuk (talk) 02:40, 5 April 2021 (UTC)

Agent utilisateur : Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:87.0) Gecko/20100101 Firefox/87.0

URL : https://fr.wikipedia.org/wiki/Margalit_Berriet?venotify=created&veaction=edit

Agent utilisateur : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0

URL : https://fr.wikipedia.org/wiki/Utilisateur:Journal1935/Brouillon?veaction=edit Bonjour Cet article est structuré. Même après plusieurs essais de corrections, je ne suis pas arrivée à un résultat convenable, par mauvaise manipulation de la syntaxe. En l’état actuel : L’article n’a pas de titre, contrairement à toutes les pages Wikipedia. Or, le titre est "Association des Étudiants Musulmans Nord-Africains" Il doit être structuré ainsi : Titre de l’article : "Association des Étudiants Musulmans Nord-Africains" 1. Historique (niveau 2) avec ses trois paragraphes (niveau 3). 2. références (niveau 2) Merci

Agent utilisateur : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

URL : https://fr.wikipedia.org/wiki/Algorithme_hongrois?veaction=edit&section=2

Bonjour, peu habitué à la section Discussions, j'écris ici : Dans l'explication de l'algorithme, les tableaux utilisés ne représentent pas nécessairement l'état de l'algorithme au moment indiqué, dans la mesure où on fait un bond entre les étapes, la compréhension en devient vraiment difficile (notamment l'explication de la partie 2'). A titre de comparaison, l'article anglais indique méthodiquement la faon de faire des coloriages. Je pense que l'idéal serait d'avoir un gif montrant l'évolution de la matrice au cours du temps

@Lofhi or @Trizek, could you find a maths editor for this content question?

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15

el.wikipedia.ord

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36

URL: https://fi.wikipedia.org/wiki/Jorma_Juhani_Miettinen?veaction=edit

I created a tag extension "led", which displays software controlled LEDs (small png graphics) in Wiki pages. When I use it like (simplified examle) <led color="red"></led> I can edit the page with VE, using <led color="red" /> editing with VE is impossible, VE hangs loading the page. Both versions are functioning and the led is displayed. The same happens to another tag extension.

This problem occurs in VE version 0.1.0, seems to be fixed in 0.1.2

Hi! In most WYSIWYG editors, like say Microsoft Word or Google Docs, whenever I want to add a paragraph, I simply place the cursor before or after and press enter a few times. I'd dare say that 100% of users are familiar with this functionality. So why is VisualEditor different and has an "Add paragraph" button appear between elements? This feature seems inconsistent with the way the rest of the VE works, and more importantly it seems to me like the main cause of differences between the rendered page and the VE surface.

It appears between floated block elements, a concept that doesn't exist in either Microsoft Word or Google Docs (because they're aping paper) but is fundamental to how HTML documents work.

If you are in a paragraph, you can just put the cursor somewhere and press return a few times, as you say.

I can't make changes on text inside the code template on VisualEditor because when I click where I want to write VisualEditor shifts the cursor as the first column, therefore the lines of code aren't visible anymore.

Does this happen in every article, or only some? Can you give me a link?

I have this problem only when there are long lines (longer than the width of the code block template widget), but I can't obviously (I cannot try every piece of code) be sure of that.

The Bit_Field page contains two code blocks.

I had this problem when I translated the page to Italian; the code with standard/textual mode.

After have copied the code try to open within the editor in visual editor mode and modify the code.

If I move the cursor from the line start in a another point of the code the first visualized column will be the cursor one, instead of the first. The heart of the problem is that, after moving the cursor, it is not possible to view or modify the first visualized columns.

https://it.wikipedia.org/w/index.php?title=Speciale:TraduzioneContenuti&page=Bit+field&from=en&to=it&targettitle=Campo+di+bit

If the problem is in ContentTranslation, then we probably need to find @Amire80.

@ZandDev, do you still have this issue now when you try to edit the article? Or did it happen only while you were translating it?

I had this problem only when I was translating it, but I've verified that it is still present.

Agen pengguna: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.3 Safari/605.1.15

URL: https://id.wikipedia.org/wiki/Actor_veelim?veaction=edit