Issue: Database Error

Issue Tools
- View Changes

June 13, 2014 9:56 AM

immolator

New Member

Database Error

Step 18 - rebuilding caches

Hi, trying to install the free version (for now), all was fine until reaching Step 18 and I get the following error:

Code:

Database error in vBulletin 4.2.2:

Invalid SQL:
UPDATE `usergroup` SET `vw_misc` =  CASE `usergroupid` 
		 WHEN -1 THEN 0 
		 WHEN 1 THEN 0 
		 WHEN 2 THEN 0 
		 WHEN 3 THEN 0 
		 WHEN 4 THEN 0 
		 WHEN 5 THEN 0 
		 WHEN 6 THEN 0 
		 WHEN 7 THEN 0 
		 WHEN 8 THEN 0 
	 END  WHERE  `usergroupid` IN (4,6,86,22,56,68,93,83,73,66,33,41,72,70,80,81,82,78,85,52,20,2,90,61,35,5,88,74,91,1,77,3,84,54);

MySQL Error   : Unknown column 'vw_misc' in 'field list'
Error Number  : 1054
Request Date  : Friday, June 13th 2014 @ 02:50:56 PM
Error Date    : Friday, June 13th 2014 @ 02:50:57 PM
Script        : [url]http://www.lomcn.org/forum/vault/install/index.php[/url]
Referrer      : [url]http://www.lomcn.org/forum/vault/install/index.php[/url]
IP Address    : xx
Username      : xx
Classname     : vB_Database
MySQL Version : 5.1.63-0ubuntu0.11.04.1

Have no idea what this means or how to fix. Please advise? Thanks

Issue Details

Issue Number 3794

Issue Type Bug

Project VaultWiki 4.x Series

Category Install / Upgrade

Status Fixed

Priority 2 - Fatal / Database Errors

Affected Version 4.0.0 Gamma 6

Fixed Version 4.0.0 Gamma 7

Milestone VaultWiki 4 Gamma X

Software DependencyvBulletin 4.x

License TypeLite

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

June 13, 2014 11:38 AM
pegasus

VaultWiki Team
If you have database access, through something like phpmyadmin, you can fix this manually by executing the following SQL:

Code:

ALTER TABLE usergroup ADD COLUMN vw_misc INT(10) UNSIGNED NOT NULL DEFAULT '0'

In the mean time, I will see if I can find what the problem is with the installer that this step was not automated.
Reply
June 13, 2014 11:43 AM

pegasus

VaultWiki Team

Fixed. I see this was a problem with our export process. It had some related files set to exclude from the Lite version when they are actually necessary in the latest release. I will make the appropriate changes to the package and vb.org should be updated with a new ZIP shortly.

Reply

June 14, 2014 6:04 AM

immolator

New Member

Thanks, I appreciate your prompt action however upon further inspection it has caused more problems. I get this error when trying to delete posts using the inline moderation:

Code:

Database error in vBulletin 4.2.2:

Invalid SQL:
DELETE FROM `vw_options` WHERE contenttypeid = 1 AND contentid = 945554 LIMIT 1;

MySQL Error   : Table 'mydbname.vw_options' doesn't exist
Error Number  : 1146
Request Date  : Saturday, June 14th 2014 @ 10:58:45 AM
Error Date    : Saturday, June 14th 2014 @ 10:58:45 AM
Script        : [url]http://www.lomcn.org/forum/inlinemod.php?t=85394&p=945554&postids=945554[/url]
Referrer      : [url]http://www.lomcn.org/forum/inlinemod.php?threadid=85394&p=945554[/url]
IP Address    : xx
Username      : xx
Classname     : vB_Database
MySQL Version : 5.1.63-0ubuntu0.11.04.1

Also, my BB codes have broken in signatures, see the image here

Hopefully you can fix

June 14, 2014 9:21 AM
pegasus

VaultWiki Team
In AdminCP > Plugins & Products > Plugin Manager, delete the VaultWiki plugins with the following hook locations:

postdata_delete
threaddata_delete
forumdata_delete

They are not needed in the Lite version and will cause the first error you are seeing. I am looking into the other issue now.
Reply
June 14, 2014 10:49 AM

pegasus

VaultWiki Team

I cannot reproduce the issue with BB-Codes in signatures on my Lite test site. My signature is functioning normally. As far as I can tell, priming of the signature cache does not work from inside wiki pages in Gamma 6, so it should not even be an issue for the rest of your site if signatures seem broken in the wiki.

Note that a signature should always read from the cache, unless it has recently been changed. That is just the way vBulletin's signatures work. So any "broken" signatures that have not been changed since VaultWiki was installed have been broken since before VaultWiki was installed. The only way for the signature cache to update without actually changing a signature is if the admin uses the appropriate vBulletin maintenance tool to rebuild the signature cache. If you are sure the signature is not currently cached (table sigparsed would be empty for all tests), you can confirm whether VaultWiki has an effect by trying it with an empty cache while VaultWiki is both enabled and disabled.

However, the issue you are having is very specific: no BB-Codes work in signatures, but IMG does. This is a behavior I have typically seen when mods like CES Parser Permissions are configured incorrectly or don't have support for add-ons like VaultWiki. However, the latter should currently be a non-issue because signature caching doesn't currently work in VaultWiki anyway.

Reply
June 14, 2014 5:45 PM

immolator

New Member

To be honest I don't understand most of what you just said but all I know is that since uninstalling the wiki, sigs have returned to normal.

I'm going to try installing again though. Have you uploaded your fixed revisions to vb.org?

Thanks again

Reply
June 14, 2014 9:16 PM

pegasus

VaultWiki Team

I have not uploaded a new package to vb.org. I was waiting to hear back about your sigs first. If the issue persists, I would recommend filling out a Ticket Support service request through our Members area.

Reply

+ Reply

All times are GMT -4. The time now is 12:29 AM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

Issue: Database Error

Issue Tools