The ID of the bodycopy asset is now part of the template tag for content variations


The HTML output of a content variation's <template> tag now includes the ID of the bodycopy asset as an attribute (data-bodycopy_id), providing more control to any custom frontend JavaScript logic that shows or hides content variations based on certain conditions.

This is useful when using content variations on standard pages and where the associated persona asset is set to evaluate its conditions client-side.

An example of the <template> tag in this HTML output will now look like this:

<template data-bodycopy_id="1234" data-client-variation_id="int-user" data-client-variation_personas='["int-user"]'>

Other improvements

  • #725 - Update Polish translations
  • #759 - Remove unnecessary sections on the Form Contents' Details screen
  • #780 - Update password field on a PDF asset to the new password field type

Bug fixes

  • #420 - Binoculars do not find first X assets in a page after a certain point
  • #746 - Odd grammar is used in the virus detected error message
  • #750 - Remove each() calls for PHP 7.2 support
  • #758 - Top level keywords replacement is disabled for redirect page asset
  • #764 - Clean up "continue targeting switch..." errors for PHP 7.3
  • #766 - When moving an asset to a new location, the permissions and metadata schema are not being inherited from the new parent
  • #769 - A forced HTML protocol redirect causes the query string to be escaped
  • #774 - The deprecated split() function is called on Scheduled Manager Jobs
  • #775 - The Bodycopy_Table asset is referenced from the User Group Security Restrictions screen
  • #796 - The asset listing displays the safe edit page name
  • #811 - When in safe edit mode, the Content Container properties pop-up box on a new standard page causes a fatal error
  • #812 - Revoking access tokens results in issues with Google Analytics when the view has a connector attached