Preference for when Trimming View is changed

Next Version:

The release notes for the next version (5.37.x) of the BLOX Total CMS client for Adobe InDesign and Adobe InCopy are here.

Where to find Fully Tested Version?

5.36.26-9 completely passed TownNews' Quality Assurance testing on 21 June 2019. This version can be found in the tcms_indesign_client share after updating to Appliance OS version 2.24.0-x

5.36.26-10 Released 2019.06.25

Bug Fix) A recent bug fix for adding all styles prevented the normal use of automatically adding missing styles during translation to break. Manually adding the missing style would allow the translation to complete during subsequent placement. This has been corrected. In addition, a different change prevented the Template Master's use of Add Missing Styles from organizing the styles properly. This too has been fixed. Finally, it was discovered that when adding object styles, some object styles would not get added because of an internal error with the parsing of object styles. This too has been corrected. JIRA INDESIGN-2577

5.36.26-9 Released 2019.06.21

Minor change) We modified the code that uploads snippet previews to Page Tracker so that it would alert the users when their site had not yet received the update to Page Tracker that enables this feature. JIRA INDESIGN-2449

5.36.26-7 Released 2019.06.19

Minor Bug Fix) The client code has a cleanup function where it will remove the legacy .version files once every 1000 launches. This works fine on legacy installs, but it failed to work with installs using the currently recommended practice of the tcms_indesign_client ActiveVersion symbolic link. This has been fixed. JIRA INDESIGN-2410

Template Master Bug Fix) A prior fix to the Add Missing Styles function caused an occasion error. This has been fixed and all styles used by the rulesets should not be added. JIRA INDESIGN-2466

Snippet Export Bug Fix) The Option to Set All File References to Match should have been UNchecked by default for Page Design Snippets. But it was instead defaulting to checked. This has been fixed. For Page Design Snippets, the option should be available, but default to UNchecked. For Design Element snippets it should default to checked. JIRA INDESIGN-2488

Bug Fix) A late change in the new feature to find and include Obituaries in the PCAB files caused an internal error to be generated. This has been fixed. JIRA INDESIGN-2540

Bug Fix) The PCAB export of obituaries listed the height in points instead of inches as requested. This has been fixed. JIRA INDESIGN-2540

Bug Fix) Sometime recently the Dead Jump function broke and exported the Dead Jumps to the wrong folder. This caused them to not be found and thus not placeable. This has been fixed. In addition, to aid the troubleshooting of a site's issues with dead jumps, we now log significantly more information. JIRA INDESIGN-2546

5.36.26-1 Released 2019.05.13

New Feature) Our PCAB export for Layout 8000 sites now supports tracking paid obits when they are properly configured. Configuration involves slugging using -obt- in the slug, placing the ad number at the end of the slug, and placing the name of the deceased in the first paragraph of the default frame as a result of translation. JIRA INDESIGN-2540

5.36.25 Released 2019.05.07

Logging Change) Through the past 8 or so years we occasionally got reports of snippets failing to place because the file itself was in use. The INDESIGN-910 ticket, released earlier, should prevent that from happening, but it not, the failure messages now list the name of the snippet. JIRA INDESIGN-369

Important Bug Fix) A recent release broke the translation of hyperlinks. Errors with the (3c) code would be thrown. This has been fixed. JIRA INDESIGN-2547

Newzware Behavior Change) Support for Newzware Ad Layout Format XML files now truncate the section letter to a single character. Thus if the BookName used NT, the section letter read will become N with the remaining character(s) ignored. JIRA INDESIGN-2548

5.36.24 Released 2019.04.30

Bug Fix) A recent change to the client for Adobe InCopy caused editing an asset in a single frame to throw multiple errors at the completion of editing. All known errors with this process have now been fixed. JIRA INDESIGN-2544

5.36.23 Released 2019.04.25

Bug Fix) A 5.35 version change allowed aliases or shortcuts of snippets to appear in the snippet menus. But it was flawed and only showed top-level aliases and snippets. They now work with subfolders as intended. This makes it easier to organize snippets because you can place aliases or shortcuts in other directories to make updating shared snippets easier. JIRA INDESIGN-698

