VaultWiki4

**alpha** · March 10, 2013

how much will be the increase of the product ?

Because i tought this will be come with the status gold of vaultwiki 4 ... normaly from alpha1 to gold is a very long way

**pegasus** · March 13, 2013

I know the wait has been long, but the vB4 version is out. If people are still unable to download it, let me know. It's supposed to be available since a week ago already. The XenForo version is coming shortly too. For those that don't believe me (and I completely understand), please refer to this blurry screenshot...

Aside from XenForo's Quick Reply being a bit snazzier IMHO, expect the XenForo release to look roughly the same as the vB one, just wrapped in XenForo's style and saved in its database.

**Alfa1** · March 14, 2013

lol! Blurry indeed. Looks like pic of a white rabbit running in the fog to me.

**Chris** · March 14, 2013

there are so many platforms that are waiting for this, I'm rather excited.

3.8 first, and then my smaller xF platforms.

**alpha** · March 14, 2013

Hello Pegasus,

I have at the moment VBulletin 4.1.10 running on my site - this should work with vaultwiki 4.x without issue?

With the current release of this vaultwiki 4 what is now available for public is similar to that one which is running here on the site?

As well is it possible to do an upgrade from Vaultwiki 3 Lite to Vaultwiki 4 ? I have there some pages created and I do not want to delete everything

Last question - is there also an sitemap addon available now for this Vaultwiki 4 release?

For general - it make sense to use Vaultwiki 4 on a live page (no testing) for productive use without problem or its recommended to use vaultwiki 3 and wait for wiki4 RC oder gold?

Thank you & waiting for your soonest reply.

**pegasus** · March 14, 2013

Hi, yes vBulletin 4.1.10 SHOULD work with VaultWiki 4. Yes, the current release for the public is nearly the same as what's running here. However, our site runs directly off the latest file revisions in our proprietary SVN (a nightmare when we have to set paths for new software), so this puts us a few builds ahead.

If you don't want to delete everything, I would recommend upgrading VaultWiki 3 Lite to VaultWiki 3.0.20 first, then upgrading that to VaultWiki 4. A test upgrade directly from Lite to 4 has not been done yet, and I'd hate for you to run into problems halfway between versions. Still, backup before upgrading, and follow all the other instructions for a 3 -> 4 upgrade that are listed in my blog.

If you use vBulletin 4's built-in sitemap, then it will work with VaultWiki 4 already. If you use the vBSEO sitemap, then also install this add-on: https://www.vaultwiki.org/threads/5498/

While VaultWiki 4 is in Alpha, it seems good enough for normal productive use at this time (or we wouldn't have released it). It has been in Alpha testing for over 9 months now, is much more stable and more usable than it was in the beginning. We hope that early adopters will help us find the remaining issues so we can call it a gold release soon. We are very responsive to new bug reports and will try to get them resolved as they are brought to us.

For new users we would recommend VaultWiki 4. It's easier to understand, and it will mean less learning for you and your users in a short time than if you upgraded again in that time.

Hope this helps.

**alpha** · March 15, 2013

hello,

that helps good - there is now nearly everything clarified.

I have one additional question - yesterday i have done update with VB to 4.2.0 PL3 - nearly everthing is perfect - but some scripts have problems - also the Vaultwiki - the page is not loading anymore as well i get an error with page not found, a white blank page or something else.

and to test vaultwiki 4 - its not possible to download the file -> the file is currently not available for download

**pegasus** · March 15, 2013

Thanks for letting me know. The path was set wrong in Members area for the non-admin download. I fixed the paths and it is working now.

**alpha** · March 15, 2013

thanks that works now but directly after trying to start installer -> fatal error
i have written you a PM and set something in the bug tracker

**pegasus** · March 15, 2013

Wrong build was in the Members area apparently (it was the one we used that gave us all the problems during our upgrade). I just changed the build to a more current one.

**alpha** · May 27, 2013

hey pegasus,

when there will be a new update with the VW4 product with new bug fixes and more?!
Because last one was 1 month ago now - hopefully soon, because for me as german member i have still a lot of issues with "Ä, Ö, ..." specially in URLS its a big issue and the the lot of "�" is all over the wiki pages is annoying (!)

**Delfi_r1** · October 2, 2013

It's time to upgrade a vWiki 3 to vVwiki 4 on a vB 4.20pl3 install?

I understand that the instructions are on https://www.vaultwiki.org/blogs/56/

My installation uses only one character set and it's not UTF-8, last try to change to UTF-8 was unsuccessful. Perhaps some day I'll try to change all to UTF-8, but now it's not the moment.

I use external images, so I'll be careful with this issue.

**pegasus** · October 2, 2013

Do a test run on a test database first. If the results are good, go ahead.

**pegasus** · October 24, 2014

VaultWiki 4 core is pretty much stable now. I think the coming RC 4 will be the final RC before the gold release.

While there are still a few minor or unfinished features for the current 4.0, at this time, we've started looking forward to 4.1. One of the new things we're looking into for 4.1 (or a fork that would merge at 4.1), is IP.Board/Invision Power Suite support. You guys lost the original poll in this thread, but we're very excited about the imminent IPS 4 and expanding VaultWiki to support that.

Because everything on our end would have to ramp up in order to release as close to IPS 4 as possible, we've started planning a fundraiser to make this transition smoothly and to start generating/rekindling interest:

http://prefundia.com/projects/view/v...ces-ips4/2933/
Once we get all the details worked out, we'll be launching the actual Kickstarter.

We want to make this proposed integration a success, so we welcome all your ideas, support, and any help you can give us in spreading the word. Thanks!