Jump to: navigation, search
Share your feedback
Report bugs

Your feedback about VisualEditor

Start a new discussion about VisualEditor.
If you are reporting a problem, please include your web browser, computer operating system, and wiki skin (usually Vector, sometimes Monobook).

Use this page to tell the Wikimedia developers your ideas and issues about using VisualEditor. The Editing team welcomes your feedback and ideas, especially on user interface decisions and the priorities for adding new features. All comments are read, but personal replies are not guaranteed. This page uses LiquidThreads, so you need to click "Start a new discussion" (not the ordinary "Edit" link) to post your message.

Start a new discussion
First page
First page
Previous page
Previous page
Last page
Last page

After 1.25 maintenance/update.php, attempts to Edit certain pages open other pages

Today, I ran maintenance/update.php on an installation. Now, when certain pages are invoked with "Edit," an entirely different page is invoked -- it is almost as if an index in the database were skewed. It is now possible to save the page and stomp over whatever was there before. Has this been observed before? I'm not even sure how to debug this -- suggestions will be appreciated!

Here is some version identification.

MediaWiki: 5a3173d06b605a8c86ace08efc9e9c290f7f171a VisualEditor: b6ad119f153cdd0f88e3152c5961785c3d46e72a

Pickle-san (talk)03:31, 25 March 2015

Only 1 cite option?

Why am I seeing only 1 cite option (Basic) while in the user manual , it shows many more options?

On Internet Explorer 11 , Windows 8.1 .

Leaderboard (talk)20:08, 23 March 2015

Which wiki? What you see depends upon the local configuration.

Whatamidoing (WMF) (talk)23:04, 23 March 2015

Well , I found this on the English Wikibooks and even the sandbox on MediaWiki.

Leaderboard (talk)11:40, 24 March 2015

Unexpected result when editting a template

Perhaps this has been mentioned before; there are so many threads, but I like to report my unexpected result.

In the article NL w:nl:Amsterdam, there are eight templates present starting with {{zie . When I editted one of them, lower in the text, the first one, on the top of the pages, was changed by the Editor. After the first time, a did an additional test to check myself and the result. Please look at the result in this edit:

I am using browser Chrome version 41.0.2272.101 m on a Dell PC with Windows 7 professional.

BTW, even as an experienced editor, I like the visual editor! Very good work!

Ellywa (talk)08:35, 24 March 2015

P.S. my wiki skin is Vector

Ellywa (talk)08:37, 24 March 2015

Thanks a lot for your report and for your encouraging words. I'm reporting this on Phabricator now. It is now T93739.

Elitre (WMF) (talk)11:52, 24 March 2015

changing / correcting links

Hi I found it is sometimes impossible to correct links in the VE. I wanted to correct after seeing that it was misspelled , at other times to exchange the link completely. Does not work in VE, the first inserted link remains and is just a renamed on the surface (thus getting [[tpping eroor|typing error]] which does not help). Had to save, go into the source editing and do it there. Kipala (talk) 07:18, 14 March 2015 (UTC)

Kipala (talk)07:18, 14 March 2015

What's impossible about clicking on the link and clicking edit?, 14 March 2015

In the wikitext editor, if the link is [[tpping eroor]], and you change what you see to [[typing error]], then you're done. But in VisualEditor, you have to change both the visible label and the underlying link, which requires two separate actions: change what you see, and then open the link tool and change the underlying link. It is not exactly intuitive, and there are multiple suggestions about how to improve it.

Whatamidoing (WMF) (talk)17:14, 20 March 2015

And? That doesn't make editing a link impossible, as OP complained about. I don't know what OP is expecting. VisualEditor allows you to edit the visuals. Is it not expected that changing the text won't change the link? And to change the link you press edit? It seems obvious, and a perfectly acceptable compromise for not having to deal with wikitext. This is how it works in any rich text editor, and is the only sensible way it can be done., 21 March 2015

Dear, surely you are right, but I am not so sure if we have the alle the people here who are right all the time. No, it is not at all obvious that "that changing the text won't change the link? And to change the link you press edit". Not a bit.

Kipala (talk)20:43, 21 March 2015

I agree with you, Kipala. We need to improve this and make it easy for everyone.

Whatamidoing (WMF) (talk)23:18, 23 March 2015

missing jamii/ category input plus WHO CAN CHNGE THE MENUE WORDING

I have a workshop next week in Tanzania and try to prepare a simple guide for first-time editors on sw-wikipedia. I want to propose to them to start in VE and switch later to source editing after getting experience. So I have tried to familiarize myself with VE.

1) The main bug for starting new articles in VE as I found about so far: I see no option to enter a category - which features prominent in my guide how to start a new entry. Is it really necessary to save and the go back to source???

2) I have no idea who tried to translate the VisualEditor.toolbar into Swahili. (someone via google-bullshit-translate??). Urgently needs corrections. Who to talk to?? Kindly answer to my sw talk page, I am not often here Kipala (talk) 07:37, 14 March 2015 (UTC)

