-
This is a demo site for the purposes of showing and testing VaultWiki in a XenForo environment. If you have real questions or need support, please visit the real VaultWiki web site here: https://www.vaultwiki.org
VaultWiki4
- Thread starter fraggle
- Start date
For vBulletin 4 is pretty much ready to go (just need to export it to ZIP AFAIK). We should be launching that in a few days.
For vBulletin 3, users will have to wait til next release.
For vBulletin 5, users will have to wait several releases.
For XenForo, pretty much ready to go, but there is still some error checking we need to do since XenForo has a higher error sensitivity than vBulletin. May launch same day as vBulletin 4, or a few days back.
For IPB, users will have to wait til next release. There was a significant new IPB version in the past quarter, so we still have to update some things.
For vBulletin 3, users will have to wait til next release.
For vBulletin 5, users will have to wait several releases.
For XenForo, pretty much ready to go, but there is still some error checking we need to do since XenForo has a higher error sensitivity than vBulletin. May launch same day as vBulletin 4, or a few days back.
For IPB, users will have to wait til next release. There was a significant new IPB version in the past quarter, so we still have to update some things.
Claw Snuff did a series of blog videos on VaultWiki 4. There's a lot more she hadn't covered, but sadly she has moved on to other endeavors. We are currently considering other people in our area to continue the work she was doing.
Anyway, here's some of her videos:
https://www.vaultwiki.org/blogs/50/
https://www.vaultwiki.org/blogs/51/
https://www.vaultwiki.org/blogs/52/
A little bit has changed since the videos. They were all posted before the Alpha started, and the team has been really great about suggesting how to improve some things. For example, there are more on-screen instructions and some terminology is changed.
Anyway, here's some of her videos:
https://www.vaultwiki.org/blogs/50/
https://www.vaultwiki.org/blogs/51/
https://www.vaultwiki.org/blogs/52/
A little bit has changed since the videos. They were all posted before the Alpha started, and the team has been really great about suggesting how to improve some things. For example, there are more on-screen instructions and some terminology is changed.
Our configuration is not really standard since we are trying to execute VaultWiki directly from SVN. This takes a bit of trial and error - we can't use the config we already made for our test builds since the paths have to make sense in the context of the live install. On top of that, there were still some problems with the upgrade script. To mention a few, that resulted in some revisions not being copied correctly, some permissions being missing, and some pages not having the right URLs.
I think we have resolved all these issues now, so we would be trying to upgrade again tomorrow. After the upgrade though, even if the wiki itself is copied fine, there are a lot of scripts we run that rely on wiki functions in order to work properly, like our shopping cart and our Members area. These need to quickly be updated and stress-tested. If this can't all be handled in less than a few hours time, it will be put off again and stretched out over several days.
I think we have resolved all these issues now, so we would be trying to upgrade again tomorrow. After the upgrade though, even if the wiki itself is copied fine, there are a lot of scripts we run that rely on wiki functions in order to work properly, like our shopping cart and our Members area. These need to quickly be updated and stress-tested. If this can't all be handled in less than a few hours time, it will be put off again and stretched out over several days.
alpha
New Member
thanks pegasus - when you think there will be vaultwiki 4 ready for public to see it and test it - because in you post it sounds that it will take much more days or weeks?
Do you have a list with features of the new vault wiki 4 ? maybe to compare with wiki 3 ?
There will be also a welcome discount for example for the new vaultwiki 4?
Thank you in advance
Do you have a list with features of the new vault wiki 4 ? maybe to compare with wiki 3 ?
There will be also a welcome discount for example for the new vaultwiki 4?
Thank you in advance
It will not be many more days to see it. Like I said, it was mainly flaws in the upgrade script (which have been fixed now), and us not using the right paths to the SVN (so we kept getting errors that files were missing). It sounds like a lot of work to update our custom plugins, but it's really not. They are localized in a small group of files that we have marked on a task list.
I haven't compiled a list of VaultWiki 4 vs VaultWiki 3 in one spot like a blog. I could try to do something like that today or tomorrow, for those of you who are curious.
Every time there is a new major version (as with 2 and 3 so far) we tend to increase the price after some weeks (the day will be announced ahead of time). Users who purchase before that day will pay the current price and they will get the same great software as users who purchase after that day and pay the increased price. After the price increases, there will also probably be a promotion or coupon to go with the release, but I'm not sure about that or what it would be.
We will not increase the price before users can buy it, and we won't have a 'pre-sale' for users unless they want to use VaultWiki 3 for a while.
I haven't compiled a list of VaultWiki 4 vs VaultWiki 3 in one spot like a blog. I could try to do something like that today or tomorrow, for those of you who are curious.
Every time there is a new major version (as with 2 and 3 so far) we tend to increase the price after some weeks (the day will be announced ahead of time). Users who purchase before that day will pay the current price and they will get the same great software as users who purchase after that day and pay the increased price. After the price increases, there will also probably be a promotion or coupon to go with the release, but I'm not sure about that or what it would be.
We will not increase the price before users can buy it, and we won't have a 'pre-sale' for users unless they want to use VaultWiki 3 for a while.
T
The Dark Wizard
Guest
Would it be safe to say that by next week we will see Vaultwiki for xF?
alpha
New Member
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 ^^
good newswould 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 ^^
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/
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
- 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
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):
To (jquery):
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).
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):
Code:
var posts = Y.Node.all("div.postbody");
Code:
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).