Closed (fixed)
Project:
Node Hierarchy
Version:
6.x-1.1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
8 Feb 2009 at 16:34 UTC
Updated:
3 Jan 2014 at 00:07 UTC
Jump to comment: Most recent
Comments
Comment #1
andreiashu commentedThe error appears only when i edit a node. Another thing to note is that the node in question is a child of another node. If i go to it's parent I can edit it without the warning appearing.
Sorry for the misleading.
Edit: the permissions are working correctly though. the users/roles that must see that node can access it and the ones that mustn't receive an access denied.
Comment #2
andreiashu commentedI modified the query in _nodehierarchy_get_parent_pulldown_items function from:
to
and the warning disappeared. Everything seems to be working just fine: the parent nodes appear in the "Node Hierarchy" fieldset.
The computed query looks like this now (copied from devel output):
I really need some feedback with this issue because my experience with Node Hierarchy and Node Access is absolutely 0.
Thanks in advance.
Comment #3
ronan commentedThat is the right fix alright. This is done in the latest dev and I'll be making a stable release with that code soon.
More info can be found at #334962: User warning when creating a child node and #341846: Conflict between Node Hierarchy and Killfile is causing SQL error when adding a new node or visiting NH configuration page
Thanks
Ronan
Comment #4
andreiashu commentednice, thanks a lot.