XF 2.0

[pegasus]

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.

[pegasus]

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!

[pegasus]

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:

DELETE FROM vw_log WHERE logtype = 'changelog'

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

[ACL]

Version check does appear to be working
vaultwiki-xf2-admincp-versioncheck.jpg

[ACL]

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.

[Alfa1]

Good point.

[pegasus]

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.

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.

Version check does appear to be working

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:

DELETE FROM vw_log WHERE logtype = 'changelog'

[ACL]

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.

[ACL]

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.

[pegasus]

The main version check window is showing b003 as the latest though.

Sounds like it's working properly with the exception of this, which is expected being that you're on build 002 currently and the changelog for build 003 includes:

changelog cache doesn't expire simultaneously w/ version-check

[ACL]

This is now implemented in Alpha 2. In XenForo 2.1:
- The font-based icon chooser separates icons by FA5 style and allows selection of the Free icons in each of those styles.
- Editor buttons are now grouped using the Button Manager, rather than a BB-Code's Wiki-Related Options. Code updated where necessary so that wiki buttons still appear and work as expected.

Wow, I wasn't expecting any XF2.1 tweaks so soon!

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?

[Alfa1]

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.

[ACL]

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.

[Alfa1]

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.

[pegasus]

CLI upgrade is already implemented. We do plan to implement other 2.x features.