Issue: VW4 Gamma 5 Upgrade Crash

Ok, that got the installer to run successfully -- thank you for the quick and helpful replies!

I'm not finding anything just yet... you mean I would find problems in the default "System" and "Wiki Pages" areas?

Based on one of the errors, I thought there might be 2 of each. If not, then you're good.

The "Wiki Pages" area is there to get started. A lot of new users didn't know they had to make an area before they could post wiki pages, so we start you off with one now.

The "System" area will be used internally by some features in future releases. There were also issues in previous releases where admins might run the wiki importer with no wiki areas and some data could not be moved because no valid targets existed yet. The system area would resolve these issues as well. It should be impossible to delete, but if you are able to, please post a bug report.

Otherwise, this release should mainly just be fixes for the last 3 weeks of bug reports, so you should be able to test those previously broken things more completely now.

A question---

Since going to Gamma 5, I've noticed that VW-related options are no longer present in the vB built-in "Form Activity" sidebar block or "Activity Stream" settings?

... is this a Gamma 5 thing, or could it be related to my installation issues?

For instance, I thought I remembered seeing a checkbox or two in AdminCP->Activity Stream setttings for wiki content, but now I don't.
Also, I no longer see any wiki-related forum block type to add, in the vB Forum Blocks Manager.
Moreover, previously if I had "All Content" checked in the vB "Forum Activity" sidebar block, it would try to show some wiki content on the resulting front-end forum block, but now it doesn't, not at all?

Basically, it looks like some fundamental integration thing, as such, isn't working or configured properly somewhere? Whereas I remember this stuff "just working" or "just there" on Gamma 4?

Widgets and vB Sidebar blocks are only installed if VaultWiki detects that the vBulletin CMS is enabled. They should still get installed if it's disabled, but installed. Since that doesn't happen, it's a bug. I would recommend enabling the CMS during the VaultWiki install/upgrade process until this issue is resolved.

Additionally, there is a bug in vBulletin where vBulletin doesn't remove the activitystreamtype records for a product during uninstall. This is unexpected behavior since vBulletin's uninstall process automatically removes records that are associated with it (notably, the package record). If these records are not removed, the IDs will not match the new package record during a re-install. It seems like vBulletin 4 will not be getting updates soon, so we cannot expect them to fix this bug. Even if they do, we have to accomodate users who would not be using vBulletin's newest version. We will have to add a step to the uninstaller to account for this.

After you uninstall, remove rows with .. section = "vw" .. from the activitystreamtype table to clear the outdated records. After re-installing you should completely rebuild the activity stream to remove any old cached entries as well.

No, I did not. They were gone after I uninstalled and figured that was that.

See above, I did a bit more investigating.

Thank you very much for the insight.

I've uninstalled, purged remnant activitystreamtype records, re-installed and rebuilt the activity stream cache.
It went very smoothly this time and seems to have resolved many of my initial problems.