Morning!
I just wanted to ask if you were planning on updating VaultWiki to XF 2.0?
Cheers,
dvsDave
Printable View
Morning!
I just wanted to ask if you were planning on updating VaultWiki to XF 2.0?
Cheers,
dvsDave
Yes, we plan to support XenForo 2.0, although I can't yet provide a timeline for release.
I had the same question. I think most vb 4.2 owners are going to switch over.
I think many vb3 and vb4 owners will switch over now that vb3/4 is no longer supported nor developed. But do mind that it will take a very long time before xf2 is stable and most addons upgraded. Certainly not this year.
What you are seeing on xenforo.com is the developer preview. Not the beta. Not gold.
That's good to hear! I don't have any plans to upgrade my copy of Xenforo to XF2.0 this year, but I'd hope this will be possible around mid-2018 without losing VaultWiki compatibility :).
Would an XF2 edition of VaultWiki initially be focused feature parity with XF1 or could there potentially be some XF2-style improvements too? Would 'live' wiki header previews be possible? This kind of thing would certainly improve VaultWiki's casual usability, I think. But I'm not sure how much flexibility (if any) there is with extending Xenforo's WYSIWYG editor.
Inspired by XF2's new hyperlink editing UI I've created a mockup but it might not be technically possible with the Xenforo editor, I'm not really sure.
Attachment 1619
Or perhaps a heading level drop down menu would be appropriate?
Attachment 1620
I suggested a change to how wiki headings work in the editor earlier (issue 5073, suggestion 3) but on reflection an approach like I've suggested in this post would be cleaner, I think...
Just ideas. :)
For what it is worth, Xenforo 2 has moved from Redactor to the Froala WYSIWYG editor (source), so it is most probably too soon to know if (and how) Xenforo 2's implementation could be extended. That said, the default Froala does have built-in heading (well, paragraph) styles (disabled in Xenforo).
The Fraola table function is very nice as well.
Not the beta. Not gold.
If there are no surprises between now and then, I would expect a public Alpha some time in Q2 2018.
Trust me: you do not want rushed software. It took years before VW4 worked well. I hope that pegasus will take any time he needs to do it well.
You can see how VW4.1 is doing: https://www.vaultwiki.org/forums/
ETA ~10 weeks.
Out of interest, could I ask what the 4.1.x progress sidebar ETA is counting towards? For instance, an initial alpha (4.1.0 Alpha 1), or some other ensuing Beta/RC release? Thanks :)
If VW 4.1.x is stable by end of September then I hope to migrate over to XenForo 2 in October. Otherwise, I will defer the upgrade until first half of 2019. November-January is when my Christmas-related site is at its busiest, so I avoid non-essential site updates during this period.
ETA is counting towards public Alpha, based on estimated time for completing various tasks, rather than a specific deadline.
Cheers for the interesting insight, thanks pegasus :cool:
And coming to Xenforo 2.1! :D
https://xenforo.com/community/thread...1/post-1287385
The question is (and without XF 2.1 available I don't expect there's an answer), would VW's table bbcode still be separate, as the syntax is different - '|-' instead of '[tr]' etc...
As for VaultWiki's bbcodes in general, it appears the new XF2.1 editor manager will support custom addon bbcode buttons:
https://xenforo.com/community/thread...1/post-1287402
Which if one day implemented by VW, this would appear to allow for reordering the buttons on the XF2 version - moving them into a "wiki" menu or whatever. Sounds interesting, anyway! :)
XF 2.1 brings quite a lot of interesting features that apply to VW. @pegasus does this change the time line for VW4.1 ?
I see the forum index lists a 2 weeks ETA. Is this correct?
We are not going to delay VW 4.1 in order to wait for XF 2.1. We did that in the past with another version, and it ended up being a mistake. It should be noted that there is not even a developer preview of XF 2.1 available at this time. Since XF 2.1 will be not be a major change over 2.0, we will add integration with various features that are new in 2.1 over time, as we have in the past with XF 1.3, 1.4, and 1.5. Our goal is an initial release that will at least have feature parity with the current VW versions running on XF 1.0.
The forum index is correct that there are about 2 weeks of development work left on VW 4.1 at this time.
I think that is a good decision. Do you have a target for full compatibility with XF2.1? i.e. a specific VW version?
VW4.1 now has 400 days of development. The forum index now keeps displaying 1 week left for several weeks. What's the status now? Are we getting close to a preview or beta?
The index is accurate in that the install/upgrade process is currently being tested for bugs. After that, the last step is packaging (updating the download script here).
Once packaging is done, we will be updating this site for a preview, and start posting some Have You Seen type news. Timing of a public alpha will depend on the success of the updates to this site and the demo.
I should mention here that XenForo 2's CLI add-on:install and add-on:upgrade has a major flaw and should not be used until the issue is fixed. We will need to add a severe warning to the VaultWiki installation instructions.
The flaw can leave a forum in an unusable state, until class-extensions and code-event listeners are disabled via XenForo's config.php.
https://xenforo.com/community/thread...eption.157346/
Xenforo 1.5 runs out of security support December 2019 so that's not a hard limit for most people to migrate.
I'm running XF2 and waiting for the "update".
I'm still on XF1.5, as a wiki component is a big deal for my forum :). Fingers crossed I can migrate over to XF2.0 (or perhaps even straight to 2.1?) in January or February. This'd be 2 years since migrating to XenForo in the first place which in itself was a big improvement over thre previous environment (SMF).
Now that you have seen XF2.1 are you going to make VW4.1 compatible with it?
XF2.1 compatibility would be fantastic, even if not for the initial VW4.1 alphas. And by compatibility I mean just work on XF2.1 without errors, but not necessarily support/implement the new features (reactions, FontAwesome 5 etc). Having said this, I've updated some of my site-specific addons to XF2.1 and the conversion from XF2.0 likes to XF2.1 reactions wasn't that complicated thanks to the included helpers.
Depending on how this pans out, I may upgrade from XF1.5 straight to XF2.1 after the beta period is over.
We will not delay VaultWiki 4.1.x in order to add support for new XenForo 2.1 features, but will add support for some throughout the 4.1.x beta period. But XenForo 2.1 should still be able to run the initial VaultWiki 4.1.x release, unless I have missed something.