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.
I get this error when using a View pane in a Mini Panel:
Notice: Undefined property: views_plugin_display_default::$panel_pane_display in views_content_views_panes_content_type_render() (line 142 of /sites/all/modules/contrib/ctools/views_content/plugins/content_types/views_panes.inc).
Comment | File | Size | Author |
---|---|---|---|
#7 | ctools-views_panes_undefined_property-1787898-7.patch | 700 bytes | Arnion |
#3 | ctools-views-panes-undefined-property-1787898-#3.patch | 700 bytes | tseven |
#1 | 1787898.patch | 832 bytes | Arnion |
Comments
Comment #1
Arnion CreditAttribution: Arnion commentedI solved this way. Do not know if this error have wider implications.
Comment #2
Arnion CreditAttribution: Arnion commentedThe error occurs when you delete a display in use.
Comment #3
tseven CreditAttribution: tseven commentedI was getting this error on every view. The patch in #1 has fixed it.
I'm attaching a reformatted patch wich can be applied using
patch -p1 < ctools-views-panes-undefined-property-1787898-#3.patch
Comment #4
Chi CreditAttribution: Chi commentedThe patch in #3 is not downloadable.
Comment #5
merlinofchaos CreditAttribution: merlinofchaos commentedHeh. Bug on drupal.org -- the # in the filename is not being encoded, but if I encode it manually I can download it.
This works: http://drupal.org/files/ctools-views-panes-undefined-property-1787898-%2...
Comment #7
Arnion CreditAttribution: Arnion commentedI upload the patch corrected.
Comment #8
jwilson3#7 resolved the issue for me, but I'm actually glad the error happened, because it alerted me to the fact that there was missing content on the page in the watchdog logs, which would have otherwise gone unnoticed.
Comment #9
jwilson3Here is a proper review:
Three lines in the patch have trailing whitespace.
I'm still not sure this is a desired solution though, such as for the case mentioned in my previous comment, when its helpful to know that something is misconfigured. Could we replace the ugly php error, with a *separate* check for isset and use a meaningful error message if its not set?
Comment #10
ajwn CreditAttribution: ajwn commented#3 resolved the issue, orphaned views referenced in the panelizer content stack. Thanks.