Is 4.0.25 still planned?
Printable View
Is 4.0.25 still planned?
Yes it would seem so, based on a reply in issue #5588: https://www.vaultwiki.org/issues/5588/ :)
As for 4.1, is there some kind of plan when it comes to the Alpha (then Beta) releases? For example, would it be safe to assume an Alpha 2 could drop around a month after Alpha 1, then Alpha 3 in another month, etc? I'm hoping for a 4.1 stable milestone in Q1/early Q2 so that I can migrate my XF1 site over to XF2.x (maybe 2.1?) soon after, with VW intact, enabled and accessible etc. But let's see what happens as quality programming and testing can't be rushed. :)
Our typical release schedule early in a branch's life is releases every 3-5 weeks. We do not place an upper limit on the number of Alpha/Beta releases. We're doing intermediate builds this time around, so I expect the Alpha/Beta period would span fewer releases than last time (4.0.x), since there is shorter wait time between some fixes and test feedback.
With XenForo 2.2 coming up within a month or so, do you anticipate VW4.1 to be compatible with XF2.2?
Based on the HYS articles posted so far, I don't see anything that would prevent VaultWiki from working correctly or that would cause any issues. However, there may be an unexpected bug or two that we would not be able to know until XF 2.2 is actually released.
Note that new XF 2.2 features, such as Writing Before Registering, would not be available for wiki content until XF 2.2 is in hand and the feature can be added, likely in a future branch like VW4.2.
Is PHP8 compatibility planned for the next release?
Yes. The update looks fairly straightforward, from where the product is now. We intend to support PHP8 starting in 4.1.2.
Note, however, that PHP8 compatibility would only be possible if you are using XenForo 2.2.2+.
Other platforms/versions are not PHP8 compatible, and VaultWiki support for PHP8 in those cannot be guaranteed as a result.
So will 4.1.2 also work on xf1 on php7?
Yes, we would not remove support during a minor release.
XF1 will continue to be supported until VW 4.2. But with XF1, you should not upgrade to PHP8, because XF1 will throw errors in that situation.
Yes, I know. I can only upgrade xf2.2 to PHP8.
XenForo 2.3 will support PHP 8.3
I will be running VW installs for XF1.5(PHP7.3) and XF2.3(PHP8.3)
Its early days, but once you know what your plan for PHP and XF2.3 support will be, please share your thoughts on this.
It seems like adding XF2.3 support may be some challenging.
https://xenforo.com/community/forums.../?prefix_id=53
There are a number of other things mentioned so far that will probably require minimal code tweaking.
I haven't seen anything in the PHP 8.3 RFCs yet that would suggest any backwards incompatibility over 8.2, which we believe should be fully compatible soon (although I think XenForo 2.2 still has some issues there).
I don't see any issues really involving the new option for dark themes. We would probably need to tweak some style properties to accommodate the fact that it can only be applied to color properties.
There could be potential issues with our ability to choose arbitrary font-icons for the wiki page icons, since XenForo is changing how FontAwesome is loaded, depending how they implement that change.
Mainly, XenForo 2.3 intends to stop using jQuery. This would mean basically all our Javascript needs to be rewritten depending on the direction they go, as our XenForo-related scripts are written in jQuery. On top of that, this would delay VW 4.2 further, as we had already moved completely to jQuery for that version. That will be a particularly painful transition for us.
Until we can get our hands on the new XenForo code, it will be hard to know for certain the scope of changes, if the anticipated changes are truly that breaking, and how long it would take.
Although the Xenforo devs don't recommend it, you could always bundle and load the needed jQuery library on the Wiki pages to not need a rewrite...Quote:
Mainly, XenForo 2.3 intends to stop using jQuery. This would mean basically all our Javascript needs to be rewritten depending on the direction they go, as our XenForo-related scripts are written in jQuery. On top of that, this would delay VW 4.2 further, as we had already moved completely to jQuery for that version. That will be a particularly painful transition for us.
But I would prefer it if we didn't rely on jQuery as it is not really needed nowadays and just adds extra to the page load...
Also, doesn't YUI provide similar features that jQuery does? if so you could probably port the code to use the YUI equivalent...
Although it would probably be best to use vanilla JS for the things needed when doing a rewrite, I mean why make your software dependent on another JS library :D
Page speed is very important for SEO, so it would be optimal if jQuery could be ditched. Especially since VW is loaded site wide.
The new Heading page anchor links in 2.3 are nice. I hope VW will support these and that you will migrate from the old functionality to the core functionality.
https://xenforo.com/community/thread...ro-2-3.217243/
I wholeheartedly agree. jQuery doesn't have a place in modern web design, especially when Vanilla JS works so well across modern browsers.
XF has finally gotten their pagespeed things in check :) https://xenforo.com/community/thread...ro-2-3.216767/
----
@pegasus, have you tried XF2.3 Beta 1 with VW yet?
I know it is still early, but I would rather not have to wait too long to install XF2.3 once it is released due to some pending bugs with VW.
And I would also not want to be the "test rabbit" that has to report all the bugs once it is out :)