18,246 Pages

On this page I'm going to collect some of my favorite bits of wiki-related knowledge.


Help pages


  • Guide to Infoboxes
    • aka "A Beginner's Guide to Templates". This page taught me how to make templates. It's really good, except that it doesn't really explain fully how to use the #If function. Check out the Parser Functions help page linked above for that info.



Rename a category page

  • Although a Category page can't be renamed or moved to another namespace with the wiki's Move function, this can be achieved by exporting the category page to an XML file, manually editing the file, and reimporting it back to the wiki. Importing a page requires Administrator rights.
    • In the exported XML file, the page's name space is determined by the numerical code within the <ns> tag. A list of codes is provided in the XML file. 0 is for the main wiki space, although that isn't completely clear in the XML file.
    • A page's name is contained within the <title> tag. If moving a page into the Category namespace, "Category:" (without the quotes) should be added to the beginning of the page's name.
    • Wikia has removed the import page from Special:SpecialPages. It can still be found at Special:Import.

Finding HTML color codes

  • To easily find an HTML color code for an element on a wiki, take a screenshot of the element in question and use this tool to determine the color code.

Wiki tables

  • To make an attribute, such as background color or centering, apply to an entire table row, add that attribute to the |- line for the row's entry. Attributes added to lines which only begin with | will only apply to a single cell.
  • To make lines between table cells invisible, add style= "border-collapse:collapse;" to the {| line of the table.
    This trick is courtesy of Ceiling Master
    • This is CSS. Other CSS can be found at W3 Schools.

Saving some typing

  • The wiki updates the autocomplete for categories about once a day. If you're gonna be adding the same newly-created category to a bunch of pages, it's easiest to add it to a single page, then wait 24 hours for the autocomplete to update before adding it to any more pages. That way you don't have to type the whole category name every time.

Page layouts at different screen sizes

This is less important now that Wikia has made changes to the way they handle monitors of different sizes. It can still be useful in some circumstances.

  • To easily see what a page's layout will look like on computer monitors which have a lower resolution than yours, Firefox users can install the Browsizer plugin. Like most extensions that were actually worth using, Browsizer doesn't work with Firefox version 57 and above.
  • Checking other resolutions is especially important for editors with widescreen monitors in order to avoid creating pages which have horizontal scrollbars when viewed on non-widescreen monitors.

Create bulleted, linked lists of pages

  • Copy a list of pages into a spreadsheet. A few columns over use the spreadsheet's concatenate function to add the necessary wiki formatting before and after the text. For example in Libre/Open Office the formula would be =CONCATENATE("* [[",A1,"]]")
  • This can also be done with a regular expression. Search for ^.*$, then replace with * [[\0]] or * [[$0]], depending on what regular expression syntax your software uses. For more regular expressions, see my regular expressions page.

Create an internal link to an old version of an edit

  • You can't link to an old version of a page using a wikilink. Instead of creating an external link, you can use Special:PermanentLink instead. The format is [[Special:PermanentLink/EDITID]], where EDITID is the edit number of the old edit. The edit ID of a revision is the number after "?oldid=" in the url of a previous edit. See the MediaWiki man page for more info.


Categories not appearing

  • When categories won't appear on a page even though they've been added multiple times, there is probably an unclosed HTML tag. In every case that I've seen, it's been a Gallery tag.

Table floats to the bottom

  • If a table always floats to the bottom of a page, it's likely because the table hasn't been closed properly with |}. This can even cause an infobox to float to the bottom of a page.

Template problems

  • If a template won't render on a page but renders on other pages, check for any unclosed tags in the filled-in parameters. For example opening a link with [[ and not closing the tag with ]] can cause a template to fail to render.
  • If a template is intended to be used in the middle of a line of text, any <noinclude> tag (such as for adding categories or documentation) must not be put on a new line. This appears to be because the new line is transcluded into the page.
Community content is available under CC-BY-SA unless otherwise noted.