As far as I can tell, it appears that this module will not work with exported panels (ie exported via Features). I want to make sure my understanding of this is correct...
I had everything working well in my test environment, but, when I exported everything out and reverted to the in-code versions, ESI stopped being able to render the panes. It appears that, both in the 6.x and 7.x versions, the pane rendering code relies on knowing the display ID. Exported panels, though, don't have display IDs, so the ESI tags lack the required did parameter, and panels_load_display() won't be able to locate the display in question.
I'm trying to determine what my course of action is here. We currently export ALL panels configurations into Features. This keeps us from being able to use these two together. I find it odd that I can't seem to find any other d.o issues about this considering that both Features and ESI use tend to run together in larger deployments.
In any case, it seems to me that the only way to handle this would be to either force a re-saving of all exported panels configurations that use ESI into the database or to rewrite portions of the module so that it is able to address the pane via the containing panels configuration (page_manager, mini panel, etc).
Is this a known issue? Has anyone else come across this and handled it somehow that can be reproduced?
Needs review
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Updated merge request to account for cases when arguments are invalid and we are unable to find a pane. Combine with 🐛 ArgumentCountError: Too few arguments to function esi_panels__esi_pane_prepare() if request made to esi/%esi_component without additional arguments Needs review patch to return 404 in menu callback when render returns FALSE.