Needs review
Project:
Hidden Nodes
Version:
7.x-1.0-beta4
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
3 May 2012 at 15:16 UTC
Updated:
27 Jul 2012 at 02:26 UTC
I get this message when in the content page I publish a node of a kind that is not defined as hidden:
Notice: Undefined property: stdClass::$hidden i hidden_nodes_node_access_records() (rad 258 av /home/henrikst/public_html/fst/si
Many thanks, this module is just what I needed!
Comments
Comment #1
komlenic commentedI have tried to reproduce the error that you describe, but have been unable to do so. I went to admin/content, selected a node of a type that is not defined as able to be hidden, and clicked publish without any error. If you can provide more information, I would be happy to look into this further. Thank you.
Comment #2
hs@henrikstrindberg.se commentedHi!
I'm using D7.14 and Hidden Nodes 7.x-1.0-beta4.
I use Hidden Nodes to create templates from nodes that have webforms. I hide them and the editor clones them to create and publish new nodes with webforms. It works very well. And simple to understand and for the editor to create new templates. So thanks again for this useful module!
Comment #3
komlenic commented@hstrindb I must have been previously confused, as I am now able to reproduce the error you described. Will work on a fix - thanks!
Comment #4
komlenic commentedThe latest 7.x-1.x dev branch has a fix for this bug. I also attempted to reproduce it in the D6 version and could not - so the changes have not been backported (at least for now).
Comment #5
btopro commentedMaybe a message after install telling people to go to the settings page and mark a type would help possibly alleviate workflow issues surrounding this as well?
Comment #6
komlenic commentedThat's not a bad idea, however this bug showed up if any nodes of types not allowed to be hidden were published/unpublished - regardless of whether any other types were allowed to be hidden or not.
The only concern I have with sticking a message in there on install, is will that trigger the message when doing a profile install? That might not be desirable?
Comment #7
btopro commentedThat would definitely trigger it as part of an install profile unless you checked to see what value was returned