5.46.07 Released 2021.01.20

Bug Fix to Updating Placement) While doing some routine testing we noticed that the placement of assets wasn't happening when initially placed as intended. Instead, it was being caught later. We don't know that there would be any issues with this other than an asset wouldn't show as being placed in the Asset Manager until later - for example after saving the document. This would present itself as a lack of icons in the Asset Manager in both the browser-based interface as well as in Adobe InCopy and Adobe InDesign. This has been fixed. JIRA INDESIGN-3136

Bug Fixes for Select Child Assets to Place) There was a long-standing bug in the Select Child Assets to Place dialog that threw an internal error when the user has Toned Image Search selected in the Asset Manager. This prevented the accurate display of the number of toned images found. This has been fixed. There was also a bug that could be triggered by double-clicking on a child asset in that dialog. This too has been fixed. JIRA INDESIGN-3138

Important Bug Fix) Client 5.46.01 introduced a feature to modify how hyperlinks in assets were added to Adobe InDesign to prevent an issue with writing-back those hyperlinks. Unfortunately, that method triggered a bad bug within Adobe InDesign that would cause it to abruptly close (looks/acts like it crashed) as the translated asset was imported into the selected frame. To work around this Adobe InDesign bug, we have reverted the 5.46.01 change for merged assets. Non-merged assets will behave with the 5.46.01 behavior. JIRA INDESIGN-3152

5.46.06-1 Released 2021.01.12

Bug Fix) Client 5.46.05 still had problems switching domains at one site. Two other sites testing that version didn't report any issues. The reported problem has been fixed. JIRA INDESIGN-3128

5.46.05 Released 2021.01.11

Better User Experience when Attempting to Log In to an Unavailable Server) If the server you were trying to log in to was not available for any of several reasons, the BLOX Total CMS Log In dialog could potentially be prevented from opening for several minutes as the client software tried repeatably to connect to it. It now will only try one time which should limit the non-responsiveness to perhaps 75-90 seconds depending upon the problem and how it is reported back to the client. This is particularly important to remote Distributed Production users. In addition, the Log In dialog will now indicate what might be the issue. Examples are shown below. JIRA INDESIGN-3032

Log In Network is unreachable.png
Log In Operation timed out.png

Distributed Production Improvement) Client 5.46.04 added a feature to build a servers.jsx file to aid with the log in process for new installations. This process has been improved to attempt to determine if it needs to create a normal installation or if it needs to make a Distributed Production Remote installation servers.jsx file. JIRA INDESIGN-3114

Login Dialog Improvement) When a site has the same server address listed in the login dialog more than once, a common occurrence with distributed production, the dialog now defaults to the choice the user last used rather than the first one matching that server. In addition, just clicking the Log In button sets the user's preference for the entry rather than needing a successful login. Thus, if you supply an incorrect password after choosing a different option, the dialog doesn't return to the previous option. JIRA INDESIGN-3115

Improvement to Logging In) If a site's servers.jsx file doesn't include a site value and yet the server supports 2 or more domains, the client software wasn't suggesting the last logged in to domain/site. Instead, it was presenting a Select Initial Site dialog with no selected options. This has been improved so that the last domain for this server will be selected. This doesn't, however, work if more than one server is regularly logged into. If you want to prefill the site option, include one in the servers.jsx file. JIRA INDESIGN-3120

Bug Fix) The prior release of the client added the ability to cache passwords. In testing, it was determined that if the user canceled the Log In process at the Select Initial Site dialog, the cached password would be removed. This has been corrected. JIRA INDESIGN-3120

5.46.04 Released 2021.01.05

New Feature to Create a site's/user's servers.jsx file) As part of the process to simplify the installation of the BLOX Total CMS for remote Distributed Production users, there is a new automatic function to create our servers.jsx file that provides the login information. JIRA INDESIGN-3013

Construct serversJSX (4) Remote with Site.png

