Installation Issues

[Moses]

Hi There,
I've had a few troubles running the install, mainly due to other upgrades / impex going on at the same time.

I originally installed it on VB3.84 then upgraded vbulletin to 4.03 and ran the impex from smf.

Now have the latest VaultWiki, but got a bunch of SQL errors when attempting the upgrade. Ran the uninstall through Product Manager, and it dissapeared from the products page. When I attempt to install the latest VaultWiki I'm getting "You have already installed VaultWiki; do you wish to upgrade?".

I suspect the best way forward would be a complete removal of all VaultWiki tables via SQL then start the installation from scratch. Any other options to consider?

Do you have a SQL script I could run to do a complete removal?
Thanks,
Moses.

[pegasus]

The closest thing we have is /vault/tools/uninstall.php

I suspect that this didn't work correctly for you because you used a version of the uninstall file that was from the newer ZIP, rather than from the same ZIP as your existing VaultWiki install.

You would have to go through the uninstall.php file line by line and make sure the SQL queries therein have been performed.

We are trying to write a more elegant uninstaller/upgrader for the next release that doesn't halt on error and result in VaultWiki being unusable.

[Moses]

Thanks pegasus,

So by the sounds of it the uninstall script will change version to version. If you wanted to put out an uninstall all script, I reckon a series of 'DROP TABLE IF EXISTS ' statements listing every table you've ever used would do the trick nicely

For the record, my magic script is:

DROP TABLE vault_namespace;
DROP TABLE vault_upgradelog;
ALTER TABLE `session` DROP `inwiki`;
ALTER TABLE `usergroup`
  DROP `specialpage_permissions`,
  DROP `vault_misc`,
  DROP `vault_permissions`;
ALTER TABLE `language`
  DROP `phrasegroup_vaultarticles`,
  DROP `phrasegroup_specialpages`,
  DROP `phrasegroup_vaultadmin`,
  DROP `phrasegroup_vaultbbcode`,
  DROP `phrasegroup_vaultdomain`,
  DROP `phrasegroup_vaultfaq`,
  DROP `phrasegroup_vaultnamespace`,
  DROP `phrasegroup_vaultprotect`,
  DROP `phrasegroup_vaultstyle`,
  DROP `phrasegroup_vaulturl`;
ALTER TABLE `thread` DROP INDEX `firstpostid`;
ALTER TABLE `forumpermission` DROP `vault_permissions`;
ALTER TABLE `poll` DROP `position`;
ALTER TABLE `post` DROP `vault_options`;

[Moses]

I've run this process successfully on my dev DB twice, would you be able to have a quick look at what I'm dropping and advise if there's anything catastrophic I'm blowing away?

Cheers, Moses.

[pegasus]

I'm guessing those are the only ones that still existed? There were quite a number of other tables added by VaultWiki.
Otherwise it looks okay and there should not be anything catastrophic (aside from losing any existing wiki information - but existing articles would just be converted to threads).

For the record, our install/uninstall process does use DROP IF EXISTS, but there is no equivalent for DROPping COLUMNs. Instead, in the next release, we begin querying each table we intend to modify before making column/index changes one-by-one to make sure the change isn't already made. I will go ahead and look into adding "every table ever used" to the uninstall rather than just the current ones.

[Moses]

I've got no wiki content as yet, my only concern was dropping something used by vbulletin itself.

Oh, that is a prick that there is no native drop column if exist in mysql!

I found a script that will do it in mysql 5+ if you're interseted
http://bitkickers.blogspot.com/2010/...if-exists.html

[pegasus]

Yes that script is very similar to the method we've moved to for the next release.

[Moses]

Thanks Pegasus,
I just got the latest version installed, after some initial difficulty running the uninstall as it wont run stand alone yet there's no product in the products section to run the script?

Anyways, I dropped all the vault_ tables and ran the 3.0.0 installation and it's gone well on my test forum. I even got namespaces set up on my 4.0.3 PL1 installation, however it doesn't look right (screenshot attached).

Anything obvious you can see with this?
Moses.Wiki screen.jpg

[pegasus]

It looks like styles weren't rebuilt somehow. You can do this manually from your AdminCP by going to VaultWiki > Wiki Style Manager > Rebuild All Styles.

[Moses]

It looks like styles weren't rebuilt somehow. You can do this manually from your AdminCP by going to VaultWiki > Wiki Style Manager > Rebuild All Styles.

Spot on as always pegasus, when I did that I got an error which I fixed with a chown

Default ... (Templates) (StyleVars) (Replacement Variables) (CSS) (Controls) Failed to write css files. Please make sure that the directory 'clientscript/vbulletin_css' is writable.Done.

[Moses]

That's looking great now Pegasus,

Now I'm setting up namespaces... I'm pretty flexible, but one config that would work is to set up the wiki with the name 'Ruggapedia', then have three groupings (namespaces?) under this as so:

Ruggapedia
- Players
- Teams
- Competitions

I've tried a bunch of times, thought it was time to ask how to set these up correctly.

Do I set up the root (Ruggapedia) as my default namespace, then the others as namespaces with no special function, then move them all around in the Forum Manager to be children of Ruggapedia? If I do that, does it still show Ruggapedia as a category on the wiki root page?

Cheers,
moses.

[pegasus]

You should avoid nesting namespaces. If you want to create a category called Ruggapedia that's fine, but I wouldn't recommend making that the default namespace. You can also name your wiki Ruggapedia using a setting: http://www.vaultwiki.org/guides/How-...e-of-Your-Wiki

[Moses]

Thanks for the link Pegasus, I've renamed the wiki now.
I'll avoid nesting namespaces as well, I'm really just after what is the best approach if I want three 'groups' of wiki article. Should this be done with namespaces, or just sub-forums within a namespace. Do I just pick one of the three to be the default?
Thanks again mate.

[pegasus]

It's up to you. If all three are separate namespaces, the main differences are going to be:

• Each group will have a unique URL format.
• Articles in each group will be linked to using different BB-Codes.
• Only 1 can be set as default (yes you can pick).

On the other hand, if they are sub-forums in a namespace:

• They will share the same URL format.
• You can link to articles in all groups using the same BB-Code.
• They would all fall under default.

[Moses]

Sub-forums in a namespace sounds good, do I just add them through forum manager and set 'Enable Wiki in this forum?' to 'wiki' ?