VaultWiki 3.0.0 Progress (vBulletin 4)

[pegasus]

The question has been popping up throughout the forums - how is the update for vBulletin 4 coming along? When will it be ready?

This post should be used as the official source on this matter. Please refrain from continually asking for updates. We will update this post as we reach significant milestones.

Keep in mind that while we are making headway updating VaultWiki to be compatible with vBulletin 4, we are also fixing outstanding reported bugs and those we come across, some of which, in the interest of time, may not be mentioned in the final changelogs.

There is currently no specific ETA. We intend to provide a Beta by the time vBulletin 4 goes Gold.

Friday, November 20, 2009

vBulletin 4 Beta 3, the first public beta, was released last Friday. Since that time, we have converted VaultWiki to use the new template system (there were over 50 templates that needed to be completely rewritten) and modified the upgrade script to detect vBulletin 4 and make additional changes for that case.

Tuesday, December 1, 2009

VaultWiki 3 has been updated and integrated with the entirely new CSS in vBulletin 4. AJAX tabs are working again in the new system. Popups have been rewritten, and collapsible headlines are functioning again.

Monday, December 7, 2009

We have merged our commercial addons into the Premium VaultWiki package, and updated those addons to work under vBulletin 4. We have rewritten our Members Area to handle this change. A number of UTF-8 issues have been resolved, native redirect support has been added, as well as support for vBulletin's friendly URLs.

Monday, December 14, 2009

VaultWiki 3 has been updated for the centralized attachments system in vBulletin 4. The Image namespace and BB-Code tag have been integrated with the Asset Manager. Since vBulletin 4 RC2, friendly URL handling had to be rewritten.

Friday, December 18, 2009

Since vBulletin 4 Gold is set for release on Monday, here's an early update on where we stand with VaultWiki 3. We have conquered the beast that is vBulletin 4's search engine and have wiki search working for the new build. The changes should allow us to add Special page integration with vB4 Search in Beta 2 or 3. We had to rewrite the upgrade system to handle proper versioning of vBulletin 3.x vs 4.x vs VaultWiki standard vs VaultWiki premium changes, so that it doesn't matter what order the components are actually installed.

Wrapping up for a VaultWiki 3 Beta 1 release early next week, we still have to test a few more things in a few more environments and correct some UI bugs, but it looks like all of the "compatibility" changes are in place and ready to be rolled out in a release. Starting Monday, look for a separate announcement in our VaultWiki News forum that will alert everyone of its readiness.

Wednesday, December 23, 2009

VaultWiki 3 Beta 1 is ready for public testing, aside from 1 important aspect. Many of the images still need to be updated. Unfortunately, this is not something we can move forward with until vBulletin.com releases the "Graphics Developer Kit" for vBulletin 4.

Thursday, December 31, 2009

Tomorrow we will be installing 3.0.0 Beta 1 on our site, so we can test it briefly in a live environment. As a result, we expect our site to be unavailable from 2-5pm EST on January 1, 2010. We fully intend to release the build to the public on Monday, January 4.

[Marv]

Sounds good to me - carry on

[Marv]

Monday, December 7, 2009

We have merged our commercial addons into the Premium VaultWiki package, and updated those addons to work under vBulletin 4. We have rewritten our Members Area to handle this change. A number of UTF-8 issues have been resolved, native redirect support has been added, as well as support for vBulletin's friendly URLs.

Means, the actual downloadable version 2.5.7 can be installed on the vb4 beta 5 ? Would be great.

[beduino]

Exactly my question
tks in advance

joao barroca

[Marv]

Hello, anyone home ?

[pegasus]

As the title of this thread is about VaultWiki 3.0.0, any information discussed here refers to that version only - not to any versions prior to that.

[baritoneace]

I'm happy to have discovered this product. You have a new customer when VB 4.0 goes Gold.

[pegasus]

As mentioned above, we're now delayed because vbulletin.com has not yet released the Graphics Developer Kit for vB4.

[Alfa1]

Since IB will convert vbulletin forum to a CMS content type, will vaultwiki be converted to a CMS content type?

[pegasus]

For backwards compatibility, VaultWiki doesn't create any additional "real" CMS content types. Changing from forum to a wiki type didn't make sense moving forward, as it would require changes in virtually every line of code. That said, some new features will be available in 3.0.0 (if you have vB4) that take advantage of the content type framework - improved search integration, for one.

[Alfa1]

Do you plan to move to a CMS content type in the future? If not, can you please explain why not?

The improved search integration, does that include getting new wiki edits in 'new posts'?

[pegasus]

Firstly, we recognize that many people are not upgrading to vBulletin 4. It would be foolish to develop a solution that excludes a very large portion of the market.

Aside from that, we don't see any pressing reason to convert to a different content type. VaultWiki is working fine under the forum/thread system. If it's working fine, why move it and potentially add many new bugs? According to some preliminary assessments that were done on the matter, the move to another content type would actually require more memory and database read/writes per page load, especially during searches.

At this time, new wiki edits do not appear in new posts. This used to be an option, but everyone found it very annoying because they were looking for new posts only - and you can just click "Recent Changes" for the new wiki edits.

The improved search integration refers to a new advanced search form in vBulletin 4 (that was possible by adding a CMS content type for search). It's similar to the "Search Posts" form, except that it only returns wiki posts, and some wiki-exclusive filters. In the future we intend to permit filtering the search results through a Special page.

[Alfa1]

I suspect many people will move to vb4 in time, when most vb code has been rewritten and vb4's code works better and vbulletins Image Gallery comes out.
vbulletin forum is going to be a CMS content type anyway, so the decision will present itself again when vbulletin forum is refactored. Because Vaultwiki will either need to convert to the new 'forum' CMS content type or convert to its own content type. As I understand it, the old vb forum as it is will cease to exist.

Thanks for explaining.