When I create a new audio node, I got this message:

user warning: Unknown table 'n' in on clause query: SELECT * FROM playlist_relate INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 0 AND na.realm = 'og_public') OR (na.gid = 0 AND na.realm = 'og_all'))) AND parent_id = '2025' AND child_id = '' in /home/hatnangc/public_html/community/includes/database.mysql.inc on line 120.

Comments

vph’s picture

vph commented

This is very odd. I think it has to do with the audio_playlist_form_alter function in the audio_playlist module. This, I think, adds a form called Playlists to the the form when an audio node is created.

When I allow autheticated users the permission to "administer nodes", I didn't see the error above. If I disallow them that permission, the an authenticated user would run into the problem. Of course, the admin role doesn't run into it.

zirafa’s picture

zirafa commented

Very strang. I see you have organic groups installed. What else is installed? When and where did this occur exactly?

vph’s picture

vph commented

not that many modules:
+ bookmarks
+ image
+ privatemsg
+ og
+ related_links
+ views
+ system_info

Like I said, when an authenticated user creates a new audio node (node/add/audio), I saw that warning and when I click the submit button. Everything *seems* to go through though.

vph’s picture

vph commented

Yes, when I disable node access control in OG, the problem disappears. The reason for it may have something to do with the node_access table.

Here's a related problem with audio_import: http://drupal.org/node/71822

zirafa’s picture

zirafa commented

This may have been related to the db_rewrite_sql problem specified here (fixed now):

http://drupal.org/node/72133

Try it now and report back if possible.

zirafa’s picture

zirafa commented
Status: Active » Fixed

Assuming this was fixed by taking out the db_rewrite_sql patch noted in #5. Please re-open if it persists.

zirafa’s picture

zirafa commented

Whoops, I meant to say I assume it was fixed by the patch above.

Anonymous’s picture

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