#1240 closed defect (bug) (fixed)
Change storage of per-project permissions
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | high | |
Component: | Translate Site & Plugins | Keywords: | |
Cc: |
Description
Currently the project IDs are stored in a user meta. That was a bad idea because there is no easy way to get all translation editors (or contributors) of a project per locale.
We should have a separate table for this. Fields: User ID, Project ID, Locale, Locale Slug, Status (editor/contributor/blocked?)
Change History (16)
This ticket was mentioned in Slack in #meta-i18n by ocean90. View the logs.
9 years ago
This ticket was mentioned in Slack in #meta-i18n by ocean90. View the logs.
9 years ago
This ticket was mentioned in Slack in #polyglots by ocean90. View the logs.
9 years ago
#9
@
9 years ago
Related: #1398
Current plan is to use the new table only for project translation editors. Schema:
CREATE TABLE `translate_translation_editors` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL, `project_id` int(10) NOT NULL, `locale` varchar(255) NOT NULL DEFAULT '', `locale_slug` varchar(255) NOT NULL DEFAULT '', PRIMARY KEY (`id`), UNIQUE KEY `user_project_id` (`user_id`, `project_id`, `locale`,`locale_slug`), KEY `locale` (`locale`, `locale_slug`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
To handle General Translation Editors a new role will be introduced.
Note: See
TracTickets for help on using
tickets.
@ocean90 Is there anything we can do to help in this ticket?!