In this release of BLOX Core (version 1.86.0), we are introducing support for concurrent relationships and two new UTL (Universal Templating Language) options, including a sort for arrays and an option to check for keywords, and a number of bug fixes.
FEATURES
Developer Note: Sorting UTL-generated arrays previously required macro-level logic, which added technical debt and reduced efficiency by pushing business logic into the presentation layer. This update introduces a native sort filter for use within UTL templates, enabling more performant and maintainable sorting operations. (TNCMS-555082)
Filter Name: sort
Options:
order: 'asc' (ascending) or 'desc' (descending). Defaults to 'desc'.
preserve_keys: true retains original keys for associative arrays. Defaults to false (returns reindexed array).
Example Usage:
[% [3, 1, 18, 9] | sort('order':'asc') | json %] [% your_array | sort('order':'asc', 'preserve_keys':1') %]
Developer Note: A new method, has_keyword(), is being introduced for all asset types to simplify keyword checks in templates. This native method improves performance by handling logic in PHP rather than through utility macros and helps reduce template complexity and technical debt. (TNCMS-555564)
Example Usage: [% this.asset.has_keyword('sports') %]
IMPROVEMENTS
We've introduced support for Concurrent Relationships, enabling newsroom teams to collaborate more effectively by preserving related photo associations during concurrent edits. (TNCMS-555631)
What’s New:
Editors can now maintain photo relationships added to an article asset while it’s being edited by another user.
When saving, newly associated photos are preserved as child assets unless explicitly removed by the editor.
How It Works:
This applies only to photos added as related items, not metadata or other asset types.
Additive relationships are maintained unless manually removed by the editor.
Normal behavior continues if no newer revisions exist for the asset.
The 60-character hard limit for SEO titles has been removed. Users can now enter titles of any length, with a visual suggestion flag appearing when the recommended length is exceeded. A tooltip provides guidance on best practices, allowing more flexibility while still supporting SEO optimization. (TNCMS-555570)
BUGS
A lock file mechanism has been introduced to reduce duplicate article submissions to Apple News, a known issue when assets are rapidly updated. This improvement ensures articles are treated as updates—not new submissions—by preventing multiple tasks from triggering before Apple News responses are processed. This feature remains in a closed beta as we continue refining integration stability. (TNCMS-555647)
Resolved an issue where the Teaser image editor was incorrectly loading the cropped version of an image instead of the original image. This prevented users from properly updating the crop. (TNCMS-555762)
Resolved an issue where ‘cms.url.path’ did not consistently return the full section path when the "Insert asset titles into asset URLs" setting was enabled and an asset had a populated SEO > URL Title. In some cases, the final section in the path was omitted, impacting use cases like Google Ad Manager (GAM) targeting. The logic now correctly reflects the canonical URL structure, ensuring accurate path rendering and consistent behavior across templates—regardless of whether SEO titles are used in URLs. (TNCMS-555622)
This release also makes minor infrastructure changes that should not be noticeable to admin or front-end users.
If you experience any issues or have any questions, please contact customer support at (800) 293-9576 or BLOXDigital.com/support.