I tried to apply permissions to a node using the content management tool and it gave this error. I am not even sure if it is safe to disable this module, how will this affect my permissions, perhaps, disable it and rebuild perms?

CommentFileSizeAuthor
drupal_node_priv_error.png46.86 KBspydmobile
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

deekayen’s picture

deekayen CreditAttribution: deekayen commented
Title: Installing this module and trying to use it on PGSql 8.3 errors out. » Installing this node privacy byrole and trying to use it on PGSql 8.3 errors out.
Project: node privacy byrole » Drupal core
Version: 6.x-1.3 » 6.x-dev
Component: Code » taxonomy.module
Category: bug » support
Priority: Critical » Normal

All those errors appear to be related to taxonomy.module. I'm not sure why you're connecting them with npbr.

spydmobile’s picture

spydmobile CreditAttribution: spydmobile commented

Sorry about that, I tend to find a lot of issues with postgres after the upgrade to 8.3 which changed lots of syntax and I am as confused as you, this was a poor bug report on my part, I dont even remember what happened, sorry.
F

dpearcefl’s picture

dpearcefl CreditAttribution: dpearcefl commented

Have you tried duplicating this issue with current D6?

mdupont’s picture

mdupont
Primary language French
Location Switzerland
CreditAttribution: mdupont commented
Title: Installing this node privacy byrole and trying to use it on PGSql 8.3 errors out. » Taxonomy trying to insert existing records on PGSql 8.3
Category: support » bug

It's just a warning because taxonomy is trying to add in the DB a record that is already existing, so the query fails with a duplicate key error. Nothing to really worry about.

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.