Kipala (talk)07:37, 14 March 2015

You can use the Link tool to add a category.

FriedhelmW (talk)11:45, 14 March 2015

Translations can be contributed on for this specific case:

TheDJ (Not WMF) (talkcontribs)00:02, 16 March 2015

Thx, but this only works partly. Some words of the menue do not appear in these list Kipala (talk) 20:39, 21 March 2015 (UTC)

Kipala (talk)20:39, 21 March 2015

Kipala, what's missing? If you click on this:

you'll see the list of "code names" in VisualEditor. For example, in the "Page options" (three lines, next to the Save button) menu, you'll see an item with the label (visualeditor-categories-tool). That corresponds to a page MediaWiki:visualeditor-categories-tool, where the name can be changed locally (by any admin). Permanent, worldwide translations (not just for the Swahili Wikipedia, but for everyone using VisualEditor in Swahili, anywhere) should be made through If you're willing to do the translations, I can get you an account there. If it's just a couple of changes, then you can send the list to me, and I can enter them.

Some things have to be turned on locally. For example, the Cite menu will be nearly empty without local changes.

Whatamidoing (WMF) (talk)23:15, 23 March 2015

Halleluia! Great revamp!

We were relectant to push the Visual Editor on the Welsh language wiki (cy), until now - it's absolutely brilliant! I do believe that it will help close the gender gap and bring in new editors. Well done all round!

Llywelyn2000 (talk)17:52, 15 March 2015

Thanks for the feedback.

Whatamidoing (WMF) (talk)16:58, 20 March 2015

Hi WMF staff, I tried it out on 2 Afrikaans pages, it gets my thumbs-up! af:Gebruiker:Aliwal2012

Aliwal2012 (talk)19:02, 21 March 2015


I see that you switched mid-edit back to the wikitext editor recently. That kind of edit seems difficult to everyone at the moment. It can be done – just open the link tool and change the contents of the box – but it's not intuitive. They're going to work on that soon. I hope you'll like it even better then.

Whatamidoing (WMF) (talk)23:07, 23 March 2015

Announcing open weekly triage meetings starting next week

The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. You can help identify these requirements. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins. Hope to see you there,

Elitre (WMF) (talk)16:02, 5 February 2015

Could you give some more information about the triage meetings, so that we can share the news (and I think it's more than only news, it's a shift in involving people into the development road) in our projects. Is it IRC, hangout? Is there an agenda?

Lyzzy (talk)21:09, 7 February 2015

