I am hoping to use the new version of phpWCMS in a school based environment. My goal is to allow the teachers to maintain a classroom webpage. The problem that I see with phpWCMS the way it is currently setup is that when you create a backend user they can add an article anywhere in the site structure. Is there, or will there be, a way to better define user rights in the new version of phpWCMS? Basically I don't want my users to be able to create content anywhere that I haven't specifically allowed.
J
User Rights
- Oliver Georgi
- Site Admin
- Posts: 9907
- Joined: Fri 3. Oct 2003, 22:22
- Contact:
Detailed Permissions
Hi,
Congratulations on a CMS implementation with better usability.
I am a PHP coder myself, and I like that you are using the database more, that leads to scalability. I am wanting to use this for my organisation, so the user rights are important for me now. I loaded the latest DEV release and I am running it on a WAMP platform, that's fine.
I see that the first steps in user management are in place.
Actually I dont think you need groups as a top priority, because you can always share a password and coordinate that way in the meantime.
I created admin and user1, but noticed that when user1 does not have ownership of an article, he may still change the visibility flags.
Also at the category level, when user1 does not have access to the level, he can still create articles in the level or move them about in the site.
Please forgive me if I have not understood the behaviours correctly, as I have only just started investigating this tool.
But I think these rights should be removed, do you agree?
Congratulations on a CMS implementation with better usability.
I am a PHP coder myself, and I like that you are using the database more, that leads to scalability. I am wanting to use this for my organisation, so the user rights are important for me now. I loaded the latest DEV release and I am running it on a WAMP platform, that's fine.
I see that the first steps in user management are in place.
Actually I dont think you need groups as a top priority, because you can always share a password and coordinate that way in the meantime.
I created admin and user1, but noticed that when user1 does not have ownership of an article, he may still change the visibility flags.
Also at the category level, when user1 does not have access to the level, he can still create articles in the level or move them about in the site.
Please forgive me if I have not understood the behaviours correctly, as I have only just started investigating this tool.
But I think these rights should be removed, do you agree?
- Oliver Georgi
- Site Admin
- Posts: 9907
- Joined: Fri 3. Oct 2003, 22:22
- Contact: