Issue: Wanted Category DB error

Issue Tools
- View Changes

July 29, 2009 9:28 AM

mickknutson mickknutson is offline

Regular Member

Wanted Category DB error

I clicked on:

http://www.blincmagazine.com/forum/w...ntedcategories

and got:

Code:

Database error in vBulletin 3.8.2:

Invalid SQL:

		SELECT COUNT(DISTINCT(title_lower)) AS rowcount
		FROM vault_link AS link
		LEFT JOIN vault_protect AS protect ON (link.title_lower = protect.title_lower AND link.namespace = protect.namespaceid AND protect.options = 4)
		WHERE namespace = 6
			AND link.targetid = 0
			AND templateusage = 1
			AND protectid IS NULL;

MySQL Error   : Column 'title_lower' in field list is ambiguous
Error Number  : 1052
Request Date  : Wednesday, July 29th 2009 @ 06:27:24 AM
Error Date    : Wednesday, July 29th 2009 @ 06:27:24 AM
Script        : http://www.blincmagazine.com/forum/wiki/Special:Wantedcategories
Referrer      : http://www.blincmagazine.com/forum/wiki/Special:Specialpages
IP Address    : 198.140.4.205
Username      : mknutson
Classname     : vB_Database
MySQL Version : 5.0.45

Issue Details

Issue Number 740

Issue Type Bug

Project VaultWiki 3.x Series

Category Categories

Status Fixed

Priority 3 - Loss of Functionality

Affected Version 2.5.0

Fixed Version 2.5.1

Milestone VaultWiki 3.0.0

Software DependencyAny

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

July 29, 2009 4:55 PM
pegasus

VaultWiki Team
In extensions/category/special/special_wantedcategories.php, find:

Code:

DISTINCT(title_lower)

Replace with:

Code:

DISTINCT(link.title_lower)

Find:

Code:

COUNT(title_lower)

Replace with:

Code:

COUNT(link.title_lower)

And if you have it, in extensions/xpages/special/special_wantedpages.php, find:

Code:

DISTINCT(title_lower)

Replace with:

Code:

DISTINCT(link.title_lower)

Find:

Code:

COUNT(title_lower)

Replace with:

Code:

COUNT(link.title_lower)
Reply

August 7, 2009 6:01 AM

vimto

Regular Member

I've just applied the above fixes and received the following error:

Code:

Database error in vBulletin 3.8.3:

Invalid SQL:

		SELECT COUNT(link.title_lower) AS number, link.title
		FROM vault_link AS link
		LEFT JOIN vault_protect AS protect ON (link.title_lower = protect.title_lower AND link.namespace = protect.namespaceid AND protect.options = 4)
		WHERE namespace = 7
			AND link.targetid = 0
			AND templateusage = 1
			AND protectid IS NULL
		GROUP BY title_lower
		ORDER BY number DESC, title_lower ASC
		LIMIT 0,0;

MySQL Error   : Column 'title_lower' in order clause is ambiguous
Error Number  : 1052
Request Date  : Friday, August 7th 2009 @ 10:58:50 AM
Error Date    : Friday, August 7th 2009 @ 10:58:50 AM
Script        : http://www.bluedragons.co.uk/forums/showwiki.php?title=Special:Wantedcategories
Referrer      : http://www.bluedragons.co.uk/forums/showwiki.php?title=Special:Specialpages
IP Address    : 79.74.206.28
Username      : XXXXXX
Classname     : vB_Database
MySQL Version : 4.1.22-log

I'm guessing that the Group clause will have the same result.

August 7, 2009 3:06 PM
pegasus

VaultWiki Team
Yeah, change the GROUP BY and ORDER BY clauses to:

Code:

GROUP BY link.title_lower ORDER BY number DESC, link.title_lower ASC
Reply
August 14, 2009 11:42 AM

Jella

Regular Member

I just tried it and I am sure I applied the edits properly and cleared my cache and history and I am still getting the database errors.

Can you just post the 2 fixed php files here since this is the commercial section for members?

Maybe I did something wrong? sniffle

Reply

August 14, 2009 11:43 AM

Jella

Regular Member

Here is the error

Code:

Database error in vBulletin 3.8.3:

Invalid SQL:

		SELECT COUNT(link.title_lower) AS number, link.title
		FROM vault_link AS link
		LEFT JOIN vault_protect AS protect ON (link.title_lower = protect.title_lower AND link.namespace = protect.namespaceid AND protect.options = 4)
		WHERE namespace = 6
			AND link.targetid = 0
			AND templateusage = 0
			AND protect.protectid IS NULL
		GROUP BY title_lower
		ORDER BY number DESC, title_lower ASC
		LIMIT 0,0;

