Next Version

The release notes for BLOX Total CMS client for Adobe InDesign and Adobe InCopy version 5.35.x can be found here.

5.34.07 Release 2018.11.14

Bug Fix) Many MacOS sites have experienced issues with the icons in the Asset Manager not displaying. We now have the MacOS based Asset Manager shake or jiggle the dialog and/or the child and related content areas. This seems to allow all the icons to display there. Note: This does not happen in MacOS with the legacy CS5 and CS 5.5 versions of Adobe InDesign and Adobe InCopy. Those versions do not allow this feature so it isn't used there. JIRA INDESIGN-401

New Feature) Users can now see the Do Not Publish status in the Adobe InDesign and Adobe InCopy Asset Manager. To view that, simply check Do Not Publish in the Preferences tab of the Asset Manager. JIRA INDESIGN-915

Logging Change) We now log the status of the Page Tracker Preview Adobe PDF Preset when saving pages. This is only for troubleshooting purposes. JIRA INDESIGN-2389

5.34.06-1 Released 2018.11.08

Important Bug Fix) There was a long-standing bug in our support for translating hyperlinks. Users would get errors either when translating or when writing-back hyperlinks from both Adobe InCopy and Adobe InDesign. All versions of those applications were affected. All known bugs regarding hyperlinks and the BLOX Total CMS client for Adobe InDesign and Adobe InCopy are now corrected. JIRA INDESIGN-2385

NOTE: Adobe Creative Cloud 2019 versions have a bug which causes hyperlinks to be shortened one character. This isn't a BLOX Total CMS client bug, but a bug in the original CC 2019 version of the Adobe InCopy and Adobe InDesign.

5.34.05 Release 2018.11.05

Newzware change) We worked with Newzware and changed our formula for placing ads vertically. The new formula allows the ads to match if the Newzware and Adobe InDesign vertical margins match. The old formula, which can still be used, allows an offset file to override the vertical positioning. This change only affects Newzware sites and only if they remove their .enabled file. JIRA INDESIGN-2388

5.34.04 Release 2018.11.04

Bug Fix) Additional problems were found and fixed with the opening of the Asset Manager. There have been ongoing problems for several versions. All affected users can now open the Asset Manager. Please create at support ticket at support.townnews.com if you notice any issues. JIRA INDESIGN-2344

Page Tracker Chained Output Changes) We have had reports from MacOS sites, who fail to keep the appropriate volumes mounted, with chained output requests that fail to complete. Unfortunately, the logging of these events wasn't detailed enough for us to determine what was happening. Now, when the chained output fails to get copied to the ultimate destination, a confirmation dialog will be presented and the user will have the opportunity to receive the properly named PDF file on their desktop. In addition, some extra logging will be done to make it easier for TownNews to diagnose the issue. Windows-based users will not see any differences unless permissions are causing a problem. JIRA INDESIGN-2379

5.34.03 Release 2018.10.30

Minor Bug Fix) If a user tried to get to the Add Selected Frame To menu without a document open, it would throw an internal error. This has been fixed. JIRA INDESIGN-2381

Minor Logging Change) When placing a story with or without children there are Adobe InDesign functions that trigger the automatic jump routines to check to see if a jump is being performed. On a single page document, it was unable to determine the name of the page in question. This has been corrected and the proper name will now be logged. This is used only during troubleshooting and doesn't affect users. JIRA INDESIGN-2383

Newzware Change) Our support for the Newzware edition files now supports reading their AdStatus field. If the value of that field is <80, we assume that the Ad file is not ready. We will add to the text frame the value of the status and also mark the ad placeholder frame internally that it is not ready. Our utility to copy ads will check this Not Ready status and it will skip copying ads when the internal mark has been set. JIRA INDESIGN-2384

5.34.02 Release 2018.10.23

Major New Feature) The BLOX Total CMS client for Adobe InDesign and Adobe InCopy now supports Collection assets. Collections can be placed on Adobe InDesign as the parent asset and all placable children can then be placed on the same page. Collections are not placable as a child of a different parent because we don't support placing grandchildren assets. Collection support requires updated rulesets to support them. Collections are also supported with Adobe InCopy Assignments. While we do generate Live e-Edition Segments for Collections, they are currently being sent as an Article asset because Live e-Edition didn't support Collection Assets when placement became functional. JIRA INDESIGN-842

  • Documentation for the Collection Support is here.

New Feature) We have added a new warning feature when opening documents that are dated prior to today. Some sites have a bad habit of purposely opening old documents to grab things that they should have created as snippets. This opening resets the purge cycle's clock and then next month the page is still in the directory causing other users to accidentally open last month's pages instead of the current pages. The problem is most prevalent at new sites that didn't make all their snippets early on, but some sites continue to struggle after opening old documents on purpose. There is now a feature that will warn a user when opening a document that is dated before today's date. The default button will close the document. JIRA INDESIGN-2207

Minor Bug Fix) We noticed an internal issue with determining the publication date that might have affected other checks of this date. We fixed that. The change might result in a very minor increase in speed as the date won't have to be recalculated later. JIRA INDESIGN-2207

UI Bug Fix) A change in the 5.31.x version of the client caused the display of most dialogs using the BLOX Total CM logo to be displayed no larger than the smallest monitor connected to the local workstation. In some cases, such as the huge Settings and Support dialog, parts of the UI was cut off. As a stop gap measure, that change from 5.31.x has been changed so that the dialogs can be no larger than the largest dimensions of any attached monitor. A future change will allow them to be reduced. JIRA INDESIGN-2226

Performance Change) The Adobe InDesign client automatically saves the Adobe InDesign document when the user has switched focus away from and back to Adobe InDesign. This saving can be slow if the user is working with a slow network connection. To speed up these users, the saving can be disabled. To disable the auto-saving, choose BLOX Total CMS > Settings and Support... Depending on your preferences either click the JT&S tab or the Jumps, Trimming & Saving tab. Uncheck the Save Document on Activation option. Note: This option does not exist if you are using an Activate.disabled file. JIRA INDESIGN-2306

Bug Fix) The 5.33.09 version of the client introduced a bug which made changing the Autoload BLOX Total CMS Preferences setting in the Settings and Support dialog impossible to change. This has been fixed. JIRA INDESIGN-2370

5.34.01 Release 2018.10.17

Major New Feature) As part of the distributed production, we now allow sites to share rulesets across multiple domains. This means if a domain doesn't need any customization different from another domain, they can cause it to use the other domain's rulesets without needing to export, delete, and import. The loading will be done automatically, in the background, by the Adobe InDesign or Adobe InCopy client. To enable domain B to use domain A's rulesets the following things must happen: (JIRA INDESIGN-2301)

  1. All Domain B's users must have login permissions for Domain A
  2. Domain B will need to have a single ruleset.
  3. The name of Domain B's ruleset will be the A's domain. For example, pleasantville.local (for appliance based sites) or mylocalnews.com (for sites without appliances).
  4. That one ruleset in Domain B must be the Default ruleset
  • It does NOT matter what is in that ruleset. It will be ignored. I suggest adding comments explaining its purpose: Redirecting to A

Prior Versions

Client 5.33 Release Notes

Client 5.32 Release Notes

Client 5.31 Release Notes

Client 5.30 Release Notes

Client 5.29 Release Notes