Correct method in upgrading VB3.8 to VB4.0?

[Jaxel]

So I have VaultWiki on my VB3.8 forum. Is there a correct way I should prepare the wiki for the upgrade to VB4.0?

Should I uninstall the VaultWiki before I upgrade to VB4.0? Or should I leave it installed and simply install the newest VaultWiki version after the upgrade? Should I install the newest VaultWiki before the upgrade?

[Mokonzi]

Don't uninstall, or you lose everything.

The way I did it was to backup and test it first in this fashion:

Close the forum, and backup, including files
Remove any mods or changes that you aren't using for vB4
Then disable any other modifications, and VaultWiki. DO NOT UNINSTALL. Just disable.
Then perform the upgrade to vB4, make sure it's installed well and is working fine on it's own, resolving any errors or issues before reenabling the mods.
Then enable each mod one by one. Run any upgrade routines they need, then check they work properly. Backup between each mod you reenable so you can roll back just one step if you have a problem.
Once done, recheck everything as thoroughly as you can
Backup.
Reopen the forums.

That worked fine for me, and took me an afternoon to run through, though I did all the Style design and initial tests over the space of a week beforehand on a test server I setup.

[Jaxel]

Why would you lose everything if you uninstall? I thought the VaultWiki was just a frontend to a specific forum; uninstalling VaultWiki would not delete the posts in that forum; it would just remove the frontend.

[pegasus]

If you uninstall, your articles and comments will be okay, but you will lose all your configuration options, your books, your forum headers, your wiki groups, your article history, need I go on?

When upgrading the vBulletin 4, you want to do as suggested above.

1. Close the forum.
2. Disable VaultWiki (and your other mods) via the Product Manager.
3. Upgrade to vBulletin 4.
4. Upgrade VaultWiki. Do NOT enable it first.
5. Update your other mods / re-enable some.
6. Re-do your styles for vBulletin 4.
7. Re-open the forum.

[Jaxel]

Okay... question... after I upgrade to the VB4 version of VaultWiki... what will happen to all the VaultWiki extension products? Will they be overwritten as well?

[pegasus]

They will automatically be removed. They are included in VaultWiki 3.

[Jaxel]

Sweet... great job pegasus, this upgrade process was a cinch... I do have a few issues though, perhaps you could look at them for me?

1 - what happened to the header namespace? I never used it, but I noticed that its broken...

2 - I can't get the htaccess working correctly...
http://www.8wayrun.com/wiki/ works great...
http://www.8wayrun.com/wiki does not...

3 - table structure seems to be a bit off... If you look at my wiki, on the main page, I have a table with character images on it. You'll notice that the left column on the table is pushing out the remaining columns. Why is this happening? Its happening on ALL tables I have within the wiki.

[pegasus]

1. In what way is the Header namespace broken? It may be necessary to set the "Header" namespace as the "Header namespace" using the Namespace Functions form at the bottom of the Namespace Manager.

2. Not sure your exact setup, but you might want to try something like:

RewriteRule ^wiki$ wiki/ [L,R=301,QSA]

Not all servers interpret this correctly, so if you have an infinite redirect afterwards, it may not be possible on yours.

3. Your table is defined with a "width=100%". When the table contents are not wide enough to equal 100%, it expands individual table cells, but doesn't do so evenly. If you want them to be even, you should either define a specific width on each table cell (if you have 10 cells, then 10%), or NOT define a width on the table itself.

[Jaxel]

This is my exact htaccess...

## Expires
<ifModule mod_expires.c>
	ExpiresActive On
	ExpiresDefault "access plus 1 seconds"
	ExpiresByType text/html "access plus 1 seconds"
	ExpiresByType image/gif "access plus 3456000 seconds"
	ExpiresByType image/jpeg "access plus 3456000 seconds"
	ExpiresByType image/png "access plus 3456000 seconds"
	ExpiresByType text/css "access plus 3456000 seconds"
	ExpiresByType text/javascript "access plus 3456000 seconds"
	ExpiresByType application/javascript "access plus 3456000 seconds"
	ExpiresByType application/x-javascript "access plus 3456000 seconds"
</ifModule>

## Compression
<ifmodule mod_headers.c>
	<ifmodule mod_deflate.c>
		AddOutputFilterByType DEFLATE text/html text/css text/xml application/x-javascript
		BrowserMatch ^Mozilla/4 gzip-only-text/html
		BrowserMatch ^Mozilla/4\.0[678] no-gzip
		BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
	</ifmodule>
</ifmodule>

