With latest dev of Panels, Ctools:
Create new panel page, without any of the special features, such as context. Creation finishes without a hitch.
In the page overview, click Context. The following error appears:
Notice: Undefined index: info_page in ctools_entity_from_field_get_children() (line 49 of /opt/local/apache2/htdocs/sites/all/modules/ctools/plugins/relationships/entity_from_field.inc).
Now, when proceeding and trying to add a view as context, I get two fields (for identifier and keyword) but no menu for choosing a view to use for the context.
On 'Finish', I get the error message 'you must select a view'. But I still have no meny with which to do that.
Comments
Comment #1
merlinofchaos commentedAssigning to EclipseGc to look at. He's been working on this system recently.
Comment #2
eclipsegc commentedI'm working pretty actively in these areas right now, but if you could give me a list of all the modules installed on your system, the version of php you're running and maybe an export of the custom page you made, that would make this easier to debug. If not, I'll just be extra watchful as I emphasize these sections for areas where I may have foreach'd an empty array element.
Comment #3
Anonymous (not verified) commentedGladly, here's the information.
Thanks,
Bas
Comment #4
erok415 commentedSubscribing
I'm having similar problems when trying to add "context" to panels.
I'm currently running D7 with PHP 5.2.x.
Here is the exact error that is a JavaScript alert when trying to add an ID to the context settings of a mini panel.
E.
Comment #5
erok415 commentedI'm getting this error also when trying to add a content pane to my panel variant. This is really odd.
E.
Comment #6
eclipsegc commented@bdhond
I don't have this issue in my current test environment. I imported your page directly with no issues at all and beyond that, there's not even an "info_page" key anywhere in this code so... I'm a little perplexed honestly. Double check to make sure you're at the latest dev, if you're still getting this code try checking:
git clone --branch 1079320 http://git.drupal.org/sandbox/eclipsegc/1073402.git ctools
In place of your current ctools. Clear caches and see if the problem goes away. If it STILL doesn't go away, then I'm thinking it's a php 5.3.x issue, but from the error you're reporting currently I'm not inclined to believe that.
The above clone is a testing branch in my personal sandbox for ctools, and I would highly recommend you NOT run it in production. We just want to test to see if the error goes away. If it does, then we're probably on our way to a fix and if it doesn't then we'll be at square 1.
Thanks!
@erok41
Please don't derail this issue into something entity module related. I understand you're seeing issues within the page_manager interface, but your errors are clearly stating there's an issue with entity module. While I don't doubt there could be some correlation, this is clearly a very different issue and you should probably address it in the entity module issue queue first. If that proves to actually indicate that it IS a page_manager issue then great, file an issue here and we'll follow up on it, but the entity support we have right now is completely core native and doesn't require entity module, so I'm sort of doubting they're related.
Eclipse
Comment #7
Anonymous (not verified) commented@EclipseGc: Thanks for pointing me in the right direction.
I managed to reproduce the error on a clean test site.
I asked for trouble, apparently, by starting to experiment with the Features module.
At some point, I deleted the content type info_page. But the Features module that was active, insisted that a shared field from this content type should still exist.
So the field was referenced in the database, as belonging to this non-existing content type.
This did not create problems anywhere else so far.
So whether it should be regarded as a ctools problem that the pages context system chokes on this, is your call...
Comment #8
merlinofchaos commentedYes, our content types are supposed to detect conditions like this; since panes can't automatically be deleted, we should be able to handle fields not actually existing. This gives us some ammunition to help figure out what exactly to do about it.
Comment #9
robin_jx commentedI met exactly the same issue. All the problem disappeard after I cleared the cache.
Comment #10
merlinofchaos commentedCommitted a quick fix that should prevent this from causing crashes in the future.
Comment #11
seandunaway commentedI think this quick fix had unintended consequences with page manager relationships.
Please see the attached image.
I have included a patch that reverts the code of commit: 72c79bc and that corrects the newly created issue.
However, I'm not sure about a solution to the original issue of this thread!
Comment #12
seandunaway commentedPage variant exported, if curious.
Comment #13
seandunaway commentedComment #14
merlinofchaos commentedThe problem is that it's testing $from_entity_info before it's assigned. Whoops. Bad me!