XF 2.0

[hollosch]

Will we get VW update for XF2 for Christmas?

[pegasus]

Fingers crossed.

[ACL]

I hope you've had a great Christmas, pegasus!

A question regarding the XF 2.0 version of VaultWiki: What kind of approach has been taken when it comes to FontAwesome support ... are you using XF's *.less fa variables or just directly referencing the unicodes? If you've adopted XenForo's FA variables in *.less templates then VW for XF 2.0 may partially support FontAwesome 5 on XF 2.1. More info in last paragraph: https://xenforo.com/community/thread...1/post-1287380

[pegasus]

Thanks; we had a great Christmas here. I hope yours was too.

VaultWiki's FontAwesome support references the unicodes directly. We did not majorly change this or develop a different approach specifically for XenForo 2.

Since someone will undoubtedly ask about progress: This site has been running VaultWiki 4.1 since the weekend before Christmas. Since then we have been monitoring the logs and correcting any issues that have occurred. A public alpha should be very soon.

[Alfa1]

Is the xenforo demo also updated to vw4.1?
Is there a xf2.1 demo?

[pegasus]

The XenForo demo was also updated to VW 4.1 at the same time.

There is not currently a XenForo 2 demo. We will be upgrading the XenForo demo to XenForo 2 shortly.

[ACL]

Moving forward is the plan to mark the XF 1.x branch of VaultWiki EOL at any point (perhaps in line with official XenForo plans in 2019)? Not that this should affect me as I intend on upgrading my site to XF 2.0 just as soon as VW 4.1 is considered stable on XF 2.0 .

Re: FontAwesome, I guess for the time being if VW 4.1 does run on XF 2.1 without fatal issues I could just change the unicodes via vw_additional.less to XF's .less FA variables for FA5 compatibility (assuming 2.0 branch has moved to less templates).

[Alfa1]

Moving forward is the plan to mark the XF 1.x branch of VaultWiki EOL at any point (perhaps in line with official XenForo plans in 2019)? Not that this should affect me as I intend on upgrading my site to XF 2.0 just as soon as VW 4.1 is considered stable on XF 2.0 .

I hope not. I would love to upgrade to XF2 but its not possible anytime soon because most addons are not yet available for XF2 and I doubt that will happen in 2019. Including some major & essential addons.

[ACL]

I would love to upgrade to XF2 but its not possible anytime soon because most addons are not yet available for XF2 and I doubt that will happen in 2019.

Oh, yes, very true. With VW now being the last of the addons I use without a XF2 version (but clearly on the way) I overlooked this (despite myself waiting through all of 2018 XF1 for a number of addons from other developers to migrate to XF2). A wiki is essential to my site and a different addon may be for you, I get it .

That said, once the security patches cease at the end of 2019, I don't think I'd feel comfortable using XF1 if new security issues were discovered, or if incompatibilities with a future PHP version occur ... without some roadmap for remaining addons identifying if they will move to XF2 at all. Even though XF1 isn't EOL yet, initially seeing the VW 4.1 progress sidebar appear here was quite the relief!

[pegasus]

The XF demo has been upgraded to XenForo 2.0. You should be able to demo VaultWiki there now.

This might have just been an issue for us during launch (different URL for staging vs production), but if you experience security errors when logging in or using AJAX, it should resolve by clearing your browser cookies for the site.

We'll monitor the demo for errors for a couple of days. Barring any showstoppers, we will make the download public for New Years.

If you encounter any bugs in the Preview yourself, feel free to report them. Please do not post feature requests at this time.

[ACL]

The XF demo has been upgraded to XenForo 2.0. You should be able to demo VaultWiki there now.

Yahoo, what a milestone! Look like this NYE won't just be a celebration of a new year

[ACL]

I've just noticed that in XF 2.0 VW 4.1 preview, some of the form fields during editing (page icon, watch content options) have been moved into a collapsed form section block using XF2's toggle click handler. This is awesome! No more site members thinking that the page icon is where proper image attachments go. I guess you could say part 1 of my earlier 3-part suggestion is implemented!

vaultwiki-xf2-editor-collapsed-form-sections-are-cool.jpg

Will there be any consideration for also moving the "treat this page as a..." field to a collapsible form section? Some of my site members in the past have mistakenly thought that at least one of the page types had to be selected. If you'd prefer I can post this as a proper suggestion when you're ready for them .

[ACL]

I do have to say though I'm not a fan of the left-hand side-navigation on page as well as the right-hand sidebar. Is the side-navigation configurable on a per-site basis? Having both at once makes things too cluttered IMO.

[pegasus]

It is using XenForo 2's widget positions. If you don't wish to have anything on the left-hand side on your site, do not assign any widgets to that position. I don't particularly like it either; just wanted to make sure other positions were working.

[ACL]

All good, and awesome about the widgets as it gets site admins flexibility of what to put where