VaultWiki vs. NuWiki

Support / Development

• NuWiki's developer has dropped off the face of the earth. No new releases have been made for several years and there is no official support available.
  
• VaultWiki is actively developed to support the newest forum and web technologies. Support is available on the VaultWiki web site.

Security

• NuWiki contains a number of security and performance loopholes that are unlikely to be fixed.
  
• VaultWiki's developers close security and performance problems as soon as they are discovered and release patches to their customers.

Namespaces

• In effect, NuWiki only had one namespace; that is, only one article could have a given title.
  
• VaultWiki allows admins to create an infinite number of namespaces. One article in each namespace may have a given title.

Tabbed articles

• NuWiki articles looked very similar to regular forum posts, without the block containing the poster's user information. Edit controls appear below the article.
  
• VaultWiki articles have tabs across the top, making it easier for users to find the controls they are looking for without scrolling all the way down the page.

Categories

• NuWiki only allowed organizing wiki pages using forums. A page could only be saved in one forum at a time.
  
• VaultWiki allows organizing wiki pages into Categories. A page can be in many categories at once. Simply put, a Category is a directory page with a certain theme.

Profile Integration

• NuWiki did not show any information on users' profiles.
  
• VaultWiki gives users credit for their wiki activity on their profiles.

Section editing

• NuWiki only allowed users to edit an entire page at once.
  
• VaultWiki allows users to edit the entire page, or just the text under a specific headline.

Wiki Syntax

• NuWiki uses a hybrid of BB-Code and MediaWiki syntax, so effectively, users have to learn new markup.
  
• VaultWiki uses BB-Code syntax, and includes several editor buttons to ease the learning curve for them.

Dynamic Templates

• NuWiki allowed using templates to dynamically insert common article content. Users could specify their own parameters to change the output. Articles that used templates could not be cached.
  
• VaultWiki allows templates as well, but also supports conditionals to make the template more versatile. Articles using templates can be cached, so there are huge performance savings on subsequent views.

Multi-Language Support

• NuWiki did not have any special consideration for wikis written in more than one language.
  
• VaultWiki contains tools for defining multiple wiki pages as translations of each other, and links the versions to the forum's installed languages. Using an article's language menu, you can switch to another translation, or write a new one.

Books

• NuWiki allowed users to organize wiki pages into containers called Books. A Book could not have its own content or be organized in any way.
  
• VaultWiki also allows organization using Books, but Books are treated as wiki pages. This means they can have their own content, and be placed inside other Books or other containers.

Special pages

• NuWiki had lists for wiki books and recently edited pages.
  
• VaultWiki includes a large number of lists filter pages in various ways, show statistics, or show pages in need of maintenance.

Social Group Pages

• NuWiki was designed for vBulletin 3.6, before Social Groups were introduced.
  
• VaultWiki allows Social Group-driven wikis. Optionally, Social Groups can own wiki pages so that only group members can edit them. In group pages, another level of Protection becomes available, which would prevent non-members from viewing the wiki page.

Centralized Images

• NuWiki allowed inserting external images into articles using the IMG tag, or by uploading an attachment. To use an image attachment in other articles, you would need to know the attachment ID or the full URL.
  
• VaultWiki allows users to upload images to a wiki repository. Using the images in multiple articles only requires knowing the name of the image. In vBulletin 4, you can select the image by browsing thumbnails in the Attachment Manager.

Integrated search

• NuWiki used vBulletin's search system
  
• VaultWiki does the same, but also includes a Special:Search page that looks for a matching article before showing vBulletin's results. If a match is found, the user is forwarded to that page.

Wiki Permissions

• NuWiki uses vBulletin's Usergroup Permissions
  
• VaultWiki allows greater flexibility by allowing permissions to be changed on a per-wiki-forum basis.

Wiki Moderation

• In NuWiki, new articles could be optionally moderated, so that staff must approve the article before it's added to the wiki.
  
• In VaultWiki, not only can you moderate new articles, but you can optionally moderate edits to those articles, so that staff must approve changes to existing articles.

Wiki Subscriptions

• In NuWiki, users would receive notifications instantly if an article they were subscribed to was modified, if they had chosen instant notifications.
  
• In VaultWiki, users will receive notifications instantly, daily, or weekly, depending on their preferences.

Forum Headers

• NuWiki allowed users to create wiki content on forum pages, called headers. The header itself was locked to that forum and did not have an intuitive name.
  
• VaultWiki allows users to create headers as well, but users can give them any name they want. Headers can be moved to another forum after their creation.

Redirects

• NuWiki allowed users to create redirect-pages, aliases for existing wiki pages that point to the same content. Redirect pages could not be cached.
  
• VaultWiki has the same functionality, but redirect pages are saved to the cache, so there are huge performance savings on subsequent views.

Article Protection

• NuWiki "protected" articles by closing them to new edits and comments.
  
• VaultWiki offers several levels of protection:
  
  • Prevent new edits from being made
    
  • Prevent the title from being changed
    
  • Only allow the page creator to make edits
    
  • Only allow admins to make edits
    
  • After deleting the article, prevent new articles with the same name from being created

Wiki Main Page

• NuWiki supported main pages that would show instead of the forum list, if the page had the same title as the containing forum.
  
• VaultWiki allows this to be any page, but it must be set in the AdminCP. VaultWiki also has a wiki landing page, so that you don't ever have to show your users that the wiki is part of the forum hierarchy.

Developer Tools

• NuWiki's functionality was difficult to modify or extend to better fit a site's needs.
  
• VaultWiki uses vBulletin's Hook system extensively, allowing admins to customize VaultWiki's appearance and functionality as they see fit.