Hey All,
I've got drupal up and running on my second drupal-based site. It sure has been easier and more enjoyable this time around now that I know, for example, what a node is :)
One thing that I haven't been able to figure out though is how do I allow anyone of a certain role to edit any page? I can create the role no problem and I can grant access to allow users to modify their own pages, but I don't see a way to allow anyone of a particular role (e.g., Content Manager) to edit any page. I don't want members of this role to be able to create new pages; I just want them to be able to edit existing ones. This seems like a pretty common use case, so it must be hiding among all these options somewhere :/
Am I missing something or is it truly not possible? If it isn't currently doable, then perhaps I'll hack page.module to make it possible ;)
On Saturday 27 August 2005 19:59, Travis Spencer wrote:
I don't see a way to allow anyone of a particular role (e.g., Content Manager) to edit any page. I don't want members of this role to be able to create new pages; I just want them to be able to edit existing ones.
I did not try, but isn't the 'administer nodes' permission exactly what you're after?
groet, Wilbert Berendsen
Wilbert Berendsen wrote:
On Saturday 27 August 2005 19:59, Travis Spencer wrote:
I don't see a way to allow anyone of a particular role (e.g., Content Manager) to edit any page. I don't want members of this role to be able to create new pages; I just want them to be able to edit existing ones.
I did not try, but isn't the 'administer nodes' permission exactly what you're after?
Administer Node gives permission to create as well as edit.
You need to use the nodeperm_byrole module, I think.
Travis,
Giving your "Content Manager" role administer node rights should do it.
This will allow anyone in this role to edit (or delete) any node, however, not just pages.
Travis Spencer wrote:
Hey All,
I've got drupal up and running on my second drupal-based site. It sure has been easier and more enjoyable this time around now that I know, for example, what a node is :)
One thing that I haven't been able to figure out though is how do I allow anyone of a certain role to edit any page? I can create the role no problem and I can grant access to allow users to modify their own pages, but I don't see a way to allow anyone of a particular role (e.g., Content Manager) to edit any page. I don't want members of this role to be able to create new pages; I just want them to be able to edit existing ones. This seems like a pretty common use case, so it must be hiding among all these options somewhere :/
Am I missing something or is it truly not possible? If it isn't currently doable, then perhaps I'll hack page.module to make it possible ;)
Perhaps I've missed the boat here, but I was under the impression that you did NOT have to have cookies enabled to log in to a Drupal site.
Someone had trouble with a log in on my site yesterday. Turns out their cookies were set to not accept cookies. They tried to log in, the Who's online module showed them as online but they could progress no further.
I have 4.6.3 and have not modified anything related to this part of Drupal.
Should this have happened? Would it have anything to do with my hosting company upgrading to PHP 4.4.0 ??
Am 27.08.2005 um 20:49 schrieb Skip Taylor:
Perhaps I've missed the boat here, but I was under the impression that you did NOT have to have cookies enabled to log in to a Drupal site.
Someone had trouble with a log in on my site yesterday. Turns out their cookies were set to not accept cookies. They tried to log in, the Who's online module showed them as online but they could progress no further.
I have 4.6.3 and have not modified anything related to this part of Drupal.
I prefer "without-cookies" as well, but a PHP-Switch must be set the right way (I tried 4.5.x only). e.g. in the PHP-Section of .htacess: php_value session.use_trans_sid On which is Off by default.
Maybe there are other switches (cookie-only or similar) relevant in this case. Try the above switch and see.
BTW, a session-management ist nevertheless necessary, so by dropping cookies the session-id will be kept with the url, which is disputed on security reasons as far as I remember. I do not know yet all factors behind it. I do not like cookies, but I am not certain wether they are the less bad thing ;-)
The log-in on the Drupal main site works only with cookies enabled, I tried ;-)
Servus Franz
On 8/28/05, Franz Iberl f.iberl@amazonas-box.de wrote:
Am 27.08.2005 um 20:49 schrieb Skip Taylor:
Perhaps I've missed the boat here, but I was under the impression that you did NOT have to have cookies enabled to log in to a Drupal site.
Someone had trouble with a log in on my site yesterday. Turns out their cookies were set to not accept cookies. They tried to log in, the Who's online module showed them as online but they could progress no further.
I have 4.6.3 and have not modified anything related to this part of Drupal.
I prefer "without-cookies" as well, but a PHP-Switch must be set the right way (I tried 4.5.x only). e.g. in the PHP-Section of .htacess: php_value session.use_trans_sid On which is Off by default.
Maybe there are other switches (cookie-only or similar) relevant in this case. Try the above switch and see.
BTW, a session-management ist nevertheless necessary, so by dropping cookies the session-id will be kept with the url, which is disputed on security reasons as far as I remember. I do not know yet all factors behind it. I do not like cookies, but I am not certain wether they are the less bad thing ;-)
The log-in on the Drupal main site works only with cookies enabled, I tried ;-)
Servus Franz
Thanks Franz. I do remember a discussion somewhere about this on 4.6.x and I thought the default (where mine is set) was to allow either. I know there are times I see the PHPSESSID in logs and sometimes not.
If the Drupal main site requires cookies, I would think there is a reason for it.
Thanks for your time on this! Skip
Wilbert, Earl, and Bill,
Thanks for your suggestions. Once I flicked the 'administer nodes' permission switch to on, it worked like I wanted.
One more small thing. When a content manager logs in, they can see the administer/content page; however, some of those pages aren't editable by normal content managers because they contain PHP code. Is there a way to hack it so those pages are not shown or disable 'em so they aren't hyper?
-
Bill Fitzgerald -
Earl Miles -
Franz Iberl -
Skip Taylor -
Travis Spencer -
Wilbert Berendsen