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.
If no defaults are defined for an entity bundle, when outputting the Panelizer Status filter the following errors can show>
Fatal error: Unsupported operand types in panelizer_handler_filter_panelizer_status.inc on line 31
Warning: natcasesort() expects parameter 1 to be array, null given in panelizer_handler_filter_panelizer_status->get_value_options() (line 27 of panelizer_handler_filter_panelizer_status.inc).
Comment | File | Size | Author |
---|---|---|---|
#1 | panelizer-n2242643-1.patch | 951 bytes | DamienMcKenna |
Comments
Comment #1
DamienMcKennaThe $options array needed to be defined before the foreach() loop, for scenarios when the entity bundle is not Panelized.
Comment #2
kepford CreditAttribution: kepford commentedCreating a view with a filter on type now results in the following message "No valid values found on filter: Fieldable pane: Panelizer status.".
Comment #3
kepford CreditAttribution: kepford commentedIf the table `panelizer_defaults` is empty and you select a type of filter you will get ""No valid values found on filter: Fieldable pane: Panelizer status." Maybe the filter should not be offered if the fieldable panel pane is no panelized?
Comment #4
DamienMcKennaOk, I guess we'll need to have a follow-on issue to handle "What to do if there are no defaults."
Comment #5
kepford CreditAttribution: kepford commentedI see the issue when there are values in the table as well. I'm not familiar enough with views_filter_handlers() to explain why yet.