Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When the panels of a displays are saved using panels_display::panels_save_display(), newly added content with a key like 'new-n' is not removed correctly due to a wrongly used id. $id was used instead of $pid to delete the displays content. Please see attached diff.
| Comment | File | Size | Author |
|---|---|---|---|
| 2014-01-13-panels-cache-not-cleared-bugfix.patch | 855 bytes | adrip |
Comments
Comment #1
miklTo expand on this, this bug manifests itself as causing Panes to be rendered twice, once you save your changes after working with Panels IPE.
So, if those Panes add JavaScript settings to the page, those will be added twice, and thanks to Drupal's habit of merging the arrays with jQuery.extend(), that means the settings will be duplicated, so otherwise scalar values will become arrays of identical strings, causing the JavaScript that reads it to explode. This patch fixes that :)
Comment #2
japerryYup, verified the issue with IPE and the patch fixes the nasty JS problem when you continue to edit panes.
Committed here:
http://drupalcode.org/project/panels.git/commit/2be964d