Help talk:Edit toolbar
Add topicLatest comment: 7 years ago by Veronica howard in topic My code
ëĜ==Doesn't work on meta==
The editing tool bar works for me on all Wikimedia projects I tried, except here on meta, the toolbar does not show up. - Patrick 16:30, 30 Jan 2004 (UTC)
- It works now.--Patrick 15:25, 2 Jun 2004 (UTC)
My code
[edit]I've added some interesting features to my toolbar, including adding a page template as a button, adding an arrow character as a button, left/center/right align, categories and getting | flash mp3 to work as a button. Just please link your images to your own local site instead of mine(but feel free to use my mp3 image button i made if you want). Source code below:
/* Any JavaScript here will be loaded for all <s>users</s> on every page load. */
/** Extra toolbar options ******************************************************
*
* Description: UNDOCUMENTED
* Maintainers: [[User:MarkS]]?, [[User:Voice of All]], [[User:R. Koot]]
*/
//This is a modified copy of a script by User:MarkS for extra features added by User:Voice of All.
// This is based on the original code on Wikipedia:Tools/Editing tools
// To disable this script, add <code>mwCustomEditButtons = [];<code> to [[Special:Mypage/monobook.js]]
if (mwCustomEditButtons) {
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_redirect.png",
"speedTip": "Redirect",
"tagOpen": "#REDIRECT [[",
"tagClose": "]]",
"sampleText": "Insert text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_template.png",
"speedTip": "Insert Grammar Page Template",
"tagOpen": "'''Grammar pattern''' : This pattern is equivalent to '''equivalent statement'''\n\n==ConjugationRule==\n*Pattern 1 : If there is no [[받침]]\n*Pattern 2 : If there is a [[받침]]\n\n==Conjugation Examples==\n*Original → After\n\n==Sentence Examples==\n*Example\n\n==Usage Exceptions==\n*Example\n\n==Pronunciation==\n*Special pronunciation rule?\n==See Also==\n*Related topic or grammar\n\n[[Category:CATEGORY NAME|WHERE TO SORT]]\n",
"tagClose": "",
"sampleText": ""};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_array.png",
"speedTip": "Insert a table",
"tagOpen": '{| class="wikitable"\n|-\n',
"tagClose": "\n|}",
"sampleText": "! header 1\n! header 2\n! header 3\n|-\n| row 1, cell 1\n| row 1, cell 2\n| row 1, cell 3\n|-\n| row 2, cell 1\n| row 2, cell 2\n| row 2, cell 3"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_mp3.png",
"speedTip": "Mp3",
"tagOpen": "<flashmp3>filename.mp3|leftbg=003478|rightbg=c60c30|lefticon=ffffff|righticon=ffffff</flashmp3>",
"tagClose": "",
"sampleText": ""};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_category.png",
"speedTip": "Insert Category",
"tagOpen": "[[Category:CATEGORY NAME|WHERE TO SORT]]\n",
"tagClose": "",
"sampleText": ""};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_align_left.png",
"speedTip": "Align Left",
"tagOpen": '<div style="text-align: left; direction: ltr; margin-left: 1em;">',
"tagClose": "</div>",
"sampleText": "Left-aligned text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_center.png",
"speedTip": "Center",
"tagOpen": '<div style="text-align: center;">',
"tagClose": "</div>",
"sampleText": "Centred text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_align_right.png",
"speedTip": "Align Right",
"tagOpen": '<div style="text-align: right; direction: ltr; margin-left: 1em;">',
"tagClose": "</div>",
"sampleText": "Right-aligned text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://www.koreanwikiproject.com/wiki/skins/common/images/Button_arrow.png",
"speedTip": "Insert Arrow",
"tagOpen": "→",
"tagClose": "",
"sampleText": ""};
}
Thanks Veronica howard (talk) 21:49, 24 February 2017 (UTC)
From pump
[edit]Eloquence has written a new feature: a JavaScript edit toolbar capable of formatting wikitext by clicking buttons. You can see a demonstration of it at test.wikipedia.org. It's a great idea but it seems to have a few minor issues at the moment:
- I cannot see Edit_toolbar in my own wiki server, I have enabled Show toolbar in my preferences and browsers have javaScript enabled. I heve tried with clean instalation of mediawiki-1.4.9 and mw1.4.6+enotifwiki3.11, and always the same no one can see edition toolbar. Any Idea? -- fermaf
Unless something is selected, the text will be inserted at the bottom, not at the cursor position- Fixed in Mozilla and IE, other browsers don't support the necessary JavaScript.—Eloquence
- In Mozilla, the edit window scrolls to the top every time a button is clicked
- This seems to be a Mozilla bug.—Eloquence
Some browsers display excess space around the toolbar- Should be fixed now, please report if it still occurs (clear cache if you've seen the toolbar already)—Eloquence
Eloquence thinks it's good enough as it is, and it should be enabled by default. However some people think some more work should be done on it first. Does anyone else have an opinion? -- Tim Starling 04:08, Jan 18, 2004 (UTC)
- I haven't seen example of the "excess space" problem yet. Can anyone reproduce that? That certainly should be fixed. The other I consider minor/unfixable (JavaScript implementation reasons), it works the same way as the phpBB edit toolbar, which is enabled by default as well. I should explain that the primary use of the edit toolbar is on selected text -- clicking the button without selecting text first inserts sample text, which is mostly intended for learning purposes.—Eloquence 04:15, Jan 18, 2004 (UTC)
- It misbehaves rather badly on Opera 7.23, I'm afraid. DOM issue, I guess... -- Finlay McWalter 04:19, 18 Jan 2004 (UTC)
- And NS4.8. As with opera, it seems unable to figure out what the selection is, and just stuffs things at the end. -- Finlay McWalter 04:29, 18 Jan 2004 (UTC)
- It can be disabled in the prefs. This discussion is about whether it should be on by default, which should be based on popular browser behavior (IE, Mozilla). What do you mean with "misbehaves rather badly"? Does it produce any errors?—Eloquence
- Even if it is enabled by default, it should be possible to disable it for user agents on which we either don't know it works, or know it doesn't. nb: I've also checked it with Konqueror 3.1-12 and again it can't recognise the select (I'd hazard a guess that this means it will probably also not work with Safari). (Sorry, "rather badly" means "always thinks the select is empty"). I'll look for error printfs tomorrow (it's sooo past my bedtime) -- Finlay McWalter 04:38, 18 Jan 2004 (UTC)
- Pretty nifty, but I think it needs work in order to be included by default, and it it can't be fixed it shouldn't be included by default. The selecting text thing is major in my opinion. Those that are most likely to use the toolbar are also those that will be most likely to be confused by the glitches. What text are you supposed to select when inserting a signature or HR anyway? Good work though! Dori | Talk 05:52, Jan 18, 2004 (UTC)
- Great work. I use Mozilla. The bug regarding the window scrolling up is serious. Needs work. Where is the source code? Can I check it? Optim 06:16, 18 Jan 2004 (UTC)
Everyone, please clear your caches before trying again (Shift+Reload may not work with IE). I've changed the JS so that the tags are inserted at the cursor position, but the scroll-up problem might be a Mozilla bug. At least now when you press a cursor key you're in the right place again, as the cursor is now in the right position. Everything should be perfect in IE now.—Eloquence 06:44, Jan 18, 2004 (UTC)
- In NS7.0 it adds only at the end of the article. Anyways: I'd rather have wikimarkup simple enough so that a human being can learn it easily than having a fancy edit script. If we need such an edit script, it should be set to off in the preferences for default. -- till we *) 18:01, 18 Jan 2004 (UTC)
- That's the default behavior in all browsers which don't support the necessary JS and still better than nothing for learning the tags. It should work in NS 7.1. In JavaScript-disabled browsers, nothing is shown at all. It will be enabled by default.—Eloquence 18:17, Jan 18, 2004 (UTC)
- I mostly use konqueror, so it doesn't help me. WormRunner 02:41, 19 Jan 2004 (UTC)
- Personally, don't like the look of it, but nice work. I reckon the WP markup is easy enough without the toolbar. If it's made default (I don't care), maybe you want to add buttons for lists and bullets? Kokiri 11:15, 19 Jan 2004 (UTC)
Nice work (IMO) ... could I ask, can these be made into bookmarklets? thanks ... [mumbels about source code =-] ... JDR
If any major feature of this doesn't work in any browser, then end users using those browsers shouldn't even see any part of it. The behavior in Konqueror is very confusing; when I select text and click the B I expect that text to be bolded (or at least the markup needed to make it bolded should be imputed). If this confused and frustrated me (a person with a great deal of computer literacy), it most certainly will confuse and frustrate rank newbies (especially ones only familiar with highly sanitized GUIs). So it should not be shown to any browser that does not fully support its functionality! Erik wants to make things easier for newbies ? that's a great goal. But any newbie not using IE on Windows (maybe a few other configs) will be more confused and frustrated with this feature than without it. They will think that Wikipedia is broken, not their browser and then go away. So if it don't work in certain browsers, then run browser detection and don't serve broken bits to newbies. They will trip over them. --mav 09:26, 20 Jan 2004 (UTC)
- I don't buy it. The input box gives the user a quick example text for each major markup function which they can copy and paste. Your reaction is simply the result of having seen previous versions of the toolbar. I fully intend to activate this inputbox for users of browsers which are not capable of handling text selections via JavaScript, as I consider it a useful feature for learning the syntax. This is important especially when following red links, where there is no example markup whatsoever.
- If you do think the text "Click a button to get an example text" is not sufficiently self-explanatory, feel free to suggest a better one.—Eloquence 01:04, Jan 21, 2004 (UTC)
- I'm afraid I'm not too keen on this whole thing, for a number of reasons:
- A key attribute of a wiki is that the syntax is incredibly simple, and this will just make it more tempting to complicate it ("Well, we can always have a toolbar button for it").
- The toolbar as it currently is has serious bugs with several browsers. Users of these browsers visiting for the first time will be confused by this. Browser sniffing is in itself a Bad Thing, because you have to arbitrarily include or disclude browsers/versions that you haven't heard of yet (or don't exist yet).
- As a learning aid, it suffers from a lack of explanation, and does little to show users how to use and read the actual syntax. (Eloquence, exactly where are you claiming the text "Click a button to get an example text" should appear? I don't see it anywhere...)
- Maybe some people would find this useful to switch on in the prefs, but with the conciseness of wikitax even this seems unlikely. But for new users, I think it creates far more problems than solutions. Better, IMHO, would just be to change the message on every edit page to include a direct link to a quick summary of syntax - a kind of compact reference version of that in Editing help But that's just my view... [Oh, one more thing - '' and ''' aren't technically italic and bold, they are emphasize and emphasize strongly. Not that it matters very much, but...] - IMSoP 13:55, 21 Jan 2004 (UTC)
- I'm afraid I'm not too keen on this whole thing, for a number of reasons:
- 1) is a very weak slippery slope argument - hardly worth responding to. There are more than enough developers who believe strongly in a simplified syntax. 2) Which "serious bugs" are you talking about? The toolbar has no bugs, to my knowledge. The only bug I know about is a Mozilla bug. 3) I think you just don't understand it. The behavior of the toolbar depends on the browser - in Mozilla and IE you get a select+click formatting, and if you click without a selection, it inserts sample text at the cursor. In other browsers, clicking on the button presents an explanation for each feature in an infobox.—Eloquence 21:21, Jan 21, 2004 (UTC)
- OK, I agree that (1) is very much a matter of opinion, and put badly at that - it just seems like a step backwards to develop a concise syntax, and then imply that a tool is needed to author it. As for "the only bug I know about is a Mozilla bug", that's all very well - but that doesn't make it any less of a bug; even once this bug has been fixed, there will continue to be users of previous builds on into the indefinite future who suffer from this rather disorienting behaviour. As for (3), you are partly right: I didn't realise your earlier message was about a different mode of operation to the one I could see. However, I'm still worried about how it is you're checking for compatibility: if you're testing the functions you want to use directly, fine; but if you're checking the User Agent string or similar, you're just asking for trouble...
- I'm sorry to be so negative about this - I appreciate you've worked hard trying to make it work, but I think that the current Wikipedia interface is very clean and consistent, and adding a colourful toolbar which in some cases will simply display information that could be given in an article anyway seems an unnecessary dilution of this.
- - IMSoP 22:06, 21 Jan 2004 (UTC)
Template tag
[edit]I think that it would be a good idea if we had a small icon to insert a template tag on the editing toolbar that would insert {{}} before and after the selected word, since templates are being widely used. -Dubaduba
- I would find that feature useful as well. Libcub 04:19, 25 February 2008 (UTC)
- I added this to my wiki, it is indeed a useful tool --24.192.88.157 04:05, 16 January 2009 (UTC)
Broken link
[edit]Link to http://angela.fused.org/bookmarklets.htm yields a 404 Page not found error. --68.62.126.118 11:53, 27 August 2005 (UTC)
How can we add feature to the Edit bar?
[edit]Do you known how can we add a button in the Edit bar??
- well? nice to have the toolbar... can we edit it? Or can there be a similar Edittools function in the same place? See, I am using the CharInsert extension with Edittools... is it possible to move this to the top of the "edit box" rather than at the bottom so it is easier to reach? --Ernye 12:31, 9 October 2006 (UTC)
- the toolbar is inserted by JavaScript and defined in the file includes/EditPage.php in the (array)variable named toolarray wich in turn sits in the function getEditToolbar(). Check the arrays that are already there and carefully add your own. "Carefully" because any omitted comma, ( or any non-escaped special character may break the file - so back up EditPage.php before you start. Mayby someone knows how to get the file used by en.wikipedia.org, so you can copy it. Borp 09:41, 11 January 2008 (UTC)
- this was my question as well, i'm glad that making my own buttons is so easy. The code for wikipedia's file is located lower in this page. I now have over 30 buttons on my wiki.24.192.88.157 15:56, 15 January 2009 (UTC)
- the toolbar is inserted by JavaScript and defined in the file includes/EditPage.php in the (array)variable named toolarray wich in turn sits in the function getEditToolbar(). Check the arrays that are already there and carefully add your own. "Carefully" because any omitted comma, ( or any non-escaped special character may break the file - so back up EditPage.php before you start. Mayby someone knows how to get the file used by en.wikipedia.org, so you can copy it. Borp 09:41, 11 January 2008 (UTC)
2006-04-17 change.
[edit]en:Wikipedia:Wikipedia_Signpost/2006-04-24/Technology_report.
Special character box on edit page
[edit]How do I get the special character box on my Media Wiki, or better yet, is there a help page on it? I've been looking for a while, and I can't find a help page on the special character box. My last resort was to copy the html... but I don't even know where the js function is. Could someone help me? By the way, I'm using media wiki 1.8.2. Hangfromthefloor 09:25, 17 December 2006 (UTC)
...never mind, I found MediaWiki:Edittools, but I still don't know how to use it. Also, can anyone give me suggestions for how to automatically change apostrophes and quotation marks in to smart ones? i.e. ' → ’ Hangfromthefloor 12:00, 17 December 2006 (UTC)
Wikipedia's Toolbar: 21 Items!
[edit]I love the Wikipedia toolbar and its 21 (!) items. How can I get a toolbar like the wikipedia's and how come there are only 11 items here on meta.wikimedia? --TheMightyHercules 03:53, 27 January 2007 (UTC)
- Yeah give it up please. It's no fair that WikiPedia gets all the good stuff! :) --Ikester 18:24, 9 February 2007 (UTC)
I tried to install the toolber as refered to on this page, but it tells meit is (far) too old for my Firefox 2.0 browser. WOuld it not be better to leave out the reference? JanEnEm 07:56, 1 May 2007 (UTC)
Anyone looking into this? I notice there hasn't been much talk here recently so maybe this comment will spark some interest...maybe? I have set up a wiki on my personal PC and its very nice but I'm still learning and I forget the wiki tags easily. It would be nice to be able to add buttons to the tool bar. 207.35.185.130 20:03, 24 August 2007 (UTC)
- the toolbar is inserted by JavaScript and defined in the file includes/EditPage.php in the (array)variable named toolarray wich in turn sits in the function getEditToolbar(). Check the arrays that are already there and carefully add your own. "Carefully" because any omitted comma, ( or any non-escaped special character may break the file - so back up EditPage.php before you start. Mayby someone knows how to get the file used by en.wikipedia.org, so you can copy it. Borp 09:43, 11 January 2008 (UTC)
- I found the code for Wikipedia's extra toolbar icons. Simply place this in your MediaWiki:common.js page:
/**/
/* Any JavaScript here will be loaded for all <s>users</s> on every page load. */
/** Extra toolbar options ******************************************************
*
* Description: UNDOCUMENTED
* Maintainers: [[User:MarkS]]?, [[User:Voice of All]], [[User:R. Koot]]
*/
//This is a modified copy of a script by User:MarkS for extra features added by User:Voice of All.
// This is based on the original code on Wikipedia:Tools/Editing tools
// To disable this script, add <code>mwCustomEditButtons = [];<code> to [[Special:Mypage/monobook.js]]
if (mwCustomEditButtons) {
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/c/c8/Button_redirect.png",
"speedTip": "Redirect",
"tagOpen": "#REDIRECT [[",
"tagClose": "]]",
"sampleText": "Insert text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/c/c9/Button_strike.png",
"speedTip": "Strike",
"tagOpen": "<s>",
"tagClose": "</s>",
"sampleText": "Strike-through text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/1/13/Button_enter.png",
"speedTip": "Line break",
"tagOpen": "<br />",
"tagClose": "",
"sampleText": ""};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/8/80/Button_upper_letter.png",
"speedTip": "Superscript",
"tagOpen": "<sup>",
"tagClose": "</sup>",
"sampleText": "Superscript text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/7/70/Button_lower_letter.png",
"speedTip": "Subscript",
"tagOpen": "<sub>",
"tagClose": "</sub>",
"sampleText": "Subscript text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/5/58/Button_small.png",
"speedTip": "Small",
"tagOpen": "<small>",
"tagClose": "</small>",
"sampleText": "Small Text"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/3/34/Button_hide_comment.png",
"speedTip": "Insert hidden Comment",
"tagOpen": "<!-- ",
"tagClose": " -->",
"sampleText": "Comment"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/f/fd/Button_blockquote.png",
"speedTip": "Insert block of quoted text",
"tagOpen": "<blockquote>\n",
"tagClose": "\n</blockquote>",
"sampleText": "Block quote"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/en/6/60/Button_insert_table.png",
"speedTip": "Insert a table",
"tagOpen": '{| class="wikitable"\n|-\n',
"tagClose": "\n|}",
"sampleText": "! header 1\n! header 2\n! header 3\n|-\n| row 1, cell 1\n| row 1, cell 2\n| row 1, cell 3\n|-\n| row 2, cell 1\n| row 2, cell 2\n| row 2, cell 3"};
mwCustomEditButtons[mwCustomEditButtons.length] = {
"imageFile": "http://upload.wikimedia.org/wikipedia/commons/7/79/Button_reflink.png",
"speedTip": "Insert a reference",
"tagOpen": "<ref>",
"tagClose": "</ref>",
"sampleText": "Insert footnote text here"};
}
/**/
- Don't forget the <nowiki> tags. Also, please be kind on Wikipedia's servers and change the location of the links to a local directory. :) 165.124.111.179 23:25, 20 February 2008 (UTC)
- The above did not work for me when I put it in my common.js script. Dang. But I modified it so it would fit easily into includes/EditPage.php as suggested above by Borp - thanks borp! Here are the extra buttons which can be easily inserted into that file's $toolarray variable, at about line # 1738. Also, as the original commenter said, make sure that only the LAST item of $toolarray does not have a comma after it's parentheses or a funky error message will stop your wiki ice cold!
- Also, note that you need to save the toolbar button image files from the wikipedia toolbar into your skins/common/images directory, as these images aren't normally installed there like the others. Just open up an edit page in wikipedia and right-click 'save image as', starting with redirect and going to the end.
array( 'image' => "Button_redirect.png",
'id' => "Button_redirect",
'tip' => "Redirect",
'open' => "#REDIRECT [[",
'close' => "]]",
'sample'=> "Insert text"
),
array( 'image' => "Button_strike.png",
'id' => "Button_strike",
'tip' => "Strike",
'open' => "<s>",
'close' => "</s>",
'sample'=> "Strike-through text"
),
array( 'image' => "Button_enter.png",
'id' => "Button_enter",
'tip' => "Line break",
'open' => "<br />",
'close' => "",
'sample'=> ""
),
array( 'image' => "Button_upper_letter.png",
'id' => "Button_upper_letter",
'tip' => "Superscript",
'open' => "<sup>",
'close' => "</sup>",
'sample'=> "Superscript text"
),
array( 'image' => "Button_lower_letter.png",
'id' => "Button_lower_letter",
'tip' => "Subscript",
'open' => "<sub>",
'close' => "</sub>",
'sample'=> "Subscript text"
),
array( 'image' => "Button_small.png",
'id' => "Button_small",
'tip' => "Small",
'open' => "<small>",
'close' => "</small>",
'sample'=> "Small Text"
),
array( 'image' => "Button_hide_comment.png",
'id' => "Button_hide_comment",
'tip' => "Insert hidden Comment",
'open' => "<!-- ",
'close' => " -->",
'sample'=> "Comment"
),
array( 'image' => "Button_blockquote.png",
'id' => "Button_blockquote",
'tip' => "Insert block of quoted text",
'open' => "<blockquote>\\n",
'close' => "\\n</blockquote>",
'sample'=> "Block quote"
),
array( 'image' => "Button_insert_table.png",
'id' => "Button_insert_table",
'tip' => "Insert a table",
'open' => '{| class="wikitable"\\n|-\\n',
'close' => "\\n|}",
'sample'=> "! header 1\n! header 2\n! header 3\n|-\n| row 1, cell 1\n| row 1, cell 2\n| row 1, cell 3\n|-\n| row 2, cell 1\n| row 2, cell 2\n| row 2, cell 3"
),
array( 'image' => "Button_reflink.png",
'id' => "Button_reflink",
'tip' => "Insert a reference",
'open' => "<ref>",
'close' => "</ref>",
'sample'=> "Insert footnote text here"
)
extraedittoolbar for MediaWiki
[edit]Would any one please be so kind to adjust MarkS/extraedittoolbar.js [1] so that we can use it for MediaWiki? Thank you.--72.197.33.182 23:27, 2 February 2007 (UTC)
- Well there is instructions for Installing XEB on your own Wiki, but creating a user 'MarkS' seems like a bit of a fudge. -- Harry Wood 13:24, 26 November 2007 (UTC)
New Toolbar
[edit]How do I get the new toolbar and new features from wikipedia to my personal wiki?
I like the new toolbar; but I can't seem to figure out how to make it work, and also the beta "show preview".
- being a MediaWiki novice myself, this took some time to figure out. Apparently, Wikipedia and sites that are part of the WMF use the extension Extension:WikiEditor to add this toolbar. However, I currently use MediaWiki version 1.16, and in this version, you need to add the whole UsabilityInitiative extension. The installation instructions for WikiEditor should explain this. --Mrusso 17:38, 11 April 2011 (UTC)
- Thanks a lot, I have been searching for that info quite some time now, as well. --Kebap 10:08, 18 May 2011 (UTC)
--Xunihuasheji (talk) 19:50, 4 May 2016 (UTC)Ĵ== mediawiki.org ==
Shouldn't this be moved to mediawiki.org? BlittleMcNilsen (talk) 07:18, 6 May 2012 (UTC)