Issue: Upgrade to 2.5.1 hangs

Hi,

i had the same the problem. Disable VaultWiki manually and run step 2 again did work for me. But i had a second hang at step 5 in the second installation part and get the following message:
I turned manually to step 6 and after that enabled the wiki manually (also the "wiki-addons") and rebuild the namespaces. Than i changed the wiki number in the addon-manager back to 2.5.0 and run step 5 again. Now the stylechanges were performed and i renamed it to 2.5.1.
For the moment it seams to work. If there was something wrong i did it will be nice to read what.
It is unfortunately a long time ago, that a update went through without problems.

Normally you don't need to disable VaultWiki on your own because the upgrade script does this. However, once plugins are re-imported we can have conflicts again.

We always test the upgrade script on our sites before making the ZIP available. We were happy to see this time that there were no immediate issues, but it appears that afterwards, when the ZIP was formed, that the correct version of the plugins file was not included.

You can complete the upgrade by disabling VaultWiki, downloading the ZIP again, replacing: vault/install/ces_nwsp_spec-plugins.xml
And navigating to: /vault/install/finalupgrade.php

That's clear, but disable the Wiki was the only way to get the upgrade run further, hanging at step 2. And than the upgrade run further just like the same as with the new ces_nwsp_spec-plugins.xml. And also with the new xml it hangs at Step 5 with the same message and i had to enable the wiki manually and than it went further to the end. As i said, just the same. Only rebuilding the namespaces i did this time after all Steps.

Since 2.3.0, rebuilding namespaces should not be necessary in the upgrade process. Is there any other reason you did this or was it out of habit?

At the first time (with the "missing" step 5) i get the message "only admins....." when trying to look at the forum. After rebuild the namespaces the message was gone away and i could see the wiki with little problems in the style (without Step 5 nothing else was to expect) and so i run Step 5 again (with changing the Wiki-version number).
Rebuild the namespaces when upgrade with the new xml was without looking - "just did it"

Okay thanks, I think that you had to rebuild was because of the workaround that was needed with the old xml file. For users who are upgrading to 2.5.1 after you noticed the xml issue, I don't see this being necessary.

Just for info: Upgrading the Live-Forum with the corrected zip runs without any probelms during the upgrade-process.
And you're right rebuilding namespaces wasn't necessary after that.

Greetings
Storyteller