Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

16 Good

About Skizzerz

  • Rank
  • Birthday October 10
  1. Allow user to Input a variable in an inputbox

    This is unfortunately not possible with just the Inputbox extension. You may be able to make use of the Page Forms extension for this purpose (it's part of Semantic MediaWiki but can be installed standalone if you don't want all of SMW installed). However, I've never actually tried it out myself so I cannot say for certain whether or not it will work. You can grab the extension at https://www.mediawiki.org/wiki/Extension:Page_Forms
  2. Sorting navigational templates

    The only use of sortkey I know of is to impact how pages are displayed when viewing a Category page directly. If you have some navigational templates with a "sortkey" parameter, you'll need to link to those templates so we can look at the source and give tips/suggestions. Otherwise, can you please clarify what you are intending to do?
  3. I have enabled uploading templates to share with other wiki users. To get there, click on "Downloads" in the top navigation bar and then "Submit a file" If you have any feedback or suggestions for the template repository, please let me know.
  4. DeleteUserPages

    Version 1.0.0


    This extension lets users delete their own user pages and user talk pages. Two permissions are added (by default not granted to anyone) which control whether or not one can delete their own user page or their own subpages. This extension does not allow users to delete pages that are not their user page or subpages of their user page. The user does not need to be the author of the page to delete it, and can only delete if they would otherwise be allowed to edit that page. For installation instructions, please see the documentation page on MediaWiki.org. For support, please post a new topic on the forums. Free support is provided on a best-effort basis. Commercial support for this extension is available by purchasing a MediaWiki Support Subscription.


  5. enable only some users to translate

    You need to change the user rights assignment for the translate right. At the moment, it seems that either '*' or 'user' (all users or logged in users) are given the translate right, and you should change that to a specific user group, such as making a new Translators group. See here for a sample configuration which adds a new translate group (which you can then assign to users you want to be able to translate via Special:UserRights)
  6. A broken layout like that is usually caused by you either having extra open tags or extra closed tag (like you have a <div> but no corresponding </div>, or you have an extra </div> without the associated <div> earlier on). Doesn't have to be div, could be any block-level tag such as <table> too. If you're copying templates from Wikipedia, you're going to need a handful of settings and extensions installed in order to make them work correctly. Click the links in each point for more info. Ensure that Tidy is enabled: $wgTidyConfig. My recommendation is to use the first example on that page under the Examples heading; it will require that the tidy PHP extension (not MediaWiki extension) is installed on your server. If Tidy is not enabled, broken layouts like the above can happen due to how the wikitext parser operates differently when not using Tidy, even if there is no actual issue with your wikitext. Ensure that you have installed the following MediaWiki extensions: ParserFunctions and Scribunto
  7. Null edit

    You can disable the parser cache sitewide with the following in your LocalSettings.php. I do not recommend this except on small wikis: $wgParserCacheType = CACHE_NONE; There is an extension which supposedly let you disable the cache on a per-page basis. I have not used or tested it, and make no guarantees that they are compatible with modern versions of mediawiki: https://www.mediawiki.org/wiki/Extension:MagicNoCache In addition, other extensions may disable the cache on pages they are used, such as DynamicPageList.
  8. Null edit

    Pages in MediaWiki are cached, meaning that the page is not processed on each page view, but rather only once and then the process page served to users. If you want a truly dynamic page, you can install an extension that disables the parser cache (preferably on a per-page basis), but keep in mind that doing so will slow down page views for such pages and increase server resources.
  9. How can I use Visual Editor Extention?

    Once Parsoid is installed, edit /etc/mediawiki/parsoid/config.yaml and modify the uri string to point to your wiki's api.php endpoint. For example, https://example.com/w/api.php Then, install and configure VisualEditor as a mediawiki extension by following the 2nd link in my above post.
  10. How can I use Visual Editor Extention?

    Installing Visual Editor is a two part process: Installing Parsoid service Installing Visual Editor For some linux distributions, Parsoid is present in package repositories and can be installed from them. See here for details on installing and configuring Parsoid. Once Parsoid is installed, follow the Visual Editor setup instructions for info on how to configure VE to work with Parsoid.
  11. Restored MediaWiki, Not Gone Perfect

    1.16 is ancient. You'll probably want to restore it to a suitably ancient version of Ubuntu as well. My first guess is that the PHP version you have installed is too new; you'll probably want PHP 5.2, as I believe 5.3+ broke compatibility with super old versions of mediawiki. You will be able to verify this for sure by checking your server error logs. A 500 error should hopefully be logged somewhere in /var/log. Perhaps syslog, perhaps an apache error log.
  12. List pages without the subpages

    This does not seem to be possible using only Special:PrefixIndex, so some other extension will be needed to generate this list. DynamicPageList can probably do it, but is likely overblown for your use case. It is possible to do this with a Scribunto module as well. I believe it should also be possible to omit the sub-pages from the PrefixIndex listing using a combination of ParserFunctions and StringFunctions (StringFunctions are included in the ParserFunctions extension, but are disabled by default), but it will be more limited in terms of functionality (can only support up to a hardcoded number of pages).
  13. Parser functions in templates

    I edited your template code above -- you had line breaks in-between the if statements which were being rendered. I commented them out with <!-- --> so that you retain the visual spacing (for readability when editing) but the line breaks themselves do not appear when the template is used. I also put the header on a line by itself, as otherwise it could cause issues in some template invocations.
  14. Parser functions in templates

    Yep. Replace that entire existing line with what I just said. No sub-template or blank.
  15. Parser functions in templates

    Replace 1 with the name of the parameter, in your case Contact_Name. Do not use a sub-template, you don't need it for something this simple. {{#if: {{{Contact_Name|}}} | : {{{Contact_Name}}} }} The pipe at the end in the first parameter of #if is very important. If you do not have the pipe at the end, it will not default to blank, and therefore it will always try to execute the "then" clause of the if. You do not need an "else" clause with {{blank}} unless Template:Blank actually has contents (and isn't just empty). Omitting the "else" clause will automatically make it blank.

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.