The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.One of the latest changes #1772834: Panels IPE Save Drops Context Specified in Page Manager fixes a problem with the IPE context, but introduces a new one with handling of contexts on the back end. In particular, there is a problem with the node_edit handler where the latest -dev no longer recognizes that a form context is present.
The attached patch helps to illustrate the problem (without it there are no form elements available to be added to a node_edit page and with it there are), but it breaks the change made in #1772834: Panels IPE Save Drops Context Specified in Page Manager.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 1801422-better-context-setting-in-cache-operations.patch | 749 bytes | populist |
| panels-node-edit-more-context.patch | 550 bytes | populist |
Comments
Comment #1
populist commentedI did more research and believe the problem we introduced with #1772834: Panels IPE Save Drops Context Specified in Page Manager was that the context caching system was dependant on a key that provided the arguments. This has trouble with you have placeholder arguments (i.e. node edit pages) and needs a more global context call to capture all of the arguments.
This patch switches up the caching logic so that conditionally loads the contexts appropriate for arguments, but if there are no arguments present it will load all arguments. It solves the problem with the node_edit handler *not* having the right context AND it allows things like the search page to maintain context with the IPE.
Comment #2
merlinofchaos commentedThe patch in #1 would not add contexts that were added as part of the handler, which only shows up if you add relationships or the like in the handler on places like the node edit page that doesn't have its own contexts tab. I added that back in and after spending some time trying to decide if this was really the right approach, I went ahead with it.