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 ')) AND ( r.nid = 8 ) ORDER BY v.weight, t.weight, t.name' at line 1 query: SELECT t.* FROM term_node r INNER JOIN term_data t ON r.tid = t.tid INNER JOIN vocabulary v ON t.vid = v.vid LEFT JOIN term_data catd ON t.tid = catd.tid WHERE (t.tid IN (0) OR catd.vid NOT IN ()) AND ( r.nid = 8 ) ORDER BY v.weight, t.weight, t.name in /home/needyd/public_html/includes/database.mysql.inc on line 172.
I apologize in advance for my noob-ness. I have not submitted a request before, and I have no idea how to fix this or exactly what was causing it. Basically all I know for sure is that whenever TAC Lite is enabled that error appears on every page when no one is logged in. If the administrator is logged in, it appears on that page after it refreshes with the login information, but it goes away after going to any other page. For users not logged in, it shows up on every page.
Here's the set up that I had using TAC Lite:
TAC Lite + ACL + Image_Gallery. I used this set up to allow my users to set images that are being displayed in the gallery as private - not displayable to the public. It worked great for about a month or so, but then started kicking out that error for no apparent reason. I hadn't made any changes to the website in 5+ days, and no user had logged in or added any content in 2 days.
I wish I was more capable to tell you exactly what was wrong, or at least enough to make some sort of suggestion - unfortunately I don't know much about this.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 230952.diff | 1.55 KB | Dave Cohen |
Comments
Comment #1
Dave Cohen commentedThis looks familiar, like something I thought was fixed. I will look into it, when time permits.
In the meantime I think adding your terms and configuring the TAC_lite settings will make it go away. See admin >> by module >> tac_lite.
Comment #2
Dave Cohen commentedHere at last is a patch that should solve the problem.
Comment #3
davidneedhamSorry for never checking back on this. I'm closing this issue for your convenience.