IMPORTANT CHANGE) When Page Tracker reaches version 1.12, the Adobe InCopy client will instantly switch to showing the snippets for InCopy that have been exported from that point on. Any prior exports will be ignored. The template Master will need to re-export those snippets -- An easy task if they were exported from the Master Document as instructed. In addition, at this same point, the use of the print_notes to force a snippet name is being depreciated and it will now rely upon the point publication placement information. JIRA INDESIGN-2399

Improvement) When a snippet has been chosen for use in Adobe InCopy the dialog to open assets now displays the snippet. Of course, this is for Creative Cloud users only. JIRA INDESIGN-2399

Minor Bug Fix) Adobe InCopy users got several warning messages when they attempted to use BLOX Total CMS > Update and Reset > Update All. This has been corrected. JIRA INDESIGN-2399

Major New Feature) Snippets for use with Adobe InCopy are now uploaded to BLOX Total CMS when they are exported. This allows their selection in the Assignment Tool and in the Publication Placement information. Consequently, it allows their automatic placement in Adobe InDesign as the page is being designed. JIRA INDESIGN-2449

Bug Fix) We have had complaints for several weeks that on occasion the wrong document would close when clicking the close box in a tab of multiple open documents. I site provided a missing part of the report which allowed us to reproduce and fix this issue. Currently, when multiple documents are open, you can click the close icon on any tab and that document will indeed close. JIRA INDESIGN-2532

5.36.22 Released 2019.04.09

Bug Fix) The prior version of the client (5.36.21) was throwing errors when using Create Pages even though the pages were actually created. This has been fixed and the errors no longer exist. This only affected a few beta test sites before it was corrected. JIRA INDESIGN-2526

5.36.21 Released 2019.03.27

Behavior Change) In an effort to reduce crashes of Adobe InDesign, we pushed the changing of showing/hiding trimmed text to an idle task on multi-page documents in version 5.36.09. Some users have objected so we added a user preference to control this. The user preference will default to the legacy behavior unless the user crashes in which case the new behavior will be enabled. The user can override the behavior with an option in Settings and Support. Click the Translation tab and then uncheck the Delay Trimming Visibility Changes option to return to legacy behavior of auto-hiding. JIRA INDESIGN-2515

+15 
Delayed Gratification.png

Minor Bug Fix) When an applied Nested Style is written back from Adobe InDesign or Adobe InCopy it would throw internal errors if the font of the Character Style didn't exist on the local machine. While a user should NEVER work without the fonts their design calls for (as we can't control write-back), we don't want to throw errors because that slows down everybody with the overhead of sending the logs repeatably. So the missing font messages are now Warnings and written only to the local user log. Note, Write-Back will still be flawed because of the missing font. JIRA INDESIGN-2517

Logging Change) When the Override .adinfo file feature was added, it originally logged to three locations. At some point, the logging stopped showing up in Page Tracker and it was inconstant in the document's log with the propensity for logging on the first page of the edition. We have returned logging to all three locations and, in addition, we now log the ad number that was Added, Relocated, or Removed from pages. This information was only indirectly listed before. JIRA INDESIGN-2520

+15 
PageTrackerLogging of Override.png

5.36.20 Released 2019.03.22

UI Bug Fix) An earlier version changed some the maximum size that the Ad Statuses dialog was allowed to grow to. Unfortunately, it failed with some odd sizes that are options on some users workstations if the user had more than one monitor available. To counteract this, if a user has more than one display attached, we are now forcing the maximum size of the Asset Manager to slightly smaller than the smallest dimensions of all screens. JIRA INDESIGN-1140

Bug Fix) The new keyboard shortcuts for snippets function had two bugs. The first was a typo in the name showing in the dialog. The second prevented failing matches from deselecting snippets in the Quick Apply style dialog. Both have been fixed. JIRA INDESIGN-2185

Vision Data Ad Layout Improvement) Our support for driving Ad Layouts via Vision Data produced XML now incorporates the use of the Value property of the <Description> field of each ad. This will produce a text-based label in the placeholder frame looking similar to this: 165431; CRUMBY CHAIR; 22331; Color; 3 x 10. Actual options depend upon the VisionData export as some sites feed us more or less data. JIRA INDESIGN-2516

