Is 4.1.0b2 suited to migrate to the xf2 version?
Printable View
Is 4.1.0b2 suited to migrate to the xf2 version?
Yes. You can perform this as follows.
1. Already have XF 1.x + VaultWiki 4.x installed.
2. Upgrade XF to 2.x.
3. Re-download the VaultWiki 4.1.x package, selecting the one for your XF 2.x version, and upload that package to your site.
4. In XF's add-ons page, you should now see an option to Upgrade next to the VaultWiki add-on.
Do you still recommend going from XF1 + VW4.0.25 to XF2.1 + VW4.1?
Or is it better to first upgrade VW4.0.25 to VW4.1 and then upgrade to XF2.1?
Either path should work fine. There are fewer steps to upgrade to XF2 first, due to the VW package containing different files for each XF version.
If you upgrade VaultWiki to 4.1 first, then you have to download/upload VaultWiki twice (once for XF 1.x, and again for XF 2.x).
For another site I want to upgrade VW to 4.1 but on an XF1 install. I see that there no longer is a vault folder nor an vault/install folder. Is this correct or am I missing files? Is the upgrade method still the same? Part of the upgrade instructions relate to these folders.
4.1.x no longer has a /vault folder in XenForo installations. However, don't remove your existing /vault folder until you have successfully upgraded.
In XenForo 1.x, you will still upgrade the same way:
- Upload the new files.
- Go to AdminCP > Wiki > Maintenance > Run Upgrade Script.
The config file location has moved to library/vw/config.php. If you made changes to /vault/config.php, you will want to merge your file into the one at the new location.
I see that some of these notes are missing from the online instructions and the READ-BEFORE-UPGRADING text file is outdated (was written for 3.x -> 4.0.x). I've made a note that these need to be improved.
I uploaded the files, then merged the config.php, then started the upgrade script and the first thing that happened was getting a whitescreen. Now my site is down. All I get is a white screen anywhere.
Updated the instructions in the READMEs and the web-based manual, as discussed. Regarding your error, I have added notes about not merging custom VW_DEPOT_PATH values from the old config, as this will cause fatal errors (files not found at that path).