5.42.06 Released 2020.01.20

New Ad Layout Format supported) We have added support for yet another ad layout format. The new format is an XML format from Naviga sites. To use it, you would configure your browser-based settings as shown below. This brings the list of fully supported formats to the following list. JIRA INDESIGN-2692

  • Ad Base PGL
  • Ad Force using an IDF file (We have a utility to produce that file if your Ad Force is too old to create it)
  • ALS (requires very customized output)
  • APT Page Master or Power Plan (three file format)
  • ATEX XML (a custom format)
  • Brainworks XML
  • DTI for Crystal Reports (customized output)
  • Media Plus
  • Miles 33 XML
  • Naviga XML
  • Newzware
  • PPI Saxotect XML (customized output)
  • SCS Layout 8000 (using .edf and .out files)
  • Vision Data XML

Bug Fix) The prior release could cause the Element Types menu to not show all the standard elements which could make building snippets difficult. This has been fixed. JIRA INDESIGN-2757

Template Master Note on Element Types: If you are adding an element type via the rulesets, the Element Type menu will not update by just using the Refresh option in the Asset Manager. You would need to use the BLOX Total CMS > Update and Reset > options for Translation Rulesets or Update All. This was done to speed the ruleset Refresh.

5.42.05 Released 2020.01.17

Important Image Statuses Bug Fix for Duplicated Images) Both the Duplicate option of the Pre-Placed Asset Policy, as well as the Duplicate option in the Asset Manager's Placement Options, failed to allow duplicated child images to used with Image Statuses. This long-standing bug has been fixed and duplicated images now work as expected with Image Statuses. JIRA INDESIGN-2580

5.42.04 Released 2020.01.17

Template Master Bug Fix) At some point in the client's history the merged element type was removed from the list of available element types. This made it hard to configure snippets for merged items like sports agate. JIRA INDESIGN-2757

Template Master Bug Fix) At some point in the client's history the ability for the rulesets to add element types was removed. This has been corrected. You can add an element type for your own purposes by creating a rule in the Export ruleset like the one below. JIRA INDESIGN-2757

FIELDVALUE
Start Tag:#!
Translate Script:<&tbu2:(,,,,NameOfElementType,ignore)>

Template Master Bug Fix) If a rule in the Export ruleset was commented out, the rule would still be processed instead of being ignored. This has been fixed. Only those rules considered Directives, those whose Start Tag: is #!, will be examined. All others will be ignored. JIRA INDESIGN-2757

Minor Logging Change for Template Masters) The log lists all the details of the Export Ruleset and where things export to, and how, but the log appeared in random order. This has been changed and that section of the log now sorts those Export Options. JIRA INDESIGN-2757

5.42.03 Released 2020.01.16

UI Fix) The shared dialog used for Check In, Save Content, or Create Assignment had a bug where it wouldn't show the fields after Notes if the Notes were very long. This has been fixed and the notes can now be scrolled within a size controlled area that allows the remaining fields to be displayed. JIRA INDESIGN-2749

Bug Fix) There was a bug introduced with the processing after adding a frame to an asset in Adobe InDesign using all of the four optional Add frames to asset functions. All have been fixed. JIRA INDESIGN-2750

+2 
The four Add menu items.png

If those options don't exist in your menu, they can be turned on in the InCopy tab of BLOX Total CMS > Settings and support...

+2 
Display Add 'items' to menu.png

Minor Bug Fix) We had a user select BLOX Total CMS > Update and Reset > Update All with an unsaved and improperly named document open. This threw an internal error that has been corrected. Remember if you need to use Adobe InDesign on non-BLOX Total CMS documents, choose BLOX Total CMS > Log out first. JIRA INDESIGN-2752

Bug Fix) Client 5.41.01 added a feature that allows assets to be duplicated on placement by checking an option in the Asset Manager (as opposed to limiting the option to the Pre-Placed Asset Policy dialog). Unfortunately, an internal bug always marked the frames for the duplicated asset with No Write-back which some users didn't like. We have corrected it and now the No Write-back option is controlled by the Asset Manager's Placement Options. JIRA INDESIGN-2755

5.42.02 Released 2020.01.09

