In the ?q=admin/logs page, I have the following error message, related with cron job:

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 '(p.nid), p.pid, p.category, p.component, p.priority, p.assigned query: SELECT n.DISTINCT(p.nid), p.pid, p.category, p.component, p.priority, p.assigned, p.state, n.title FROM project_issues p INNER JOIN node n ON n.nid = p.nid WHERE n.status = 1 AND p.state = 2 AND n.changed < 1114601819 en la línea 66 del archivo /home/iesdonan/public_html/includes/database.mysql.inc.

Comments

rickyniano’s picture

rickyniano commented

Another similar error message I got:

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 '(p.nid), p.pid, p.category, p.component, p.priority, p.assigned query: SELECT n.DISTINCT(p.nid), p.pid, p.category, p.component, p.priority, p.assigned, p.state, n.title FROM project_issues p INNER JOIN node_access na ON na.nid = p.nid INNER JOIN node n ON n.nid = p.nid WHERE (na.grant_view = 1 AND CONCAT(na.realm, na.gid) IN ('all0','term_access1')) AND n.status = 1 AND p.state = 2 AND n.changed < 1114621204 en la línea 66 del archivo /home/iesdonan/public_html/includes/database.mysql.inc.

rickyniano’s picture

rickyniano commented

I realize the problem is a compatibility issue with taxonomy_access. Disabling the 'taxonomy_access' module solves the problem.

killes@www.drop.org’s picture

killes@www.drop.org commented

This was a problem with project.module and should be fixed.

Anonymous’s picture

(not verified) commented