Jump to content

Jack Phoenix

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jack Phoenix's Achievements


Newbie (1/14)

  • First Post
  • Reacting Well Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges



  1. The solution depends on your specific requirements (e.g. does it need to work without JavaScript?), but you might be interested in the MonobookSidebar JavaScript (live example on Halopedia), which is used to implement a nested navigation menu on the MonoBook skin, similar to the menu found in the Monaco and Nimbus skins. The source code, including the menu items' definitions, can be found on Halopedia's MediaWiki:Monobook.js page and the styles are naturally found on the MediaWiki:Monobook.css page (look for the comment "/*** Monobook Sidebar ***/"). The gradient image that the CSS code refers to can be found at https://www.halopedia.org/images/menu_gradient.png . Note that the CSS assumes that your local MediaWiki:Sidebar page follows a format similar to Halopedia's, including the word "Navigation" being written with an uppercase N. If and presumably when this is not the case for your wiki, you'll need to tweak the CSS as appropriate.
  2. As the error message says, you should use the variable called $wgLocalInterwikis (plural) instead of $wgLocalInterwiki (singular). You will most likely find the offending line of code in your wiki's settings file, LocalSettings.php. Additionally, if and when you're seeing that (and/or similar notices) on top of your pages, you should verify that your LocalSettings.php file does not contain a line like ini_set( 'display_errors', 1 ); or ini_set( 'display_errors', true ); anywhere. That's what is enabling the displaying of PHP notices, warnings, errors, etc. and it is not recommended to show such messages on a production environment for a variety of reasons.
  3. Your site appears to be serving a white page on the specified URL (and the root domain serves a Fedora test page indicating that the server is successfully running Apache), so I can't comment on your specific case, but as a general rule: yes, it's CSS. As for what rules you need and where they are located depends on a few things. Most wikis will have the infobox CSS rules in the on-wiki page called MediaWiki:Common.css for CSS rules placed there will be applied to all skins. For the Swedish Wikipedia, that page can be found at https://sv.wikipedia.org/wiki/MediaWiki:Common.css although it seems to lack the styles we're looking for. Another possible place for the rules to be is the skin-specific MediaWiki:<skinname>.css wiki page; as of now (late 2018) the skin used by default on all Wikimedia sites (Wikipedia, Wiktionary, Wikiquotes, MediaWiki.org, etc.) is called "Vector", so maybe we'll find the styles on MediaWiki:Vector.css: https://sv.wikipedia.org/wiki/MediaWiki:Vector.css ...nope, that's empty too, dang. Wikipedia and other Wikimedia Foundation operated wikis (the aforementioned Wiktionary & friends) are somewhat special in that many of them implement infobox CSS via the Gadgets extension. This does not mean that you would need to install the Gadgets extension to get infobox CSS working! It just means that there are a few more places where the CSS rules in question could be located. The Special:Gadgets page (https://sv.wikipedia.org/wiki/Special:Finesser on the Swedish Wikipedia) lists all the MediaWiki:*.css and MediaWiki:*.js pages used by each gadget. It is probably a bit easier to go through that filtered list than to manually browse Special:AllPages/MediaWiki:, though that certainly remains an option as well. tl,dr: On the Swedish Wikipedia (and other WMF sites), templates' CSS is served via the TemplateStyles extension. The page you're looking for is located at https://sv.wikipedia.org/wiki/Mall:Faktamall/styles.css and you can find this by viewing the https://sv.wikipedia.org/wiki/Mall:Faktamall_biografi template page in edit mode, where you'll find a collapsed-by-default listing of templates used on that page (titled "Mallar som används på den här sidan:" in Swedish).
  4. According to the MediaWiki.org manual page for generateSitemaps.php, the script has an option named --urlpath (which you should apparently use almost always with the --server option), which allows setting an absolute URL and seems to have been specifically implemented to support Google's requirements for sitemaps.
  5. It should be noted that there are several — more or less stable — free and open source software solutions for MediaWiki, such as WikiForum or the (in)famous LiquidThreads. (Mandatory disclaimer: I am one of the authors of WikiForum, although WikiForum has been in a maintenance mode for quite some time and hasn't received any new features and isn't actively being worked on by me or anyone else.) In addition to that, some sites integrate with an external (FOSS) forum, i.e. wikiHow uses Vanilla Forums for their forums with authentication done by a custom MediaWiki extensions (found in the /extensions/wikihow/Vanilla directory in the wikiHow source code dump); Wikia historically had a phpBB-based forum which even supported wikitext parsing, but this was achieved via various hack to the underlying phpBB codebase, and as such, the code wasn't exactly portable and/or reusable without modifications. That being said, a copy of said hacked phpBB codebase can still be found online (for example, on my GitHub mirror of Wikia's old Google Code account), so if someone were to want to clean up these hacks into a reusable phpBB modification that works on the current phpBB codebase, it's at least theoretically possible. One of the main issues that basically all of these FOSS forum solutions share is the same: a lack of developers. MediaWiki — as in the core wiki software — is great because it's widely used and has received a lot of attention from developers who use it in varying contexts with varying requirements. Building a forum(-like experience) inside MediaWiki is doable but hard, as witnessed by WikiForum and similar extensions. In my opinion, the correct way forward would likely be to use MediaWiki for authentication (via OAuth or somesuch) while using an external forum software package for actually implementing the forums. With different modifications, the forum software -- be it phpBB, Vanilla or even the non-free Invision Community -- could be made to support wikitext and whatnot, even.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.