Permissions

hrm, makes sense, never thought about that actually. Something like 'Configure nodes in block on node edit page' should be ok right ? (or something alike)

Committed to dev version. The permission is called 'deny configuration on node form'. It acts as a restristrive permission (except for user 1). If the user has this permission, it won't have access to the nodes in block fieldset.

hello, reopened the issue as bug report. the permission 'deny configuration on node form' hide the 'nodes in block' fieldset in the 'edit node form'. but if i try to submit a change on a node, i get a error message "Visibility field is required.". in this way, the permission blocks any node edit permission.

Wow, and I was about to throw a new release today :) Patch attached and committed to CVS. Thanks for the report!

thanks for the quick patch. unfortunately, it dont prevents the message "Visibility field is required."
for me, this change in line 285 of nodesinblock.module works:

- if ($node->nodesinblock_delta != -1 && empty($visibility)) {
+ if ($node->nodesinblock_delta != -1 && empty($visibility) && !user_access('deny configuration on node form')) {

i just realize, that my suggestion deactivate visibility validation for all users (incl. user 1), if 'deny configuration on node form' is set. anyway, it helps me. just want to give the hint to others who may read my comment.

Should now be fixed in D6 branch.