The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
CES NuWiki Special Pages Details »» | |||||||||||||||||||||||||
CES NUWIKI SPECIAL PAGES
Version: 1.0.1 ** THIS MOD IS NO LONGER SUPPORTED ** We are no longer developing this, since we have created a stand-alone commercial product instead: VaultWiki You can still feel free to use this mod as you wish, but understand that we cannot offer support for it any longer. Requires:
*** NEWS *** 8/21/2007 - v1.0.0 - 1.0.1 released Products to Install: 1 (+1 Project Tools) Plugins Included: 37 (+5 Project Tools) Files to Upload: 14 New Templates: 8 Template Edits: 0 Files to Edit: 7+ What It Does: This mod extends NuWiki by adding namespaces and Special Pages, allowing for much greater expandability than before and closer MediaWiki emulation. If you run vBulletin Project Tools install the Project Tools Expansion for this mod too for maximum integration! Follow the development progress of this mod and its child mods at: http://www.crackedeggstudios.com/project.php?issueid=28 Current Features:
Known Issues: - None *** Changelog *** As of Version 1.0.1: - fixed some parse errors As of Version 1.0.0: - initial release Show Your Support
|
Comments |
#22
|
||||
|
||||
Quote:
Also, will it be fairly easy to upgrade a pre-existing (and heavily popualted) NuWiki installation with this support pack? |
#23
|
|||
|
|||
It should be pretty easy to upgrade - the reason I'm taking so long to debug is to make sure nothing from default NuWiki is broken. A number of hooks have been changed, so I'm currently moving all the existing plugins to the new hooks.
Also, a number of AdminCP tools are going to be included to help with the various database changes (for example, old posts would need to be reprocessed using the new system). It will be highly recommended to turn off your board while applying this pack because every existing post will (ideally) need to be (auto-)modified during the upgrade process and the install scripts will probably slow down your site quite a bit during that time. But don't worry, since a detailed readme will be included explaining all of this, as well as (I think) a Help namespace to describe the functionality of the changes. |
#24
|
||||
|
||||
Good to know, thincom. Thanks!
When you say "every existing post", do you mean every post on the forum? Or just posts in wiki forums? My site has over 1.5 million posts, so re-processing all of them might be traumatic, so I will want to plan ahead. Thanks again! |
#25
|
|||
|
|||
By "every existing post" I mean every post on the forum. This is to properly support the (now deprecated in my patch) [wiki] bbcode that your users may have used. If you haven't used this code in non-wiki forums, I can add a setting to only process wiki articles.
As of this morning in my debugging: - redirects working - templates working (going to add permissions -> you can't "include" a template that you can't edit) - tables of contents working again, using [TOC]no/force/book/_blank_[/TOC] bbcodes |
#26
|
|||
|
|||
I am anxiously awaiting your work as well thincom. Just thought I ould pop by the thread and let you know you have at least 1 more person very interested in the extra functionality you are providing now that ElfMage has gone MIA.
|
#27
|
|||
|
|||
Quote:
Since templates should be more for quick formatting than for content anyway, I guess I should be satisfied to leave template-including permission-free. I spent today updating post preview with the new parser, and fixing all the horrible bugs that arose. Now post preview will show a fully-rendered wiki article in the wiki postbit, instead of the bland "Preview" box. Left on the agenda: - rewrite wikify second post (probably about 2 days) - test auto-links (probably about 1 day) - test cached posts (need to delete postparsed row on save of used link to support templates and "red" links) (1 more day) - handle inlinemod deletespam (2 hours or so) - create legacy-to-bbcode permanent conversion tool (3 hours or so) - create help articles (2 to 3 days) - create install.xml (2 hours or so) So that leaves about a week before this is ready for public release. Keep your fingers crossed that I can actually write the help system faster than that. |
#28
|
|||
|
|||
Okay I wanted to ask who actually uses the Second Wiki Post feature. This is the most incompatible piece of code I've come across so far that I think I may just revamp the way they are utilized and handled completely (e.g. with a [SPLIT] bb-code), so that as far as the database is concerned the first and second wiki post are actually the first post.
Whoever uses it, please tell me WHY (what makes it a good feature for you) so that I make sure not to break anything when I do rewrite it. |
#29
|
||||
|
||||
Hi Thincom,
Looking at this thread I see you have been extending NuWiki ? I am planning to integrate Wiki functionality on a new vB (3.7) powered site. But due to the absence of ElfImage from the NuHIT forum I am a bit worried. Would you be able to offer (paid) support and bugfixes to NuWiki (and your extension) ? Or do you know of a similar (but supported) vB/wiki extension ? Thanks, Taco |
#30
|
|||
|
|||
Hi. Yes, I believe myself to be knowledgeable enough about NuWiki to be able to offer support for it.
In other news, just a tiny set-back. While working on the Second Post feature, I attempted to merge 2 articles, only to discover that the system I had written to handle NuWiki article merges didn't work as expected. |
#31
|
|||
|
|||
Is this newest iteration of yours going to be 3.7 tested? That is about the biggest issue for me at this point. All the other changes and tweaks you're making over and above 1.3 RC1.
Also, thanks for this! |
Thread Tools | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|