For a custom content type, the "author" role is granted view, edit, delete permissions by default through this module. (Nobody else is granted permission to interact with this content type.) However, after an Author creates the content, it is not accessible to them (a not authorized to view error).

The problem is corrected after permissions are rebuilt, or User1 edits and re-saves the node.

After some trial and error, it appears that the problem is related to a trigger. I have set up a trigger to redirect the user to a different page after new content is created. When I disable this trigger, the above problem goes away.

I had experienced a similar problem between trigger and custom cck fields, which was traced back to a module weight issue (see http://drupal.org/node/414762). This smelled like a similar problem to me. Yet, after adjusting the weight of the trigger module to be heavier than the privacy-by-node module (and in fact, heavier than all other installed modules) the problem persists.

Thoughts?