Extension talk:WikiEditor

Jump to navigation Jump to search

About this board

pre LQT talk on this page

Icons on buttons do not appear

Fexadom (talkcontribs)

I have a new Mediawiki 1.26 installation in Centos 7, everything works fine except the WikiEditor. After installing the Wikieditor extension and configuring the Localsettings.php according to the extensions README file, the new editor appears but the icons are not showing. The tooltip shows correctly and I click the buttons and the correct action is executed but no icons. I've tried this in the latest Firefox, Chrome and IE browsers and I get the same results. Also, I tried already editing the Common.css wiki page as suggested in a couple of forums but it doesn't work. I am running out of ideas. Any suggestions? Thanks! (talkcontribs)

Same as in my installation at Centos 7

JohnEagles (talkcontribs) (talkcontribs)

I am having this issue on CentOS 6.7, mediawiki 1.26 with WikiEditor version info:



The buttons do not render and while the default toolbar renders as a single line when mediawiki is disabled, the button regions render as two empty table cells next to the tabs. I believe that 72db6c7 is the latest version published - is there any update or am I missing something? (talkcontribs)

Same problem. Did anyone get this figured out?

4ndY (talkcontribs)

I had the same issue. The fix is to add 'data:' in the Content-Security-Policy.I've added it in the nginx config.

Reply to "Icons on buttons do not appear"

Compatibility issue with Page Forms

Drfoland (talkcontribs)

WikiEditor 1.32 has a compatibility issue with the Page Forms extension. This is due to the fact that


$.wikiEditor.modules.dialogs.config = {




has been replaced with


module.exports = toolbarConfig;


Page Forms still relies on the jQuery module, and thus fails to render the WikiEditor toolbar when using the form editor. This is easy to resolve by redefining the jQuery module for backwards compatibility, but may be more appropriate to resolve with the Page Forms team.

Jdforrester (WMF) (talkcontribs)

We won't bloat the experience for all users of WikiEditor just to provide compatibility for PageForms; the maintainers of code dependent on WikiEditor are responsible for maintaining that, sorry.

Whatamidoing (WMF) (talkcontribs)

Pinging @Yaron Koren, because this incompatibility should probably be documented somewhere (assuming it can't be fixed).

Yaron Koren (talkcontribs)

I thought this was fixed in Page Forms already, but maybe not. What version of Page Forms are you running? Or are you just looking at the current code?

Reply to "Compatibility issue with Page Forms"

WikiEditor not showing in version 1.31.4

2 (talkcontribs)

I upgraded my Wiki from version 1.31.1 to 1.31.4. Everythings works fine except that the WikiEditor ist not showing up during editing any more. The WikiEditor is listed on the special pages "Version". Error tracking is on. I do not get any errors. Examining the page in Firefox with F12 showed also no errors. I didnt't change my LocalSettings and I ran the update script. Any suggestions?

Greetings from Basel

Thomas (talkcontribs)

I changed back to version 1.31.1 an the editor is showing up. Switching back to 1.13.4 the editor is gone again.

Reply to "WikiEditor not showing in version 1.31.4"

iOS Safari: Can't save edit in WikiText editor after....

Summary last edited by Kghbln 20:25, 27 June 2019 1 year ago

Bug: some contributors editing using Safari on iPhone are having difficulty saving. This issue is actively being worked on. The real time progress on this fix can be tracked in Phabricator.

PPelberg (WMF) (talkcontribs)

Today, 14-March, it was discovered that some contributors' edit saving flows are being severely disrupted.

More specifically, contributors using mobile Safari on iPhone are finding the "Save" button is both a) out of view and b) unable to be scrolled to, rendering saving an edit extremely difficult. [1]

Current status: this bug is actively being worked on. The progress of which you can follow in the Phabricator ticket linked here and above.

1. Technically, the "Save" button can be accessed, and an edit saved, by "pinching to zoom out"

PPelberg (WMF) (talkcontribs)

Current status: as of approximately 5:00pm UTC today, 15-March, T218352 has been resolved.

We should note that: in prioritizing deploying a solve for the above in short order, we knowingly introduced some other – less than desirable – changes to the mobile editing experience.

Changes to mobile editing as a result of the above:

• The editing toolbar on mobile VisualEditor is not sticky (read: it can be scrolled out of view) on iOS


• The headers in all mobile overlays is inconsistent between iOS and Android


Hide custom sections in namespaces

Loman87 (talkcontribs)


I am trying to find a method to show my custom toolbar sections only in some namespaces. I know that is possible to show/hide buttons, using the 'filters' parameter; anyway I need to hide an entire section, is that possible? I tried using the 'filters' parameter in the 'section' level, but it didn't work.

Thanks in advance,


Erutuon (talkcontribs)

