Next Version

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

5.33.10-2 Release 2018.10.16

Bug Fix) InDesign CS5, CS 5.5, and CS6 users reported that the asset manager was walking across the screen on each open. This was due to the way that these legacy versions recorded dialog positions. The client code has been changed to set the dialog to the correct location. However, some users might notice that the size of the dialog wants to grow to show all controls. JIRA INDESIGN-2344

Bug Fix) The 5.33.08 and 5.33.09 versions had a bug caused by a fix to a different hyperlink export bug. This cause it to throw an error when the hyperlink couldn't be exported because it had no Adobe InDesign or Adobe InCopy identification number. The lack of an identification number would have prevented export anyway, but we have fixed the display of the bug and now display the lacking identification number. JIRA INDESIGN-2350.

Feature Confirmation) We had a report that the MacOS version of the client was failing to locate the keyboard shortcut sets to export so that they could be loaded by other users. We confirmed, as did the reporting site, that the feature was working correctly. JIRA INDESIGN-2366

5.33.09 Release 2018.10.10

UI Bug Fix) The Ad Statuses dialog could be displayed larger than a user's monitor. While the default button selected in the browser-based preferences would be still the default (and selectable with the enter/return keys) and the escape key would click cancel, functionality was reduced by the oversized dialog since not all the controls were reachable. This has been corrected. JIRA INDESIGN-1140

Bug Fix) The technique we use to check how the shares are mounted in MacOS (we are looking for SMB 3 for ultimate performance) do not work for users without local administrator privileges. This resulted in a lag in launching Adobe InDesign and logging in as the internal errors were processed. Now, if a user's client fails this check, their client will no longer check the shares on subsequent launches and logins. JIRA INDESIGN-2323

Important Advertising Support Bug Fix) There is a possibility that this error has affected more than the one site that reported it and provided logs for us to look at. If this sound familiar, you should upgrade your client to 5.33.09 or newer. If your site uses our Advertising support and if they use Page Content Types, there was a chance that we would mark some ads on pages as unknown ads and the defaults to Fix Errors or Fix Errors and Warnings in the Ad Statuses dialog would remove those ads. This was caused by having a page content type whose number of characters after automatic cleanup of spaces and punctuation matched the length of the Adobe InDesign page naming convention. This has been fixed and the length of the two names no longer matters. JIRA INDESIGN-2360

Bug Fix) The ability of Adobe InDesign to Autoload Adobe PDF Presets was inadvertently configured so that it also required the autoloading of BLOX Total CMS preferences in Adobe InDesign. This dependence has been removed. You will see the preference to Autoload Adobe PDF Presets in the Autoload (renamed from Preferences) tab of BLOX Total CMS > Settings and Support... JIRA INDESIGN-2361

Available MacOS Workaround) As a last resort for a couple of MacOS sites that have an occasional workstation that will not load the .framework package that provides our communication with BLOX Total CMS, we have added an ability to not required the daily unzipping of the local framework file and instead it will rely upon the use of one created by a site administrator. If you need this workaround, please contact Customer Support at and request assistance with JIRA INDESIGN-2363.

5.33.08 Release 2018.10.08

Minor Bug Fix) If a site using our advertising functions was creating an edition for the 2nd (or more) time and canceled the dialog for selecting which .adinfo files to delete, a warning dialog would have been presented. The warning is no longer provided unless an error occurred deleting the .adinfo files. JIRA INDESIGN-845

Bug Fix) Some non-Creative Cloud users found that some of the recent changes to the Asset Manager prevented the window from changing size while the tabs would reduce in size. JIRA INDESIGN-2344

Bug Fix) We had reports again of issues exporting hyperlinks when creating an assignment and have added both better logging and extra error protection for the problem. We still do not know the actual causes nor have we been able to replicate the issues which result in the hyperlink being removed from the asset. JIRA INDESIGN-2350

Bug Fix) A single MacOS user managed to perform a series of actions quicker than their workstation could keep up with. That then caused a failure in their final action of performing a Save As which then broke and triggered several errors. We have modified the BLOX Total CMS for Adobe InDesign client to return the same document rather than the new named one if this happens again. JIRA INDESIGN-2352

Bug Fix) The Close all Documents feature was not configured to update Page Tracker. It now does this. In addition, it there are assets on the pages, it will also update the Document Jump Segment Cashing and update any assignments. JIRA INDESIGN-2354

