- Moderated by:
- Support
-
- rank:
-
Freshman
- registered:
- July 2007
- Status:
- offline
- last visit:
- 30.05.08
- Posts:
- 30
permission scheme eh. that means almost nothing to me =p. PostNuke is new to me, and the only thing i know about permission is to put people in certain groups to give them rights.
i'll elaborate. i just want to give specific users the ability to add articles/stories without giving them permissions to turn off the site, change settings, etc. is this in any way possible?
-
- rank:
-
Softmore
- registered:
- April 2004
- Status:
- offline
- last visit:
- 19.02.08
- Posts:
- 57
Hey David,
Bonus Round: :)
How do I give admin permissions to only ONE topic of the stories?
I was able to use this thread to give one group permis. to admin all stories, but I'd like to keep one group specific to admin all stories under one particular topic, but read only in all the others.
Code
1 Admins .* .* Admin
2 All groups Menublock:: Main Menu:Administration: None
3 Editors Topics::Topic PrivateAdminDocs:: None
4 Editors Topics::Topic (specificTopicName) Admin
5 Editors Stories::Story .* Admin
...
This permis. set allows the "Editors" to admin all stories, no matter what the topic.
When I remove Line 5, they can no longer edit any stories, so it looks like line 4 isn't doing anything... unless I don't have the right syntax.
Any suggestions?
AmmoDump
Okay, you are talking full site admin, I was saying why not give Group X full admin to Stories only.
http://community.postnuke.com/module-Forum-viewtopic-topic-53713.htm
-
- rank:
-
Helper
- registered:
- February 2003
- Status:
- offline
- last visit:
- 01.12.08
- Posts:
- 193
Personally, I found the online documentation pertaining to permission to be useful.
It's not that easy to find, so here's a link.
http://community.postnuke.com/Wiki-PermissionsAdmin.htm
Frank's comment about reading the permissions from the bottom up worked for me too :)
--
- Darryl -
Every time someone refers a new Zikulan to the SVN, God kills a kitten.
Visit ZikulaPlus.com for......PLUS! -
- rank:
-
Softmore
- registered:
- April 2004
- Status:
- offline
- last visit:
- 19.02.08
- Posts:
- 57
I did actually find that article before posting here (but thanks for the link anyway, I should have stated that in my post) and that's where I started my permissions test. But the results are stated above, I can't limit to one topic, so I must not have the right second or third column syntax right. I've tried specifying a topic and the permissions ignore that I've set only for one topic. The system does the same for all topics (either all or none).
I've even tried setting "read" for the other topics and "admin" for the one. (i.e., Frank's restriction lines above access lines)
But that meant nothing to the permissions also. -
- rank:
-
Team Member
- registered:
- December 2003
- Status:
- online
- Posts:
- 2993
awpresley
Hey David,
Bonus Round: :)
How do I give admin permissions to only ONE topic of the stories?
You people are all crazy...
With your double-secret topic schema. I must tell you I have never once created a restricted topic. Anyway I think the 'trick'
here is to add your topic ID (sorry too much coffee)
[quote=awpresley]Code
1 Admins .* .* Admin
2 All groups Menublock:: Main Menu:Administration: None
3 Editors Topics::Topic PrivateAdminDocs:: None
4 Editors Topics::Topic (specificTopicName) Admin
5 Editors Stories::Story .* Admin
...
Ding.. Ding.. /start bonus round/
For Example:
3 Editors Topics::Topic PrivateAdminDocs::8 None
--
David Pahl
Zikula Support Team -
- rank:
-
Softmore
- registered:
- April 2004
- Status:
- offline
- last visit:
- 19.02.08
- Posts:
- 57
Hi David, Thanks for replying. :)
Actually line 3 works just fine as demo'd above. It prevents people from seeing pages while I or my staff works on them before publishing. (kinda like a staging site that every good website needs.)
What I'm having problem with is line 4 and/or 5.
the permis. shown do prevent the PrivateAdminDocs from showing, but your comment made me think that maybe I should use the topic ID NUMBER instead of the topic name?... Maybe that's what's missing from my permissions?
So, seriously... you've NEVER restricted a topic? Anyone can post a new story in your webpages??? Employees and Customers? -
- rank:
-
Softmore
- registered:
- April 2004
- Status:
- offline
- last visit:
- 19.02.08
- Posts:
- 57
ok, progress, but I'm not quite where I want to be yet.
So, I figured I'd post my progress for anyone else who may want to see and or give a test.
(see original permis. above)
changed line 4 to
Code
4 Editors Topics::Topic EditorTopic::4 Admin
I got the "topicid" number (EditorTopic::4) from Administration>Topics then mouseover the topic desired and read status bar.
Then removed line 5 to see if this would give access to only the stories in "EditorTopic" topic.
It did not. HOWEVER... it DID give the selectable option to the Editor when they went to "AddStory". :) (this user could not select a topic previously.)
So, I restored line 5 and the Editor could then edit all stories, no matter what topic. :|
So, next I'll try limiting the other topics for this group and see what happens then.
edited by: awpresley, Feb 18, 2008 - 03:24 PM -
- rank:
-
Softmore
- registered:
- April 2004
- Status:
- offline
- last visit:
- 19.02.08
- Posts:
- 57
AmmoDump
Ding.. Ding.. /start bonus round/
For Example:
3 Editors Topics::Topic PrivateAdminDocs::8 None
David,
unfortunately this did not prevent the user from viewing nor prevented him from editing the story in that topic. :(
even after removing:
Code
5 Editors Stories::Story .* Admin
users in this group could still access and edit stories in that topic.
so I also removed:
Code
6 TrainingEditors AddStory:: :: Edit
then they could read the story (even though it states "none") and they could see the "edit" button on the story, but they could not use it.
All good information. Like Thomas Edison said, "I definitely know more ... ways how NOT to make a light bulb."