New Feature for Logging In) The BLOX Total CMS client for Adobe InDesign now supports the caching of passwords. If you successfully log in, the password will automatically be kept to make logging in next time easier. This works providing two things: 1) The password has at least 12 characters; 2) You are using a non-appliance based version of BLOX Total CMS or your appliance-based BLOX Total CMS is at Appliance OS 2.28 or newer. In addition, if you are using a pool of appliance-based servers, all need to be at Appliance OS 2.28 or newer. If you need to clear the cached passwords, choose BLOX Total CMS > Update and Reset > Reset Password Cache... JIRA INDESIGN-3047

Cached Password TFA .png

5.46.03 Released 2020.12.29

Bug Fix) The prior change didn't fix all the issues with logging in if the user had access to more than one domain. Instead, they would get an empty BLOX Total CMS menu with only the Log Out menu item. This has been fixed. No sites received this or any prior 5.46.x version. JIRA INDESIGN-3112

5.46.02 Released 2020.12.29

Bug Fix) An internal change in 5.46.01, that no sites received, removed a property that some legacy, but sparsely used, fileServerDetails.jsx files expected. To allow them to work without causing upgrade problems we have added the property back for all sites using fileServerDetails.jsx files. JIRA INDESIGN-3112

There is a chance that some legacy utility scripts could also use the removed property. Client 5.45.x revamped how the utility scripts were configured, so if you use any of them, please request a current set via a support ticket at crm.tn-cloud.net/contactlogin/

5.46.01 Released 2020.12.28

Behavior Change for Creating Editions) During the use of BLOX Total CMS > Documents > Advertising > Create Edition from Edition file..., or its equivalents, if the user attempts to process the same or a modified edition file the user gets prompted to select which .adinfo files to delete. In the past, however, clicking the Cancel button in that dialog did not cancel the process. It now cancels the process of creating the edition file and it should attempt to close the initial document without creating any .adinfo files. JIRA INDESIGN-2358

Which of the existing adinfo files should be deleted.png

Minor Logging Change) We now include the active domain in the log message when a lack of layout files prevents the automatic opening of Ad Statuses. This is only to aid in troubleshooting sites with multiple domains. JIRA INDESIGN-2568

But Fix for using Create Pages with non-standard Templates) Client 5.44.09 added the option for the BLOX Total CMS templates for Adobe InDesign to be stored in Page Tracker and downloaded when needed. This was done for Distributed Production. This change broke the use of BLOX Total CMS > Documents > Advertising > Create Pages... for non-standard templates - those that were not created with BLOX Total CMS > Development > Spawn Template... This has been fixed. JIRA INDESIGN-2816

Minor Change to Development Mode's Add Components for Template Masters) In the past, the Add Components feature would complain in a dialog that it could not add the Advertising layer to the Layer's panel unless the 'Ads on Separate Layers' choice was activated in the browser-based preferences. This check no longer happens and the layer will be added by default. The site's template master can move the layer and change any attribute other than the name to suit the site's needs. JIRA INDESIGN-2924

Bug Fix) During routine testing, we noticed that there were certain occasions where the _BU document created with the Create Edition from Edition file... feature would not close following the use of Create Pages. This appears to be resolved. JIRA INDESIGN-2962

New Ad Layout Format) TownNews has developed a Very Simple Ad Layout system to aid those sites still holding on to the discontinued Managing Editor's Ad Force. Our system does more than Ad Force did and it is completely free for BLOX Total CMS users. It's been in use at sites for a couple of years now but we finally added native support for its new Edition file export. Users can select it as a custom Ad Layout Format in the browser interface, or it is now an option in the Configure Multiple Ad Layout Formats. JIRA INDESIGN-2983

Configure Multiple Ad Layout Formats for BLOX Very Simple Ad Layout System.png
BLOX Very Simple Ad Layout configuration.png

Improved Ad Position Detection) We had a site that was using a Save As function to rename documents. This triggered Ad Statuses to look at the ad positions when they used the Override .adinfo file... feature to recreate the advertising information for what is now, after the rename, a new publication. But because of their procedures, templates, master pages, or some other unknown issue, the ads move slightly to the left of zero and this caused serious problems with a vast number of dialogs warning of an unknown ad position. We now check those positions in the same way as with the column alignment and provide up to 1/2 of a column gutter of tolerance. JIRA INDESIGN-2991

