Will we get VW update for XF2 for Christmas?
Printable View
Will we get VW update for XF2 for Christmas?
Fingers crossed.
I hope you've had a great Christmas, pegasus! :D
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
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.
Is the xenforo demo also updated to vw4.1?
Is there a xf2.1 demo?
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.
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).
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!
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.
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! :cool: :D
Attachment 1644
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 :).
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.
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.
All good, and awesome about the widgets as it gets site admins flexibility of what to put where :)
This may be of some assistance: Changelog for 4.1.0 Alpha 1
Just a few more things to try out before giving it the rubber stamp for release.
The Alpha is now public to download. Please do your diligence, backup your database, and use it in a test environment first.
If you will use it with XenForo 2.0, remember that only 2.0.x is compatible at this time; there may be issues on 2.1.x.
If you wish to install using XenForo 2's CLI add-on installer, make sure that you are using at least XenForo 2.0.12. Due to a bug in earlier versions of XenForo, the CLI installer will fail to install VaultWiki and damage your forum installation. I have not personally confirmed that the fix is working in 2.0.12, but the fix is listed in the changelog for that version.
If you encounter installation issues on XenForo 2, the installer progress log is saved to a file in internal_data/vw_logs
The importer is not included in this alpha.
Happy New Year!
I would be interested to know if the Version Check link in the AdminCP shows that build 002 is available, and if you can pull up the changelog from there. This screen updates once every 24 hours, so you can try running this query if you think the screen might be stale:
In the past, some users weren't sure whether they should update to a new build -- now you can check what's in it. The changelog is always tailored to the build you currently have installed. If it's working correctly, only items that are broken/not available on your build will appear in the changelog. (So once you update to build 002 you won't be able to test this again for a bit).Code:DELETE FROM vw_log WHERE logtype = 'changelog'
Version check does appear to be working :)
Attachment 1647
Are the head links (.vw-head-links) customisable at all? I'd like to remove/disable the section 'top' links, since XF 2.0 has its own floating top button.
If this isn't currently possible, I could create a feature request.
Good point.
There is a feature request for that: https://www.vaultwiki.org/issues/5156/
Feel free to bump it so we remember to handle it during Alpha.
Thank you for posting the screenshots. It showed that our version check response was incorrectly omitting some changelog entries. Now that we've corrected it from our end, you can clear the log to see what I mean:
Code:DELETE FROM vw_log WHERE logtype = 'changelog'
Yep, I see now :). I'm locally running build 002 at the moment. I can wait for build 004 before doing an upgrade, to see what sort of information version check reports with 2 new versions.
Below is an attachment showing how version check is looking on b002 with b004 available to download.
The overlay is showing changes/fixes for the two newer 003 and 004 builds and the blue button at the bottom specifies b004 is the latest.
The main version check window is showing b003 as the latest though.
Wow, I wasn't expecting any XF2.1 tweaks so soon! :)Quote:
Originally Posted by pegasus (in issue 5513)
So far I've been testing VW 4.1 Alpha 1 and XF 2.0. Once Alpha 2 is released would you prefer testing (and reports, if any) to remain XF 2.0 focused or would it be worth testing with XF 2.1?
As soon as XF2.1 is released, XF2.0 will be essentially dead. Quite a few developers have set the minimum xf version to 2.1 even before 2.1 stable is out.
On the Special:RecentChanges page, a couple of XF2 points for discussion (I wouldn't call these bugs):
1. Is there a need for the per-change Options menu to have the "menu--wide" class? With just the "Compare to Previous" and "View history" options I think this looks nicer in the more compact menu format. Even with "Report", "Undo", "Purge", it would still look better without the menu--wide class, IMO.
2. Within the "Filters" menu, the submit button "Go" would better match stock XF if this instead said "Filter" ... IMO.
:)
I know that you intend to implement the new XF2.1 features (FA5, bookmarks, reactions, Push, API, etc)
Are there any plans to implement the XF2.0 features? (custom fields, CLI upgrade)
Especially custom fields is a major step forward.
CLI upgrade is already implemented. We do plan to implement other 2.x features.