5.36.19 Released 2019.03.21

Major New Feature) There is a new feature at BLOX Total CMS > Documents > Combine Multiple... that allows a user to combine multiple pages into a single document. When chosen, a dialog will appear. Simply check the pages to combine and click the OK button. JIRA INDESIGN-197

+15 
Combine Multiple

5.36.18 Released 2019.03.19

Minor Logging Fix) Sites using fileServerDetails.jsx files to relocate the paths to files weren't getting the Crash_Logs, Error_Logs, nor User_Logs placed in the correct location. Instead, they were frequently filed by domain leaving the raw locations (created before the fSD file is used) empty. To help identify the issue, we now log the three folders. JIRA INDESIGN-2514

5.36.17 Released 2019.03.18

Bug Fix) An Adobe InDesign user who threads frames on the same page and then eventually jumps the story to a different page was finding that the Turnline appeared at the end of the first frame as opposed to the last frame on the Turnline's page. This has been corrected. JIRA INDESIGN-2327

Minor Logging Fix) The function for adding placement information to assets that have an Adobe InCopy assignment was incorrectly logging a path as a warning. This has been corrected and the path is now an information log item. No harm from being a warning, but it was confusing when doing troubleshooting. JIRA INDESIGN-2460

Minor Logging Change) The internal code for locating the active document in Adobe InDesign was throwing an internal error when Adobe InDesign had open documents and layout windows, but no active document. This has been corrected. JIRA INDESIGN-2509

Minor Logging Change) When an asset has no default frame (usually because a user deleted an image's caption frame) we were logging the issue as an error. That was generating large numbers of error logs at some sites and slowing down all users due to increased network traffic. The lack of a default frame is now logged as a warning where it is only logged to the local computer until the user's log is copied to the tcms_purged share. This should improve performance slightly. JIRA INDESIGN-2510

5.36.16

This was an internal release for testing purposes.

5.36.15 Released 2019.03.13

Bug Fix) When creating a new document with BLOX Total CMS > Documents > New..., a user could not unselect a Page Content Type once one was selected. This has been fixed and there is now an empty menu item at the end of the Page Content Type menu. Keep in mind that Page Content Types can be used to automatically apply Page Design Snippets. JIRA INDESIGN-2150

Minor Bug Fix) When creating a new document with BLOX Total CMS > Documents > New..., a user could select the blank menu item for a snippet. But then they would get multiple warning/error dialogs that the snippet couldn't be placed. This has been fixed. JIRA INDESIGN-2150

Minor logging change) Fixed a minor logging bug that is encountered when trying to update an Assignment's revision file when the lock on the file wasn't cleared by another user. Nobody will notice any differences in operation. JIRA INDESIGN-2351

Minor Bug Fix) Adobe InCopy users could not control if the Development Mode menu appears in Adobe InCopy. Previously the ability to show/hide that option was limited to Adobe InDesign users. Now, both applications have access to show/hide the menu option used by a site's Template Master. JIRA INDESIGN-2404

Minor Bug Fix) Since client version 5.12.80 we have been tagging page labels (those informational frames at the top of the page that indicate page content type, page name, and/or page color) with domain tags. This wasn't necessary and added unnecessary details to the user's log file. JIRA INDESIGN-2438

Improvement) Version 5.34.x of the client added a warning when opening single documents whose publish date is before today. But that warning didn't occur to those using the BLOX Total CMS > Documents > Open... dialog. The warning now works when opening documents from that dialog too. JIRA INDESIGN-2474

+15 
Opening multiple past due documents

5.36.14 Released 2019.03.11

Bug Fix for Exporting Jump Items) When Exporting Jump Items returns were not correctly being turned into the markers. This prevented the items exported with returns from being able to be read and used for jump items. This has been fixed. Both Returns and Line Breaks are supported for all three jump items. JIRA INDESIGN-2287

Bug Fix) We had a report of a MacOS site having issues with the capitalization of Volumes in paths and locating jumps, nearby documents, and combine with. We believe this has all be resolved. JIRA INDESIGN-2478

