Bugfixes
- Global CSS: a page loaded at the moment of the one-time backslash conversion could show the unconverted CSS once, and a page cache could keep it
- Item skin editor: a “between” visibility rule lost its second value when the rules dialog was opened again, so after a save the layer showed on every item
- A stored name or value with a quote or a bracket stopped the item skin editor, the grid editor, a post’s Essential Grid settings or Export with a script error
- Grid editor: navigation modules placed outside the grid showed the grid’s navigation skin instead of their own, and a save could give the other modules the grid’s skin
- Duplicating an item skin also copied the Global CSS rules of other skins whose names start the same way
- Import: the Append or Overwrite choice for an item element was ignored, or applied to another element, when the stored element had a different id
Changes
- Security: The item skin editor builds layers and layer styles from stored skin values as text and keeps only valid CSS declarations, so a stored or imported value can no longer add markup or CSS rules in the editor
- Security: Imported item skins and item elements get their handles the way the skin editor makes them, for every user
- Security: The front end builds video frames, video posters, lightbox thumbnails, the mobile filter list and the cover effect styles from item data as text, never as markup
- Security: The image options of a post are stored only as one of their choices, and the lightbox links of a skin’s content images are escaped
- Security: Gallery grids show only image attachments as items, and Load More shows only images the visitor may see
3.2.6

