I'm posting this question here because OG Forums is the only place I'm NOT having a problem. Maybe someone here will have a clue.

Shortly after applying the Drupal 5.2 patch, I noticed that whenever I go to a forum, I get these errors:

* warning: Invalid argument supplied for foreach() in /modules/node/node.module on line 521.
* warning: implode(): Bad arguments. in /modules/node/node.module on line 525.
* user warning: 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 1 query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE in /includes/database.mysql.inc on line 172.

I looked at these two issues:
http://drupal.org/node/164499

http://drupal.org/node/180529

But, then don't seem to relate to me as I don't have the book, subscriptions or privatemsg modules installed. I get the error every time I click on a forum, and it appears no other time.

The only exception is when I click on a forum created by OG Forum. Do not receive any errors on OG Forums.

Does anyone have any idea why this is happening? Thanks for any suggestions.

Comments

somebodysysop’s picture

somebodysysop commented

By the way, I just updated the site to Drupal 5.5, and still get the same errors.

rconstantine’s picture

rconstantine commented
Status: Active » Postponed (maintainer needs more info)

Could you install the devel module and turn backtrace on? That should drill down to the calling function that causes these errors. I tell everybody to use devel, so maybe I should add it to the README. It sure would save a lot of time if the first post of an issue had the devel info in it.

rconstantine’s picture

rconstantine commented

Perhaps you could also supply a list of active modules? I literally have 100+ modules active (with no problems and acceptable response times), so my combination seems to work just fine. I wonder if 100+ modules is a record? I have 235 tables in my test database! (231 on my live site)

Always good to see you around SomebodySysop.

somebodysysop’s picture

somebodysysop commented

Thanks. BTW, I don't believe this is an OG Forum issue. It's just that the only time I do NOT get the error is when I select a forum created by OG Forum.

I installed the devel module, turned on backtrace, but I don't know where the additional info is I'm supposed to see when go to the url that gives me the errors. I still get only:

    * warning: Invalid argument supplied for foreach() in /modules/node/node.module on line 521.
    * warning: implode(): Bad arguments. in /modules/node/node.module on line 525.
    * user warning: 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 1 query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE in /includes/database.mysql.inc on line 172.

Is there ome other setting required in order to see additional information? Thanks again!

rconstantine’s picture

rconstantine commented

Uh, I don't recall for sure, but maybe you need to make sure you have errors turned to the 'screen and log' setting in the standard drupal settings. Or maybe you have to check the first two database checkboxes on the devel settings as well (at the top). I do it all of the time, but it's one of those things where you get used to something and don't notice the steps you're taking.

Anyway, the data that we'd use would just spit out all over the screen AT the URL that causes the problem. You'd get a table which can sometimes be very long. It will be a reverse order of the queries and function calls that fired off, along with the arguments; very useful.

somebodysysop’s picture

somebodysysop commented
Status: Postponed (maintainer needs more info) » Fixed

Thanks. Couldn't figure out how to see the backtrace, but did figure out the problem. It was, sigh, an OGR issue. I had made a change some time back in order to do theming that performed a particular search if OG Forum was installed (which is why it worked with OG Forum forums). This was the solution: http://drupal.org/node/194214.

Thanks for your help!

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.