5.36.13 released 2019.03.08

fileServerDetails.jsx Behavior Change) When a MacOS user is using a fileServerDetails.jsx file to locate the paths, we no longer look for specific MacOS paths when logging in as the fileServerDetails.jsx files are set to provide OS specific paths. In the past, users would get warned if the MacOS specific version of the various Advertisting Paths weren't located when they weren't even going to be used. This has all been corrected and a working fileServerDetails.jsx always overrides the browser based Path Configurations. JIRA INDESIGN-2365

Improvement) The Close All documents feature will no longer prompt when closing documents with more than 3 pages. It will automatically close them without any prompts. JIRA INDESIGN-2390

Improvement) We have noticed a few sites that have experienced crashes of Adobe InDesign after it has been running for an extended time and the memory usage of Adobe InDesign has ballooned. With this change, we have begun to allow Adobe InDesign to warn the users of this very rare situation. If it happens, they would likely see an Adobe InDesign warning similar to the one below. If the user clicks No, Adobe InDesign will likely keep warning the user every few minutes. If the user clicks Yes, we are allowing the assets to be checked in and the documents safely closed to prevent a crash. JIRA INDESIGN-2495

+15 
Adobe's Low on Memory warning

Adobe's Low on Memory warning

MacOS Bug Fix for Image Statuses) The MacOS version of Image Statuses was configured to use OSX versions of the exportFolderPathOSX and tonedImageFolderOSX folders. Unfortunately, both were ignored and the default exportFolderPath and tonedImageFolder versions were used instead. This has been corrected so that MacOS sites can use either version of the tags with the OSX version taking precedence and the Window uses only using the default versions. JIRA INDESIGN-2504

5.36.12 released 2019.03.01

Bug Fix) Recent versions of the client software (sometime earlier in 5.36.x series) starting causing reflows of assets and other situations to attempt to log in to a non-existent domain. That then reset the user's path configuration and they were warned that they were not configured to store documents. We believe this is now fixed. JIRA INDESIGN-2503

5.36.11 released 2019.02.28

Bug Fix) If a user tried to merge an asset into a locked frame (via Object > Lock) it would throw an error. It now unlocks the frame first. JIRA INDESIGN-1757

Bug Fix) Noticed on MacOS that the display of the OS version was cut off in the login screen if the web-service returned extra white space. This has been fixed. JIRA INDESIGN-2143

Improvement) In the 5.36.05 version of the client, we changed the code that determines if the text is Bold or Italic, especially for nested styles. We've changed it again to log more information when that process generates errors because of problematic fonts. JIRA INDESIGN-2467

5.36.10-2 Released 2019.02.27

Bug Fix) While looking at some logs from sites that have access to multiple domains, we noticed that occasionally opening a document from a different domain would cause the BLOX Total CMS client for Adobe InDesign to not be able to locate the correct folder for the documents when checking for Document Jump pages. We have modified some of the low-level functions that help direct the location correctly. JIRA INDESIGN-2496

Bug Fix) We noticed a couple times when looking at logs from users where the BLOX Total CMS client wasn't able to locate the Error_Logs folder because it got the wrong base folder for the tcms_purged share. This seems to happen most often at sites that don't use our appliances and thus don't have our normal shares configured. We believe the issue is now fixed. JIRA INDESIGN-2498

5.26.09 Released 2019.02.25

Bug Fix) Redirected sites still had problems which slowed down application launch by a minute or so. This has been corrected. JIRA INDESIGN-2143

Snippet Export Improvement) A recent release modified the Design Element Snippet Export to set all of the File References of the frames being exported to be the same. One site complained that they wanted the option to choose to do that or not and so we have added an option in the Export Snippet Dialog allowing the file references to remain as set or match. JIRA INDESIGN-2488

+15 
set all file references to match

Bug Fix) A long-standing internal bug related to our frequent sweep page items was found and fixed. We haven't determined the special case that triggered the appearance of the bug at one client site, but its fix makes things run faster there. JIRA INDESIGN-2489

