5.22.05-2 Released 2017.12.04

Verified Proper Behavior) We had a report that using the Skip Check-in option in the Create InCopy Assignment function would trigger errors. This is no longer the case and the function is working properly by both creating the InCopy Assignment and leaving the related assets checked out. JIRA INDESIGN-1023

Bug Fix) There were several related issues reflowing assets in Adobe InCopy after editing the asset of an InCopy Assignment in the browser interface. Those issues have now been fixed. JIRA INDESIGN-1761

Bug Fix) The BLOX Total CMS client for Adobe InDesign was sending coordinate data or segments to Page Tracker even when that option had been disabled in the browser interface. We have changed the client so that if the preference is disabled, no segments will be sent. This enhances the performance of the client as it does take a part of a second to gather the segments on a page. NOTE: If you notice that Page Tracker no long has segment information, shown in the Wireframe view, then enable the e-Editon coordinates: preference by setting it to true. JIRA INDESIGN-1814

Verified Proper Behavior) We were told that there can be problems reflowing Adobe InCopy assignments when there is no content (main story element) for the asset. We have verified that this is working properly now. There were some related changes in the client code several months ago that likely fixed the issues. JIRA INDESIGN-1831.

Major Bug Fix) There were bugs with the write-back of ordered and unordered lists if they also contained combinations of notes, hyperlinks, and some styles such as bold < strong > or italic < em >. This has been corrected. If you encounter a list that doesn't export from Adobe InDesign or Adobe InCopy, please create a support ticket at https://crm.tn-cloud.net/contactlogin/ and include the asset with the ordered lists in the correct position (from a prior revision of the asset) and we will fixe the export. Currently, all the options that we could think of a site using have been taken care of. JIRA INDESIGN-1899

Change for PPI > Saxo > XML) Create Edition from Edition file will now warn users of the ppisaxoxml custom ad format when the database dump doesn't contain any relevant pages. The prior procedure resulted in it attempting to build an incorrect InDesign document. JIRA INDESIGN-1932

Verified Proper Behavior) We had a report where if a main story frame was set to No Export from this Frame that a series of warnings and errors would be generated. We have verified that that behavior no longer happens. Likely some recent changes to the behavior of empty content fields fixed the issue. JIRA INDESIGN-1933

Internal Change) We had a report where a site built a large document and had hundreds of assets placed and the BLOX Total CMS client was unable to get the Asset Statuses of all the placed assets. We made an internal change to correct this. JIRA INDESIGN-1959

Minor Bug Fix) Saving the content or checking in an asset in Adobe InCopy or Adobe InDesign could through an internal error if the asset had no workflow assigned. This has been fixed. It is not known if this issue affected any sites. It was found during routine testing by the BLOX Total CMS team. JIRA INDESIGN-1965

Verified Proper Behavior) We had a report that paragraphs exporting with tags from the Export ruleset were not exporting properly if they followed a heading tag such as the < h3 > tags. We have verified that they do export correctly in every case we tested. JIRA INDESIGN-1968

Important Bug Fix) The was a significant bug in the trimming of assets during translation during placement and reflow. If there were multiple cases of trimming, including inline assets or links, and one or more of the pieces of trimmed text crossed Adobe InDesign Text Style Ranges, where the format is different in any attribute, including hyperlinks, the trimming could be expanded to trim more text or shortened to not include all the relevant < span > tags. An issue with trimming had been reported to us, but it took a user noticing that it only happened with multiple Text Style Ranges to provide us with the necessary steps to replicate the problem. Once we replicated the problem we were able to engineer a fix for this issue. This is, however, an edge case for trimming. There are very few valid reasons to trim across multiple text style ranges. JIRA INDESIGN-1975

Bug Fix) One site reported a problematic document that was generating internal errors because the links were checked for Document Jump pages were invalid. Invalid links are no ignored and these errors are no longer generated. JIRA INDESIGN-1976

Minor Log Change) When the Override .adinfo file function is used, we now log the contents of the .adinfo file to the log file so that it can be used in troubleshooting other issues. JIRA INDESIGN-1978

Important Bug Fix) We had one site that had multiple occurrences of PDFs failing to make it to output or Page Tracker. Their Adobe InDesign was generating zero K files which, unfortunately, the BLOX Total CMS client incorrectly thought were acceptable. The BLOX Total CMS client for Adobe InDesign now warns the user when small files are generated. JIRA INDESIGN-1980

5.22.04-1 Released 2017.11.10

Major Bug Fix) If a site was logging into a BLOX Total CMS appliance via the BLOX Total CMS client for Adobe InDesign or Adobe InCopy using a DNS name or a fully qualified name (fqn) versus the virtual IP address, the client was frequently logging in using http:// communication instead of the more desirable https:// communication. This will really be important as sites move to Appliance 2.18.0 when http:// is disabled for all uses. JIRA INDESIGN-1962

