500 error when attempting to add some content to panelizer

This appears to be a bug in Panopoly.

When I stick a print_r() in the exception in entity_extract_ids(), I discover that panopoly_magic.module is calling fape_field_edit_field_form() on line 650. However, the $entity is not valid, and fape has no provisions for that being called with an invalid entity. (This may be a validation bug in fape, from that perspective).

Moved back to main queue

Assinging to beeradb sine he loves UUID and FAPE

The base issue is that when editing a pane that uses an entity context, you cannot assume the entity is already known. If it comes from arguments then the entity is merely a placeholder when using the back end. I put a hack in our panopoly magic to check for the entity before adding the FAPE call (and submit handler), and it seemed to do the trick, but I have no idea if that's correct.

Mind posting the code you have from #4? Panopoly Magic is making a lot of conditional judgements and adding a logical check there sounds fine.

Here's a patch which prevents the issue from occurring.

Long term it would be nice to refactor the code around determine the entity type, field name, and entity ID. This refactoring would need to occur outside of Panopoly, as the primary issue is that the data isn't available in form_state values, so we're forced to use a combination of url args, form state values, and finger crossing to hope we can determine the correct entity. In cases like this (where this is no entity), we don't have much of a recourse currently but to do some defensive coding around the possibility.

Great. Reviewed + Pushed.