Bug Fix) The client code was throwing an internal error when listing the event listeners. This has been corrected with some simple housekeeping code in the client. The only thing that users might notice is a very slight change in speed for the better. JIRA INDESIGN-2490

Behavior Change) While looking at some crash logs for 3 sites we found two cases where an Adobe InDesign crashed shortly after translation. The long file indicated that it had changed the visibility of the Print Trim condition. We modified the client code to now do that function on idle after translation and document activation is complete. We hope this will help prevent crashes related to Adobe InDesign's issue with changing text condition visibility. JIRA INDESIGN-2491

5.26.08 Released 2019.02.20

Important New Features) The Show All Asset Notes option in the Translation Tab of the Settings and Support dialog now causes even the child asset Print Notes to be displayed. In addition, if a child asset uses the alert flag, it will show now. In the past child notes were ignored. Finally, the print notes in the Select Child Assets to Place dialog now have some additional cleanup done so that more text can appear. JIRA INDESIGN-960

+15 
Show All Asset Notes

Bug Fix) The new feature to show the Appliance OS versions in the Log In dialog (added in version 5.36.06) caused problems with sites that use a redirected URL via the servers.jsx rediret:true parameter. This has been corrected and those sites will now show 'redirected' in the lower left of the Log In dialog. JIRA INDESIGN-2143

Bug Fix) Some recent change caused the Create Assignment dialog and the Check In dialog in Adobe InDesign to fail to have the respective dialogs to have the Edit Details checkbox unchecked when it first opens. This has been corrected and if the assets have been download from the CMS before the dialog opens, the Edit Details checkbox will be automatically chosen. JIRA INDESIGN-2483

+15 
InCopy Check In and Create Assignment Dialog

5.36.07 Released 2019.02.18

New Feature) Internally, TownNews has used a function to examine Adobe InDesign and Adobe InCopy logs for speed issues. We've now built this feature into both applications. A user can click the Slow Line Finder button in the Support tab of the Settings and Support dialog. Activities that took longer than 3 seconds are considered slow and they will be listed in a new log file. We will be continuing to fine tune this function. There are still cases where it is counting user interaction time which makes things look horrible. JIRA INDESIGN-1838

Important Bug Fix) Exporting a snippet that had Adobe InDesign markers (like the Current Page Number) had those markers removed. Those markers are treated as XML processing instructions and the cleaning up of the Snippet XML was removing those. This has been fixed. JIRA INDESIGN-2443

InCopy Improvement) We've extended the modernization of the event listeners to Adobe InCopy. Users won't notice any changes to this under the hood change, but it should help increase stability. JIRA INDESIGN-2481

5.36.06 Released 2019.02.13

Adobe InCopy Improvement) Adobe InCopy does not have access to unlock frames. But locked frames triggers internal errors during reflow in Adobe InCopy. So to prevent this, we now automatically unlock all frames in Adobe InDesign that are part of an Adobe InCopy Assignment. All other frames, including those for ads, will remain locked if the system or a user locked them. JIRA INDESIGN-1936

Minor Bug Fix) While testing the BLOX Total CMS client for Adobe InDesign, we noticed it can throw internal errors without warning the user when they try to place an asset and/or create an assignment when the document is either not named correctly or not stored correctly. The user will now see a warning and translation will be halted. JIRA INDESIGN-2103

New Feature) The log in dialog has been modified slightly. The default buttons are now flush right to conform with UI standards. And the bottom left of the dialog will show the OS version when logging into appliances. The client code will also store the appliance OS, when known, in other dialogs and in the user's local log file. JIRA INDESIGN-2143

+15 
osVersion.png
+15 
withOSVersion.png
+15 
hosted.png

Improvement for Template Masters) The former Development Mode function Show Output Preferences Folder Path has been changed to Show OS Specific Paths. It now shows Operating System specific paths for the browser-based Path Configuration, Image Toning Preferences, as well and the Output Preferences of the legacy system. The displayed preferences can be copied and pasted as needed. JIRA INDESIGN-2325

+15 
Various Forms of MacOS Paths

