The preferred place to discuss issues and ask for support is on github. Please consider using it, thanks! --Thai (talk) 06:26, 28 April 2018 (UTC)Reply

Help with custom CSS extension


Hi I am not sure how to use a custom CSS extension as described at

I have done the following:

  1. Create MYEXTENSION directory under extensions/ folder
  2. Added extension.json file in MYEXTENSION directory, with following content:
$wgResourceModules['x.MYEXTENSION.styles'] = array(
'styles' => array(
'screen.css' => array( 'media' => 'screen' )
 'localBasePath' => __DIR__,
 'remoteExtPath' => 'MYEXTENSION',

$wgTweekiSkinCustomCSS[] = 'x.MYEXTENSION.styles';
  1. create screen.css file in MYEXTENSION directory (I assumed that's what the screen.css refers to in the code in extension.json file?)
  2. Tried adding the following to LocalSettings.php: (Adding this line breaks the wiki completely and it doesn't even load anymore, so probably not right)
wgLoadExtension( 'MYEXTENSION' );

I would then want to add my custom css in the screen.css file and have it change the styling of the wiki... What am I doing wrong?

Any help is appreciated :)

--sonjabrits (talk) 15:30, 20 January 2018 (UTC)Reply

Hi Sonja. Sorry for the confusing description in Tweeki's documentation. It was referring to the old way of doing things (before we used extension.json). I updated it but I fear it's still not detailed enough if you don't have much experience with writing your own extensions. Therefore I would recommend you to simply use MediaWiki:Common.css, it's the easiest way to add custom CSS.
Hope this helps! --Thai (talk) 09:23, 1 February 2018 (UTC)Reply

not compatible with Extenions:HeaderTabs


Unfortunatly there is a bug when using this skin and headertabs together. The tabs are created but the text (heading) of the tabs are missing. Could this be fixed? Thanks! --M art in (talk) 14:57, 4 July 2016 (UTC)Reply

I've got some idea what the problem could be but not the resources to fix this in the near future. I would gladly accept any patches, however. Meanwhile, you can use Bootstrap's Togglable Tabs. See the documentation to see how to do it. --Thai (talk) 21:08, 7 September 2016 (UTC)Reply

blanks the wiki


Hi Tried installing the skin, but upon adding the require inside Local Settings it blanks the wiki.

Hi. The problem could have been due to the typo in the git command (see below). Could you try out if it works after renaming the skin folder from tweeki to Tweeki? If not, could you try adding the following two lines to LocalSettings.php (before requiring Tweeki):
error_reporting( E_ALL ); 
ini_set( 'display_errors', 1 );
You should then see some error message instead of only a blank page. Could you please post it's content?
Thanks! --Thai (talk) 11:08, 25 March 2016 (UTC)Reply

Typo in git command


Nice skin I am playing with it and while a tad lost at first it has some nice features. Thanks.

I think you made a typo in your git command.

git clone tweeki

The rest of your info calls for it to be in Tweeki so think you meant.

git clone Tweeki

I may of missed something but without that it causes quirks it seems. Pisnaz (talk) 03:33, 22 March 2016 (UTC)Reply

Thanks for the hint, you're perfectly right. I had the correct link on the project page and on github but had forgotten to change it here... --Thai (talk) 11:00, 25 March 2016 (UTC)Reply

Having trouble with latest mediawiki version 1.27


I am trying install and use this skin but it doesn't work with mediawiki version 1.27. Images are not showing up and internal links are broken... Could it be updated for the mediawiki version 1.27? Jisookmeister (talk) 16:23, 9 August 2016 (UTC)Reply

Hi, I'm using Tweeki with MW 1.27, it should be working now. Please report back, if there are still problems... Thanks, --Thai (talk) 21:01, 7 September 2016 (UTC)Reply

Revision History


For the life of me, I can't figure out how to get to the page's revision history within the UI. I had to work around that and edit the page and change the URL from action=edit to action=history. What am I missing??

Finalfenix (talk) 02:19, 7 August 2017 (UTC)Reply

Some of MediaWiki's advanced features are hidden by default in order not to overwhelm users. Tweeki's default scenario is that of wiki-as-a-website with only some advanced users. You can of course easily change that and you have several options:
  • If it's important that you can access the history but not the other users go to your preferences and check “Show advanced features” under “Appearance”. The default “edit” button will then turn into a dropdown that contains a selection of the most important “views” and “actions”. See also the description of EDIT-EXT in Navigational Elements' documentation.
  • You can make the dropdown visible either by changing the preference's default value for your users or changing the default configuration option that reduces EDIT-EXT to EDIT for non-advanced users. You can do so by adding the following to LocalSettings.php or your extension: $wgTweekiSkinHideNonAdvanced['EDIT-EXT-special'] = false;
  • The history is part of the „views“, so you can add the VIEWS navigational element to any navigational section.
--Thai (talk) 09:43, 7 August 2017 (UTC)Reply

Is there a way I can show EDIT-EXT to all logged in users?
Finalfenix (talk) 08:12, 16 August 2017 (UTC)Reply

Yes, you can hide it for anonymous users. So you'll have to make it visible to non-advanced users with the line above and additionally add this: $wgTweekiSkinHideAnon['EDIT-EXT-special'] = true;
--Thai (talk) 10:45, 16 August 2017 (UTC)Reply

interferences with other skins


I've set tweeki as my wiki's default skin, but now "edit source" don't show up anymore on sections with other skins… (which is a shame as most of my users use vector) --Loizbec (talk) 11:26, 12 September 2017 (UTC)Reply

Should've been fixed in the latest development version. Please confirm. Thanks! --Thai (talk) 13:19, 20 September 2017 (UTC)Reply
Still not working for me. Edit source is not there. --LiaVeja (talk) 13:45, 9 November 2017 (UTC)Reply
Could you provide some screenshots or is your wiki publicly available so that I could have a look at it? --Thai (talk) 17:34, 9 November 2017 (UTC)Reply

Tweeki as a website (layout)


Thank you so much for this brilliant theme and idea. I want to use the theme in a "as a web site" scenario, and I wonder what would you recommend in order to add layout, columns on a per page basis. I.e. what would the code be to display a site like your home page (text box background colour, rows with different number of columns and icons with different size text next or below).--Spiros71 (talk) 09:52, 15 October 2017 (UTC)Reply

The documentation is a read-only Wiki, but you can always inspect the source code by appending &action=edit to the URL like this. For rows, columns, and all the other styling features you should have a look at Bootstrap's documentation. Hope this helps, --Thai (talk) 15:12, 15 October 2017 (UTC)Reply

Content not showing as expected



I have a fresh local SWM installation and enabled Tweeki. The topbar is much higher now than on my private online site, and the text "Navigation menu" is showing on the upper left corner with quite big font. The hight is twice the size as this:

Any ideas?

Regards, Pål

Hi. Thanks for the report. Could you provide some screenshots? You could use github's issue tracker here to upload your images... What version of MW are you using? And what is the language of your installation? --Thai (talk) 13:22, 16 February 2018 (UTC)Reply
It's exactly the same as the open issue on github (#98).. I will update my issue there.
Regards, Pål

Hello, I tried to add a BS carousel to an article on my wiki, but it seems not to work. For reference, I just tried copy-pasting the example from the W3C tutorial onto one of the pages on my wiki to play around with it. I am still quite new to BS and CSS, but would you be able to point me in the direction of how to add one? I know there are some carousel classes included in the Tweeki Bootstrap CSS file, but it seems like there are some classes missing. Any help would be appreciated! TIA Lucidlywisely (talk) 07:49, 2 March 2018 (UTC)Reply

Hi. I'm sorry, but carousels are currently not supported by Tweeki. I never needed it and so never felt the urge to implement the style fixes (the classes are not missing it's just that MediaWiki's classes with higher specificity mix things up). Besides styles it probably also needs some code to be rewritten as carousel's javascript relies on specific attributes. I will happily accept any working patches but I won't have the resources to implement this myself in the near future – and to be honest I'm not a big fan of slideshows. Others advise against using it, too ;) Also, they raise issues in terms of accessibility. --Thai (talk) 11:50, 3 March 2018 (UTC)Reply
Bmulckhu provided the necessary css fixes and also started to write some documentation on how to use it. Carousels should probably work now, please help testing it. --Thai (talk) 18:27, 8 June 2018 (UTC)Reply

Long TOC and showing the category


Hello! I hope this is the correct place to share these two questions, as I am not familiar with github. I have been using Tweeki and found that it looks great, thank you!, and have two little questions about it: (1) when there are many first-level headings, the TOC at the sidebar only shows down to the a few, is there a way to make it so that the TOC is also scrolled up when there's, say, 20+ headings to be shown. I guess it involves touching the php code here and there, just some guidance would be greatly appreciated! (2) How can I show the categories of every page? I navigate using category pages a lot, I would love to have the link visible somewhere. Thank you so much for your work!!! Houjou (talk) 15:45, 13 March 2018 (UTC)Reply

Hi. Happy to hear, that you like the skin. (1) I see several possibilities for you here. If you want it fancy, that is, if the TOC should always stay in sight but slowly scroll down as you approach the end of the page, you'll have to write your own javascript. This would be rather advanced. One easy solution is to “unfix” the sidebar(s) with this simple line of CSS that you can put into MediaWiki:Common.css:
.sidebar-wrapper { position:absolute }
The sidebar would then move together with the rest of the page. A third possibility – the one I would prefer – would be to group them so that you only have a handful of first-level headings and a number of subheadings that will only be shown in the TOC for the section currently in view.
(2) The categories are only hidden via CSS. You can make them visible with this line:
#catlinks { display:block }
Good luck, --Thai (talk) 20:44, 13 March 2018 (UTC)Reply
Thank you so much for your quick and useful reply! (1) Until I am confident enough to prepare my own js for this, I'll keep the sidebar non-absolute and see if I can reorganize the headings of the affected long articles. (2) Yes! Thanks!!! --Houjou (talk) 15:36, 15 March 2018 (UTC)Reply
For anyone getting issues using position:absolute with mobile sized screens (for me the sidebar and logo would overlap the rest of the page instead of moving to the bottom), you can use something like the following to use absolute position only if the screen has space for it:
@media only screen and (min-width: 600px) { .sidebar-wrapper { position:absolute } }
--Yochie92 (talk) 14:09, 5 May 2021 (UTC)Reply

No button to "Cancel" when using VisualEditor


Hello Thai! I'm using Tweeki on several websites and I find it's very flexible and it's looking great! Only recently I tried using Tweeki in combination with VisualEditor, which seems to work quite seamless... with one exception! When editing a page with VE there is no "Cancel" button! There's only some impractical workarounds, like clicking page-back on my browser or switching to the conventional editor for cancelling... Not nice!! Would there be some way to include a "Cancel" button in the navigational menu's? Cancelling would actually be a link to the standard page in read-modus! Bmulckhu (talk) 15:50, 19 April 2018 (UTC).Reply

Hi. If I understand it correctly the missing “Cancel” button is not specific for Tweeki, right? But in Vector you have the “Read” tab to return to the page. You can of course add a “Cancel“ link to the navigation (e.g. with {{FULLPAGENAME}}|Cancel). VisualEditor loads dynamically and adds classes to the html tag, so you could use these to show/hide the button. In order to do so you should add a custom class to the link (e.g. {{FULLPAGENAME}}|Cancel|customclass). Then you could add the follow CSS (in MediaWiki:Common.css or in your own extension):
.customclass { display:hide; }
.customclass { display:none; }
.ve-active .customclass { display:block; }
--Thai (talk) 20:07, 19 April 2018 (UTC)Reply
Hi! Thanks for your reply. This is exactly what I meant.
1- The proposed solution would be nice. There is an issue with the proposed CSS, though. I added the CSS to MediaWiki:Tweeki.css, but the Cancel-link is not hidden when not editing. It is always there. I did inspect with Google dev-tools and the customclass is assigned correctly to the link: <a href="/w/index.php?title=Pagename" active="1" id="n-.7B.7BFULLPAGENAME.7D.7D" class="customclass">Cancel</a>. What's going wrong?
2- Would it also be possible to add the Cancel-link to the actions in the dropdown from the EDIT-EXT?
3- Or even better - since the Edit-button is actually dysfunctional when editing - would it be possible to change the Edit-button into a cancel button?
Bmulckhu (talk) 21:11, 19 April 2018 (UTC).Reply
1 - sorry, you're right. It's a question of specificity. Bootstrap's .nav > li > a overrules .customclass. So .nav > li > a.customclass and .ve-active .nav > li > a.customclass should work as selectors.
2 - that is possible but it requires some PHP skills. You can use $wgTweekiSkinSpecialElements to override EDIT-EXT or create your own special navigational element. There you can customize the dropdown in the way you prefer it and add the classes that you need in order to show and hide elements depending on the state of VE.
3 - it's possible that you can achieve this with CSS if you play around long enough but I guess it will be easier with the solution from 2.
Good luck, --Thai (talk) 05:59, 20 April 2018 (UTC)Reply
Hi & thanks again for your extensive reply. I'll stick with the the first option for now, and try to figure out the second some time later.
The selectors you proposed are not working though (I did clear the cache). I did put the Cancel-link in the right sidebar; would that make a difference for the .nav part of the selector? Bmulckhu (talk) 22:52, 20 April 2018 (UTC).Reply
I was typing to fast the other day. It should read display:none; instead of display:hide;. If you put the link in the sidebar there should be no need to override Bootstrap CSS rules of higher specificity. --Thai (talk) 18:31, 22 April 2018 (UTC)Reply
Okay, I realize that probably I'm starting to get annoying now... :-) . And it's true: I should have been able to find the display:none; issue myself. But.... it is still not working !?!? Same issue - the selector doesn't make the Cancel-link disappear... I googled and fiddled but can't get it working right. Bmulckhu (talk) 07:26, 24 April 2018 (UTC).Reply
That's weird. Your wiki is not public, by any chance? Could you post the contents of your MediaWiki:Tweeki.css and your MediaWiki:Tweeki-sidebar-right? I just tested it (without VE installed) – hiding the link works like a charm… If you inspect the applied styles with dev-tools---does the style for .customclass get applied? And what's the rule that overrides it? --Thai (talk) 07:59, 24 April 2018 (UTC)Reply
Yes, weird indeed. The wiki is public now: please find tweeki.css here. The customclass I'm using is ve-annuleren-link. You can find the css in MediaWiki:Tweeki.css (link above). The "Annuleren"-link (Cancel-link) is visible here f.e. Bmulckhu (talk) 17:23, 24 April 2018 (UTC).Reply
Thanks for your perseverance. Again, I wasn't exact enough in my answer above. If you put the link in the sidebar and not in the navigation there's not only no need to use the specific selector it's also harmful. If you use only .ve-annuleren-link and .ve-active .ve-annuleren-link as selectors it should work, I hope. Good luck, --Thai (talk) 18:11, 24 April 2018 (UTC)Reply
Uhm... please don't kill the messenger... : this isn't working either! I also tried a few variants with and tried to add !important, but none of those worked. Bmulckhu (talk) 19:10, 24 April 2018 (UTC).Reply
Interesting in just how many ways it can go wrong – I found another possible culprit and I'm curious what will happen next ;) You accidentally commented out your carefully crafted rules, that might be the problem... Nice work, that you're doing there, btw. --Thai (talk) 20:21, 24 April 2018 (UTC)Reply
Ok... my bad: the last one did it! Just for clarification: the working solution is:
.ve-annuleren-link {display:none;}
.ve-active .ve-annuleren-link {display:block;}
Thanks a million for your patience and support (and your compliments for the work)! Bmulckhu (talk) 21:06, 24 April 2018 (UTC).Reply
Hi! I recently found the "annuleren"-link in the right sidebar on the page Speciaal:Voorkeuren ("Special:Preferences"). This is quite confusing, since this page does not use editing at all. I tried to hide it in several ways, but wasn't able to get rid of it. Here are some examples of lines that i put in MediaWiki:Tweeki.css (in addition to the lines above), but none of them did have any effect...:
.ve-active .rootpage-Speciaal_Voorkeuren .ve-annuleren-link { display:none!important; }
a[href*='Speciaal:Voorkeuren'] .ve-annuleren-link {display:none!important;}
.rootpage-Speciaal_Voorkeuren .ve-annuleren-link { display:none!important; }
What am I doing wrong??? Bmulckhu (talk) 10:53, 29 April 2018 (UTC).Reply
Site CSS customizations are disabled by default on Special:UserLogin and Special:Preferences for security reasons (see the manual). You can change this behaviour using $wgAllowSiteCSSOnRestrictedPages or put your CSS in an extension. --Thai (talk) 12:02, 29 April 2018 (UTC)Reply
Ok, this is the final edit on this subject from my side... Adding the (standard CSS) class hidden to the link in mediawiki:tweeki-sidebar-right (the full link there is now: {{FULLPAGENAME}}|Annuleren|ve-annuleren-link hidden) and changing the custom CSS to:
.ve-annuleren-link {display:none;}
.ve-active .ve-annuleren-link {display:block!important;}
circumvents the issue that the "cancel"-link ("annuleren") gets displayed on Login and Preference pages (without the need for an extension). Actually the first line in custom-CSS is superfluous as well... Bmulckhu (talk) 17:40, 2 May 2018 (UTC).Reply

Changing “Edit section links” when using VisualEditor


Normally (in case you’re not using VisualEditor) when hovering a section title Tweeki will neatly show an “edit section” link with the label “source” (nl: “brontekst”) and a pencil glyph. The label is linking to editing the section with the conventional editor. When using VisualEditor there are three links that show up behind the section title, separated by “pipes”:

  1. Just the pencil glyph, linked to editing the page (not the section!) with VE. class=“tw-editsection-onhover mw-editsection-visualeditor”
  2. Just the tekst “edit source” (nl: “brontekst bewerken”), linking to editing the section with VE. class=“tw-editsection-onhover”
  3. The tekst “source” (nl: “brontekst”) and the pencil glyph, linking to editing the section with the conventional editor. class=“tw-editsection-onhover”
  4. Also the pipes are always visible, even when not hovering the section title. Class=“mw-editsection-divider”

Dev-tools also shows a container span (class=“mw-editsection”) and square brackets spans (which are hidden anyway, class=“mw-editsection-bracket”).

Finally my questions:

  1. How can the first pencil glyph be removed (including dividing pipe)?
  2. How can the second text be adapted to “edit with Visual Editor” (“bewerken met Visual Editor” or a plain “bewerken”)?
  3. How can the third text be adapted to “edit source” (“bewerken bron”)?
  4. How can the dividers (pipes) be hidden when not hovering the section title?

I’m aware of the manual (, but couldn’t find out how to get it working as described.

You should have a look at the SkinEditSectionLinks hook. Either you disable Tweeki's handling (setting $wgTweekiSkinCustomEditSectionLink to false) and implement what you would like to have in your own extension or you could also provide patches for Tweeki. They would be warmly welcome. Have a look at these lines if you want to go down that road. (I just updated Tweeki, btw, because it had used the deprecated DoEditSectionLink hook.) --Thai (talk) 14:30, 26 April 2018 (UTC)Reply
Hi! I understand what you're saying, but my PHP-programming skills are (very) limited (i.e. non-existent). It took me an age to figure out a work-around in CSS and I will publish it here soon. I'm a fan and I would really like to contribute to Tweeki, but it won't be on the coding part, I'm afraid! I could add one or two examples though, to your "how-to" documentation, if you'd appreciate it? Bmulckhu (talk) 15:55, 27 April 2018 (UTC).Reply
Any contributions are very welcome and with the documentation there's definitely room for improvement ;) Would you prefer to just send me your examples or would you rather get your own account for the documentation wiki? Just drop me a line. --Thai (talk) 06:31, 28 April 2018 (UTC)Reply
Hi, this is not so much a "solution" as a "work around" for the issues above. The simplest work around, of course, is to suppress the link, but this work around aims to end up with an "edit" link and an "edit-icon" separated by a dividing "pipe". This work around also works when Visual Editor is disabled for a user (then just a glyphicon is being displayed).
1a & 4- Hiding the dividers (and brackets) in the "edit-section" link in case the section title is not being "hovered" by the mouse:
/* Divider hidden */

h1 > .mw-editsection >,
h2 > .mw-editsection >,
h3 > .mw-editsection >,
h4 > .mw-editsection >,
h5 > .mw-editsection >,
h6 > .mw-editsection > {display:none;}

h1:hover > .mw-editsection > span:nth-last-of-type(2),
h2:hover > .mw-editsection > span:nth-last-of-type(2),
h3:hover > .mw-editsection > span:nth-last-of-type(2),
h4:hover > .mw-editsection > span:nth-last-of-type(2),
h5:hover > .mw-editsection > span:nth-last-of-type(2),
h6:hover > .mw-editsection > span:nth-last-of-type(2) {display:inline;}
.mw-editsection-bracket {display:none!important; }
1b - Removing the the first link in section-edit and the pipe (divider) following this link:
/* Remove the first link and following divider */
.mw-editsection-visualeditor > span.glyphicon {display:none;}
.mw-editsection-visualeditor + {display:none;}
2 - Change the text in MediaWiki:Visualeditor-ca-editsource-section into the general "edit" (or any other text you'd prefer).
3 - Optionally, change the icon in MediaWiki:Tweeki-editsection-icon into glyphicon-edit to make it look different from the standard "glyphicon-pencil"
Better or smarter solutions (workarounds) are always welcome! Bmulckhu (talk) 09:07, 29 April 2018 (UTC).Reply

Grid not working!


Had a long issue about the grid not working, and finally realized I'd forgotten to set container-fluid! All fixed. Many thanks for all the work you've done on this terrific skin, BTW!

Glad to hear that you could make it work and that you like the skin! --Thai (talk) 21:17, 23 June 2018 (UTC)Reply

I've been having great fun working with the skin, but I'm stumped on a point:

The Recent Changes option from the Interaction section of the sidebar on standard wikis is something I and many users miss. I know how to just add a 'Recent Changes' link to the navbar, but is there some way to place it into the TOOLBOX? That seems an ideal way to keep things compact.


--Balerion300 (talk) 14:29, 24 June 2018 (UTC)Reply

I've added the new navigational element TOOLBOX-EXT that should do what you want.
Btw, you could always use $wgTweekiSkinNavigationalElements to overwrite the handling for TOOLBOX or any other navigational element like so:
$wgTweekiSkinNavigationalElements['TOOLBOX'] = 'myToolbox';

function myToolbox( $skin ) {
  /* copy the code from and modify it according to your needs */
--Thai (talk) 18:30, 29 June 2018 (UTC)Reply

Thank you!

--Balerion300 (talk) 19:00, 29 June 2018 (UTC)Reply

Two Probs.

  1. My biggest problem is that my first line in a section -- a double return gets displayed with only a few pixels of vertical space -- but all subsequent double-returns works fine. I can fake it in the first line with <br /><br /> but then I have to do that for all the other lines in that section. I can't figure out how to fix that.
  2. A lesser problem is that I downloaded the latest using the directions and it just doesn't work on my install. Since I made a copy of the older one, I just switch back. I can't figure out how to find a version of the skin from an install to communicate what the versions are.


Hi. I'm not sure if I do understand you correctly, but here are some hints that might help:
  1. Note that paragraphs (blocks of text seperated by a double return) are interpreted as html paragraphs, that means they are packed into <p></p> tags by MediaWiki's parser. The space between the paragraphs or between a heading and a paragraph is controlled via CSS. But maybe your problem is a different one, because in the default setup the .margin-bottom property is set to 10 pixels for headings and paragraphs alike. Could you provide a screenshot of what you're talking about?
  2. That sounds not so good and it would help if you could provide some additional information on error messages and on your setup. You can go to Special:Version on your wiki to find out what versions of MediaWiki, PHP, mysql and Tweeki you're running.
Thanks! --Thai (talk) 14:41, 3 November 2018 (UTC)Reply
As a sidenote: Please sign your contributions by adding the following code at the end: --~~~~. Upon saving it gets translated to something like this: --Thai (talk) 14:41, 3 November 2018 (UTC)Reply

Thanks for your help. I added a couple of screen shots

  • [1] this source you'll notice there's a double link break in the source between sentences.
  • [2] this is the display -- the first line shows as a single breaks, the second line double-breaks -- but in the source, they're both double-breaks. (Missing whitespace). The line "I can tell you,..." should be an extra line down.

For item 2, I can't use Special:Version on the latest because if I use the newer Tweeki I just get all white display / nothing. If I use the original it says "1.0.4 (a8b5154) 03:09, 21 February 2018". I have both older and newer versions in different folders, and I just rename /tweekiOLD (or NEW), to /tweeki to activate/deactivate. The old one works, the new one just is blank. -- 21:17, 3 November 2018 (UTC)Reply

Compatibility with MW 1.28



I am getting the following error on trying to get Tweeki working:

Uncaught exception 'Exception' with message 'Tweeki is not compatible with the current MediaWiki core (version 1.28.2), it requires: >= 1.29.0.' . I saw in the threads here that it has worked with v1.27 as well, so why this error? Is there a workaround?

the exception is thrown because of a requirement definition in skin.json that was put there because Tweeki's latest code uses features introduced in MW 1.29. You can try using an old version of Tweeki (e.g. v1.0.5) if you're bound to MW 1.28. --Thai (talk) 18:08, 17 February 2019 (UTC)Reply

Using parser founctions in subnav



Is is posssible to use parser functions in Tweeki-subnav (or others navigantion elements). something like Template:Ifeq: Tweeki

Regards JMU

Hi. One way to achieve what you want, is to define your own navigational elements for which you can use whatever logic you like (see the documentation). Another (limited) possibility is to use the {{#tweekihide}} parser function to hide elements from specific pages. Your idea is interesting, I opened an issue on github for a {{#tweekinav}} parser function that allow overwriting the content of navigational sections. --Thai (talk) 20:44, 17 December 2019 (UTC)Reply

Thank you.

toc fixed or maybe overflowed?


it would be great to have the toc on the left or right side (maybe in a sidebar?), just like for example mkdocs-material or dokuwiki's bootstrap-template(demo), where the table of content sits on the right and also sticks when scrolling down.

The advantage is that you can always see where you are in a longer article and also can jump between the headings quickly.

Hi. The toc actually should be fixed in the right sidebar and it should be using Bootstrap's scrollspy feature. Have you had a look at Tweeki's documentation? --Thai (talk) 22:59, 5 April 2020 (UTC)Reply

The example site with how-to's is down, pls provide how-to's on the extension page


Just as the title says, the example site that explains how to use the extension is down, can you please provide how-to's on how to use/configure the theme on the extension page to help us to use it (and prevent this in future)? Many thanks! :)

Both the link provided on Github ( is down and the example site with all the config instructions ( is down. All the help info referrs to those. Pls provide backup. :<

TiltedCerebellum (talk) 21:54, 4 April 2020 (UTC)Reply

I'm very sorry the server is temporarily down from time to time. I plan to migrate to a new server within the next few months. --Thai (talk) 23:03, 5 April 2020 (UTC)Reply

Flyout sidebar



Can you provide an example of a flyout sidebar ?

Regards JMU

Hi. Could you explain in more detail what exactly you would like to achieve? In general, if you want to change the layout of the page you would have to implement your own Page Renderer function using the $wgTweekiSkinPageRenderer configuration option. --Thai (talk) 09:01, 13 May 2020 (UTC)Reply

Hello, I would like something like in Bluespice, a left or right sidebar that can expand or collapse using an icon button. I am not a developper.


This is currently not provided out of the box, you would have to implement it yourself. --Thai (talk) 13:54, 13 May 2020 (UTC)Reply

Bootstrap version 4



Is it possible to implent support for bootstrap 4? If so, how? Thanks!

Hi. Support for Bootstrap 4 is in development and will be published soon. If you can't wait you can checkout Tweeki's development branch. Bootstrap 4 will be opt in, so to enable it add $wgTweekiSkinUseBootstrap4 = true; in your LocalSettings.php. --Thai (talk) 22:40, 4 October 2020 (UTC)Reply

Missing Mediawiki release tags


Hi Everyone,

I hope this is not too petty. Most Mediawiki extensions and skins follow Mediawiki conventions and provide well known branches. For example, REL1_31, REL1_32, ..., REL1_35.

When I attempt to update Tweeki using this script, Tweeki causes an error due to the missing branches:

Updating /var/www/html/w/skins/Tweeki/
HEAD is now at 230972f run hooks only if tweeki is actually used
Already up-to-date.
error: pathspec 'REL1_34' did not match any file(s) known to git.

Here's the code that performs the update:


for dir in $(find "$WIKI_DIR/skins" -name '.git' 2>/dev/null);
    cd "$dir/.."
    echo "Updating ${dir::-4}"
    git reset --hard HEAD && git pull && \
    git checkout -f "$WIKI_REL" && git pull

It would be nice if Tweeki tagged its releases.

Here is what running the script usually looks like.

Updating /var/www/html/w/skins/Gamepress/
HEAD is now at 33048fd Localisation updates from
Already up-to-date.
Already on 'REL1_34'
Already up-to-date.

Noloader (talk) 18:39, 13 December 2020 (UTC)Reply

Hi. Thanks for reporting this. The branches REL1_3136 are now available. --Thai (talk) 19:26, 3 January 2021 (UTC)Reply

Categories in Sidebar?


Is there a way to add page categories as a vertical list on either sidebar, rather than the page ending horizontal bar? Having a little difficulty making it happen. Thanks. :)

There's currently no easy way to do it. If you're fluent with javascript you could just move #catlinks ul to the sidebar, add some class and style it as you like. --Thai (talk) 19:56, 10 March 2021 (UTC)Reply
I've come up with two methods
Method 1: places at bottom of sidebar
In Mediawiki:Commons.js
var one = document.querySelector("#sidebar-right");
var children = document.querySelector(".catlinks").children;, function (child) {
Method 2: place anywhere in sidebar
In Mediawiki:Commons.js
var one = document.querySelector(".catlist");
var children = document.querySelector(".catlinks").children;, function (child) {
In LocalSettings.php
$wgTweekiSkinSpecialElements['CATS'] = 'cats';

function cats( $skin, $content ) {
   echo '<div class="catlist"></div>';
In MediaWiki:Tweeki-sidebar-right or what ever bar you use add 'CATS' in the order you want
ZyMOS (talk) 22:08, 27 October 2021 (UTC)Reply

Deprecated: Use of BaseTemplate::getToolbox was deprecated in MediaWiki 1.35


Hi Everyone,

We recently updated to Mediawiki 1.36. I'm testing some of our installed skins under it.

Use of Tweeki is causing this warning to be printed on the top of each page:

Deprecated: Use of BaseTemplate::getToolbox was deprecated in MediaWiki 1.35. [Called from TweekiTemplate::renderNavigation in /var/www/html/w/skins/Tweeki/includes/TweekiTemplate.php at line 405] in /var/www/html/w/includes/debug/MWDebug.php on line 376

and this warning to be printed on the bottom of each page:

Deprecated: Use of BaseTemplate::getFooterIcons was deprecated in MediaWiki 1.35. [Called from TweekiTemplate::renderStandardFooter in /var/www/html/w/skins/Tweeki/includes/TweekiTemplate.php at line 1414] in /var/www/html/w/includes/debug/MWDebug.php on line 376

I have no idea why we are running debug code on a production server. I guess that's a separate issue for the Mediawiki folks.

My apologies if this is not a Tweeki issue.

Our mediawiki information can be found here.

Thanks for reporting! Should be fixed in the latest version on github. --Thai (talk) 16:43, 3 June 2021 (UTC)Reply

Admittedly I am a bit lost when looking at the respective instructions. What I would like to do is add a link directly above "Powered by MediaWiki" and "Powered by Semantic MediaWiki" called e.g. "Funded by Whatever Foundation". From the docu I get that $wgTweekiSkinHideLoggedin['footer-custom'] = false; should be added to "LocalSettings.php", however after doing so and adding "|Funded by Whatever Foundation" to page "MediaWiki:MediaWiki:Tweeki-footer-custom" nothing changed. Should I still add $wgFooterIcons for this to work? Hmm ... Any advice appreciated. [[kgh]] (talk) 22:06, 24 June 2021 (UTC)Reply

Ah, it looks like you have to edit the system message "MediaWiki:Tweeki-footer". And you need to log out since it is for anons only. :) Good, it is working. [[kgh]] (talk) 10:00, 25 June 2021 (UTC)Reply

Linking edit button to forms when using Page Forms and Tweeki


We encountered an issue as described on GitHub. If someone else is running into this issue it will be great if you could share your findings or at least note that it is happening for you, too. [[kgh]] (talk) 10:37, 3 March 2023 (UTC)Reply

Return to "Tweeki" page.