Just found this out:

When panel variants are exported as Features, they are incompatible with one another. The reason is they're assigned with the same page manager handler - "node_view_panel_context".

To solve the incompatibility, we modify the page manager handler name, after the feature was created. The name exists in 2 files:

*.info
*.defaults.inc

Search for "node_view_panel_context" and replace it with a unique name like "node_view_panel_context_biography".

That should make the panel variant features compatible with one another.

Comments

jonskulski’s picture

jonskulski commented

subscribing

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented
Version: 6.x-1.0-beta6 » 6.x-1.x-dev

Yes, same issue here. Changing the code is a decent workaround, but it would be great to be able to set an alternative context machine name in the UI somewhere. To be honest though, this may be a Panels feature request, rather than a Features bug!

?

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Cross-posted this in Panels too: #813754: Ability to set variant machine name in Panels UI

hnln’s picture

hnln commented

subscribe

crea’s picture

crea commented

Subs

mpotter’s picture

mpotter commented
Status: Active » Closed (won't fix)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.