5.21.09-1 Released 2017.10.20

Adobe InCopy Bug Fix) Reflowing assets in Adobe InCopy were occasionally causing errors when the frames in Adobe InDesign were locked. Because Adobe InCopy isn't allowed to unlock a frame, it caused the reflow in Adobe InCopy to fail. While the need to lock content frames is rare or non-existent, we had a client bring the issue to our attention, so it was fixed. JIRA INDESIGN-1922

Major Adobe InCopy Bug Fix) Adobe InCopy had problems reflowing out of date assets. Specifically, if the asset had no text in the body copy field, the reflow would fail for a variety of reasons. Other reflows would also fail. This has been fixed and we currently know of no issues reflowing content within Adobe InCopy. JIRA INDESIGN-1924

Bug Fix) The 5.21.06 release broke the File References menu. It has been fixed and is fully functional again. Only a single beta site has the issue. JIRA INDESIGN-1934

5.21.08-1 Released 2017.10.18

Bug Fix) The prior version of our support for inline assets and inline twitter and related content broke the support for regular print trimming if the asset also had an inline asset or other inline items. This has been fixed and both can be used simultaneously. JIRA INDESIGN-1712

Bug Fix) There was a logging based bug in the original release of INDESIGN-1785 in the client version 5.19.32. That bug has been corrected and is included in the 5.19.40-4 version and subsequent releases. JIRA INDESIGN-1785

Minor Log Change) We now log the name of the web-service endpoint when logging the pausing and resuming of the idle events. This is to aid in troubleshooting. JIRA INDESIGN-1931

5.21.07-1 Released 2017.10.13

Performance Change) When saving an asset with LOTS of placements, parents, and children, the data returned from the CMS is quite large. It caused a drastic slowdown of performance in the BLOX Total CMS client for Adobe InDesign and InCopy when the returned data was processed. Unless needed, this extra data is being removed prior to processing and the performance when working with evergreen assets in Adobe InCopy and Adobe InDesign is greatly enhanced. JIRA INDESIGN-1925

Minor Internal Change) There were locations in the code that handles communication with the CMS where the requests weren't properly formatted. It is doubtful this caused any issues, but those requests have been corrected. JIRA INDESIGN-1927

5.21.06-1 Released 2017.10.09

Bug Fix) The 5.21.04 version modified how assets without default frames are examined. But that caused a new bug when the first frame of the asset is one without a parent story (such as an image asset). This has been fixed. JIRA INDESIGN-639

Bug Fix) Adobe InCopy assignments would not properly write-back inline assets. This has been fixed. JIRA INDESIGN-1894

Bug Fix) An earlier 5.21.x version added the ability to list software versions in warning dialogs. That function attempted to read the user’s BLOX Total CMS preferences to control the dialog fonts. However, in certain cases the dialog was needed before the user preferences had been established and it caused a different error which prevented login. No sites ever experienced this issue. It was caught by TownNews staff during routine testing. JIRA INDESIGN-1923

5.21.05-1 Released 2017.10.06

Change) Our support for PPP based XML in a custom Saxotect format now locates the bottom of the ads at the bottom of the page margin. This is a change from the original support request. JIRA INDESIGN-1869

Bug Fix) Our support for PPP based XML in a custom Saxotect format no longer attempts to replace all the .adinfo files when reprocessing the XML file. It now only touches those sections that have been selected for processing. This is similar to the way all other advertising formats are handled. JIRA INDESIGN-1869

5.21.04-1 Released 2017.10.04

Improvement) If an Adobe InDesign user deletes the default frame on an asset and then attempts to make an assignment, it used to fail later in the process. It now immediately tells the user that the default frame is Required and it releases the rest of the asset's frames as they will eventually be released automatically without a default frame. The default frame is the 'main story' for an Article asset, a 'caption' for an image or PDF asset, and the 'table' frame for a Table asset. These frames cannot be removed from the rest of the asset's frames and maintain communication with the asset. JIRA INDESIGN-639

Improvement) If and Adobe InDesign user removes the default frame from an assignment, the assignment will be removed and the asset released from the page when checking the asset in. This prevents the Adobe InCopy user from wasting time working with a damaged assignment. JIRA INDESIGN-639

Bug Fix) The InCopy dialog offering the option to reflow an out of date asset didn't. It just ignored it because both it and the ignore buttons pointed to the same functionality. JIRA INDESIGN-639

Change in Behavior) If an Adobe InCopy user attempts to open an out of date asset that has no default frame in its assignment from Adobe InCopy, the user will be warned twice and the only result will be a closure of the asset. The asset will need to be returned to Adobe InDesign where an assignment with a default frame will be required. JIRA INDESIGN-639

UI change) Our BLOX Total CMS alert dialogs now contains a set of versioning information above the OK button. JIRA INDESIGN-1912

5.21.03-1 Released 2017.09.29

Bug Fix) During testing of write-back of inline twitter searches, we discovered a bug in our support of all inline items when the asset is edited in Adobe InCopy before it is edited in Adobe InDesign. We believe this is now fixed. JIRA INDESIGN-1894

Bug Fix) The new option to allow a user to prevent Adobe InCopy from auto opening wasn’t sticking. It has been fixed and works correctly now. JIRA INDESIGN-1900

Bug Fix) The original 5.21.01 version of the client moves dialogs to the left of very wide monitor configurations. But at one site where 5.21.02 was being tested, it caused the dialog to be drawn off the left side of the screen where it wasn't visible. This been fixed. Now if tries to move it too far to the left, it won't move the dialog from its default location. JIRA INDESIGN-1904