## Rewrites
<ifmodule mod_rewrite.c>
	RewriteEngine on
	Options +FollowSymlinks

	RewriteCond %{REQUEST_FILENAME} -s [OR]
	RewriteCond %{REQUEST_FILENAME} -l [OR]
	RewriteCond %{REQUEST_FILENAME} -d
	RewriteRule ^.*$ - [NC,L]

	# VaultWiki
	RewriteRule ^wiki.php$ showwiki.php [L,QSA]
	RewriteRule ^showwiki.php?title=(.*)$ wiki/$1 [L,R=301]
	RewriteRule ^wiki/Article:(.*)$ wiki/$1 [L,R=301]
	RewriteRule ^wiki$ wiki/ [L,QSA,R=301]
	RewriteRule ^wiki/(.*)?$ showwiki_proxy.php [L,QSA]

	# Media Library
	ReWriteRule ^media/m(\d+).*/tags$ media.php?do=tags_edit&mid=$1 [QSA]
	ReWriteRule ^media/m(\d+).*/edit$ media.php?do=details_edit&mid=$1 [QSA]
	ReWriteRule ^media/m(\d+).*/report$ media.php?do=report&mid=$1 [QSA]
	ReWriteRule ^media/m(\d+).*/c(\d+)$ media.php?do=comment_edit&cmt=$2 [QSA]
	ReWriteRule ^media/m(\d+).*/p(\d+).*$ media.php?do=details&mid=$1&pid=$2 [QSA]
	ReWriteRule ^media/m(\d+).* media.php?do=details&mid=$1 [QSA]
	ReWriteRule ^media/p(\d+).*/edit$ media.php?do=playlist_edit&pid=$1 [QSA]
	ReWriteRule ^media/p(\d+).* media.php?do=playlist&pid=$1 [QSA]
	ReWriteRule ^media/c(\d+).* media.php?do=category&cid=$1 [QSA]
	ReWriteRule ^media/u(\d+).* media.php?do=user&uid=$1 [QSA]
	ReWriteRule ^media/tag/(.*) media.php?do=tag&tid=$1 [QSA]
	ReWriteRule ^media/results/(.*) media.php?do=results&query=$1 [QSA]
	ReWriteRule ^media/advresults/(.*) media.php?do=advresults&query=$1 [QSA]
	ReWriteRule ^media/letter/(.*) media.php?do=letter&query=$1 [QSA]
	ReWriteRule ^media/browse.* media.php?do=browse [QSA]
	ReWriteRule ^media/search.* media.php?do=search [QSA]
	ReWriteRule ^media/random.* media.php?do=random [QSA]
	ReWriteRule ^media/submit.* media.php?do=submit [QSA]
	ReWriteRule ^media/tagcloud.* media.php?do=tagcloud [QSA]
	ReWriteRule ^media/playlists.* media.php?do=playlists [QSA]
	ReWriteRule ^media/pcreate.* media.php?do=playlists_create [QSA]
	ReWriteRule ^media/pmine.* media.php?do=playlists_mine [QSA]
	ReWriteRule ^media/favorites.* media.php?do=favorites [QSA]
	ReWriteRule ^media/subscriptions.* media.php?do=subscriptions [QSA]
	ReWriteRule ^media/admin/edit/s(\d+).* media.php?do=admin_host_edit&sid=$1 [QSA]
	ReWriteRule ^media/admin/delete/s(\d+).* media.php?do=admin_host_delete&sid=$1 [QSA]
	ReWriteRule ^media/admin/export/s(\d+).* media.php?do=admin_host_export&sid=$1 [QSA]
	ReWriteRule ^media/admin/(\w+).* media.php?do=admin_$1 [QSA]

	# Media Library from Video Directory
	RewriteCond %{QUERY_STRING} do=viewdetails&videoid=(\d+)
	RewriteRule ^video\.php$ media.php?do=details&mid=%1
	RewriteCond %{QUERY_STRING} viewcategory&categoryid=(\d+)
	RewriteRule ^video\.php$ media.php?do=category&cid=%1
	RewriteCond %{QUERY_STRING} viewuser&userid=(\d+)
	RewriteRule ^video\.php$ media.php?do=user&uid=%1
	RewriteCond %{QUERY_STRING} viewtag&tag=(.*)
	RewriteRule ^video\.php$ media.php?do=tag&tid=%1
	ReWriteRule ^video\.php$ media.php

	# Forum
	RewriteRule ^threads/.* showthread.php [QSA]
	RewriteRule ^forums/.* forumdisplay.php [QSA]
	RewriteRule ^members/.* member.php [QSA]
	RewriteRule ^blogs/.* blog.php [QSA]
	ReWriteRule ^entries/.* entry.php [QSA]

	RewriteCond %{REQUEST_FILENAME} -s [OR]
	RewriteCond %{REQUEST_FILENAME} -l [OR]
	RewriteCond %{REQUEST_FILENAME} -d
	RewriteRule ^.*$ - [NC,L]

	# MVC
	RewriteRule ^(?:(.*?)(?:/|$))(.*|$)$ $1.php?r=$2 [QSA]
