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.Quote:
Originally Posted by Alfa1
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 :)
We have a XF 2.3 test site and we have mapped out the code changes it has introduced. We are currently in the process of working through the showstopper issues (if you have current VaultWiki enabled and you update to XF 2.3, your forum will break immediately due to incompatible changes).
How is VW for XF2.3 coming along? XF2.3 RC4 has been released and has some changes for addon compatibility:
https://xenforo.com/community/thread...ported.222390/
Yes, as you noticed with that link, XenForo 2.3 has been a bit of a moving target for developers. Each 2.3 release so far has had major changes from the last, sometimes to things that were only introduced in 2.3. We already need to have 2-3 variations for a single content-type handler class, due to multiple callback signature changes between betas. It has made supporting it before a final release nearly impossible. But rest assured we do review each release candidate as it comes and make changes to our code base in response.
At least now XF2.3.0 is out and it's no longer a moving target.
Yup its out and I have a test site running (took the opp to upgrade back end architecture into a VPC whilst I was at it)
How are we looking?
Finally looking good. Just have work out the kinks when using the new Embed system to embed wiki content anywhere (embedding into wiki content finally seems stable). Once we're satisfied with the results there, we should be able to package this for release.
Awesome, thank you!
All that's left is to build and test the package for release. This usually takes a day or two. Thank you all for your patience!
How are VW4.2 or 4.1.9 coming along? Can we expect a new release in the near future?
We had been waiting for XenForo 2.4 to release as it was estimated for as early as 5 months ago. In the past we have made a release and then a few days later XenForo made a surprise big update, which tends to confuse customers. But it did not work out that way this time. From what I can see, 4.1.9 is otherwise a relatively small maintenance release. We could put it out in a week or two if there is no news from XenForo by then.
As for 4.2, development has been going steadily for the past couple of years. We have had incomplete builds running on a few of our parent company's sites live for a long time now, so it should be pretty stable when it finally releases. There aren't really any major architectural changes from 4.x, just a bunch of features that were requested a long time ago.
As I'm one of the few people who've had a chance to use it live so far, one of the most exciting features for me personally has been the ability to make custom wiki URLs, from the domain, to the path, to the name. Note this brings back some of the old VW3 ability to have multiple domains in one wiki. I feel like this ability alone makes it a worthwhile update, but I know there are still quite a few other features slated that still need work.
I think its important to recognize that the XenForo release cycle has changed to an ongoing process where HYS keep getting posted, devs are working on multiple versions and there is no clarity of when or what the next release will be. We don't know how many HYS there will be for XF2.4, XF2.5, etc.
And when Kier finishes XF3 then that release will be next instead. It could be next month, but also in some years.
With the new release cycle there will always be an upcoming release to wait for. ad infinitum.
No matter when you release, Murphy's law is likely to strike again.