VaultWiki4

[alpha]

thanky pegasus for the reply good news

would be great to find a welcome price with vaultwiki 4 for me as new customer - because i think you investigate a lot of work into the new major release and i hope it would be great because i like the system but at the moment i am looking for a little bit more ^^

[pegasus]

Some heavy reading, but as published so far, the most complete list of changes in VaultWiki 4 over 3.0.20: https://www.vaultwiki.org/blogs/54/

[ZakRhyno]

Are you still going to support IPB?

[pegasus]

That's the plan. It's included in the list I posted, albeit subtly.

[pegasus]

Three more glaring issues that I see currently that need fixing before reopening the wiki for everyone:
- some options are missing from the editor
- wiki attachments are stored in the file system with the wrong IDs, bound to happen if you keep running the upgrade repeatedly without emptying the attachment directory first
- YUI Javascript files need to be served locally to avoid issues with HTTPS theory

[Alfa1]

YUI??? Why no jquery?

[pegasus]

This should not come as a surprise, as it was one of the earliest items in the tracker for VaultWiki 4: https://www.vaultwiki.org/issues/2030/

At the time VaultWiki 4 development began, YUI was the only library supported by vBulletin. There was no inclination that they would ever support or ever so move to jquery. At the same time, we were not entirely pleased with YUI 2 that vBulletin was currently using.

Looking forward, vBulletin's current use of YUI 2 and other open tickets in their tracker suggested that, looking forward, we should utilize a later version of the same framework. In addition to this, we looked at both jquery and YUI3 from our standpoint as developers writing a visible source product, and we concluded that YUI3 generated more readable, more understandable code. Not only that, but at the time development began, YUI3 had some features we really needed that jquery did not yet.

When vBulletin 4.1.8 finally was released and vB began using jquery in the mobile style, there was still no greater suggestion that YUI would be dropped completely by the vB development team. It was not until vBulletin 5 went into beta, and more users like us were able to see the code, that we felt duped.

All said, YUI3 is a really great library and I'm quite pleased with it. If jquery were as readable, or it had developed certain features sooner, maybe this post and VaultWiki 4 would have been different.

In the mean time, compare (YUI3):

var posts = Y.Node.all("div.postbody");

To (jquery):

var posts = $("div.postbody");

Regardless of which library we chose, we would still be at this point right now, fighting with our live server software over the best way to compress the includes (the way VaultWiki wants, not the way the server wants).

[Alfa1]

Yes, I thought this was the reason. Though I had expected that VW4 was written to be independent from vbulletin and targeted at multiple community software solutions.

[alpha]

short question

is vaultwiki 4 working with all vb 4.x ? because I use allready 4.1.10 and I am not expecting an update because some addons what i use do not support 100% the 4.2 or higher

Thanks & looking forward when new wiki is online for public

[pegasus]

VaultWiki 4 is currently working with vBulletin > 4.1.4. vBulletin < 4.1.4 uses the same editor as vBulletin 3, and vBulletin 3 support has not yet been heavily tested.

[alpha]

ok that means i have no problem with my vbulletin 4.1.10 to use vaultwiki 4 - with the editor you mean the changed CKeditor?

[pegasus]

Images are currently broken (image file types aren't flagged correctly), category membership is missing, some options are still not showing up in the editor, and there are a few other minor things here and there... but the wiki is now turned on for users to check out and start testing.

[alpha]

...

[alpha]

pegasus thanks for the great job - looks really good with the changed style - it doesnt look like a normal forum style

when is this vaultwiki 4 (it is beta status now or RC ?) ready for testing on the own server ?
as well is the sitemap addon for vbseo also working with the vw4?

when i buy the product now - then i get also access to the vaultwiki 4 when its ready for download?

Thanks

[pegasus]

I'm glad you like the style. We tried not to change it too much that people wouldn't recognize it, but at the same time we wanted to update it and give it a slightly cleaner look. There are still some cross-browser issues that need to be fixed since modern browsers have now added support for CSS-3 properties and deprecated transitional properties.

VaultWiki 4 is still Alpha status for now. Any addons for VaultWiki will have to be completely rewritten for VaultWiki 4 or they won't work and will probably give your site serious errors. This includes the sitemap addon. A new version will have to be released, if it is needed at all.

Yes, if you buy the product now you would get access to VaultWiki 4 as well. VaultWiki 4 is still alpha status from our perspective.

More generally, on the 25th I will have to create a blog entry about everything users should really do when upgrading to VaultWiki 4. A script can only do so much, and there are many other things that need to be considered and catered for. Keep an eye out for it.