Minor Change for MacOS) If a MacOS, failed to mount or to provide access to the path for any of the MacOS specific paths to Advertising or Ads, the BLOX Total CMS client for Adobe InDesign would revert to the default paths in the tcms_purged share. But if the advertising files or ads weren't actually located there, the user couldn't place ads or perhaps couldn't build a proper edition. Now, when the users log in, of the users will now be warned if the specified paths are unavailable. They will be allowed to continue to log in or they can choose to fix the problem and then log in. JIRA INDESIGN-2365

+15 
Failed to Mount MacOS Path

Important Bug Fix) Exporting a snippet that had any leading or trailing spaces near a text style range would have those spaces removed. This has been fixed. JIRA INDESIGN-2443

Bug Fix Creative Suite Versions of Adobe InCopy) The 5.36.01 version of the BLOX Total CMS client for Adobe InCopy introduced a bug for opening an article in a single frame. This bug has been fixed. JIRA INDESIGN-2479

Minor Logging Changes) We now log the beginning, ending, and total time of responding to an activation event. This is for troubleshooting purposes. Users will not notice any differences. We also do similar for idle events when there are idle tasks to process. Again, the user's won't notice anything. Finally, we stopped logging a message when multi-page documents were opened and no changes were found because those messages were appearing too frequently. JIRA INDESIGN-2482

5.36.05-2 Released 2019.02.01

Bug Fix) The Development Menu function for Template Masters to Enable or Disable Adobe InCopy failed to recreate the local user's menu and also failed to set the local user's preference to match the enabled / disabled status of Adobe InCopy support. JIRA INDESIGN-2368

Minor logging Bug Fix) When updating the color of Adobe InCopy assignments, there was a long-standing bug that prevented the UUID or File Reference of the asset from being logged. This has been corrected. JIRA INDESIGN-2429

Bug Fix) On occasion, an Assignment File for use with Adobe InCopy would report that it wasn't being properly updated when in fact the client software had a bug which sometimes made it impossible to determine if the file had been properly updated. The bug has been fixed and additional logging has been added. JIRA INDESIGN-2429

Improvement) If a user loses network during work on _BU document or on an un-split document, attempting to Create Pages or Split Document displayed a pair of warning dialogs for each and every page in the document. This has been changed. The user will get warned with just one pair of messages. In addition, the warning dialogs will display the missing (dropped) path in a more user-friendly manner. JIRA INDESIGN-2436

Bug Fix) Exporting a snippet was removing spaces between Adobe InDesign Text Variables within the snippet. This has been corrected. JIRA INDESIGN-2443

Stability) We've made additional changes to the event listeners used by the BLOX Total CMS client for Adobe InDesign. The goal is to cut down on crashing, particularly on MacOS and particularly with multi-page documents. JIRA INDESIGN-2464

Check-In Bug Fix) An earlier change to the handling of preferences caused both Adobe InDesign and Adobe InCopy to occasionally forget the user's setting for both Handle Children Simultaneously and Assign the same Workflow to Children. This has been corrected. JIRA INDESIGN-2469

Important Bug Fix) A recent release changed the snippet export feature to automatically tag all Design Element Snippet frames with the same file reference. This makes exporting snippets with Images really easy. But unfortunately, this same feature was unintentionally enabled for Page Design Snippets which made them unusable. This has been corrected. JIRA INDESIGN-2470

5.36.05-1 Beta Released 2019.02.01

UI Improvement) Users complained that they couldn't find the Set Pre-placed Asset Policy button in the Translation Options of the Settings and Support dialog. While it is still there, we have added an option to call it from the bottom of the Update and Reset Menu. JIRA INDESIGN-2446

Important Bug Fix) When Related Content was brought inline to an asset's body copy the tagging from both Adobe InCopy and Adobe InDesign wasn't parsed correctly during write-back and the related content was effectively removed as an inline item. This has been corrected. JIRA INDESIGN-2465

Template Master Bug Fix) A Template Master function we use to add style groups for the Add Missing Styles function had an error that prevented it from working in certain situations. This has been corrected. JIRA INDESIGN-2466

