Issue: VW 3.0.2 to 4.0.0 RC1 upgrade error

If you have a lot of data on 3.0.2, I wouldn't recommend doing a clean install. The issue is that you are about 40 versions back, so you are bound to run into problems... the first of which is that we no longer have the upgrade script posted for such an old version.

But you WILL need VaultWiki 4 installed, in order to begin this process. In vault/core/controller/install/db/insert/bbcode/vb3.php, find:
Replace with:
This should get you on your way.

The transfer process from VaultWiki 3 into VaultWiki 4 only supports 1 version: VaultWiki 3.0.20. So while you are getting VW4 installed, I will see if I can find that other upgrade script for you.

EDIT: Looking back at your the registration/purchase dates on your account, it appears more likely that you have VaultWiki 3.0.20 installed, rather than 3.0.2, which is a difference of 18 versions. Please confirm, as it could save me some unnecessary work building another VCS today.

Sorry...yes I got my numbers transposed. It is 3.0.20.

It looks like the text above that I'll be replacing, is the same as the old text?!?

Thanks
Gerry

There should be 3 backslashes \\\ before each " that appears inside the gallery tag. For some reason vBulletin keeps removing them from my post.

This change is applied already in build 003 if you just want to download the ZIP again.

OK, I will re-download. Should I just re-install all the files and overwrite the earlier files I uploaded? My Wiki is still turned off and everything is just as I left it ... new folder created for attachments, Wiki disabled, etc.

If you reupload all the files you should be able to continue where you left off.

Marking this issue as fixed, since it is now possible to download VaultWiki 3 for users who need to update a really old version like 3.0.1, to get to a version that VaultWiki 4 is able to import.

Finally have time to re-install all the files and re-start the upgrade.

OK, I re-uploaded the new VaultWiki files, modified the config.php slightly to remove extraneous (non VB4) lines, and ran the auto-installer script. Everything seemed to install OK, and after deleting the installer directory I was able to access the control panel for the new VaultWiki.

I modified the base URL to be my forum's URL with the wiki extension: http://www.500eboard.com/forums/showwiki.php

When I click on the radio button to turn the wiki on, and click "save" it still stays on "No" - effectively it's not letting me turn the Wiki on.

I tried this both in the new VaultWiki Admin panel, as well as the "Options->Settings" part of the main control panel.

Can you advise on how to force the system to turn the wiki on at the radio button?

Also I am getting the following message at vBulletin when I click on the Wiki button in the top bar:


vBulletin Message
The wiki is currently disabled while we perform maintenance. Please try again later.


Thanks
Gerry

Also, is there anything I need to do in terms of actively importing pages, data, attachments, etc. in to the new VaultWiki so that I can see things displayed?

The wiki will only turn on when there are no data rebuilds in progress that were triggered by a previous setting change. If this takes more than a few minutes, then the data rebuild is probably frozen and you will need to submit a Support Ticket service via the Members area so a developer can find out why and correct the problem.

So far, I have only seen the builder get frozen if there were rebuilds already in progress from an earlier version and the wiki was upgraded to RC 1 while they were still in progress. So if you have a frozen builder on a fresh installation, that definitely deserves a look.

EDIT: It seems the setting value will not save as "Yes", even when there are no rebuilds in progress. In vault/core/model/settings/vw_enabled/vw.php, find:
Replace with:

Yes, you must actively run the import script. See: https://www.vaultwiki.org/blogs/56/#...ultWiki-3-Data
If you have any trouble or errors with the script, please just submit a Ticket Support service. It will save a lot of time and headaches.

Note that currently there is a known issue where reputation points gained from wiki comments are not imported. If this is okay by you, then go ahead and run the importer.

Didn't do any good.

I am not seeing any content imported anywhere, and am not able to access the wiki even though I should be able to.

I guess this upgrade is just a total loss.

Is there any way I can just down-grade to my old version of the software, 3.0.20, so that I can get the functionality back for my users?

This is pretty ridiculous and I can't believe that I paid money to deal with this.

I've never in my life had problems like this with any type of forum upgrade or mod, phpBB, vBulletin, or whatever.

PLEASE post downgrade instructions. Given that I now do not plan to use VaultWiki 4.0.0 on my site any longer, I'd also like to get a refund on my money paid for the license.

Thank you.

Just so you know, the import script gave me the following:

There is no "downgrade" process, as VaultWiki 4 is a separate product. If you performed the edit in my previous post here: https://www.vaultwiki.org/issues/3899/#note21103, then you would have been able to turn the wiki on, as I was able to confirm your issue and the edit fixed it. And if you submitted the Ticket Support as I suggested, I would have performed the import for you without you paying for it.

If you've never had problems like this with any forum or web software, then you are lucky. I have had issues with nearly every vBulletin upgrade due to PHP incompatibility. As another example, PayPal's Merchant API is not compatible with Zend Opcache, which took me almost 2 days to figure out.

We cannot give refunds after the software has been downloaded. This is made plain in the license text here: https://www.vaultwiki.org/pages/Info...nt#a-5-Refunds
Which you are presented with before every time you download the product.

However, as you have seen we are committed to our product and supporting our product, and I guarantee that we will get this working for you.

I performed the edit as listed in your previous post. It did not change anything.