Bug Fix) We modified the plug-in code to work with more versions of Adobe InDesign and in doing so broke support for Adobe InDesign CS 5.5. This has been fixed and CS 5.5 can be launched again. However, please upgrade your Adobe InDesign CS5 and CS 5.5 versions to Creative Cloud. Adobe no longer provides support for CS5 or CS 5.5 and BLOX Total CMS don't provide all functions in those legacy versions. JIRA INDESIGN-1911

5.21.02-1 Released 2017.09.27

Bug Fix) testing of the prior version revealed a bug in the process of creating assignments after placing assets. This has been fixed. JIRA INDESIGN-1908

5.21.01-1 Released 2017.09.25

User Interface Changes) In the first of many steps to pare down the number of items in the BLOX Total CMS menu we have allowed both a site and a user to remove the Adobe InCopy Assignment options. Continuing with the do no harm mantra, any existing sites that use Adobe InCopy should find all the options still in place. But a site that has never used Adobe InCopy will find the menu items removed. In addition, if the menu items have been removed, the Asset Manager will not have the Create Assignment placement option. JIRA INDESIGN-216

New Feature) There is a new user option to enable or disable the Adobe InCopy Assignment Menu options. New sites should find the option disabled while existing sites will find the setting matching the site enabling as discussed in the below option. A user can change the option by choosing BLOX Total CMS > Options > Enable Adobe InCopy Assignment Features. JIRA INDESIGN-216

New Feature) There is a development menu item to enable to disable the access to the Adobe InCopy Assignment features. The function is a toggle and it either deletes or adds the special resources file that enables the features. The new feature can be found at BLOX Total CMS > Development > Enable/Disable Adobe InCopy... Selecting it will provide a dialog with the option to enable or disable it. By default, the Adobe InCopy options in Adobe InDesign will be disabled unless Adobe InCopy has been used at a site. This means that Adobe InCopy assignments cannot be created. In the past, the menu items would exist but would generate errors. Now they will not appear. JIRA INDESIGN-216

Change) The path to the assignment files is now considered an optional path if Adobe InCopy has never been launched before. This allows some of the above features to work if the site isn't actually using Adobe Adobe InCopy yet. JIRA INDESIGN-216

Minor Bug Fix) Adobe InCopy users who were editing in single frames were generating silent errors when attempting to change the column width because that is not Adobe InCopy can do. It BLOX Total CMS client for Adobe InCopy no longer attempts to do that and the errors are no longer generated. JIRA INDESIGN-675

Bug Fix) When updating Adobe InCopy Assignments in Adobe InDesign, the BLOX Total CMS client for Adobe InDesign removes any assignments that are no longer connected to anything. However, there is one assignment that always exists and is protected. Unfortunately, on some versions of Adobe InDesign, this assignment is named slightly differently internally and the client wasn't determining that it was a protected assignment and thus the client was throwing errors and failing to update the other assignments. This is an esoteric error, but it has been corrected. JIRA INDESIGN-1100

Bug Fix) When using Adobe InCopy and Adobe InDesign there was a logic bug that prevented the easy updating of content changed in Adobe InCopy. If the Adobe InCopy user kept the asset open but used Save Content, the Adobe InDesign user was prompted to reflow the asset (though clicking Cancel would instead perform a necessary update). Now, the BLOX Total CMS client for Adobe InDesign can recognize that the asset has been saved in Adobe InCopy and only an update in Adobe InDesign (instead of a full reflow) is necessary. This is a nice fix for sites that use InCopy to compile agate or briefs in Adobe InCopy. JIRA INDESIGN-1898

New Feature) For many years Adobe InCopy users would automatically have the Asset Manager opened for them after closing a document. For staff editing copy, that combined with Adobe InCopy's Auto Search functionality makes for an efficient editing. However, for occasional editors, the auto opening is problematic because it prevents Adobe InCopy from quitting while the Asset Manager is open. Thus, there is now a user preference to control if the Asset Manager auto opens after closing an InCopy file. The preference is at BLOX Total CMS > Options > Auto Open Asset Manager. This option is only available for Adobe InCopy users. JIRA INDESIGN-1900

New Feature) There are two news text variables that can be used in Adobe InDesign folios for the months. In addition to the 'H' with the normal full spelling of the month's name, there is an H4 with a 3 or 4 character month's name and no punctuation and an H5 value which uses the Associated Press style guide for months. JIRA INDESIGN-1902

Bug Fix) The Adobe InCopy Assignment Exists icon wasn't showing in Adobe InCopy. This has been fixed. Adobe InCopy users can now safely determine if the asset has an Assignment. InDesign users icon continues to show correctly for the active publication. JIRA INDESIGN-1903

UI Change) If a user has a superwide monitor the dialogs will be moved from the center to a location that places the dialog on the left half of the screen. This doesn't apply to dialogs such as the Asset Manager or Clone and Move that remember their sizes and positions. JIRA INDESIGN-1904

Bug Fix) The recent changes to the support for inline links (Twitter and Related Content) was flawed. If only these inline items were used it was possible that they would be ignored and not properly trimmed. This has been corrected. JIRA INDESIGN-1905

Bug Fix) We had a site present an error log with difficult tracking the naming of pages with zones. We don't know how to trigger the error but have added some extra data checking and logging to trace the error. JIRA INDESIGN-1906

Behavior Change) We had a single site that managed to incorrectly apply some jibberish as a section prefix or section marker. That, in turn, causes a rash of internal errors that hurt performance. We have modified the code to prevent applying that jibberish to the placement information of assets. The result is no internal errors and drastic better performance when a user improperly applies section starts to pages. JIRA INDESIGN-1908

Prior Releases