Nested Style Write-Back Behavior Change) When certain non-traditional fonts were used with Nested Styles, neither Adobe InCopy nor Adobe InCopy could determine the font family in use. Our function for ignoring during the write-back the nested style formatting then failed. This would usually result in the entire paragraph being formatted online (and in print after a reflow) with the character attributes of the Nested Style. Now, if the font family can't be determined, but the font styles still match, we will ignore the Nested Style. JIRA INDESIGN-2467

Export Bug Fixed) When styles are applied to paragraphs that add write-back tags via the Export ruleset, adding trimming or other formatting at the end of the paragraph could cause the tags to be doubled up. This had the effect, on occasion, of bolding entire paragraphs instead of certain parts. Or it might have caused a single paragraph format to extend to the next paragraph by adding an additional write-back tag. We believe this is fixed. JIRA INDESIGN-2468

5.36.04 Released 2019.01.24

Major New Feature) Continuing with the ability to edit an asset in a snippet in Adobe InCopy, if that has happened, the snippet will now be placed in Adobe InDesign as the asset is placed. In this current version, the selected frames are replaced with the snippet frames, unless it is the snippet itself that is selected (from a prior placement). A future feature will the user to choose to replace the snippet or not, use a different snippet and to scale the snippet to the page area. This is the first step to all those new features. JIRA INDESIGN-2440

Major New Feature) When Snippets are exported using Adobe InDesign Creative Cloud version's BLOX Total CMS > Export Snippet..., we now generate previews of the snippets. These previews will be available in the Asset Manager, Snippet Shortcuts, and in the browser's Assignment Tool (when that update is released). JIRA INDESIGN-2448

5.36.03 Released 2019.01.16

Performance Enhancement) When closing documents, the process checked the statuses of the document's placed assets more than once. It now checks just a single time to increase the speed at which documents, specifically multi-page documents, close. While users might not notice the change it is, however, a measurable change. JIRA INDESIGN-1103.

Bug Fix Affecting Performance) We found several places in the client code where some quick checks of data integrity were failing because they were worded incorrectly. Thus a more complete data check was necessary and this slowed down the individual processes. User's will not notice the difference, but it could be seen in the user's logs. JIRA INDESIGN-1103

Bug Fix) We had reports that the menu option at BLOX Total CMS > Page Content Types > Clear Page Content Type Snippet Tracking wasn't working. We have made some logging and logic changes and are happy to report that if you have a Page Content Type change on a page, you can use this feature to get the correct snippet to apply. Without using this function snippets won't automatically place with Page Content Type changes because the client software doesn't want to place more than one Page Design Snippet on a page. JIRA INDESIGN-1759

Minor Bug Fix) We have a feature that removes legacy .version files from Appliance based installs of the BLOX Total CMS client for Adobe InDesign and Adobe InCopy. Unfortunately, that feature didn't work once sites switched to the Appliance based installs using the version of the client on the tcms_indesign_client share. It now works in those installations too. JIRA INDESIGN-2410

Depreciating New from Template) The Adobe InDesign menu option at BLOX Total CMS > Documents > New from Template > template choice was replaced over a year ago, but New from Template still remains in the Documents Menu. Starting with this release, any user selecting it will be shown a dialog asking the user to switch to the upgraded replacement version. The dialog looks similar to the following: JIRA INDESIGN-2425

+15 
Upgrade to New...

5.36.02 Released 2019.01.10

Logging Change) Lines 5-7 of the users local Translate.log file will now list the folder on the workstation where the client code exists. This helps with troubleshooting. JIRA INDESIGN-1639

New Feature) Regional Design Centers have a tendency to not save their pages often and thus Page Tracker doesn't update the Page PDFs often. This makes it hard for the remote newsrooms to gauge how their pages are coming along. We now support the use of a autoUpdatePageTracker.enabled file that will attempt to update Page Tracker once every 15 minutes. Like other .disabled or .enabled files, the autoUpdatePageTracker.enabled file is a text file that goes placed loose in the same folder as the client code folder (usually the tcms_data share). If however, you add a number to the first line of this file, then the BLOX Total CMS client for Adobe InDesign will use this number as the number of minutes to wait between updates. JIRA INDESIGN-2382

