Just downloaded the new development version to test the yellow marker feature. This module is getting to be pretty interesting! Thanks for your efforts.

In trying to use annotation, I am experiencing some MySQL errors, so I thought I would update you with my problem:

* 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 'DISTINCT(n.nid), a.visibility, a.note FROM annotations a INNER JOIN node n ON a.' at line 1 query: SELECT n.title, u.name, u.uid, DISTINCT(n.nid), a.visibility, a.note FROM annotations a INNER JOIN node n ON a.nid= n.nid INNER JOIN users u ON a.uid=u.uid WHERE a.nid = 3 AND 1=1 in /home/mysite/includes/database.mysql.inc on line 172.
* 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 'DISTINCT(n.nid), a.visibility, a.note FROM annotations a INNER JOIN node n ON a.' at line 1 query: SELECT n.title, u.name, u.uid, DISTINCT(n.nid), a.visibility, a.note FROM annotations a INNER JOIN node n ON a.nid= n.nid INNER JOIN users u ON a.uid=u.uid WHERE a.nid = 3 AND 1=1 in /home/mysite/includes/database.mysql.inc on line 172.
* warning: mysql_fetch_object(): supplied argument is not a valid MySQL result resource in /home/mysite/includes/database.mysql.inc on line 188.

Thanks for any help fixing this. I am looking forward to the functionality of this module!

Comments

clemens.tolboom’s picture

Component: Code » annotate (private)
Assigned: Unassigned » clemens.tolboom

This is an issue about private annotations. If you want to test the yellow marker (annotate_ym) select that module!

This bug is important though. What modules are you using? And then especially the access control ones? TAC or OG or ...? This has to do (again) with db_rewrite_sql i'm afraid. (I'll have a look this week.)

Regards,
Clemens

bomarmonk’s picture

I have organic groups installed... I'll try disabling some of the other modules and see if it is some kind of bad interaction.

clemens.tolboom’s picture

Your could try alter the offending query by adding 'n.nid' in front.

clemens.tolboom’s picture

Have you tested any further? I want to reproduce this.

clemens.tolboom’s picture

Status: Active » Closed (duplicate)

This is the same as the newer bug #209369. But that is using i18n.module too.