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).

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Arnion’s picture

FileSize
832 bytes

I solved this way. Do not know if this error have wider implications.

Arnion’s picture

The error occurs when you delete a display in use.

tseven’s picture

I 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

Chi’s picture

The patch in #3 is not downloadable.

merlinofchaos’s picture

Status: Active » Needs review

Heh. 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...

Status: Needs review » Needs work

The last submitted patch, ctools-views-panes-undefined-property-1787898-#3.patch, failed testing.

Arnion’s picture

I upload the patch corrected.

jwilson3’s picture

#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.

jwilson3’s picture

Here is a proper review:

+++ b/views_content/plugins/content_types/views_panes.incundefined
@@ -139,7 +139,12 @@
+      !$view->display_handler->access($GLOBALS['user']) ¶
+      || !isset($view->display_handler->panel_pane_display) ¶
+      || !$view->display_handler->panel_pane_display
+      ¶

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?

ajwn’s picture

Issue summary: View changes

#3 resolved the issue, orphaned views referenced in the panelizer content stack. Thanks.