XF 2.0

[ACL]

Cheers for the interesting insight, thanks pegasus

[ACL]

The Fraola table function is very nice as well.

And coming to Xenforo 2.1!
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...

[ACL]

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!

[Alfa1]

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?

[pegasus]

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.

[Alfa1]

I think that is a good decision. Do you have a target for full compatibility with XF2.1? i.e. a specific VW version?

[Alfa1]

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?

[pegasus]

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.

[pegasus]

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/

[expanserpb]

Xenforo 1.5 runs out of security support December 2019 so that's not a hard limit for most people to migrate.

[hollosch]

I'm running XF2 and waiting for the "update".

[ACL]

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).

[Alfa1]

Now that you have seen XF2.1 are you going to make VW4.1 compatible with it?

[ACL]

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.

[pegasus]

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.