Bug Fix) A recent change in the client code to remove support for the legacy translation files failed to properly remove all support. And users with a personal preference to use them found that they could no longer translate anything in Adobe InDesign or Adobe InCopy. This has been corrected and the legacy personal preference is now ignored. JIRA INDESIGN-2357

5.33.07 Released 2018.10.02

Bug Fix) An event handler was generating errors when attempting to close documents. This could have caused document to not close properly. We believe this issue is now fixed. JIRA INDESIGN-2340

Bug Fix) We had a report from a single site that some permissions on some document folders caused other users to not be able to properly access some of the sub-folders and this, in turn, caused some errors to be presented concerning the Ad Statuses function. We believe we have protected the client from displaying the errors, but if something causes a permission error, Ad Statuses still might not function correctly. JIRA INDESIGN-2341

Minor Logging Bug Fix) The output functions logged some of the pdf preset information incorrectly. It is now more readable by listing the requested name and the found preset. This only affected TownNews' troubleshooting. JIRA INDESIGN-2342

Bug Fix) A recent change to the asset manager caused several users to generate errors while attempting to restore the asset manager's size and position to values from prior to the update. We believe this has been corrected. JIRA INDESIGN-2344

Bug Fix) A change in January of 2018 broke the Benchmarking function. It has now been fixed. Benchmarking provides a way to compare current, past, and new versions of the client for responsiveness to the file server shares. It doesn't test CMS responsiveness, just file server responsiveness. JIRA INDESIGN-2345

Bug Fix) The Build Edition Report function didn't enable and disable with the Enhanced Mode. Instead, you had to log out and back in to swap the activation of the Build Edition Report menu item. This has been fixed and the menu item toggles with the status of Enhanced Mode. JIRA INDESIGN-2346

Translation Bug Fix and/or Translation Change using Nested Styles) When exporting text using Nested Styles in Adobe InDesign or Adobe InCopy that applied a bold or italic based attribute, sometimes the entire paragraph would be wrapped with a strong or em tag. Nested styles should not have been exporting any tags to BLOX Total CMS other than one for the paragraph if it was specified in the Export ruleset. IMPORTANT NOTE: This might cause a change at some sites. We do not know how long this bug existed or what change caused it. It could have been in place for a long time and not reported. If you were used to seeing certain formatting from the Adobe InDesign page or Adobe InCopy article written-back, those formats might no longer be written back. Please do testing after installing this version. JIRA INDESIGN-2348

5.33.05-06 Released 2018.09.11

Bug Fix) The initial version of the feature to clean up legacy version files was throwing an internal error with every login if no .version files existed. This has been corrected. JIRA INDESIGN-1730

Bug Fix) The function released in client 5.30.02-1 that added the ability for a template master to push a set of user preferences didn't work for a new user, only existing users. This has been corrected and sites can now create the desired preferences file and when the Adobe InDesign and/or Adobe InCopy users first login, they will get the default BLOX Total CMS preferences file. JIRA INDESIGN-2262

Asset Manager Preference Bug Fix) The prior 5.33.04 version added a preference for Lock Size of the Asset Manager to prevent it from growing too big when using multiple monitors or when using excessive numbers of search results. Unfortunately no default value was provided so it could act odd when first used. The default has now been set so that if the user has more than one monitor, it will automatically be turned on when opening the Asset Manager. JIRA INDESIGN-2278

Asset Manager Bug Fix) The prior 5.33.04 version automatically removed from the UI the Create Assignment button from the Asset Manager if Adobe InCopy Assignments weren't enabled in the BLOX Total CMS > Settings and Support... dialog. But unfortunately, during certain translation options, the rest of the Placement Options couldn't be read and acted upon. This has been corrected. JIRA INDESIGN-2278

Minor Bug Fix) If multiple .version files were located when a user launches, and if this was the 1 in 1000 launches that clears the .version files, the client logged some incorrect information about the files that remained after purging. This has been corrected and the logged information is correct. This can be simulated using the Development Mode function, Remove Legacy .version Files. JIRA INDESIGN-2337

5.33.04 Released 2018.09.10

