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?
Printable View
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?
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.
OK, and when it will be ready you think?
With content type do you mean a CMS content type?
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.
Are you talking CMS content types? When we actually do upgrade to vaultwiki 4 how will it affect the data we have already created?
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.
Will it be possible to place CMS widgets on the same page as VW4? Or place VW within the CMS?
That would be a great benefit.
"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.
Any updates on the status of vaulwiki 4?
Where is the development of VW4 at? Is a beta to be expected in the near future?
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.Quote:
Originally Posted by Alfa1
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.
So you expect the first beta could be out within a month?
are you releasing 3.0.14.003 first before VW4 since you have been talking about the 003 build? and when would we expect either of the two?
Should be published now. Please check your Members Area.
cheers, will run a full conv again tomorrow
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.
I have to admit I'm disappointed that we haven't heard anything. I need vaultwiki for my site but if all updates stop I don't know if I would renew again.
I removed VaultWiki from my forum recently. Sorry, I can't wait forever.
Im getting worried about Vaultwiki4.
If it continues like this i will be better off using a other solution its been weeks for good solid updates and if they say dates it does not mean anything at all because it seems that every time something happens. Going to see if using a normal wiki is possible almost waiting a year on VaultWiki4 now and still nothing to show for.Quote:
Originally Posted by Alfa1
I recently switched from mediawiki to vaultwiki, although i have had some major issues converting everything (i wont recomment converting pages if you have a large mediawiki install with loads of extensions) I must say i am pretty happy with vautwiki compared to mediawiki.Quote:
Originally Posted by we_are_borg
the most important thing for me was the flawless integration with vbulletin. VW does that very well.
I dont see a reason why you would "wait" for vw4 while this version is just fine.
The only thing where i am worried about is that in two months i got soo much custom code.. what will happen once it comes :)
Many features that I really need will be in VW4.Quote:
Originally Posted by Lord Doys
Most of those are integration functions, like reputation for wiki edits, better notifications, suggest post to wiki, etc. Such features would be of great benefit to my community and to wiki use on my site. If VW4 has hit some major roadblock or if it is not coming, then I need to consider alternative options, like custom development.
VaultWiki 4 is still coming. It has not hit a major roadblock or something like that. I've been hesitant about giving dates because I know it is very difficult to judge once all things are considered, and I tend to be wrong.
There are many factors involved, but as I've mentioned in the past, development is slow because it's a completely separate product branch. All the code (so far) is new. We don't have the resources to develop multiple branches at the same time at the rate our customers have become accustomed to, and this is something we've had to deal with for the past year. It's one of the reasons for the upcoming discontinuation of the Standard License with VaultWiki 4.
Whenever we get a lot of bug reports for VaultWiki 3, it takes time away from 4 (and we usually have to spend additional time re-engineering the changes for 4) - we can't just ignore bug reports. This is not to blame anyone for posting bug reports, it's a major part of the formula that keeps the product moving forward, but it's a huge factor.
As I mentioned last time, VaultWiki 4 is close to Alpha release. I'm not sure why, but it seems like people believe there is no activity in the VaultWiki 4 milestones on the site. This is just not true. If you're looking at Active Issues, you may not see much activity, because this is a list of items we haven't gotten to yet. But if you compare that list to Total Issues (https://www.vaultwiki.org/milestones/9/list/), you'll see that we are indeed making headway daily. I feel like I've mentioned this before, but if you're ever in doubt about development activity, just look at that list, or the tracker in general.
We've tried to have more transparency about where we are in the process using the tracker and additionally on the forum home page. There's a widget "VaultWiki 4 Progress" that mentions the feature we're currently focusing on that day, and additionally, how many new files have been added to the product between VaultWiki 3 and VaultWiki 4. If it's hard to comprehend, once you finally see the file system in the /vault, you'll realize that VaultWiki 4 is just immense.
Let me also mention that VaultWiki 4 will probably disappoint some people initially with the Alpha 1 release. It's mainly a back-end update, so you won't notice many visible changes or new features except with some content types that required a new architecture (like redirects or attachments). That doesn't mean new features won't be coming shortly afterward, but we're trying to keep the first release as simple as possible since the code will be almost completely new. You can get an idea of what's in Alpha 1, again by just having a look at the tracker.
Of the ones Alpha1 mentioned, VaultWiki 4.0.0 Alpha 1 does include (already) better notifications - for both moderators and subscribed users.
For users waiting for VaultWiki 4 to switch from vBulletin to XenForo or IPB, keep in mind that you can always run both side-by-side until your platform is supported. It would be akin to running a separate standalone wiki for the time being - you wouldn't have the added difficulty of trying to find a way to export the data without losing your current wiki configuration, or the hassle of reposting everything.
If some of the phrases in the milestone were confusing I have changed the phrases:
'active' to 'unresolved'
'completed' to 'resolved'
Well, as you know (and you are active on vb.org as well) no solution is per se 100% of your "needs" and alsway need some kind of modification. And the strong part of vbulletin is the whole vb.org community.Quote:
Originally Posted by Alfa1
I also think VW lacks of some functionality and flexibility, but that doesnt hold me back on using it, or indeed what you say: custom development (MODS!) .. i have rewritten lots of stuff in VW to fill my needs
One thing i really miss here on VW is the "vb.org" community.. other VW users creating mods for VW.. share your cutom VW code or ideas with the rest of the users.
Thats why i asked for Modwriting guidelines recently.
I believe the power lies in the community with mods using the VW framework
That would indeed be beneficial.Quote:
Originally Posted by Lord Doys
Thanks for the update Pegasus. It had been so long I was worried the project had gone under. I'll keep waiting.
It's very big project and I know that many of us are impatient. But, on the other hand, I think that it is more important that project is done well than fast.Quote:
Originally Posted by pegasus
I have working VW3, it works fine and I could wait for VW4.
If only you could post more news, what's happening, things like that? I mean, more things in words that would mean more to us all. I know that tracker shows updates, daily activity, but news updates would be probably appreciated from all.
And yes, I'll stick with VW, it's best wiki for vB there is.