</ifmodule>

I don't think your explanation of the table problem applies here. It worked perfectly fine on my old vb3 forums with an older version of VaultWiki. I understand that individual cells are not expanded evenly, but usually it does it the best it can without forcing a line break. However, if you look at the page linked here:

http://www.8wayrun.com/wiki/Talim_-_...V_-_Frame_Data

You can see that its not following the format that tables have followed in the entire history of the internet. The table should be expanding the right most cell, since it has the most text, not the left most cell. Here is the old version of the exact same page...

http://beta.8wayrun.com/wiki/Talim_-...V_-_Frame_Data

[Jaxel]

Okay... I figured out the issue with the tables... the tables were using ALT2 as the class, which is outdated...

But now I'm having another issue with tables. No matter what, there is ALWAYS a 1px black border set on my table. No matter what styles I try to add to the table, the border is always there and I can't get rid of it. How do I fix this?

[Mokonzi]

Hmm. I think that's the tables from the normal CMS tables of regular vBulletin. Let me see if I can find what I did to fix it.

[Mokonzi]

Fix is here in this bug thread:

http://www.vaultwiki.org/issues/1293/

[Jaxel]

Also... it appears I can no longer do IF statements... are parser extensions gone?

[Mokonzi]

No. Still there. What's your code that you are trying to do?

[Jaxel]

Here is a sample... wiki page code...

[template]framesSTR[/template]
[template]framesROW| atk=Elbow Witik | cmd=:A::B: | lvl=:H::M: | dmg=31 | imp=10 | grd=-8 | hit=0 | cnt=0 | scr=- | nts=NC[/template]
[template]framesEND[/template]

And here is the framesROW template

|-
| style="white-space:nowrap" | <small>{{{atk}}}</small>
| style="white-space:nowrap" | <small>{{{cmd}}}</small>
| style="white-space:nowrap" | <small>{{{lvl}}}</small>
| style="white-space:nowrap" | <small>{{{imp}}}</small>
| style="white-space:nowrap" | <small>{{{dmg}}}</small>
| style="color:#000000; background-color:#[if={{{grd}}}==0]CCFFCC[else /][if={{{grd}}}>0]CCCCFF[else /][if={{{grd}}}<0]FFCCCC[else /]FFFFCC[/if][/if][/if]" | <small>{{{grd}}}</small>
| style="color:#000000; background-color:#[if={{{hit}}}==0]CCFFCC[else /][if={{{hit}}}>0]CCCCFF[else /][if={{{hit}}}<0]FFCCCC[else /]FFFFCC[/if][/if][/if]" | <small>{{{hit}}}</small>
| style="color:#000000; background-color:#[if={{{cnt}}}==0]CCFFCC[else /][if={{{cnt}}}>0]CCCCFF[else /][if={{{cnt}}}<0]FFCCCC[else /]FFFFCC[/if][/if][/if]" | <small>{{{cnt}}}</small>
| style="white-space:nowrap" | <small>{{{scr}}}</small>
| align="right" | <small>{{{nts|-}}}</small>

As you can see, the background color should be determined by an integer value.

IF = 0 -- CCFFCC
IF > 0 -- CCCCFF
IF < 0 -- FFCCCC
IF <> 0 (text) -- FFFFCC

Yet for some reason, EVERY cell on my site is turning up as CCCCFF... it worked fine in the old version...

NEW: http://www.8wayrun.com/wiki/Talim_-_...V_-_Frame_Data
OLD:http://beta.8wayrun.com/wiki/Talim_-...V_-_Frame_Data

-----

For some reason, it appears that the parser functions are always reading every IF statement as a TRUE positive integer. I have other places in my wiki that don't use numbers, but text... So I do something like:

[if={{{title}}}]|-
! colspan="2" | {{{title}}}[/if]

This of course is part of a table and it should only create the title row if a title exists. However, now with the new version, even if the title doesn't exist, it still creates the row... and I end up with an empty title row.