Bug Fix) Earlier in 5.33.x, we changed the automatic jumping functions to prevent it from wanting to provide jump lines when threading frames. But on occasion, at some sites, with some versions of Adobe InDesign, it was falsely indicating threading rather than jumping and prevented any jump from working. We have changed this so that now it must have a positive indication of threading before preventing jumping. If you are threading frames on the same page, there is a preference at BLOX Total CMS > Settings and Support... in the Jumps tab to Confirm Auto Jumps. JIRA INDESIGN-734

Asset Manager Bug Fix) A relatively recent update of the Asset Manager caused it to no longer recall its last used size and position. This bug has been fixed. If the Asset Manager is completely on a single monitor screen, it should reopen to the same size and position providing it wasn't closed using the Cancel button. JIRA-INDESIGN-2278

Asset Manager Change) Some Windows 10 users have discovered they can change the UI settings to enlarge certain aspects of the user interface. The problem is Adobe InDesign isn't aware of these options (particularly the non-Creative Cloud versions) and dialogs become too large for the monitor. We have added an option in both Settings and Support's Dialogs tab and the Asset Manager's Preferences tab to request a reduction in the size of the Asset Manager. When selected several of the search options are removed and the amount of internal spacing between items in the Asset Manager are reduced to allow the dialog to open on the equivalent of a smaller monitor (using Window's enlarge UI has the same result as using a monitor with fewer pixels). JIRA INDESIGN-2278

Asset Manager Change) You can now search for 75 assets at time in the Asset Manager. Previously the available number of assets to return were 12, 20, 25, 50, and 100. The 100 value tends to cause issues with enlarging the dialog too large and triggers an automatic reduction of the Asset Manager's size, so we have added an option for 75 which skirts this limit. 50 assets, however, is a really good value. If you think you need more, you really need better searches. Saved Searches are your friend and time saver, not more search results. JIRA INDESIGN-2278

Adobe InCopy Change) If Adobe InCopy Assignment support has been removed for a site, the Asset Manager will no longer show the option to Create Assignment. The only impact of this is that some sites use Create Assignment to automatically create a combined asset for of merged items for use in the Live e-Edition's river of news. If this is needed, just enable InCopy in the Adobe InCopy tab of BLOX Total CMS > Settings and Support. JIRA INDESIGN-2278

Minor Logging Fix) When the BLOX Total CMS client for Adobe InDesign or Adobe InCopy logged all the advanced searches, it listed them with character encoding that made it hard to read. This has been changed. JIRA INDESIGN-2336

5.33.03 Released 2018.09.07

Bug Fix) The recent changes for jumping with and around threaded frames on the same page had a bug which in some cases prevented the page name from being determined which prevented jumping. JIRA INDESIGN-734

IMPORTANT Image Toning Bug Fix and Change) Some sites used non-file safe characters such as apostrophes, colons or slashes in their slugs. This prevented the sites from exporting a images for toning using the advanced options in Image Statuses. All images exported for toning, and thus searched for for replacement of a toned image, will have all non-alphanumeric characters and all non-hypen and non-underscore characters converted to underscores. If anything appears similar to an HTML tag, it will be removed. Double-spaces will be converted to single spaces. Double-underscores, space underscore, and underscore space sequences will be changed to a single underscore. Any name ending with an underscore will have the trailing underscore removed. If you are toning images in advance, the toned copies will need to use this image naming cleaning rules. We continue to recommend using our Image Statuses option and export sized images with unique naming for the best image quality and perfect image swapping. In addition, because of the cleaning up of the slug, if you insist on doing toning in advance, please keep the naming simple and completely unique so that the conversion to underscores doesn't prevent a match with your pre-toned image. JIRA INDESIGN-804

Bug Fix) The Image Statuses dialog never indicated if the image was out of date or missing. It now has a column for the image link status. If the link is normal, no icon is shown. If the linked file is out of date the normal will appear. A missing image will show the red stop sign icon with a question mark. If, for some reason, some other status exists, a question mark will be shown. Some additional processes will remove the ability to export or import an image whose link is not normal. JIRA INDESIGN-1097

Bug Fix) The Image Statuses Export function was failing to recall the last use export choice. It now does this. JIRA INDESIGN-1695

Improvement) When an Image's status is not normal (missing, out of date, etc), the Image Statuses function will now automatically open Adobe InDesign's Links panel so that the user can fix the issue in Adobe InDesign. JIRA INDESIGN-2195