Verified Legacy Behavior) We had a report of assets not maintaining the proper lock ownership when an asset was moved from page to page within a multi-page document. Our testing indicates that the desired behavior is working as intended and we could not reproduce the report. However, this could have been fixed with the recent changes to the core code that locates the assets within a document or it could be something unique to the site in question. JIRA INDESIGN-2511

Template Master Bug Fix) The 5.34.02 version of the BLOX Total CMS client for Adobe InDesign and Adobe InCopy added the ability to load rulesets from alternate domains. This works great for design centers that don't want to maintain multiple sets of identical rulesets. But unfortunately, the process was flawed in that the Update Rulesets functions didn't work with this new method. This has been fixed and you can now use BLOX Total CMS > Update and Reset > Translation Rulesets, BLOX Total CMS > Update and Reset > Update All, and the Refresh options in the Asset Manager while in Development Mode. JIRA INDESIGN-2575

Advertising Bug Fix) Since client version 5.25.03 released in January of 2018, after using Create Edition from Edition file, the Edition file and Layout file (if different) would be backed up to keep the Advertising folder cleaner. Shortly after that, we added the ability for a site to disable that feature. That request to disable didn't disable the backup of the Layout files if, like for APT, or SCS Layout 8000, the Edition file and Layout file are two separate files. This has been corrected and if the backupEditionFiles.disabled file is added to the root of the client software share, we will no longer back up the separate Layout file. JIRA INDESIGN-2460

Minor Bug Fix for APT PowerPlan Sites) The above features to backup the edition and the layout file never backed up the Pages file (.lp) from APT sites. This has been fixed and they will now be backed up unless the backupEditionFiles.disabled file is correctly installed. JIRA INDESIGN-2460

Bug Fix) The common dialog for Create Assignment, Check In, and Save Content has always had a bug where if the workflow of the asset was changed, the Promote and Demote buttons didn't update to the correct workflow. Even though the dialog has been in use since 2012, no site ever reported the issue. Instead, the issue was discovered by TownNews during routine testing. The bug has been fixed and now when the workflow is changed, the Promote and Demote buttons should automatically update. JIRA INDESIGN-2680

Minor Bug Fix) Attempting to Log Out of the BLOX Total CMS client for Adobe InDesign when a misnamed (or unnamed) document was open was throwing internal errors. This has been fixed. JIRA INDESIGN-2697

Improvement) If a site has cleared the maximum number of pages, any Adobe InCopy or Adobe InDesign user who logs in following this change will get warned. The setting is in the browser-based Settings > InDesign > Page creation settings' Index tab. JIRA INDESIGN-2723

+2 
Incomplete Page Creation Settings

This Warning dialog indicates that the site's naming convention is missing a maximum number pages per section. This is an issue for the site's Template Master to correct. 

Important Change for Multi-domain sites) In the past if a document being opened didn't have assets in it, we would NOT check to see if it was from another domain. We now check the document's domain and will switch domains if necessary. Note, documents created with BLOX Total CMS > Documents > Advertising > Create Edition from Edition file... will have the active domain inserted into the document. Documents created with other tools might not. JIRA INDESIGN-2731

Important Document Naming Change for Multi-domain sites) If your site does pagination work for more than one domain (site, web-site, etc.) operating on joined appliances or multiple non-appliances BLOX Total CMS sites hosted in our datacenters, the document naming should match across all domains. Remember, the document naming does not have to match your output naming, which is controlled by each domain's Output Preference XML file. TownNews will be glad to help you adjust output naming if your document naming needs to be modified to match all other domains. JIRA INDESIGN-2731

Minor Change in Opening Documents) If you open a document that is NOT named correctly for the active domain, we will no longer create the folder for the document's log. JIRA INDESIGN-2731

Minor Bug Fix for Ad Statuses) If an Ad Statuses user clicked on a Page, Block, or Color Mode line in Ad Statuses it would trigger an internal error as it looked for the related links. Alas, as these aren't ads, they won't have links. This has been fixed and internal errors are no longer triggered. JIRA INDESIGN-2732

Speed Enhancement for Large Documents or Master Documents) Some of the recent changes to better handle items placed on pasteboards (the proper way to remove an image caption is to place it on the pasteboard) caused a slow down when working with large documents. Complicated layouts like the Template Master's Master Document might take over a minute to open, save, close, etc. This has been corrected. JIRA INDESIGN-2733

