5.80.00-07 Released 2025.09.09

Template Master Support to Remove Image Toning Preferences) There is now an option for the Template Master to remove any uploaded Image Toning preferences from Page Tracker on a domain-by-domain basis. Originally, the uploads were intended to provide Remote Distributed Production users with a way to access the site’s image toning options. However, some sites handle image toning post-output, and thus users at that site need no image toning preferences at all. There is now an option at BLOX Total CMS > Development > Image Toning Options > Remove Uploaded Image Toning Preferences... to remove the uploaded preferences files. In addition, there is a menu option nearby to remove the local preferences. In both cases, the preferences are moved the the Backups folder. INDESIGN-4116

Change to Combine Pages when Non-BLOX Total CMS document is open) When choosing BLOX Total CMS > Documents > Page Management > Combine Pages..., the BLOX Total CMS client for Adobe InDesign first checks for any open documents that don’t match the current page naming convention and halts the process. We had a site that used documents not named for the active domain, and that caused issues when all documents needed to be closed to safely combine pages. INDESIGN-4437

Revised Distributed Production Metadata formats) To maintain compatibility with the BLOX Total CMS plug-in for Adobe InDesign, both the package metadata and the link information are now written in a different format. INDESIGN-4475

WARNING: If you’re a Distributed Production site, you need to upgrade the client versions at the same time. Clients running versions before 5.80 may encounter an error when attempting to read files produced by clients running version 5.80 or later. If a remote user only works on pages they create, no errors will be generated. If remote users build pages and in-office users output pages, update the in-office users first.

Modification Distributed Production Document Activation) Client version 5.75 added a change for Distributed Production users to allow the missing links to be recreated in Adobe InDesign. This was needed becuase editing assets in the browser while the Adobe InDesign document was closed caused the links to be missing when opening the document. Unfortunately, it recreated more links than were necessary. This caused assets to appear checked in after document activation events. That appearance then prevented the output methods from checking the assets in properly. Without the ability to check them in, the asset’s workflows were also not advanced. This resulted in some assets in Distributed Production documents from reaching the final process. If the site used the workflow process to trigger website visibility, it could cause the assets to switch to becoming e-Edition Sourced assets. The behavior has been changed, and now only missing links caused by the browser-based edits will be recreated. INDESIGN-4476

Auto Image Export Improvements) Internal testing would occasionally experience a race condition when opening BLOX Total CMS documents and immediately placing image assets. If the page wasn’t marked as being Color or Black and White, then when the user was prompted to select the page’s color, a delay would sometimes cause the auto image export for toning to silently fail. This issue has been improved, and it now exports all images at the time of placement if the toning preferences request it. INDESIGN-4480

Confirmed Snippet Placement) An earlier change to the BLOX Total CMS client for Adobe InDesign for placing Page Content Snippets only confirmed that they place correctly when creating pages using BLOX Total CMS > Documents > New... We’ve now ensured that they are placed when the Page Content Types are assigned during the creation of the edition. In addition, if the user cancels the application of a plug-in produced snippet, it no longer attempts to locate the legacy snippets. This last change speeds up the creation of the edition. INDESIGN-4482

Workaround for Improper Related Content items) The original version of BLOX NXT’s Related Content items didn’t get a UUID as expected in legacy BLOX. Since the UUID is expected for write-back of related content items, that issue should never happen. The BLOX Total CMS client for Adobe InDesign wouldn’t translate assets with related content missing their UUID, since they wouldn’t write-back. Now, it will simply remove the related content item with a logged entry. Importantly, the assets missing the UUIDs were a temporary issue with BLOX NXT that has been resolved. INDESIGN-4485

Better Descriptions from Failing to Update Placement on Children In Draft Status) If you place an article asset on an Adobe InDesign page with children that are in Draft status, you will now be told that the children will be released. The segmenting information for the released children will be retained, as that feature was added in client version 5.79. INDESIGN-4489

Prevention of Forced Frame Check Out) During routine testing of the BLOX Total CMS client for Adobe InDesign, one of the BLOX Total CMS team members determined that an asset with a Draft status could have its Adobe InCopy link, used by the client for asset locking, forcibly unlocked by using the native Adobe InDesign’s InCopy > Check Out function. This use is now monitored, and the native Check Out will be canceled. INDESIGN-4489

Child assets with an active Draft cannot have their placement information saved, as neither BLOX nor BLOX NXT allows Adobe InDesign to overwrite an asset with an active Draft. Because of this, by default, children with an active Draft will not be automatically selected for placement on Adobe InDesign. This can be overridden, but the result will be that the assets will need to be released to the Adobe InDesign page. However, since client version 5.79, the asset can still be included as a child for the live e-Edition. To facilitate the transfer of knowledge about the draft mode, the Draft column, available in the Asset Manager, is now included in the dialog for selecting child assets to place. INDESIGN-4492

Prior Version

The release notes for client 5.79 can be found here.