If I click "Customize this page," "Add new pane," "Entity" I get:

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /panopoly/panels/ajax/ipe/select-content/panelizer%3Anode%3A3/contentmain/entity
StatusText: Service unavailable (with message)
ResponseText: EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7539 of /Users/abyron/Sites/panopoly/includes/common.inc).

Comments

wim leers’s picture

Same here.

populist’s picture

This might be related to #1627862: Unable to add 'entity' to a pane, but it can be solved by better passing the $context in Panopoly Magic.

populist’s picture

Status: Active » Fixed
StatusFileSize
new1.2 KB

Here is a patch to address #2

esmerel’s picture

I opened the same problem in panelizer yesterday since I wasn't sure of the right place to put it. I've closed that one as a dup.

esmerel’s picture

I'm willing to assume I'm not doing something correctly here, but:

I applied the patch
- download to sites/all/modules/panopoly_magic
patch -p1 < 1598990-panopoly-magic-better-renderer.patch

It said panopoly_magic.module was patched

I tried it and got the same error. I tried drush cc all, refreshed the page and still the same error.

I'm not going to re-open it yet - if someone else tries it and gets the same results then I'll know it's not just me :)

esmerel’s picture

And just so I can be more annoying: I get a similar error when I try to add "Existing pages" as well. 500 error, AJAX HTTP error, and a long url path

My access_log shows this, which is the same long url message I'm getting in the pop up.

"POST /panopolynodemo/panels/ajax/editor/select-content/panelizer%3Adefault%3Anode%3Ablog%3Anode%3Ablog%3Adefault/top_right/existing-pages HTTP/1.1" 500 - "http://esmerel.logrus.com/panopolynodemo/admin/structure/types/manage/bl..." "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.52 Safari/536.5"

%3Adefault%3Anode%3Ablog%3Anode%3Ablog%3Adefault ... I admit I'm not a code person, but that looks hinky to me.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.