View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 1798 | Composr | import | public | 2015-02-08 17:45 | 2016-04-23 09:23 |
| Reporter | Chris Graham | Assigned To | Guest | ||
| Priority | normal | Severity | feature | ||
| Status | new | Resolution | open | ||
| Summary | 1798: Transfer Comcode ownership properly when importing | ||||
| Description | Currently Comcode ownership goes to the user doing the importing. This can cause something of a problem if that user then is no longer having 'reuse attachments' permission, as attachments will stop showing up. The ownership should carry over according to the user who owns the resource being imported OR even better the exact same owner it had in the source site (for an cms_merge import). | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | 5 | ||||
| Sponsorship open | |||||
|
|
Various solutions to this. One is to call insert_lang in API functions with the submitter user parameter of the function. Another is to fix it up after the API call finishes, resetting it to the correct Comcode owner for the import. Another one is a mass fix afterwards, with queries like: UPDATE cms_translate t JOIN cms_f_posts p ON p.p_post=t.id SET t.source_user=p.p_poster,text_parsed='' WHERE t.source_user<>p.p_poster; These approaches are not necessarily mutually-exclusive. |