How about only adding the toolbar sections in the certain namespaces like this?

if ( [ /* numbers of the namespaces where you want to show the toolbar sections */ ].indexOf( mw.config.get( 'wgNamespaceNumber' ) ) !== -1 ) {
	/* then add the toolbar sections */
Reply to "Hide custom sections in namespaces"

Missing WikiEditor options in 1.31

AnonymusGdpr (talkcontribs)

Hi there! I have just upgraded our test wiki to Mediawiki 1.31. Previously, in the user settings there have been options for the width and height of the editor window, these are missing now. Also there has been an option for the WikiEditor font called "browser default". Am I looking at the wrong place or have they been removed intentionally?

Dinoguy1000 (talkcontribs)

I don't know offhand about the font, but the width and height options were intentionally removed, yes. It is preferred to customize these via sitewide or user CSS.

AnonymusGdpr (talkcontribs)

Great. And how can I do that?

Dinoguy1000 (talkcontribs)
#wpTextbox1 {
  width: ##;
  height: ##;
AnonymusGdpr (talkcontribs)

That's it! Thank you very much!

What's the difference between this and the Visual Editor?

Thedonquixotic (talkcontribs)

From the description it is not clear. Is this an older project that was eventually superseded by the Visual Editor but had similar ideas?

Jkmartindale (talkcontribs)

They're actually quite different. As the name suggests, Extension:VisualEditor provides a visual editing interface that doesn't require knowledge of wikitext. On the other hand, Extension:WikiEditor extends the standard wikitext editing interface. You may have noticed that the default editor included in MediaWiki core doesn't have as extensive a toolset as the wikitext editor on Wikimedia sites. The additional wikitext editor toolbars these wikis have are added by WikiEditor.

Thedonquixotic (talkcontribs)

@Jkmartindale Thank you, I can kind of get the gist of that but I wasn't clear on what their relationship was to each other within the organization? As in, if I were a new dev coming in, and I wanted to start learning how MediaWiki works, and I wanted to only focus on the new tools that would be actively evolved and developed going forward, which one would I focus on? Are they both being actively developed and have different use cases? Are the reasons why they're kept around due to a difference in design philosophy?

I eventually found a conversation on a third party website where an article described the WikiEditor as being superseded by the VisualEditor which confirms the idea that I got from their visual design etc, but it might be helpful if this information was explicated in the article in some way. I don't mean to tell you guys what to do, I'm just saying as a developer coming from the outside, it's difficult to see what the main thrust of the community or org is right now in it's development process. (for instance I can tell you off the top of my head what Wordpress, Canonical, ES6, Mozilla etc are all focusing on as communities and orgs, but it's much hard for me to parse this when looking at the MediaWiki project because things seem to be a bit all over the place).

Jkmartindale (talkcontribs)

It's been a while since I've been actively participating (if you could call it that) in the MediaWiki project, but judging from a quick glance at the trunk of WikiEditor, it's still actively developed. Not as actively as VisualEditor, but it's still getting bug fixes and being kept up-to-date with MediaWiki releases. WikiEditor is also pretty much "finished", so I'm not sure what else would be added to it other than maintenance fixes.

Don't treat this as an official statement or anything other than speculation, but I'm pretty sure WikiEditor is going to be around for a long time. VisualEditor is still "unstable" and some people like myself prefer WikiEditor by far (I've actually disabled VisualEditor on every Wikimedia site I'm a part of). Additionally, VisualEditor relies on Parsoid which in turn relies on Node.js, and I'm pretty sure WikiEditor would be kept around so that MediaWiki installs won't require both PHP and Node.

However if you're a new dev wanting to see how MediaWiki works, definitely ignore VisualEditor for now. You want to learn about MediaWiki core first, and when you get to extensions you'll want to look at simpler extensions. VisualEditor has a ton of moving parts that aren't necessarily tied to MediaWiki, so it's not going to give you much information that other extensions can't.

As far as what the main goals of the MediaWiki developers are, I don't really have a clue. I sort of just started fixing what I came across that was broken, or adding things that I wanted to a handful of extensions. I never really did figure out where all the developers hang out, except maybe IRC.

Whatamidoing (WMF) (talkcontribs)

WikiEditor (aka the 2010 wikitext editor) is in active maintenance. That means that it will be kept working, but no new features are planned. The visual editor (aka VisualEditor's visual mode; it also has a wikitext mode) is still under development. The Editing team's current focus is VisualEditor on the mobile site.

If you are trying to figure out which one you're using, then you can go to the page Editor to see the screenshots.

SSethi (WMF) (talkcontribs)

@Thedonquixotic I understand your frustrations! I would like to share with you our New Developers guide which might give you an idea of our broader technical community, projects and recommended steps to start contributing. If you are interested in contributing to MediaWiki, then extension writing is what we recommend starting with and not MediaWiki core as its codebase is complex and we've limited resources to help with support and code review. If you would like to share your thoughts on how we could improve our New Developers guide to explain better what we do and anything else, I would love to hear your thoughts on the talk page.

Thedonquixotic (talkcontribs)

@SSethi (WMF) Thanks! I'll check it out. I'm going to start by fiddling around with creating skins since I'm really mostly a designer learning frontend development right now. But I've got some ideas of things I can do and it will help me learning the wiki way of doing things :) thanks!

Whatamidoing (WMF) (talkcontribs)

Side note from a non-technical person: Apparently, MediaWiki's definition of a "skin" is very narrow and specific, so some things that people call skins aren't really skins here. I don't know where (or even "if") that is documented properly.

Thedonquixotic (talkcontribs)

@SSethi (WMF) BTW here's another example of what I find really confusing when coming to MW: Topic:Unh0a9wd2ho92o09 I basically get the relationship between the wikitext editor and the visual editor (espc since I now know how the 2017 wikitext editor integrates into visual editor when you have both installed) but then I find stuff like multiple WYSIWYG editors (which seem MW supported, at least at some point though one of them seems to be supported by some org called BlueSpice?)

Maybe some kind of "Editors Explained" page that had every single major extension, past or present that served as an editor could be stacked up and compared, along with some comparative analysis on what they offer strengths and weaknesses wise, and what their current development status is etc.

Also btw, idk if you guys have looked at Gutenberg much but I'm a WP guy and I'm really excited about it. It might be something MW folks should check out, especially since Drupal peeps recently proved how it could be decoupled from the underlying CMS and pretty easily migrated to a new CMS. https://wptavern.com/first-look-at-live-demo-of-the-gutenberg-content-editor-for-drupal-8

Whatamidoing (WMF) (talkcontribs)

Editor has a list of (most of) the editors that are or were recently installed on wikis that are supported by the Wikimedia Foundation (e.g., the English Wikipedia). Most, but not all, of the software on that page is supported by devs employed by the Wikimedia Foundation.

The ones that aren't on that list are more like "this can be run on MediaWiki" rather than "supported".

I guess you could think of software in these groups:

  • the editing environments on the Wikimedia Foundation's wikis,
  • the third-party options, not on the Wikimedia Foundation's wikis, e.g., all things BlueSpice.
Reply to "What's the difference between this and the Visual Editor?"

Toolbar disappears when activating assistants

Summary by TheDJ

Missing php7.2-xml

AnonymusGdpr (talkcontribs)

Hello there! I found a little problem with the WikiEditor toolbar. In my user preferences, I've activated the extended toolbar (german: "Erweiterte Bearbeiten-Werkzeugleiste aktivieren"), which works fine so far. As soon as I activate the Links&Table-assistants (german: "Assistenten zum Einfügen von Links und Tabellen sowie die Funktion „Suchen und Ersetzen“ aktivieren"), then, when I open the editor, the toolbar disappears.

Mediawiki: 1.27.4 Apache 2.4.29 PHP 7.2.10

The day before, I updated the server system software to Ubuntu 18.04. With the previously installed 14.04 and PHP 5.5, the toolbar assistant did work. I suspect the PHP version to cause the problem. Can anyone offer any hints, please?

AnonymusGdpr (talkcontribs)

The problem has been solved. After the upgrade to PHP7.2, there was one package missing: php7.2-xml. I have installed it and now everything works. Thank you anyway ;-)

Zoglun (talkcontribs)

preview tab disappeared with MW 1.31 upgrade.

It was one of the most used on our wikis, and everybody like it.

How can we reactive preview tab?

FreedomFighterSparrow (talkcontribs)

Unfortunately, it's gone for good, unless someone develops an appropriate extension. See discussions here: phab:T165112 and phab:T185555.

Reply to "How to reactive preview tab?"

I am deeply saddened ...

Summary by Kghbln

That's the way it is even though it radically cripples MediaWiki editing. No need to discuss further.

Kghbln (talkcontribs)

... by the removal of the preview feature which was working fine. The publish feature was indeed a bit suboptimal but the preview feature was great and working fine for years. This is a big step towards making MediaWiki editing less awesome for people who do not want or cannot use parsoid. I guess this is a sign of a lost perspective and for defying reality.

FreedomFighterSparrow (talkcontribs)

True. This isn't cool.

Ralfk (talkcontribs)

Missing the preview feature as well! (talkcontribs)

Is there any way to reactivate the preview?

2600:1700:1D01:22D0:BCF3:11DA:6306:20BB (talkcontribs)

I am both saddened and highly annoyed. The feature was one of the most used on my wiki.

Reply to "I am deeply saddened ..."