MySQL Error   : Column 'title_lower' in order clause is ambiguous
Error Number  : 1052
Request Date  : Friday, August 14th 2009 @ 11:39:50 AM
Error Date    : Friday, August 14th 2009 @ 11:39:50 AM
Script        : http://tvlampforum.com/showwiki.php?lampwiki=Special:Wantedpages
Referrer      : http://tvlampforum.com/showwiki.php?lampwiki=Special:Specialpages
IP Address    : 98.229.127.230
Username      : admin
Classname     : vB_Database
MySQL Version : 5.0.81-community

August 14, 2009 2:11 PM

pegasus

VaultWiki Team

Please see my previous post.

Reply
August 14, 2009 5:52 PM
Jella

Regular Member
I did that

Code:

GROUP BY link.title_lower ORDER BY number DESC, link.title_lower ASC

in both special pages and I still showing the db error on special category, can you please help.

I got special pages to work http://tvlampforum.com/showwiki.php?...al:Wantedpages

NEVERMIND I FIXED IT, I swear I will not upgrade this thing again.
Reply
August 15, 2009 3:28 AM

pegasus

VaultWiki Team

Haha, sometimes it's good to wait for a x.x.1 or x.x.2 before upgrading. A lot of folks are planning to wait several versions when vBulletin 4 comes out, because generally when there's a large version change, it means a lot of things are different and there's more potential for bugs.

If you're not a technical user (which you have mentioned you are not), I recommend this as a rule of thumb.

I'm always pensive when a new build of VaultWiki comes out. While each build fixes a lot of existing bugs, a new build means new bugs. It's a vicious circle.

However, from what I've seen, it seems that you have had more problems (serious problems anyway) upgrading vBulletin than upgrading VaultWiki.

Reply
August 15, 2009 6:08 AM

Jella

Regular Member

Oh Peg....NOT TECHNICAL is an understatement you are too kind, I am a moron.

I can't handle another bulletin upgrade either, it's just too stressful. After the 3.83 fiasco on my sites (that you fixed) and the fact they are going to charge more even though I have 6 vb licenses all up to date I will be damned if I give them more $$$.

I am staying away from 3.8.4 too though I just tried it on my test site, a storm site.

I have one more issue with the new Wiki, it seems I have lost the chapters PREVIOUS and NEXT

I checked all settings even redid one book http://tvlampforum.com/showwiki.php?...ville+Patterns

What can I do???? the TOC is there but NO navigation of Previous and Next

HELP!!! ahhhh

Reply
August 15, 2009 7:12 PM

pegasus

VaultWiki Team

It looks like you did some kind of moderation on these articles recently (i.e. moved from another forum, merged some threads, etc).

Please let me know what you did to these articles recently (or at all).

I ask this because the article metadata is missing. You may be able to fix this by moving the articles to a non-wiki forum, then moving them back. You will need to add these to the Books again afterwards.

I'll write a tool that recreates corrupt metadata soon, but for now you'll have to use the steps outlined above.

Reply
August 15, 2009 8:40 PM

Jella

Regular Member

What I did when I realized the PREVIOUS and NEXT wasn't working was... I deleted the book, then created a new book and reinserted some of the Wiki pages for this Roseville Patterns Book.

Also my other books are gone, (I figured I'd start with rebuilding the Roseville Pattern Book first) nothing is all my books since the upgrade.

That's all I've done since the settings are ok.

Reply
August 15, 2009 9:22 PM

Jella

Regular Member

So you want me to move books to a regular forum then back? Or wiki articles then back? Or both?

Reply
August 16, 2009 12:54 AM

pegasus

VaultWiki Team

Only move the wiki articles that you want inside the Books.

Reply
August 16, 2009 7:00 AM

Jella

Regular Member

OK I did that then moved a few back to the patterns book and still no PREVIOUS NEXT http://tvlampforum.com/showwiki.php?...ville+Patterns

Reply
August 18, 2009 1:26 AM

pegasus

VaultWiki Team

Well I rebuilt your articles and revisions (meaning reset them at 1 per article), but couldn't find any source of the original problem. It was as if someone ran a TRUNCATE command on the article and revision tables. It's also possible that a database crash could have done this, if it occurred while these tables were being written to.

My changes should make the wiki usable again.

While I didn't think of this before, did you receive any unusual database errors during or shortly after upgrading to 2.5.0?

Reply

+ Reply

All times are GMT -4. The time now is 2:55 PM.

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: Wanted Category DB error

Issue Tools