For a project of ours in which we're using Nodes in Block we're having a little trouble finding the proper permission settings for this module.
As administrator, who has all the permissions whatsoever, there's no problem. But when the Nodes in Block-permissions are set for the site owner (our customer), some things are still not available for him. More specifically the field in which one can set the pages on which a particular block should be visible.
The only thing the site owner can see is on what pages the blocks are visible, be he can't add or remove pages (url's) from that list. For the site owner this overview can be accessed through an extra tab (ingaves voetblok rechts in our case), and every entry has a "view/edit" option next to it. But the edit-option just allows the site owner to edit the node itself, not its visibility.
I've attached some screens to illustrate te problem. Can someone help us out please?
Thanks in advance.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | Afbeelding-6.jpg | 34.66 KB | knalstaaf |
| permissions-nodes-in-block.jpg | 35.51 KB | knalstaaf | |
| tab.jpg | 38.43 KB | knalstaaf | |
| user-site-owner.jpg | 36.41 KB | knalstaaf | |
| user-admin.jpg | 64.66 KB | knalstaaf |
Comments
Comment #1
knalstaaf commentedI must have overlooked what the permissions were actually saying.
Unchecking "Deny configuration on node form" on admin/people/permissions solves our problem.
Comment #2
ancym commentedOH dear - I hate to admit how much time I lost looking for the option to choose the visibility settings.. You got me, too - obviously, I did not read the permissions carefully - just ticked all of the boxes for administrator, as usual. Since then, I have relied on being user 1 in order to be able to set the Nodes in Blocks visibility settings.
It is a bit unusual to lose power by selecting a permission option - can't think of any other setting where ticking the box decreases choices. I mean, I did go back and check permissions - several times, without noticing that I had removed my power to set visibility... Do you think that this permission setting could be mentioned explicitly in the documentation? Just a heads up?
If it is there, I still somehow missed it...
Thanks.(and thanks also to knalstaaf for supplying solution)
revised:
I see that this is related to http://drupal.org/node/901858 and also http://drupal.org/node/1173284...
Originally, here you suggested a permission of 'Configure nodes in block on node edit page'
Wouldnt that be more in keeping with the usual permission settings? Would it be too painful to re-configure the permission settings?
Comment #3
ancym commentedThink I should add that this permission does need to be changed, as it is more or less unusable like this: if i deny permission to authenticated users, by default, the permission for site administrator also becomes checked (so denied - so no one can use the visibility settings)...in effect, this permission cannot be used. Right?
Thanks.
Comment #4
ancym commentedchanging the category...
Think I should add that this permission does need to be changed, as it is more or less unusable like this: if i deny permission to authenticated users, by default, the permission for site administrator also becomes checked (so denied - so no one can use the visibility settings)...in effect, this permission cannot be used. Right?
Thanks.
Comment #5
doncroy commentedWas having the same problem due to 'skimming' the text. Fixed it. Works great.
Comment #6
hecate commentedI agree that the permission should be changed since in all other instances I've come across a 'tick' in the box grants user(s) a right to do something and so I 'skimmed' them too. Perhaps it could be changed as ancym suggested in #2 or at least the peculiarity of it should be mentioned in the readme file.
I have wasted so much time battliing with this, thinking I *must* be doing something wrong, even installed the dev version and it's still the same :-/ Glad to have found the solution though!
Comment #7
dmkelner commentedThis has been open for two years. Is this module being maintained? A permission should not be denied by checking it. If I had the expertise I would fix this. For reasonability sake check boxes should always mean that you have a permission, not that you are taking it away. This really conflicts with other modules that automatically grant the admin every permission once a module is enabled.