Important Behavior Change) If a document is not considered named properly, the function that checks for page items will now only look for placed assets and will ignore placeholders, cutouts, and ads. This will speed up the use of these documents. It is still STRONGLY recommended that, except for the Template Master working with Master Documents, if you aren't using a properly named document, you should choose BLOX Total CMS > Log Out. JIRA INDESIGN-2733

Esoteric Bug Fix with Image Captions) There was a legacy (>10 years old) issue with a check for a variable often used with image captions that could have caused stand-alone images to not properly tag the caption frames and then trigger a No Default Frame message for the related image assets. This should now be fixed and new stand-alone images should be fine moving forward. JIRA INDESIGN-2733

Potential Stability Improvement) If multiple documents were open and then some of them closed, the Adobe InDesign event listeners could remain for the closed documents. Then, if those closed documents were later re-opened, Adobe InDesign could have potentially created a duplicate set of event listeners which could have caused Adobe InDesign to crash. We were unable to replicate any crashes because of this issue, but we verified cases where event listeners for documents that were not open existed during the examination of crash logs. Thus the issue is correlational and not causational. If you are worried about Crashes of Adobe InDesign we STRONGLY RECOMMEND upgrading to the current version of Adobe InDesign Creative Suite 2020. Remember, Adobe no longer supports Creative Suite and we do not develop or QA test using it. JIRA INDESIGN-2739

Esoteric Bug Fix) The developer encountered a situation during routine testing where after logging out of the client (as is recommended when using non-BLOX Total CMS named documents) that upon logging in again, the prior idle events for logging out were still running and it essentially caused Adobe InDesign to go to a not responding state. This has been fixed. JIRA INDESIGN-2745

Asset Manager Refinement) When logging into a domain for the first time (including during the first launch of the BLOX Total CMS client for Adobe InDesign and Adobe InCopy), the Asset Manager would likely show the Preview panel too narrow. This has been corrected. JIRA INDESIGN-2746

5.42.01 Released 2019.12.23

Bug Fix) The 5.38.01 version added the ability to force a PDF to open in your system's default PDF viewer and then acknowledge the PDF as being valid before proceeding to move it to its final location. This is a Page Tracker output method option turned on by using <approveFirst>true</approveFirst> in your Output Preferences XML file. Unfortunately, it was supposed to stop processing that page when the user marked the PDF as failed. But it proceeded to send the PDF anyway. This is now fixed. JIRA INDESIGN-1918

New Image Statuses Feature for Design Centers) All folders for Images referenced in the Image Toning Preferences XML file can now use %%pubcode%% to insert the active document's publication code into any of the listed paths. This allows for unique toning for CMYK, for example, by publication code without needing a unique menu option. To make the process even easier, many, if not all, of our hub or design center locations use a publication code prefix in this type of fashion CNTR-PUB and we will strip the non-alphanumeric separator and all that follows so that %%pubcode%% becomes just the prefix (CNTR in this example). This greatly simplifies the number of export locations. The use of %%pubcode%% works in both the defaults area and in the menuItem area of the XML. JIRA INDESIGN-2698 Additional information available here: https://help.bloxcms.com/knowledge-base/total-cms/technical_users/article_8e511f9e-e9f6-511c-bb99-2e55d6199933.html

Minor UI Bug Fix) The BLOX Total CMS > Update and Reset > menu was missing the option to update the Image Toning Options. That has been returned and its named changed from Image Export Preferences. In addition, there had previously been an option in the Template Master's Development Mode menu to Update Naming Convention, but this superfluous duplicate has been removed as it exists in the Update and Reset menu. JIRA INDESIGN-2698

Minor Logging Change) As sites have been updating Adobe InDesign and the client software, we have had a couple of reports of Ad Statuses not automatically opening as expected. We've added some additional logging to help track down why that might be. The current best guess is that the site wasn't using a template document spawn from the master document using the current version of Adobe InDesign this would open the pages in an unsaved condition where idle tasks can't run. We are hoping that this additional logging will confirm or deny this assumption. JIRA INDESIGN-2736

Minor Logging Change) All calls to Save Asset are now always logged. This is being done to allow for better troubleshooting during write-back as some write-back changes will be happening in this 5.42.x version. JIRA INDESIGN-2738

Prior Versions: