We're using Panopoly for a project and are generally really happy for all the great functionality it brings. We have amongst other things based some functionality on the Categories taxonomy, and have now run in to some problems.

We would really like to change the default layout of the panelized term page for Categories via Features, but as this has already been done via the panopoly_core feature, we have no way of providing our own configuration without overriding the setting directly in our prod environment.

It would have been nice to be able to use something like features_override to do a "clean" override of the feature, but unfortunately panelizer is not compatible with features_override.

So, we have implemented a small patch that
- Provides a new system setting that allows a user to disable panopoly_core's panelizer features.
- Adds a system_info_alter that hides the exportables specified in the modules .info
- Adds a conditional around the ctools_plugin_api part that announces the exportables

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

danquah’s picture

Status: Active » Needs work
FileSize
5.25 KB

Patch attached.

Current version of the patch only seems to apply on 1.0-rc3, I'll do a reroll as soon as possible.

populist’s picture

Project: Panopoly Core » Panopoly

Awesome to hear. Moving to the main queue for review, but check out http://drupal.org/project/features_override which might help you right now.

kasperg’s picture

Unfortunately Features Override does not support Panelizer as Panelizer does not provide an alter method.

beeradb’s picture

Status: Needs work » Postponed (maintainer needs more info)

Thanks for bringing this up. I'm hesitant to move forward with a one-off solution for this stuff that isn't in line with a more standardized way of doing things. Does someone mind giving a more detailed overview of what the issues are between making panelizer and features override play nicely together? If possible, it'd be preferable to focus efforts in that direction over creating a one-off solution.

kasperg’s picture

I have started an issue on the topic in the Panelizer issue queue.

I do not think it lies on Features Override to deal with this unless the approach taken in this patch - messing with hook_ctools_plugin_api() and hook_system_info_alter() - is sanctioned out of necessity.

populist’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)

I am going to close this issue since I think the #1856076: Support Features Override is the right place to chat about this!

kasperg’s picture

In case anyone stumbles upon this, Panelizer now supports Features Override so the patch in this thread should no longer be necessary. Current users should switch to Features Override.