Bug Fix) While rare, we discovered that a user who logs out of the BLOX Total CMS client for Adobe InDesign or Adobe InCopy and then logs in again, will have extra event listeners. This means that a single user action could cause multiple responses and could lead to crashes. The client now deletes all event listeners during log out. JIRA INDESIGN-2426

Internal Change) In most cases when no Adobe InCopy or InDesign documents are open, the BLOX Total CMS client will now remove any document based event listeners as well as clear the lookup tables to allow new ones to be added. The hope is that this will prevent multiple document based event listeners from responding to the same events and that this will speed up and increase the stability during document saves. JIRA INDESIGN-2426

Performance Boost) The BLOX Total CMS client for Adobe InDesign has traditionally automatically saved the front or active document whenever the application is activated (when a user leaves Adobe InDesign and returns). Unfortunately, this slows the bouncing back and forth between Adobe InDesign and other applications (particularly on underpowered workstations). To help with this, we have increased both the base time limit that a user must be away from Adobe InDesign as well as the increase the effect that each placed asset has on the total time. Finally, for documents with multiple pages we now only process approximately 5% of these activations instead of all of them. This will further increase the speed of reactivation for document with multiple pages. JIRA INDESIGN-2432

Minor logging change) We will now log the average number of idle events per minute when doing the internal Garbage Collection routines. This is a performance metric that can help us diagnose problems. Some computers go idle quickly and some MacOS workstations rarely go idle which prevents the client from doing background tasks. JIRA INDESIGN-2432

5.36.01 Released 2019.01.03

Template Master Snippet Export Feature Returned) When Adobe released the Creative Cloud versions, they broke part of the user interface functionality they provided. What broke is the ability to display a directory tree. We kept waiting on Adobe to fix it, but they didn't so we recreated our own, somewhat limited, version of a directory tree. Development Mode users can now see, select, and create sub-folders to export their snippets into. An example is below. JIRA INDESIGN-2415

+15 
Export Snippet Directory Tree for Creative Cloud Users

Adobe InDesign Creative Cloud users now have this as a directory tree when exporting snippets in Development Mode. Folders can be added and traversed in this dialog.

Minor Logging Fix) There was a bug in the log information triggered from a failure to process a mailto: hyperlink. The log information has been corrected. This didn't affect anyone other than TownNews' troubleshooters. JIRA INDESIGN-2422

Prior Versions

Client 5.35 Release Notes

Client 5.34 Release Notes

Client 5.33 Release Notes

Client 5.32 Release Notes

Client 5.31 Release Notes

5.36.21 Released 2019.03.27

Behavior Change) In an effort to reduce crashes of Adobe InDesign, we pushed the changing of showing/hiding trimmed text to an idle task on multi-page documents in version 5.36.09. Some users have objected so we added a user preference to control this. The user preference will default to the legacy behavior unless the user crashes in which case the new behavior will be enabled. The user can override the behavior with an option in Settings and Support. Click the Translation tab and then uncheck the Delay Trimming Visibility Changes option to return to legacy behavior of auto-hiding. JIRA INDESIGN-2515

 !Delayed Gratification.png|thumbnail!

Minor Bug Fix) When an applied Nested Style is written back from Adobe InDesign or Adobe InCopy it would throw internal errors if the font of the Character Style didn't exist on the local machine. While a user should NEVER work without the fonts their design calls for (as we can't control write-back), we don't want to throw errors because that slows down everybody with the overhead of sending the logs repeatably. So the missing font messages are now Warnings and written only to the local user log. Note, Write-Back will still be flawed because of the missing font. JIRA INDESIGN-2517

Logging Change) When the Override .adinfo file feature was added, it originally logged to three locations. At some point, the logging stopped showing up in Page Tracker and it was inconstant in the document's log with the propensity for logging on the first page of the edition. We have returned logging to all three locations and, in addition, we now log the ad number that was Added, Relocated, or Removed from pages. This information was only indirectly listed before. JIRA INDESIGN-2520

[Do Not Release]

Minor bug Fix) Some recent changes in the handling of idle events in Adobe InDesign and Adobe InCopy were, on rare occasions, throwing internal errors. We believe this has been fixed. JIRA INDESIGN-2521

Tags