Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2008-08-14 10:21:32

FireFusion
Member
Registered: 2005-05-10
Posts: 698

Custom user groups through admin interface

I was just looking at Chyrp and saw how they have a custom user groups option. I thought if something as basic as that can have it why can’t we :)

It just has tick boxes for the different permissions and place to type a group name.

“Groups” could be a subtab under users

Preset groups and permissions seem very out of date to me.

Last edited by FireFusion (2008-08-14 13:47:45)

Offline

#2 2008-08-14 13:58:00

renobird
Member
From: Gainesville, Florida
Registered: 2005-03-02
Posts: 786
Website

Re: Custom user groups through admin interface

I was just thinking about this the other day.
This is a great idea

Offline

#3 2008-08-14 14:11:55

ruud
Developer Emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 5,068
Website

Re: Custom user groups through admin interface

I’m guessing this would break just about any plugin that depends on a privilege level.
Not that I don’t like the idea… just considering the consequences.

Offline

#4 2008-08-14 14:21:23

variaas
Plugin Author
From: Chicago
Registered: 2005-01-16
Posts: 402
Website

Re: Custom user groups through admin interface

wouldn’t the fix for the plugins be as simple as the fix required to be compatible with 4.0.6?

Offline

#5 2008-08-14 15:45:33

ruud
Developer Emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 5,068
Website

Re: Custom user groups through admin interface

I think currently most plugins assume that the permissions are set identical as a fresh TXP install. If privilege level 1 is suddenly re-assigned to a group of freelancers, that would give those people far to many privileges in some plugins. The ability to completely re-define privilege levels makes it difficult to write plugins that rely on privileges in they way they currently do.

The privilege fix that was required for some plugins to function in 4.0.6 was due to implementation errors in those plugins, that already existed, but were not exposed until 4.0.6

Last edited by ruud (2008-08-14 16:16:37)

Offline

Board footer

Powered by FluxBB