Wiki 2.0 Issues

Jump to: navigation, search

The following documents issues and bugs with the new wiki 2.0 launch.


Known Issues

Syntax Highlighting is Ugly

  • The default syntax highlighting stylesheet does not match the look and feel of This is because the extension has been installed as is, and a custom stylesheet hasn't been produced for languages.

Many pages have duplicate headings

  • Some pages are displayed with two titles. These are pages which haven't been updated to use the <entry-title> mark-up for page headings yet. They are currently displaying the MediaWiki default heading, as well as the heading from the previous wiki install. The page needs to be updated to use the new mark-up.
  • Default my-page headings could be dynamically reformatted. To save manual overrides of every page on the wiki, add reformatting rules to convert ‘wiki-2-issues- into ‘Wiki 2 Issues’ and so on. --BenWard 00:00, 12 January 2009 (UTC)
    • It be necessary to have special handling for ‘hcard-issues’ to ‘hCard issues’ for capitalization, but can handle most cases. Just keep a little list of known microformats? --BenWard 00:00, 12 January 2009 (UTC)

User Preferences have been reset

  • All user preferences have been reset to defaults. To switch to the new theme, user preferences had to be overwritten. Sensible defaults have been applied, but apologies to those who had customised their profiles. You need to adjust your setting again from the Special:Preferences page.


  • The #microformats IRC bot is nolonger reporting page edits. Edits of either major or minor type are nolonger echoed into #microformats IRC
    • Need to check with Ryan King or Tantek regarding how to reconfigure that. --BenWard 10:16, 17 November 2008 (UTC)
      • I just checked with Ryan on irc, maintainer of mfbot, and according to him it needs to be rewritten [probably due to the database schema change]. Since the bot was originally derived from a bot from the Wikipedia community, it may be possible to upgrade mfbot using their latest bot code. Ryan does not have time to look into this now, so we need to add this to the wiki-2 upgrade fix-up to-do list. --Tantek 18:05, 17 November 2008 (UTC)

Top Navigation Bar

  • Absolutely beautiful upgrade, Ben. But because the wiki is now so integrated with the uf look and feel, people are going to wonder where the About/Code+Tools/Get Started links have gone. 17:12, 17 November 2008 (UTC)


  • As well as "Specifications" and "Draft Specifications", I'd suggest "Pre-Draft Specifications" for efforts like haudio, figure, hproduct, and hrecipe, which seem to be converging on relatively stable specs, but haven't got there quite yet; and "Exploratory Discussions" for efforts which are still in the early stages. (But no custom style sheets for those categories.) TobyInk 17:37, 17 November 2008 (UTC)

New Users cannot edit their own User: page

  • Newly registered users are able to edit pages in the global wiki namespace, but not within User:. --Reported by Rob Manson, November 29th
    • This is presumably a configuration issue concerning default user-group permissions. Likely overwritten, or the format changed, when we upgraded to MediaWiki 1.13 --BenWard 21:25, 30 November 2008 (UTC)

Generate front-page content from categories

  • Also, would be nice if the Main_Page listings of drafts and specifications could be auto-generated from the categories, but that's probably unlikely. TobyInk 17:37, 17 November 2008 (UTC)
    • Agreed, that would be neat. I'll take a look into doing that with an extension. --BenWard 22:49, 17 November 2008 (UTC)


  • Surely it's possible to create a plugin which looks at edits from users with no edit history, and blocks the edit if and only if it seems to create a one-word paragraph at the top of the page? TobyInk January 5th 2009
  • I recommend the ReCAPTCHA plugin for MediaWiki as a way of preventing spambots from signing up. It's one of the least annoying CAPTCHAs I've seen: the words presented are part of the Project Gutenberg book scanning, and it has an audio version - but there is some dispute regarding accessibility - see here. The ConfirmEdit extension allows you to trigger a CAPTCHA on a variety of events. If someone can come up with some regular expressions which match the spam problem, you can always use the SpamRegex extension. I'll have a little think about possible anti-spam regexes, but it could be something of a tough problem as spam is subject to Darwinian principles... --TomMorris 20:49, 5 January 2009 (UTC)

CAPTCHA loop problem

  • If you edit a page and add some external links, then save without an edit summary, you get the CAPTCHA which pops up. You fill in the CAPTCHA, and then it goes to a page which tells you that if you hit save again, it'll post your edit without an edit summary. But if you try to do so, it then brings up the CAPTCHA again. The only way that the user can post edits with external links is to post an edit summary. Of course, every edit should have an edit summary. But I was being lazy. Dunno what the right way to resolve this is. –TomMorris 10:14, 15 August 2009 (UTC)

Fixed Issues

TOC overlaps preceding text

  • The TOC overlaps preceding paragraphs of text. This is an error in the stylesheet. For visual effect the TOC gets pulled upward to overlap titles, but does not account for being preceded by a paragraph, rather than the page heading.

Related Pages


Wiki 2.0 Issues was last modified: Saturday, August 15th, 2009