Using Panels to override the node view display for certain content types. I have placed to different node fields directly into two different regions. One field is a field from the node (Og group type field), the other is a field from a field collection. They are both set to dispay as 'system blocks' in the panels style settings.

Of the resulting panes, one has a class 'block-entity-field-229', the other 'block-entity-field-229--2'. However, the Skinr links for two pane blocks are admin/structure/skinr/edit/nojs/block/entity_field__229/configure - meaning that they both share the same Skinr configuration. So making a change to the skin of one pane also affects the other.

CommentFileSizeAuthor
#3 skinr-panels_uuid-1330306-3.patch20.31 KBmoonray
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

moonray’s picture

Status: Active » Postponed

Indeed they should. This is a limitation with panels... we need unique UIDs for panes, but panels won't put them in. So until they do, there are several problems with Skinr's panels implementation.

moonray’s picture

Issue summary: View changes
Status: Postponed » Active

Panels now uses UUIDs! Hooza!
Patch coming.

moonray’s picture

Status: Active » Needs review
FileSize
20.31 KB

With UUID for panels panes our settings should no longer disappear or get applied to the wrong pane.

  • Commit 6b1249f on 7.x-2.x by moonray:
    Issue #1330306 by moonray | mrfelton: Updated skinr_panels to use UUIDs...
moonray’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.