Ticket #1746 (new enhancement)
Opened 13 months ago
Translator Permission Handling
| Reported by: | ischommer | Owned by: | bfojcapell |
|---|---|---|---|
| Priority: | medium | Milestone: | |
| Component: | i18n | Version: | |
| Severity: | high effort / impact | Keywords: | |
| Cc: | Hours: |
Description
// i18nRole.php
function extraDBFields() {
return array(
'db' => array(
'i18nStatus' => "Enum('NotAUser, Translator, Banned')",
'i18nReceiveUpdates' => 'Boolean(1)'
),
'defaults' => array(
'i18nStatus' => "NotAUser",
'i18nReceiveUpdates' => true
)
);
}
we're usually assigning stuff like i18nStatus on a group-base. you're already got permission like CMS_ACCESS_i18nTranslator in there, should be sufficient from what i see. permissions don't cope with user-specific flags such as "banned", but i don't think we need this very urgently.
can you reason why this user-specific columns exist, and if we could get rid of them in favour to the silverstripe-permission-system?
Note: See
TracTickets for help on using
tickets.
