Permission suggestion

  Hi!

At my work as the webmaster at my school I recently happened to wipe all the 
permission settings for all about 170webpages of the site. (Don't know if the 
fault was mine, being tired... or Typo3 being unreliable and buggy as 
usual. :-) I thought that I was screwed, until I found that because people 
have only their own threes (=collections in FluxCMS) mounted when logging 
into the CMS they won't even notice my screwup.

So what could we learn from this exept that working late night on important 
tasks or using Typo3 is a big no no? :-) I think the thing we can learn is 
that very often a site is structured in such a way that sertain people are in 
charge for sertain parts (=threes) of the site, including all the subpages of 
those threes.

And what does this mean for Flux CMS? I think it means that implementing a 
rather simple permission feature, which only limits what collections a 
sertain user/usergroup sees when logging in would be sufficient in many 
cases.

Of course a more complicated way to limit access to editing pages one by one, 
in a more UNIX filesystem-like manner (or something) could be useful, but I 
guess it'd be harder to implement... so that could be left for the "Advanced 
permissions plugin" that you've planned for sometime in the future.

For now maybe a simple limitation of which collections a user could mount 
would be a good choise. What do you think?

Happy Easter holiday! ;-)

  cheers, Simon
-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms