Release Notes: Picturepark Content Platform (May 2019 Update)

Picturepark Content Platform is released in its newest version:

  • Platform release date: 3-May-2019.
  • Picturepark version: May 2019 Update (10.1.2).
  • Platform(s): {name}
  • For this release all current instances on the affected platforms are updated.


Release Summary

The Picturepark May 2019 Update is focused on improvements in UX, data core, permissions handling, search and batch editor, and documentation.

Most notable changes worthwhile to know:

  • Circular references (or cyclic dependencies) are now supported making it possible to refer from one record to another, and vice-versa.
  • Creating filters in tagbox fields is now simpler. A generate default values button has been added for Checkboxes as well as single- and multi- tagboxes.
  • The content search has been split into a “Simple” and “Advanced” search mode with support for advanced query syntax.
  • Channels now feature a “View for All” flag which no longer requires administrators to add (new) user roles to each channel, unless such access restrictions are needed.
  • Display patterns now feature an improved editor and the DotLiquid engine for rendering these patterns has been replaced with Fluid for better performance.

Release Details


Users and Editors will enjoy an improved UX in many areas of the system such as the batch editor, creating display patterns, search and permissions.

The content search has been split into a “Simple” and “Advanced” search to improve performance (see screenshot below). The simple search is the default search and it escapes all ElasticSearch reserved characters and boolean operators, automatically adding the “AND” operator among all search terms. When using the Advanced search, users can make use of e.g. “AND”, “NOT”, “OR” and other Boolean operator among the terms if that is their intention. The Advanced search is only enabled if the user clicks on advanced with the last search mode used stored in the user settings and preserved for the next search.

Easier toggling between simple and advanced search modes.

Users find the content schema of virtual items instead/aside the display pattern so that they can more easily identify such content.


Editors can import/export large amounts of virtual content and list items (we have removed the 10k limit; the 20k limit for file items on transfer (upload and import) however still remains.

The Batch editor has been reworked and will function much more smoothly with better UX for confirmation messages (see screenshot below). Parent-child layers are now also supported in the Batch editor too so you can add and batch edit multiple Parent / Child layers conveniently.

The batch editor enables to edit huge amounts of content fast and reliably, now also supporting parent-child layers.


The creation of channels and permission sets via API is now possible and the API complete to setup or configure a complete customer in a fully automated way.

Formats can now be repaired via API for failed content items which did not render properly e.g. due to the rendering service being unavailable or rendering component improvements. An automatic job is configured to run every hour to re-render failed items.

Note: The new dedicated permissions for “extracted data” such as XMP, EXIF etc. might cause microsite SDK breaks – please consult Support for change management advice.


Display patterns are easier to create with the new editor, we have also replaced the DotLiquid template language with the Fluid template language (see screenshot below). This is due to DotLiquid appearing not to be maintained anymore and also due to the performance improvements gained by using Fluid. The syntax for the display patterns will have changed and requires you to rework your display pattern code if not yet done so properly.

Due to the new editor, display patterns are now easier to create.

Admins can automatically create a filter based on the default values of Tagbox fields, and then refine the filter as needed. This eases filter creation substantially.

Admins can define dedicated permissions for “extracted data” such as XMP, EXIF etc. which will now also be shown as layers (this will cause microsite SDK breaks – please consult Support for change management advice).

Admins can define edit/assign permission for layers which enables only permitted editors to assign the layer or edit layer metadata even if they can view the layer content. This helps better control and protect metadata stored via layers for content.

Admins can now use a “View for All” flag which no longer requires administrators to add (new) user roles to each channel, unless such access restrictions are needed.

Known Issues

Here a list of known major issues that you need to be aware of when using the Content Platform in its current version:

Batch Editor The Batch editor has limited support for some field types and shows a few minor inconveniences:

  • Fieldset, Relationship and Geopoint fields can not be edited at the moment. Support for these fields in single edit mode of the batch editor is scheduled for a next release.
  • Translations are not visible in View mode.
  • It can happen that the thumbnails change size and are displayed smaller, with a white border.

Shares The effective expiry date set in Picturepark is an hour after the Expiry date displayed in the Share Widget to downloading users.

Import/replace Replace file does not replace the thumbnails anymore when you refresh the content browser. You have to refresh your browser using F5 in order to see the new thumbnail.

Permissions Users that don’t have permissions to root channel cannot search or share content. This is scheduled for resolution in a next release.

Picturepark updates When a new Picturepark version becomes deployed, the user has to reload it in the browser manually via F5.

Contact Picturepark support if you encounter any known issues not listed above.