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.
It would be useful if the Panelizer system was weighted to take effect after the other Page Manager handlers. Currently the weight is set to -100, which effectively makes it show first, thus blocking all of the other Panels content type definitions, this should probably be set to 100 to load after them instead.
Comment | File | Size | Author |
---|---|---|---|
#1 | panelizer-n1290452-d6.patch | 1.16 KB | DamienMcKenna |
#1 | panelizer-n1290452-d7.patch | 1.09 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaThere isn't a good place to control this, so I just implemented a "hidden" variable called "panelizer_handler_weight", but I did at least document it in README.txt. Patches for D6 and D7 are included.
Comment #2
merlinofchaos CreditAttribution: merlinofchaos commentedThe panelizer default is actually intended to process as early as possible by default so that it can be sure to process instead of other items. Moving it last seems like you would then be in danger of accidentally having panelized nodes fail to panelize because some other less important variant picks it up first. (Plus, you end up spending more resources calculating variants when you probably didn't mean to).
So I am not sure I think this change is correct.
Comment #3
merlinofchaos CreditAttribution: merlinofchaos commentedPerhaps #1268902: Selection rule doesn't seem to be a selection rule is the appropriate solution.
Marking postponed on this, we can come back and see if this is still needed after that is resolved.
Comment #4
merlinofchaos CreditAttribution: merlinofchaos commentedIt seems highly unlikely to me that we need to change the weight now. The task was not letting non-panelized nodes through. That was a major bug; with that fixed, we want the panelizer task to be a high weight so that it will always panelize rather than let default node variants happen.