Hi Lyzzy! So from what I know, what happens this week is that Damon and James will elaborate a bit about the criteria for triaging bugs which are now listed among the Measures of success - Prioritised functional and technical objectives here (that is, bearing in mind this quarter's goal of making sure VE is a good experience "for anonymous users and logged in users who have never edited"). Then they'll start evaluating VE tasks on Phabricator live, according to the criteria just discussed. This live evaluation is what the meetings will be about. (That's why we're looking for volunteer devs who might want to provide their angle and, hopefully and most importantly, try their hands at fixing some bugs.) I still have no information about how this will happen, partly because it depends on the kind of support we get from the IT team in San Francisco, partly because it's quite likely that the format will change in time based on participation - one thing is interacting with 10 people, another thing is interacting with 100 or 1000, and we really can't predict right now what the turnout will look like. What I do know is that the process of announcing the series of events is a work in progress - further notices will be sent to mailing lists, technical village pumps etc. in the next hours. I can't make any promise about when more information will appear on the Portal page linked above: shortly before the meeting begins is accurate, although we're doing everything we can to get most details fleshed out ASAP. Thanks for your note,

Elitre (WMF) (talk)21:22, 8 February 2015

User:Lyzzy, and others, please see Talk:VisualEditor/Portal#How_to_join_the_triage_meetings. Thank you!

Elitre (WMF) (talk)19:49, 10 February 2015

That page also has a link to an e-mail message with the results for each nominated bug, plus information on the next meeting (which is about 22 hours from now).

Whatamidoing (WMF) (talk)17:22, 17 February 2015

The next bug triage meeting will be at midnight UTC on Thursday, which is 16:00 PST on Wednesday for West Coast folks. This one is timed to be easier for some people in Asia to attend. Information about how to join is at Talk:VisualEditor/Portal (if you've never used WebEx, then please plan some extra time to get it set up), but as of this message, the "follow this link" will take you to last week's meeting, which won't be very useful. I'm trying to track down the new link, and it will be posted there before the meeting starts.

Minutes from the last one can be read on wikitech-l here.

Whatamidoing (WMF) (talk)05:21, 24 February 2015

Howdy. This is your reminder that the upcoming VE triage meeting will be held on Wednesday, 4 March at 08:00 PST (16:00 UTC). Full information about how to join the Webex call or the IRC channel, and the links to the IRC logs and minutes for the last appointment, live as usual at mw:Talk:VisualEditor/Portal. I'm looking forward to seeing you there!

Elitre (WMF) (talk)18:36, 2 March 2015
Edited by author.
Last edit: 11:53, 18 March 2015

Hi again. This week's triage meeting will happen on Wednesday, 11 March 2015 at 12:00 (noon) PDT (19:00 UTC). We hope to see you there, but in case you can't make it, please remember you can still nominate "blocker" tasks in advance on Phabricator, or you can read the IRC logs and minutes which are usually published shortly after the end of the meeting to see what was discussed. So see Talk:VisualEditor/Portal for details (notice the new format, a Google Hangout). Thank you, and talk to you soon,

Elitre (WMF) (talk)17:28, 10 March 2015

Hello again, as you guessed I'm here to announce that the VE team will conduct the next triage meeting on Google Hangouts and IRC this Wednesday 18 March at 4pm PDT, that is 11pm UTC. As usual, you'll find other info about how to participate at, and we hope to meet you there. Best,

Elitre (WMF) (talk)17:05, 17 March 2015

No community members attended this week's meeting. If you want to attend but had problems, please let us know.

Whatamidoing (WMF) (talk)17:24, 20 March 2015
Edited by author.
Last edit: 20:31, 23 March 2015

This is the last chance in this quarter to inform the developers about VisualEditor's bugs they need to prioritize now. Show up on Google Hangout this Wednesday, 25 March 2015 at 12:00 (noon) PDT (19:00 UTC), and read the page at for details or to nominate a task for review even if you're not planning to attend the meeting. Talk to you later this week, then!

PS: Related to VE, this Friday 27 March at 15:00 UTC an office hour about VE will be held on IRC. Previous logs and other information, including how to participate, can be found at Meta. It will be the last office hour in this format, but we'd like to discuss alternative formulas which are more useful for everybody. Therefore, please see and comment the related Phabricator task, or just come and discuss the future of these conversations with us on Friday. Best,

Elitre (WMF) (talk)18:25, 23 March 2015

Can you give me some more details as to how should I attend these meetings , though Google Hangouts?

Leaderboard (talk)20:23, 23 March 2015

I edited my message to point that details (that is, the actual link) is on the triage meetings'page. Does that answer your question?

Elitre (WMF) (talk)20:33, 23 March 2015

Very slow for average Africa

Hi, we had the first day of our workshop for introducing Swahili wikipedia and gaining new editors. We had planned to start the introduction with the Visual Editor. We had to cancel this because on a test run the evening before we could not open pages this way, whereas by going to source edit we entered in a short time (after 5-8 seconds, but waiting more than 10 minutes for Visual editor - in vain. Just now a night later test repeated: 4=5 sec source, 75 seconds VisEditor. I gladly keep on testing this as long as I am in the country.

Kipala (talk)22:06, 21 March 2015

Thank you for this information. Some major improvements to performance were made late last week. I believe those improvements are why the performance improved from many minutes to 75 seconds. However, 75 seconds is still too long for people to wait. The team is working on speed as one of the most important needs for users.

Whatamidoing (WMF) (talk)18:42, 23 March 2015

Displaying Wikidata in infobox template

In Slovenian wikipedia we use in our infoboxes a lot of data from Wikidata. When I try to change the contents of the parameter (for example image parameter) that collects data from Wikidata, clicking button "Apply changes" in template dialog box does not show any changes. You can test this in slovenian article sl:Stanley_Kubrick.

Pinky sl (talk)17:44, 20 December 2014

This is a known problem. Unfortunately, it's a very difficult, fundamental problem.

Whatamidoing (WMF) (talk)18:49, 20 March 2015

Updated special character inserter tool

The new design for the special character tool is available here at You can test it by going to and choosing the "Ω" button in the main toolbar.

This wiki (currently) only has a small, basic set of characters. The list can be expanded and customized at each wiki. Follow the instructions at VisualEditor/Special characters to add more characters. However, the method for customizing the tool will probably change during the coming months.

Please test this out and let the devs know what you think about it. Is this new, full-width tool better than the old floating palette in VisualEditor? How could it be improved?

Whatamidoing (WMF) (talk)18:47, 5 March 2015

Far better than the old one. Especially I like that this does not get closed after clicking a character. Maybe box size of characters could be a bit smaller, idk, but at least it's easier now to choose correct character on mobile version.

Stryn (talk)19:20, 5 March 2015

Seems a lot better than the one I tried a long time ago. I also like the fact that it stays visible after adding one character, so you can keep adding other characters.

First suggestions for improvements:

  • Loosing less space: reducing line height for titles ; smaller boxes around charaters ; less space between boxes ; smaller font (same size as the rest of the menus ?)
  • Ability to resize vertically the special characters area
  • Behavior for quotes is not intuitive when text is already selected: I expected the quotes to go around the selected text (which is the current behavior on the French Wikipedia for the special characters tools that appears below the wikitext editing zone ; which is also the behavior for the tool that is available in the toolbar above the wikitext editing zone in this wiki) not to replace the selected text
  • I also prefer the behavior of the wikitext characters tool when text is selected: the selected text is not deleted
NicoV (talk)19:57, 5 March 2015

Agree very much with these points. Resize would definitely be nice. Smaller boxes would also be great so you don't have to scroll so much when more characters are added (perhaps the box borders could be removed altogether?) Overall a great improvement already!

Danmichaelo (talk)20:13, 5 March 2015

It seems far better than the old one. Like previous commenters I think that the quotation marks as well as some other tools would benefit from wrap-in instead of overwrite behaviour and that fitting more characters in the same space would make sense. One idea was to make the characters itself smaller. In addition I would suggest to reduce the space that is taken by the navigation to character categories: There is the sidebar with the TOC and the headlines above each section. This takes about 1/3 of the space. Shrinking the sidebar and rotating the headlines by 90° or getting rid of the headlines altogether or somehow integrating the headlines into the symbols grid (start of the row or so) would be worth trying.

Simulo (talk)08:59, 6 March 2015

It seems far better than the old one. Like previous commenters I think that the quotation marks as well as some other tools would benefit from wrap-in instead of overwrite behaviour and that fitting more characters in the same space would make sense. One idea was to make the characters itself smaller. In addition I would suggest to reduce the space that is taken by the navigation to character categories: There is the sidebar with the TOC and the headlines above each section. This takes about 1/3 of the space. Shrinking the sidebar and rotating the headlines by 90° or getting rid of the headlines altogether or somehow integrating the headlines into the symbols grid (start of the row or so) would be worth trying.

Simulo (talk)08:59, 6 March 2015

This new character tool is much better designed.

At first sight, it is great ! There is just a tiny defect : the tool does not work ! It does not insert any character.

The categories being one above another are a nice idea. Being able to scroll from one to another would be even better. The previous category is visible above. It is inconsistent that I cannot scroll up to it.

The name of the category "Lettres accentuées" is not correct. In this cat, some characters are not accented letters (œ, ø...). I suggest to name this cat "Lettres".

I have Safari on iOS 7 on an iPad mini.

Thank you for the improvements !


Nnemo (talk)14:24, 6 March 2015

In english, this is even worse.

The cat is named "Accents". I suggest to name it "Letters". And another cat is named "Mathematical". Some word is missing. I suggest to name this cat "Mathematics" or "Maths". It will be simpler.

Thank you.

Nnemo (talk)14:48, 6 March 2015


Following your suggestion, I replaced "Lettres accentuées" by "Lettres". However I don't know when the translation will be available on the French Wikipedia. The translation for special characters currently in use is very old.

NemesisIII (talk)10:58, 12 March 2015

Are the existing local symbols going to be automatically imported? If not that is bad news. They have already had to be re-entered by hand once because they were lost when vised was first implemented. Having to do it a second time is just make work for someone else.

SpinningSpark13:33, 7 March 2015

It's using the old JSON format for now. Eventually, a better system will be added.

Whatamidoing (WMF) (talk)19:49, 10 March 2015

It is much better than the old one, yet I would still prefer if it was located below the actual editing box and not above it. I think the common paradigm (also seen on mobile phones) is to have input tool placed on the bottom.

Smihael (talk)14:54, 10 March 2015

I agree with the size issue. VE always tends to make things bigger than needed. For the maths symbols I didn't think much of the initial selection, use of the special superscript character is discouraged for maths articles its better to use the sup tag 1234567890 compared to superscript chars ¹²³⁴⁵⁶⁷⁸⁹⁰. The ²³ have some use for doing units like m² but the other have very limited use.

Salix alba (talk)08:05, 11 March 2015

I think that whether it's bigger than needed depends upon your computer set up as well as your vision. We have more than one user who zooms in to be able to see things comfortably in VisualEditor. (The toolbar, in particular, needs to be re-designed to behave better when zoomed. Right now, it wraps and covers a lot of the screen.)

Whatamidoing (WMF) (talk)18:07, 20 March 2015

Hi, the new special character insertion tool is a lot better than the previous one: It now takes two clicks to insert a special character instead of four. However, that is still twice as many clicks as in the Wikitext editor, where inserting a special character only takes one click, thanks to the extended editing toolbar.

Quotation marks that wrap around selected text (as they do in the existing Wikitext editor) would be really cool. To highlight the importance of this feature, please note that, for example, the German-language community will have to insert each and every quotation mark using this tool because German uses different quotation marks than English ("" vs. „“). The same, as far as I know, goes for French ("" vs. «»).


Gnom1 (talk)14:22, 11 March 2015

Hey User:Gnom1, by "extended editing toolbar" do you mean the Sonderzeichen one inside the toolbar, or the one at the bottom of the page? Thanks,

Elitre (WMF) (talk)15:47, 17 March 2015

Hi, I totally agree with the users above. The new tool is much better than the previous one. I also think the tool should a bit smaller because it takes a lot of space on small screens. Otherwise, it is much more practical and easier to use. You did a good job with this. Thanks,

NemesisIII (talk)10:51, 12 March 2015

Unfortunately the new special character inserter tool doesn't work in the reference editor.

NemesisIII (talk)11:50, 15 March 2015

Or for typing in the names of templates or categories, or several other issues. Those items are on the list as necessary improvements for the future.

Whatamidoing (WMF) (talk)18:05, 20 March 2015

This is an immense improvement over initial attempts. Good job!

I would welcome some improvements mentioned by other people above, such as the behaviour for quotation marks and the ability to resize... but these are more nice-to-have details. The only major issue that I see now is that it works only in the main text zone, not in references and other templates.

Klipe (talk)17:32, 15 March 2015

Table editing capabilities available in VisualEditor extension to MediaWiki 1.23?

The table editing functionality is very much wanted. Will this be available with MediaWiki 1.23?

Paugul (talk)14:42, 10 February 2015

It's very unlikely. Back-porting that much code would be perilous and complicated, and it's not something we're planning to work on at WMF.

Jdforrester (WMF) (talk)02:17, 17 February 2015

Thank you for your reply.

May I ask for an advice?

We are finishing an upgrade of our wiki from MW 1.16 with FCEditor extension.

We decided to use MW 1.23. The reason is: MW 1.23 is a LTS version.

We want to use VisualEditor, but without table editor it seems like we will offer our editors poorer functionality with VisualEditor than the existing functionallity they experience with FCEditor.

Will VisualEditor in combination with MW 1.24 (latest stable) give us table editor?

Will MW 1.25 be a better choice?

We are not in a position where we can use much resources on keeping MediaWiki and extensions up to date. That is why we wanted a LTS version.

Paugul, 20 February 2015

It looks like LTS versions are only released once every two years, and the last one (1.23) was in 2014. Unless you're willing to wait until 2016 for this, then I think you'll have to go with the current version.

Whatamidoing (WMF) (talk)18:02, 20 March 2015

How can I Use 'Table' and 'Gallery' in Visualeditor extension to MediaWiki 1.24.1.

I see the Media, Templeate, Comment, Formula, and Reference list in Insert Menu But, I can't find Gallery and Table.

How can I Use 'Table' and 'Gallery' in Visualeditor extension to MediaWiki 1.24.1.

I installed this version. VisualEditor-REL1_24-af11aa1.tar.gz.

Redkreuz (talk)05:34, 18 March 2015

I'm not sure, but I think that version is about a month before Table support was added. You might need to upgrade to the latest version.

Whatamidoing (WMF) (talk)17:09, 20 March 2015

Special character list...edits do not appear

Web browser: Firefox 36.0.1 Operating system: Windows 7 Wiki skin: Monobook

I edited the special character list at When I try to edit an article, my edit to the list does not appear. I went to to validate the code, and it says:

Parse error on line 1:
Expecting '{', '['

However, I don't see anything like <!DOCTYPEhtml><htmll in the list. After trying to find <!DOCTYPEhtml><htmll, suddenly all the symbols and characters in the list changed to Unicode points (like "\u2212": "\u2212"). I don't know how that happened and I can't seem to revert it.

Stephen G. Brown (talk)17:50, 14 March 2015

Works for me, for example try

Stryn (talk)16:14, 16 March 2015

Okay, I see what it is now. I have to have the Navajo language selected in my Preferences before I can see the edited list. That does not explain why all the symbols changed to Universal Character Names (UCN). I’m going to try re-entering each affected letter and symbol in the list to see if I can get the Unicode letters and symbols back again. Thanks.

Stephen G. Brown (talk)23:45, 17 March 2015

Issues with Cite from URL

[Reposting from the English Wikipedia; no response there in over a week.]

The option, under the Cite menu, to paste or type a URL and have VE (via Citoid) build a citation is great. But:

  • Right now, after the URL is put into the dialog, and the user clicks "Insert", the dialog closes. This makes no sense. The dialog box should remain open, showing the citation that has been built. If Citoid were perfect, then of course it would be fine to close the dialog. But it's not perfect. For example in the MSNBC article whose URL I used ( ), VE/Citoid didn't add a date (though it did create an accessdate), it put "|MSNBC" in the title, it didn't list a publisher, and it didn't create first and last fields for the author's name. So the dialog should stay open so that a user can fix Citoid errors and incompleteness.
  • The Cite from URL dialog retains the last URL used when opening. It should not. First, it's unlikely that the user is going to want to use the same URL twice. Second, it's contrary to Wikipedia procedures to create two distinct but identical citations. That's why "Re-use" is an item in the Cite menu. So, can we nix the retained URL thing, please?
John Broughton (talk)17:20, 9 February 2015

Just in case anyone else reads this: this was long since fixed in production, but won't be fixed in the temporary script that John has been using.

Whatamidoing (WMF) (talk)17:40, 5 March 2015

Table: switch cell while in edit mode.

While editing a cell, would be nice if one could switch the cell using tab or the arrow keys.

The team plans to do this. Users will be able to navigate between cells with the Tab key.

Whatamidoing (WMF) (talk)17:38, 5 March 2015

Individuals as beta testers?

I'm not part of a community, I just have a wiki running at work and at home. The primary barrier to rolling out the wiki to everyone else at work is the editor. Is there a way for an individual user or customer of MediaWiki to become a beta tester of VisualEditor and provide feedback?

Parrotheadcali (talk)20:48, 3 March 2015

On your local wiki, you mean? You could set VisualEditor as a Beta Feature, I guess - there's a related extension, but I don't know what you would need to do after installing it, so I recommend asking the VE team live on IRC, #mediawiki-visualeditorconnect, usually after 5pm UTC.

Elitre (WMF) (talk)11:44, 4 March 2015

Welcome to, Parrotheadcali. You can provide feedback on VisualEditor here, even if you don't contribute to Wikipedia or similar public communities. Many people who use VisualEditor at work use this page to let us know about the problems they encounter and the ideas they have.

Whatamidoing (WMF) (talk)17:36, 5 March 2015

Two issues from cs.wn

Dear friends, as the VE was made available on Czech Wikinews, I started experimenting with it as I also use it on Czech Wikipedia. However, I met two issues, that are probably rather special for WN:

  • We use standard aliases [[w: to link the Wikipedia articles. When the article is editted in VE, the links are however interpreted as external links [ ]. If no change is made within them, they are not changed, but one cannot edit them as aliased interwiki links.
  • For creating new articles or new daily survey pages, the pre-filled templates are used. When the user links the "create new article" box or a "create new daily survey" link, the classical wikitext editor window is opened pre-filled with the template. Is VE ready to use such a functionality?

Thanks for answers/improvements.

Okino (talk)01:42, 19 December 2014

HI there, sorry for the belated answers. About n.1, regardless of what the links currently look like, they can indeed be edited (of course, you won't be able to see suggestions of possible articles you'd want to link to), you only have to change the actual page title and not worry about the rest of the URL. About n.2, not really (but could pre-filled templates be added, would TemplateData allow this? Asking @User:Jdforrester (WMF) here), but I think that when switching back and forth between VE and wikitext editor will be possible, that should be an acceptable workaround.

Elitre (WMF) (talk)12:05, 4 March 2015

The John Lennon Wall

Hello, I have been visiting Prague with my company and our professional photographer... I uploaded some 2015 photos from The John Lennon Wall... Maybe you want to use them, to show little more from the John Lennon Wall in Prague.


Aworldofdifference (talk)19:21, 28 February 2015


Perhaps this question is too broad for this page, but I would like to know if there is plans for an interactive "onboarding" process for first-time users of the Visual Editor?
Currently, when you first hit "edit" in the visual editor, there is a popup box that says welcome, and some info about the VE. After you dismiss that, you're on your own. I recently came across this blogpost which explains the the onboarding process for Duolingo, it also reminded me of the similar, and very very good, onboarding process I experienced when using the new OpenStreetMap editor for the first time. Both seamlessly took me through a little training exercise before letting me loose on the real project.

So... I know it's not in the scope of the VE team's work to improve the software, but is there plans to create a seamless, interactive (i.e. not "go read the documentation first then come back and try again") onboarding system for the Visual Editor - that a first-time editor is presented with? There are obvious questions to answer about "would this interfere with the 'immediate satisfaction of seeing your changes' that gets many anon's to start editing in the first place?" and "would this be presented to existing users who are using the VE for the first time, or only to newly registered users?". But, as a general idea, is this on the drawing board?

Wittylama (talk)18:07, 6 February 2015

Hi Liam, so I think that what you want is something like this. I'd +1 your idea so badly. Unfortunately, as you can see, there's code writing involved (not exactly my "piatto forte" ;) ) and there may be blockers behind the initiative (like this one) on which I have no control either. Maybe James will come up with an even better idea!

Elitre (WMF) (talk)19:02, 6 February 2015

I'd also look at what Jack Herrick at WikiHow has done in this regard, as they did lots of testing and tweaking to find out what the first edit experience would be like for WikiHow. He's done Wikimania talks about this in the past, but I'm sure he'd be happy to share this verbally too.

Fuzheado (talk)16:04, 9 February 2015

Thanks, Andrew!

Elitre (WMF) (talk)16:14, 9 February 2015

Actually, I just learned that [1] exists :)

Elitre (WMF) (talk)18:05, 11 February 2015

Yes, that is a good idea! I realised after my initial suggestion that the two distinct user-groups (new wikimedians vs. existing Wikimedians using the VE for the first time) have quite different needs... The former group would probably benefit most from a guided tour that focused more on the "rules of wikipedia" but the latter group would benefit most from a technical tour specifically designed to highlight the "new ways to do x, y and z". Not only are these different things, these require different wording. e.g. for a guided tour about external links. We would want to tell:

  • Newbie editors about what kinds of links are appropriate (referring to "reliable source" policies).
  • Existing editors to place the text they want linked first and thento highlight those words and click the "link" icon - not the other way around which they are used to.
Wittylama (talk)15:46, 16 February 2015

"Save" at the end of the toolbar

Why is the VisualEditor "Save" button is at the end of the toolbar? (Right in LTR, left in RTL.)

In other desktop word processors the save button is in the beginning of the toolbar.

I somehow didn't think about this till now because it didn't bother me personally, but a user in the Hebrew Wikipedia asked about this, so I'm wondering: why is it so?

Amir E. Aharoni (talk)09:27, 9 January 2015

Per the Design team, progressive actions in the workflow are on the right (left in RTL).

Jdforrester (WMF) (talk)02:28, 17 February 2015
First page
First page
Previous page
Previous page
Last page
Last page