Minor Log Change) The logging of the servers.jsx information and the login result now clearly state the values of https, redirect, and tunnel. JIRA INDESIGN-1962

5.22.03-1 Released 2017.11.09

Bug Fix) The handling the advanced formatting that is part of the Storytelling tools in CMS 1.35 didn't properly support write-back from Adobe InDesign or InCopy if the inline items followed an <h#> style inline head format. This has been corrected and they now work correctly. JIRA INDESIGN-1700

5.22.02-3 Released 2017.11.07

Important Bug Fix) for sites that changed domains after the creation of their Master Document and thus, their template, the original domain was likely still tagged on the documents. Then when that template was used with the new domain, the BLOX Total CMS client for Adobe InDesign would want to convert the domain of the new documents. This caused the release of the document's assets and that in turn played havoc with live e-Edition. We now tag the main document prior to the use of Create Pages or Split Document to ensure that all the pages for an edition are configured with the active domain. JIRA INDESIGN-1956

Minor bug fix) We discovered that if the Split Document function failed to complete, that the Adobe InDesign panels that are closed to speed up the function aren't reopened. This has been fixed, and the panels should automatically reopen. JIRA INDESIGN-1956

Bug Fix) A very old, but previously unknown, bug of merging assets with inline notes has been fixed. Prior to this fix, only the assets up to and through the first one with an inline note would be able to merged in one pass. Then the Asset Manager would be needed to do the next set of assets to merge. No errors were logged and the only indicator of a problem was a less than helpful message to select something first – when the user already had selected something prior to opening the Asset Manager. The actual bug is that the selection was de-selected as part of the translation of the notes via the <&notes:()> Translate Script command. This deselection has been corrected. Note: Merged assets themselves do NOT support notes. They will always be removed from the final merged frame. This has always be the case and will likely remain this way unless Adobe changes the features of the Adobe InDesign Tagged Text file format that is used internally for merged assets. JIRA INDESIGN-1957

5.22.01-1 Released 2017.10.30

Bug Fix) When using Combine With, some users were generating an internal error as the BLOX Total CMS client for Adobe InDesign attempted to look for prior .adinfo files that might have come from earlier editions or zoned versions of the page. It is not known if any sites experienced a valid problem with this internal error, but it has been fixed. JIRA INDESIGN-1942

Bug Fix) Using Adobe InDesign CC 2018 and the BLOX Total CMS client for Adobe InDesign 5.21.09 and older running on MacOS, we experienced several occasions where Adobe InDesign would get into an infinite loop when using BLOX Total CMS > Documents > Advertising > Create Pages after using BLOX Total CMS > Documents > Advertising > Create Edition from Edition file... in Enhanced Mode. This appears to have been corrected. You might, however, find that the _BU document is left open on the rare workstations where it was happening. Not all MacOS workstations were affected. We could not replicate the issue on Windows workstations. JIRA INDESIGN-1943

Performance Fix) An internal function was being called repeatedly to verify the section letter of the active page. This no longer happens. The result of the fix is a couple millisecond improvement in performance. JIRA INDESIGN-1945

Major Performance Change) Due to a change in the response from the communication web-services several appliance versions ago, we now get more information about the parent assets and child assets than we need. It can slow down the client when placing and updating content in Adobe InDesign and Adobe InCopy. We added code to remove the parent information in a prior release but we found a quicker way to clean it. We also added extra logging so we can troubleshoot the issue at sites that have reused a child asset (as is intended) several hundred times. JIRA INDESIGN-1946

Behavior Change affecting sites who have changed Domains) Sites that have used an alternate domain or used templates that originated in alternate domains could have experienced situations where the internal function that tracks the frames for Translation, InCopy links, InCopy Assignments, Write-back, out of Segmentation, etc. could incorrectly mark a frame from the prior domain. This could cause it to not write-back, to mark itself out of date, to lock itself on the page, or to force the page to want to convert to the prior domain. None are good choices. The algorithm to set the domain now has a preference for the active domain over a legacy domain. Sites that haven't been exposed to more than one domain will not notice any changes. But sites that have used multiple domains should see fewer domain-based issues using this new method. JIRA INDESIGN-1947

Minor Bug Fix) We fixed a minor bug where some of the document information wasn't passed along and the naming convention couldn't be subsequently determined. We don't know the actual impact of this other than performance should be ever so slightly better because some internal calls will no longer be wasted. JIRA INDESIGN-1951

Prior Version

The prior version of the client is 5.21.x and its release notes are here