The fix for this issue involved a fundamental change for handling double-truck ads. If your Ad Layout Format supports double-truck ads, please test several before needing one in a live publication. We didn't have samples from all the Ad Layout Formats that we support and could not test every scenario.

Bug Fix for Number of Pages in a Brainworks Edition) There was a bug in our support for Brainworks XML as an Ad Layout Format. Brainworks allows for an odd number of pages in a section, but BLOX Total CMS being a print-based system wants all sections printable so the number of pages is rounded up to an even number. But the client software failed to increase the total number of pages. So if, for example, a page was added to a section, the total number of pages would have previously been one page too short and the final section would have been missing that page. This has been corrected and now all sections will be fully populated. JIRA INDESIGN-2994

Distributed Production Change) When logging into a server for remote production, the Dead Jumps options are disabled. JIRA INDESIGN-3075

Document Jumps Disabled for Remote Distributed Production) The technology used with Distributed Production prevents the use of Document Jumps. Dynamic Jumps (aka. Combine With) remains a valid option if the remote user has access to all the documents. JIRA INDESIGN-3077

Template Master Spawn Template Improvement) To further reduce the size of templates, especially those created from legacy documents versus the recommended procedure from scratch, we now remove any embedded hyperlinks from the Master Document during the process of Spawning a template. JIRA INDESIGN-3092

Hyperlink Translation Improvement) Client version 5.45.04 included a workaround for when hyperlinks are added to assets placed on pages and then the assets get moved to another document and then that document is either removed or not available to be opened during write-back. This version adds a feature to add the initial hyperlinks in a manner that prevents the dependence on the original placed document. JIRA INDESIGN-3100

Template Master Improvement for Page Content Type Support) The Template Master feature to Add Components will now add the paragraph style named 'Ad Page Type' to the 'Advertising' Style Group. This is used at the top of the page when adding Page Content Type labels to the page. The style can be redefined as desired by the site. JIRA INDESIGN-3103

Performance Enhancement) A change several major versions ago allowed _BU documents created with the BLOX Total CMS > Documents > Advertising > Create Edition from Edition file... feature to start updating Page Tracker with both segments and PDF previews when closing that document. That caused the closing to be slower than desired, especially on documents with many pages and/or those with excessive template file sizes. The client code has been changed to only update Page Tracker from the pages _BU documents if the following conditions are met: (JIRA INDESIGN-3105)

  • The page has no assets placed. That can happen if this is a second _BU or if a page was created in advance.
  • The page is NOT at the final process of the Pages workflow. This can occur when the ad layout people open _BU documents to check for new ads when pages have already been completed.
  • The user is using an output function. You can perform outputs to Page Tracker if your output preference includes such an option.
Create Edition Options.png

Clarification of Updating Page Tracker when using Override .adinfo file) The Override .adinfo file function now sports two checkboxes for updating Page Tracker with wireframes and previews when the override is performed on the _BU documents created with the {{BLOX Total CMS > Documents > Advertising > Create Edition from Edition file...}} feature. Because of the above change users of the Override .adinfo file feature would need to force an update to Page Tracker if they want the current state of the pages to match in Page Tracker. JIRA INDESIGN-3105

Override adinfo on Backup Document.png

Esoteric Output Bug Fix related to Page Color) The 5.44.x version of the client added a new feature for page color labels that allows pages to be named uniquely and or sent to unique destinations based on if the page is marked as a color page or a black and white page. Unfortunately, there was a typo in the output features that was triggered by not using the feature but having the legacy output specify a unique name with a <namingConvetion> value in the output preferences. That bug would cause the users to be prompted to select a page color when they should not have been prompted at all. This bug has been fixed. JIRA INDESIGN-3106

Ad Statuses Bug Fix) A recent version of Ad Statuses or Ad Statuses with Creative Cloud 2021 can cause the dialog to grow too large. This has been fixed. JIRA INDESIGN-3109

Prior Versions:

The release notes for all prior versions can be found at this link: