[geeklog-devel] GSOC 2010 application for Improvement in Configurations GUI

Abhishek Shrivastava abhi.nitt at gmail.com
Sun Mar 28 12:59:24 EDT 2010


> I would hate to see the feature table expand by several hundred entries
that most people would not use. The should be grouped.
> Anyone who can change the site_url should have equal access to every other
path related configuration. There's no reason to
> separate it. Likewise, anyone who could change the site_name, should have
equal access to many other settings. The existing
>features (like polls.admin) are sufficient for adding permissions to the
configuration system. In the end if you need to add more than
>a handful of features to the system, you've gotten too fine grained.

I understand your concern. Thats why I suggested there should be a different
table for configuration permissions. All the configurations will be grouped
into certain groups and those groups will also have permissions as a whole.
For mapping configuration to groups, this can be done in the existing
conf_values table itself without having to add any new rows. Only a new
column is required to be added in the conf_values to take care of which
configuration belongs to which groups.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20100328/c1a4cb30/attachment.html>


More information about the geeklog-devel mailing list