[CMS] Database error after disabling CMS

[SoftDux]

Hi all,

I keep getting the following Database errors via email after disabling the CMS:

Database error in vBulletin 4.1.6:

Invalid SQL:
SELECT u.username, n.userid, a.contentid,
               a.pagetext, i.title, n.publishdate, i.creationdate, i.html_title, n.nosearch,
               n.new
               FROM vb4_cms_article a
               LEFT JOIN vb4_cms_node n on n.contentid = a.contentid
               LEFT JOIN vb4_cms_nodeinfo i on i.nodeid = n.nodeid
               LEFT JOIN vb4_user u on u.userid = n.userid
               WHERE a.contentid = 48 AND n.contenttypeid =;

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 '' at line 8
Error Number  : 1064
Request Date  : Thursday, September 22nd 2011 @ 02:40:09 PM
Error Date    : Thursday, September 22nd 2011 @ 02:40:37 PM
Script        : [URL="http://www.airgunsports.co.za/cron.php?rand=1316716808"]http://www.x.x.x/cron.php?rand=1316716808[/URL]
Referrer      : [URL="http://www.airgunsports.co.za/forum.php"]http://www.x.x.x/forum.php[/URL]
IP Address    : 209.153.253.234
Username      : Unregistered
Classname     : vB_Database
MySQL Version :

I simply disabled the CMS in admincp > Plugins > Manage Plugins (as per another forum thread here).

So, how do I stop these errors? The CMS obviously doesn't work now, but where is what still trying to access it?

[Wayne Luke]

You have something in the scheduled task manager still trying to update things. However the error suggests you uninstalled the CMS and didn't disable it. Disabling doesn't remove the database tables. Check you scheduled tasks and set any referring to the CMS to an inactive state.

[SoftDux]

The CMS isn't uninstalled, just disabled.

And the only scheduled task I can see related to the CMS, "CMS Daily Cleanup" is disabled as well, as you can see

The scheduled tasks log doesn't show any error either.

[Wayne Luke]

Is there an entry in the tasks log for 2:40 p.m.?

[SoftDux]

Is there an entry in the tasks log for 2:40 p.m.?

Nothing which relates this this error.

But I also noticed that the server's time was out by 8 hours (different time zone) so I corrected the server's time zone and pruned the logs, but something is not 100% right here.



Here's the latest error message:

Database error in vBulletin 4.1.6:

Invalid SQL:
SELECT u.username, n.userid, a.contentid,
a.pagetext, i.title, n.publishdate, i.creationdate, i.html_title, n.nosearch,
n.new
FROM vb4_cms_article a
LEFT JOIN vb4_cms_node n on n.contentid = a.contentid
LEFT JOIN vb4_cms_nodeinfo i on i.nodeid = n.nodeid
LEFT JOIN vb4_user u on u.userid = n.userid
WHERE a.contentid = 48 AND n.contenttypeid =;

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 '' at line 8
Error Number : 1064
Request Date : Friday, September 23rd 2011 @ 04:40:40 PM
Error Date : Friday, September 23rd 2011 @ 04:41:07 PM
Script : http://www.x.x.x/cron.php?rand=1316788827
Referrer : http://www.x.x.x/showthread.php?2505-Setting-the-record-straight&p=30942
IP Address : 196.46.x.x
Username : Unregistered
Classname : vB_Database
MySQL Version :

And these are the log entries:



Yet, there's no entry for September 23rd 2011 @ 04:41:07 PM, or even close to this time. Please see the attached screenshot.

Is there any other place to check for errors, or how / where do I see what's generating this error?

[Dead Eddie]

How about Search Queue Update? That query looks suspiciously like the query used to index articles.

You may have an article stuck in your index queue that the system can't process because the CMS isn't active (and, as such, can't figure out the content id).

[Wayne Luke]

Could be an article. Without knowing the tasks that ran at that time, whether they seem related or not, we can't really figure out the problem. I suggest re-enabling the CMS and seeing if the error recurs. If you don't want people seeing the CMS, then disable the plugin for its Navbar link and edit the index.php to point to forum.php. The plugin is called: Navbar: Insert CMS Navbar Entry

Let the system run for a few days and clear out any queues. Then disable the CMS again.