Bug Fix) When the Image Statuses function could not import a toned image, the dialog that was displayed didn't indicate what was wrong with the image that was preventing Image Statuses' use. The dialog that is displayed now has more details and includes the images link status. JIRA INDESIGN-2195

Template Master Bug Fix) When using the Spawn Template function, sometimes the name of the Master Document failed to increment and instead produced an endless number of _2 versions of the Master Document. This has been corrected. The recommended naming is still Prefix Master Document SequenceNumber. For example petmi Master Document 05.indd or Broadsheet_MasterDoc_14.indd. JIRA INDESIGN-2330

Template Master Bug Fix) We had a report that the great new Template Master function to Spawn a template wasn't always properly sorting the names of the styles. This is because they were being sorted in the Master Document and the export through the .idml file would unsort them. We now sort in the Template and in the Master Document to keep both sorted. JIRA INDESIGN-2331

Bug Fix) The login routine was creating both a Add-ons folder and an unused Add-Ons folder. This has been corrected. Only the Add-ons folder is needed. JIRA INDESIGN-2333

Template Master Bug Fix) Spawn Template did not export fonts when sites were using the Legacy Creative Suite versions of Adobe InDesign. This has been fixed. Sites should still move to the Creative Cloud versions of Adobe InDesign and Adobe InCopy as Adobe no longer support the CS versions and TownNews no longer tests with CS5 or CS 5.5. JIRA INDESIGN-2334

Template Master Bug Fix) The Spawn Template should have forced the Allow Pages to Shuffle option so that the folios were set correctly when using Create Edition from Edition file followed by Create Pages. It now does this. JIRA INDESIGN-2335

5.33.02 Released 2018.08.31

Important Bug Fix) During work on the <&hiddenlabel:> issue below we noticed that the visibility of the print_trim text condition is changed during the fitting of place head frames such as the print_headline frame. This is not necessary because those frames cannot have trimmed content (the browser interface doesn't support it) and so the change of the trim condition only make the process less stable (prone to crashing Adobe InDesign) and wasted time. Now, the <&fit:> command will only change trimming visibility when it is fitting a frame that supports trimming. JIRA INDESIGN-91

Template Master Bug Fix) We had reports that the <&hiddenlabel:> translation script function was flawed. This has been corrected and it now works fine. This can be used to push into notes tags from the raw assets that sites want to keep. For example, the slug tag can be turned into a note if desired using this Translate Script command. JIRA INDESIGN-91

  • Notes, in general, don't get along well with several of the translation functions as they are both visible to, but unchangeable during, translation. Thus, do not add the <&hiddenlabel:> or <&notes:> at a location in a ruleset where its content will be further modified.
  • Notes are never able to be merged. Thus when merging, they will always be removed. This is the way Adobe InDesign handles the process and not something that the BLOX Total CMS client can work around.

Long Standing Bug Fix) Until this point of time, the menu item at BLOX Total CMS > Story Flow Options > would not check any options if more than a single frame was selected. This has been corrected. If all the selected frames have any Story Flow Option property set, then that menu item will be checked. JIRA INDESIGN-280

Minor Performance Enhancement) When changing the element type or file references of selected frames we now use a quicker method of passing along the active document. It is doubtful the users would notice any difference. JIRA INDESIGN-280

Bug Fix) The Document Jumps Manager's Relink function wasn't properly sending the document reference to a sub-function which was then throwing an error. This has been corrected. JIRA INDESIGN-554

Bug Fix) The Document Jumps Manager had a bug which failed to allow it to use its Relink function. Relink is used when a user and manipulated the pages in a document receiving document and thus the Document Jump page is displayed incorrectly. The bug prevented Relink from asking which document to relink to. It has been corrected. JIRA INDESIGN-633

Bug Fix) A long standing (dates to 2015) bug was fixed. The Document Jump Manager would not allow relink to be completed if the original linked document was no longer there. This could happen if after one user Created a Document Jump page another user then used Combine with on the same page. That causes the Receiving Document to not be valid and thus, because of the fixed bug, the Document Jump Manager would fail to relink it. Now, when the Receiving Document cannot be found, a new option is available: Relocate. In the case of another user using combine with, the Document Jumps manager will locate the correct page in its new home. If, for some strange reason, a user has physically removed the receiving document, then the Document Jump Manager's Relink option will allow another document in the section to be used instead. Remember, users should never physically delete BLOX Total CMS documents. They should be moved to the document's Backups folder instead. JIRA INDESIGN-633

