|
Thursday 20 January 2005 2:42:10 am
Yeah yeah.. we have thought about this, please have a look here: http://ez.no/community/news/the_administration_interface_project ...and here... http://ez.no/var/ezno/storage/images-versioned/141595/1-eng-GB/screenshot31.gif ..as you can see, the menu was planned; but unfortunately it was left out of 3.5 because of the following reason: It would require more processing & bandwidth because of the necessary permission/access information. We could of course skip this, but then the risk of users getting ACCESS DENIED (because they do not have permissions to create a certain type of object at a certain location) would emerge. Some people think that this is bad. Feel free to discuss what you think is best:
1)
Not having the menu.
2)
Having the menu without the necessary permission checks (in other words: the menu will include all classes regardless if the logged in user is allowed to create all those classes at that exact location). Some users might get ACCESS DENIED, but it might just work for the most typical/usual cases (where only one admin or a bunch of admins without limitations are using the interface).
3)
Having the menu with the necessary permission checks - this will most likely slow down the interface (a lot).
4)
Perhaps make it configurable.. (on/off and just go with suggestion 2). Allman
|
