Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Currently exporting panels and views overrides is intentionally disabled, only because it seemed unlikely they would work.
Issue is that plugins may be their own object type. The way exports currently are serialized won't handle that.
To investigate: should we export to text when saving in the DB? That way we could try to get the native export. However, would require using drupal_eval()
.
Comments
Comment #1
nedjoActually, serializing shouldn't be a problem, the question is whether the export to text will get the object types correct. Do we need to call the native export functions?
#895250: Address performance issues will remove the exclusion for panels and views. Testing will be needed from there.
Comment #2
nedjoApplied #895250: Address performance issues in http://drupal.org/cvs?commit=468526.
Comment #3
nedjoAdded code to detect and handle recursion when iterating arrays or objects in http://drupal.org/project/cvs/894352. Views overrides now export. More testing needed.
Comment #4
nedjoRemaining work moved to #932806: Test/fix overriding of Panels and Views.
Comment #5
nedjoFixed in #1048322: Recursion errors when adding view override component.