Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.At the moment there is no way to export a scald context and its configuration.
For example after adding a new context through the UI, it would be nice to be able to export that context in a feature. Also it is possible that we change the transcoder of a context. So should be able to export not just newly created contexts but even the default contexts' configuration.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | scald-exportable-1890104-3.patch | 8.16 KB | jcisio |
Comments
Comment #1
jcisio commentedThis would be a task!
Comment #2
jcisio commentedComment #3
jcisio commentedThis is a patch to make Context transcoder setting Ctools exportable. Only the settings is exportable, as contexts are defined in code and UI created contexts are already in a variable. I just make a mininal patch without any unnecessary refactoring.
update.php is required, as there is database schema change.
Comment #4
jcisio commentedIt needs to clear cache automatically when reverting.
Comment #5
jcisio commentedWell, I don't think that bug prevent this patch from getting in. Thus I went ahead and committed it. We need to clear cache after features-revert and it could be fixed in a follow-up, low-priority issue.
Another follow-up is to replace the deprecated structure
$contexts[$name]['type_format'][$type]with$contexts[$name]['transcoder' and so on].Comment #6
jcisio commentedHere you are: #1914506: Switch to $contexts[$name]['transcoder'] structure and #1914508: Must clear cache after features-revert to update context config.