Issue: Upgrade from 4.0.25 to 4.1.1 (XF1) stalls at Step 69 (27%)

Hi pegasus,
I had to postpone the migration due to other obligations and now I'm back on track.
I had to translate the language XML first into German and was not happy with it. Please try to reduce it in later versions. It is rediculous big and has still not caught all translatable phrases.

As of the upgrade: I got stucked exactly where is has been described in issue 6197. I got the database error immediatly. I changed the Setup.php as recommended in the issue. The ugrade starts but did not come to an end. After about an hour, I broke it. It must be some infinite loop. Unfortunately, the Web upgrader of XF2 dosen't show any written progress, just dots. It is just the 4.1.1 XF1 -> 4.1.1 XF2.
I have no errors in the logs.

How can we proceed? VW is just one piece of the upgrade and it makes the most hassle.

Cheers

Unfortunately I have not experienced this infinite loop in any of my own tests. It might be limited to certain data or certain configurations. If you are experiencing an infinite loop, please file a ticket so we can investigate your situation and finish your upgrade: https://www.vaultwiki.org/members/?do=newticket

Ticket is open.

I do stop the last attempt of upgrading now - after 1h 03 minutes.

Cheers

By going back to ACP I got this error message:
DEBUG: vw_enabled - Callback vw_XenForo_Option_Enabled::renderOption ist ungültig (error_invalid_class).
ist ungültig means is not valid.

Fixed the infinite loop on your site and completed the upgrade. You should download the latest patch if you need to apply the code changes to another installation.

This occurs when the forum had VaultWiki 4.1.1 on XenForo 1.x already, upgrades to XenForo 2.x, then upgrades VaultWiki to the XenForo 2.x version. It occurs due to a difference in naming conventions between some database tables starting at 4.1.1 depending on the forum platform. When selecting which naming convention to use, simply checking the version number was not enough. We also needed to check the last recorded platform version.

This correction has been applied to the July patches for 4.1.1 and 4.1.2 respectively.

So, I understand that the recommendation is now to get the patch for 4.1.1, upload it and try the upgrade again?
No rollback necessary or other things to consider?

Cheers

I would recommend downloading the patch and trying again from the previous state (XenForo 2 with VaultWiki for XF 1). Right now your test is already running VaultWiki for XF 2, so it would have no changes if you did that. If it works this time, you should be safe to upgrade your main site.

Ted,
I was able to upgrade, took less than 2 minutes.
Thanks for your support.

In order to upgrade to the latest version, do I have just repeat the procedure with uploading all files in "upload" and restart in ACP?
I'm not sure whether something might have changed in XF2

Cheers

Yes just upload, then go to AdminCP > Addons, and click the Upgrade button next to VaultWiki.
If you made a custom library/vw/config.php file (had some hidden settings), you might want to make a custom src/addons/vw/vw/config.php

A lot is different between XenForo 2 and XenForo 1 generally. But in VaultWiki, these come to mind:
- Wiki "Sidebar Blocks" are now handled by AdminCP > Appearance > Widgets.
- The wiki Integration panel (for putting wiki areas in the forum list) is now handled by AdminCP > Forums > Nodes.
- BB-Code settings for displaying wiki BB-Codes in the editor are now handled by AdminCP > Content > BB code button manager.