[Forum] Invalid SQL: DELETE FROM activitystream...

[Valter]

I get this error while moving posts to another thread:

Database error in vBulletin 4.2.0:

Invalid SQL:
DELETE FROM activitystream
WHERE
typeid =
AND
contentid IN (SELECT postid FROM post WHERE threadid IN (16682,27746));

MySQL Error : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND
contentid IN (SELECT postid FROM post WHERE threadid IN (16682,27746))' at line 4
Error Number : 1064
Request Date : Thursday, May 24th 2012 @ 12:29:53 PM
Error Date : Thursday, May 24th 2012 @ 12:29:54 PM
Script : http://www.XXX.com/inlinemod.php?do=...,828035,828234
Referrer : http://www.XXX.com/inlinemod.php?threadid=16682&p=
IP Address : XXX
Username : XXX
Classname : vB_Database
MySQL Version : 5.0.95-community

So typeid is blank.

In thread.php:

typeid = {$typeid}

and:

$typeid = vB::$vbulletin->activitystream['forum_post']['typeid'];

How to fix this?

[faquick]

Got the same error here on our forums, same scenario: moving posts to another thread.

[Lynne]

You should enter this into the bug tracker.

[Dolomites]

Same error while moving posts to another thread, important to solve because actually it is impossible move posts without errors....

[Lynne]

Did anybody enter this into Jira? If so, please post a link here so other's can follow the bug.

[KittyWireless]

Same error here.

[jimnyc]

Did anybody enter this into Jira? If so, please post a link here so other's can follow the bug.

I honestly have no idea how to do anything with Jira, but I too am getting the same error, as follows:

Database error in vBulletin 4.2.0:

Invalid SQL:
DELETE FROM activitystream
WHERE
typeid =
AND
contentid IN (SELECT postid FROM post WHERE threadid IN (35291,35297));

MySQL Error : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND
contentid IN (SELECT postid FROM post WHERE threadid IN (35291,35297))' at line 4

[Sunka]

Lynne, coud you enter this error into Jira?
It is major problem vB 4.2.0

[Lynne]

Lynne, coud you enter this error into Jira?
It is major problem vB 4.2.0

I cannot duplicate it at all. I need specific steps in order to duplicate this so I can write a bug report.

what I did (which resulted in no database error):
- wrote two posts in a thread
- selected those two posts while in the thread and selected Move Posts from the dropdown Moderation Tools menu
- on the next screen I entered the URL to an existing thread
- everything worked fine

[Paul M]

@ Anyone who has this error ;

In your ACP, try going to Options > Activity Stream and then re-save the options. The error suggests your AS datastore may not be correctly populated.

[Amaury]

@ Anyone who has this error ;

In your ACP, try going to Options > Activity Stream and then re-save the options. The error suggests your AS datastore may not be correctly populated.

Well, it fixed the issue of it not highlighting posts after the 1st post, but I'm still getting a DBE, and it's the same when trying to merge threads or posts. They go through, but the error appears.

I'd be more than willing to submit it to JIRA, but I want to make sure that it's a bug 100%.

[Paul M]

Well its not one I can reproduce (nor can Lynne).

From looking at the code, it gets the typeid from the activity stream datastore.

So, tbh, without site/ftp/database access, not much more we can do.

[Lynne]

Try disabling all your modifications and use a totally default style and then try the merge and see if you still get the same database error.

[Amaury]

Also, I'm not sure if it was always like this and I'm just noticing it now or if it happened on 4.2.0, but the editor box is too much to the right on the merge page.

[Lynne]

I believe it's your style. Create a new style with no parent:

• Styles & Templates > Style Manager > Add New Style
• Parent Style: No Parent Style
• Title: Default vBulletin
• Allow User Selection: Yes
• Save

Then browse the site using that totally default vbulletin style - do you still have the same problem?