Closed (duplicate)
Project:
Chaos Tool Suite (ctools)
Version:
6.x-1.8
Component:
Exportables
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Feb 2011 at 00:09 UTC
Updated:
25 May 2011 at 18:32 UTC
Comments
Comment #1
sagannotcarl commentedtagging.
Comment #2
edward_or commentedIt looks to me that Custom Content Panes can not be exported using Features. I would, however, love to be wrong.
Comment #3
merlinofchaos commentedMy understanding is that anything exportable via export.inc should be exportable by features, but I am not familiar with features specifically.
Comment #4
edward_or commentedI have asked #1068528: Custom content panes Integration? over on the Features issue cue to see if they might be able to answer.
Comment #5
logickal commentedAfter digging though the Features code and talking a bit with merlinofchaos, it looks like Features is not handling exportables who have an API owned by 'ctools' - I still have a limited understanding of the intricacies of Feature's code, but it looks like that Features goes through and tries to create a hook_features_api() implementation for each module, passing through the ctools export functions, causing some sort of collision for these particular submodules that are owned by ctools. The Page Manager and Panel Layout modules are owned by themselves, so they have no problem being exported.
Comment #6
logickal commentedFor those that are interested, I've posted a patch to Features over in #7 at #1068528: Custom content panes Integration? that seems to fix the problem.
Comment #7
sagannotcarl commentedI'm marking this a duplicate.
It looks like #1079440: Module name check prevents panels custom content panes export has a long-term solution and #1068528: Custom content panes Integration? has a short-term fix (or so I gather from suggestions on those threads.
Comment #8
sagannotcarl commented