When will VaultWiki4 Alpha or Beta be available for download?
Did you rewite it to store all data in Content type instead of Forum as you were going?
Did you rewite it to store all data in Content type instead of Forum as you were going?
-
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
Hi,
Yes we've been working on VaultWiki 4. And yes, as far as we've gotten, all data is stored in content types instead of forum threads.
However we don't have very big staff, so we've had to juggle keeping VaultWiki 3 compatible with each new vBulletin release (especially the ckEditor release). These changes always need to be merged into 3 other product types: Standard, Lite, and 4. So every time we have to update the current version, it dramatically reduces development focus on 4.
Yes we've been working on VaultWiki 4. And yes, as far as we've gotten, all data is stored in content types instead of forum threads.
However we don't have very big staff, so we've had to juggle keeping VaultWiki 3 compatible with each new vBulletin release (especially the ckEditor release). These changes always need to be merged into 3 other product types: Standard, Lite, and 4. So every time we have to update the current version, it dramatically reduces development focus on 4.
we_are_borg
New Member
Pegasus thats not what people wanted to hear but thank you for being honest that development is slow because of supporting the older versions. I hope version 4 comes soon so that we can enjoy that version.
vBulletin made a mistake in naming them CMS content types (and requiring vBCMS to rebuild them). vB customers who only bought the Forum and not the Suite still have database records for content types that keep track of group messages, PMs, posts, etc. These are all separate content types, and they don't really affect the CMS. It will be the same with VaultWiki 4.
A
Arkham
Guest
"Content types" are vBulletin/Suite-based, not "CMS-based". The CMS articles for example are one content type. I think pretty much the only content type, as the forum posts etc. have not yet been refactored into content types.
Their lethargic development of content types is my single biggest gripe to date. Still. I haven't been back here for a while, but I can safely say that the development of VaultWiki towards content types is promising. At least *someone* is moving forward.
Their lethargic development of content types is my single biggest gripe to date. Still. I haven't been back here for a while, but I can safely say that the development of VaultWiki towards content types is promising. At least *someone* is moving forward.
we_are_borg
New Member
Want to know the same because in April it was said to be soon and its now September and still nothing. They have one set back at another it seems.
First, let me apologize to everyone, especially those who've been waiting to purchase VaultWiki or migrate their sites because they've been waiting for VaultWiki 4.
In April, we had to wait for CKeditor (for vBulletin) to be released. CKeditor wasn't released until June. It took until July to get VaultWiki working fully with CKeditor, so we could get back to VW4 development. I'm not sure how many people missed this information when it was going on, but that's where the April date went. However, at that point it was July and everyone usually takes their vacations then. So in the past 5 months, we've had a solid 1 month of development on VW4 itself. Which is, honestly, just terrible.
Customers aren't happy, and our owners aren't happy. We're now behind schedule on a lot of things at the company because of these delays. But there is an end in sight. The tracker for Alpha 1 is pushing 90%, and my personal task list for the release has been reduced to about the size of one sticky note. With the exception of 1 or 2 items, we've finished pretty much all the front-end stuff now. Just need to convert plugins and templates to the new code format, and do a round of basic testing.
We really want to get this out before the 1 year mark since development began, which is less than 20 days from now. I don't see why we shouldn't be able to achieve this, as long as nobody else takes a vacation before then. However, the tracker target hasn't been adjusted as this isn't "official" word. This is just my impression based on how we're all feeling and where we're at.
In April, we had to wait for CKeditor (for vBulletin) to be released. CKeditor wasn't released until June. It took until July to get VaultWiki working fully with CKeditor, so we could get back to VW4 development. I'm not sure how many people missed this information when it was going on, but that's where the April date went. However, at that point it was July and everyone usually takes their vacations then. So in the past 5 months, we've had a solid 1 month of development on VW4 itself. Which is, honestly, just terrible.
Customers aren't happy, and our owners aren't happy. We're now behind schedule on a lot of things at the company because of these delays. But there is an end in sight. The tracker for Alpha 1 is pushing 90%, and my personal task list for the release has been reduced to about the size of one sticky note. With the exception of 1 or 2 items, we've finished pretty much all the front-end stuff now. Just need to convert plugins and templates to the new code format, and do a round of basic testing.
We really want to get this out before the 1 year mark since development began, which is less than 20 days from now. I don't see why we shouldn't be able to achieve this, as long as nobody else takes a vacation before then. However, the tracker target hasn't been adjusted as this isn't "official" word. This is just my impression based on how we're all feeling and where we're at.
we_are_borg
New Member
Pegasus any update on VW4 like you said in September there where holdups but its now almost 2 months later and still nothing. There seems to be an Alpha build to see on errors reported but in a few months it only seems that minimum work was done or that the tracker is not updated. Its getting later and later but no solid time frame is given when the beta will be released or even the RC version.