Ticket #1079 (new defect)

Opened 4 years ago

Last modified 4 years ago

Problem handling same permission names in different modules

Reported by: rofranco Assigned to:
Priority: normal Milestone:
Component: module - user Severity: major
Keywords: Cc:


We submitted ticket #1060 in order to allow the detection of permissions in managers with the same name but in different modules.

Now we realize that some new managers with the same name (like "FileMgr?" or "CategoryMgr?") have been added to Seagull, but the "detect&add" functionality is not working.

The "permission" table has a unique key using the name of the permission. So, maybe we should change Seagull in order to construct the permission names using the module name also.

Change History

07/26/06 10:08:48 changed by demian

  • priority changed from high to normal.

Hi rofranco, can you give more detail regarding "the 'detect&add' functionality is not working"?

i don't think it's a good idea to include the module name in perm name, for 1 it would require a mass of changes, for 2, FileMgr? is only in two places because whole of publisher module will soon be superceded by cms module, in progress.

my idea so far is to default installer to install core modules only, rest can be chosen, then disallow media and pubisher modules to be simoultaneously installed. what do you think?

07/27/06 06:07:34 changed by demian

  • owner deleted.

only core modules are installed by default now, however i'd still like to hear if there is a prob with 'detect and add' as you say.

08/13/06 17:15:32 changed by demian

  • milestone deleted.