Bug Fix) The Update option in the Document Jump Manager will NOT be available if the Document Jump page has its link missing. JIRA INDESIGN-633

Bug Fix) The settings for asking about jumping in a single page document were stored in the wrong location. That could have caused the value to be ignored. This has been fixed. JIRA INDESIGN-734

Bug Fix) The function for adding the jump items to an article incorrectly prompt for the jump Keyword and Jump Head if you were threading a story on the same page of a multi-page document. This prompting no longer happens if the frame created by picking up the Adobe InDesign Out Port is on the same page any any other frame of the thread. JIRA INDESIGN-734

Improvement) You can now jump an article asset across many pages of the same document. Previously we limited jumping to single pages. While that makes complete sense for true written word articles, it doesn't work well for calendar listings or things like restaurant guides where there is an actual likelihood that someone would bother to follow the jump. JIRA INDESIGN-734

Bug Fix) If you attempt to jump a story in Adobe InDesign that another user had checked out, an error dialog would have been displayed that wasn't clear on the issue. This has been changed and now the user will get a dialog explaining that the asset is in use. The dialog will look similar to the one below. The jump itself will actually be created, but the asset will not get the Jump Keyword or Jump Headline added to the actual asset (since it is locked by the other user). The page, however will be fine. JIRA INDESIGN-2312

Bug Fix) MacOS users are able to reach the BLOX Total CMS menu when dialogs are open, but Adobe InDesign and Adobe InCopy frequently cannot act on even properly displaying the menu items when a dialog is open. But when a user would try, errors would be thrown. We now attempt to prevent the menus from being drawn for MacOS users when a dialog is open. JIRA INDESIGN-2317

Important Bug Fix) For several years, jump items have been able to use line breaks if the various frames by including <&r> for a return or <&br> for a soft return or line break. Unfortunately, they weren't always converted back to the returns or line breaks. This has been corrected. JIRA INDESIGN-2318

Bug Fix) While examining a log file from a client, we noticed an error that can prevent the processing of placed child assets. We've made a slight adjustment in the client to help prevent that error. JIRA INDESIGN-2321

Bug Fix) We had a log from a client site that led us to believe that a particular user's Adobe PDF Preset for Page Tracker, the PageTrackerPreview preset, was bad. That in turn caused an internal error and the inability to send previews to Page Tracker. We believe this has been fixed, but as we can not reproduce the problem we cannot verify the change. JIRA INDESIGN-2322

Bug Fix) If one of a MacOS specific Advertising paths was set to a hard coded path on a different location than the MacOS Root Path, it could not be used. This has been corrected. If you need to set to a different share, or even the local machine, remember to preface the path with // or \\. JIRA INDESIGN-2324

5.33.01 Released 2018.08.22

Major Bug Fix) If, in the browser interface, text was trimmed at the end of the article asset (like the AP tagline information) and if that text managed to get more than one text style range in Adobe InDesign before the trimming happened as a result of translation then the text could end up not trimmed in Adobe InDesign or Adobe InCopy but the closing </span> tag would be removed and the opening one would be left in place, but likely converted. This has been fixed. The issue was that after removing the closing span tag, the internally found text would become invalid in both InDesign and InCopy and the rest of the trimming would error. This seems most likely after the URLs in those AP taglines became actual hyperlinks and thus added additional text style ranges. JIRA INDESIGN-2138

Vision Data Bug Fix) Because of a change with Live e-Editions and Page Tracker, the page Category values in Vision Data XML files being used in Adobe InDesign to feed the Ad Statuses dialog will now be sanitized to only contain lower case alphanumeric characters. For Vision Data sites using the Page Content Types to place Adobe InDesign snippets, the snippets will need to be renamed (or reexported) so that they are lower case and alphanumeric. For example the name 'MAIN NEWS|CLASSIFIED' will become 'mainnewsclassified'. JIRA INDESIGN-2316

Instructions for using the new built in version of Update PDF Presets and access to a new utility script to load Print Presets.

Prior Versions:

Release notes for the most recent prior versions of the BLOX Total CMS client for Adobe InDesign and Adobe InCopy are linked to below:

Version 5.32.31 Release Notes

Version 5.31.05-7 Release Notes