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.
Panopoly users is used within Open Atrium and oa_panopoly_users tries to override (features override) page_manager_handlers.pm_existing_pages_user_login_panel_context.conf|body_classes_to_add
and because it doesn't exist in panopoly_users, panopoly_users tries to add it to its page_manager_handlers. It seems if the defaults of: 'body_classes_to_add' => '',
and 'body_classes_to_remove' => '',
are added to panopoly_users then the problem is resolved, does this seem right? I will upload the patch just in case.
Comment | File | Size | Author |
---|---|---|---|
#1 | panopoly_users-body_classes-2193399-1.patch | 882 bytes | scottalan |
Comments
Comment #1
scottalan CreditAttribution: scottalan commentedComment #2
scottalan CreditAttribution: scottalan commentedOk, I may have just learned something about `defaultconfig`. When I patched this feature with the patch above, the feature is no longer showing overridden. This is related to https://drupal.org/node/2193381.
This is what
drush fd panopoly_users
was showing:I didn't realize that even though a
drush fd [FEATURE]
would show it overridden, thatdrush fd
does not.Comment #3
dsnopekI'm not sure I understand the problem. What's the symptom of this bug? Is something overridden? Or is a Feature not reverting/installing correctly?
Comment #4
dsnopekNo reponse for a long time! Closing for now, but feel free to re-open if you add them.