Super weird, when I try to create Mini Panels, the drop downs for the context and and relationships now include dozens upon dozens of each type of context. There are about 20 of each Comment, File, Node, Taxonomy, Profile, Profile Type, Relation, Rules, Rules Configuration appearing in the drop down (see screenshot). Views and Node Add/Edit appear only once. When I click a random one, the ajax screen pops up and says it's an "invalid context type". So now I can't create any Mini Panels.
I have been seeing this same drop down appearing in other panels, but it was small at first and didn't seem to affect anything.
Please help. I need my panels.
Note, I did test the dev version and still had the same issue. I also completely uninstalled all of Panels and re-added it and still had the same issue.
| Comment | File | Size | Author |
|---|---|---|---|
| mini_panels_bug.jpg | 36.49 KB | prodigeek |
Comments
Comment #1
prodigeek commentedAlso, this is happening on Node Panels as well. There aren't as many drop down items as on Mini Panels.
Comment #2
merlinofchaos commentedalready fixed in latest dev of CTools.
Comment #3
prodigeek commentedAwesome, thanks
Comment #4
prodigeek commentedThat didn't work. There are fewer duplicate entries and this time only for required context, not regular context.
Comment #5
karens commentedI'm seeing this too on latest dev release (for both CTools and Panels). The duplicates in required context are still there.
Comment #6
prodigeek commentedI did find out, this is caused when the Views content pane is enabled. Disabling it removes all duplicates.
Comment #7
mrfelton commentedI'm seeing this too. Latest ctools dev. I have Views Content panes enabled too. Looks a bit like this.
Comment #8
merlinofchaos commentedWhile annoying, this is clearly not critical.
Moving to CTools, where this bug has to exist. Maybe there was something I missed.
Comment #9
alanom commentedBug still there in today's dev release with yesterday's Views dev release - and it's still giving a 'Invalid context type' error as in the initial issue on any of the items that I try, so as well as being annoying, it is also breaking functionality.
Curiously, for me there are four items in the list that aren't duplicated, and these don't fail with the 'invalid content type' error - for me these are 'Node Add Form', 'Node Edit Form', 'User edit form', and 'String'.
As for the others, there look to be 11 of each, and it seems that each of these 11 duplicates fail. Contrib contexts (e.g. from search api) get duplicated and fail like the others.
Like everyone else here I have Views Content Panes enabled, and this problem seems specific to Mini Panels 'Required contexts'. Unchecking 'Make all views available as panes' in panels settings doesn't change anything.
Hope some of this info helps.
Comment #10
alanom commentedOkay, actually it's not 100% broken, just ludicrously inconvenient... there is a workaround.
I had another look at mrfelton's post and noticed that all the 'duplicates' had different value attributes. Hitting the mini panels page with Firebug, I'm finding that if you can wade through the mess of duplicates and find the one with the appropriate value attribute, it seems to work without causing an error.
For example, for 'node' context, I'm finding the fifth 'Node' option in the 11 node options has the html...
<option value="entity:node">Node</option>...and works, whereas all the ones that fail have one of the other entity types between 'entity:' and the correct entity type.
Also, like in mrfelton's HTML, in mine it looks as if like each of the entity types that gets duplicated causes a duplicate in each other, if that makes sense. So instead of the values being a pattern like this:
...seems like they're being written like this (but without such an obvious order)...
Hope that helps, at a guess I'd say looks like a nested loop gone rogue.
Comment #11
merlinofchaos commentedThe issue is, I think, that entity children are accidentally reprocessing themselves and causing invalid duplicates to appear in the list. I fixed this once but I can't seem to find the commit in the logs now. It's also possible that it needed to be fixed in two places; one for contexts and one for required contexts.
Indeed that's correct; my previous fix wasn't the best fix. I just committed a new fix that should fix this once and for all.
Comment #12
NathanM commentedAlso having this issue. Will try out the fix here.
Comment #13
NathanM commentedUpdating to latest ctools and panels dev seems to have fixed the issue for me.
Comment #14
bryancasler commentedI can confirm that updating to the latest devs does indeed fix this.
Comment #15
raulmuroc commented