Upgrade of VW3.0.16 to vB4.1.2

[Alan_SP]

I'm still on vB4.1.2 and I'm wandering could I upgrade to VW3.0.16, will it work correctly? As I don't have new editor...

[pegasus]

We have branched VaultWiki's code so that it should still work even if it detects that CKeditor is not supported. So yes, I expect that you will be fine.

[Alan_SP]

Just to report, I think that everything went fine, but I had some strange problems.

First, from my members area, I have installed "Last downloaded 3.0.11 Build 002 on March 24, 2011". I mean, this was my first installation of VW.

In options I choose to download only changed files, and as version that was 3.0.11 Build 001 (there's no build 002). This may caused problem I had.

Of course, for targeted version I choose 3.0.16 Build 001.

When I started upgrade I run upgrade script in vault/install directory. And it said it will update my version to 3.0.11, but this one I already have. When I clicked proceed (you have small textual bug there, not very big, name of the button you reference in text is not actual button name, as I said, not very big thing, but you might consider correcting it) it run upgrade_3p3011.php (or it may be 3x3011, not really sure, but I think it is with p).

Anyway, running this files didn't produce any results, you can call it dead loop, or whatever. Just run it and run it, nothing happened when I clicked on proceed button.

I tried again running upgrade.php, didn't helped, it went again to same file.

As it is my version file and I'm already using that version, I changed manually file in browser from 3011 to 3012. After that upgrade script went fine as far as I can tell. It upgraded wiki to 3.0.16 as far as I can tell, everything at the moment works ok (didn't have much time to test it extensively).

For some reason (maybe build difference, as I had build 002, and downloaded build 001 files) upgrade script tried to upgrade me to VW to 3.0.11, it said that and I think that's why it run in dead loop.

Did I do good to manually changed file name called from browser and is everything now ok as far as you can tell? Also, try to correct what's wrong in upgrade script, for others who will use it.

[Alan_SP]

Ok, I found one thing that doesn't work at the moment.

It's AJAX preview of article. I enabled it in "VaultWiki: General Settings", it is on yes, but I couldn't see preview when I put mouse on name of some wiki article. Nothing happens, it acts just like any other link. OK, not completely like any other link. It doesn't show link address in browsers link preview (not sure how to name this, but when you put mouse on some link you can see link).

[pegasus]

Some links won't show a preview if:

• You don't have permission to view the target page, OR
• The target page didn't contain any valid preview text.

Also sometimes the Javascript that creates the previews isn't loaded if every post on the page is already saved to the cache.

[Alan_SP]

I'm talking about articles that showed preview before upgrade, that are visible to guests. Now I cleaned articles post cache in wiki maintenance tools, still no preview.

[Alan_SP]

I'm still not having AJAX previews of articles.