5.44.08 Released 2020.10.16

Minor New User Preference to not display the Incomplete Log In dialog) If a user's account is such that they don't have access to one or more domains on is a server pool with multiple domains, an Incomplete Log In dialog will be displayed. This dialog was added with version 5.43.17-1. Pooled servers are exceptionally rare and primarily only used in larger groups of design centers. But at such a site that limits users' access for a valid reason, they didn't like seeing the informational dialog at each login so we have added a Settings and Support option to prevent its display. If the dialog has been shown to a user they will have the Hide Incomplete Log In Dialog option. Check that and click OK and it won't be displayed again unless the user's BLOX Total CMS preferences are reset. Resetting preferences is usually handled with BLOX Total CMS > Update and Reset > Reset User Preferences... JIRA INDESIGN-2990

+23 
Incomplete Log In dialog.png
+23 
Hide Incomplete Log In Dialog Option in Settings and Support.png

New Option for Output Validate Name scripts) When calling validateName scripts (function names in a .jsx file in your Add-ons folder) the page's default Page Content Type is passed as the second argument. This allows you to put the page content type in the name of the file. For example, you can output 'sports', 'news', 'obits', etc in the name of the file created by BLOX Total CMS > Documents > Output > menu group > method. Here is one sample of a complicated page naming convention: 2020-10 October-14-Wednesday_BLOX Total CMS_Alocalnews-2_BlackOnly_vn.pdf. If you need to take advantage of such an output name please request assistance at support.townnews.com JIRA INDESIGN-3000

New Support Feature) The Support tab of the dialog reached at BLOX Total CMS > Settings and Support now how a button to take users to the client release notes. Unfortunately, some user's local browser security settings might prevent this button from functioning. JIRA INDESIGN-3008

+23 
Client Release Notes Button.png

UI change for Change Document Domain) One of our regional production sites managed to add enough domains that they outgrew the original design for the dialog reached by BLOX Total CMS > Set Document Domain. That dialog now displays multiple columns of domains if there are too many for a single column. For a small number of domains, it has a slightly different appearance. INDESIGN-3009

+23 
Revised Set Document Domain Normal.png

5.44.07 Released 2020.10.09

Huge New Output Feature) The 5.44.x version of the BLOX Total CMS client for Adobe InDesign has slowly been adding features to allow pages to marked with their color. This becomes important as most, but not all sites, have limitations on the number of pages that they can print in full color. In addition, some sites need to either name their color and black and white pages differently or to send them to different locations. This unique naming and destination can now be automated. In the past, a site needing a unique name for the output folder needed to have multiple output methods defined in their output preferences. While completely functional, this added complexity to the output, and users would sometimes select the incorrect options. This 5.44.07 version of the client adds a huge new feature that can rename or direct the final output to different folders. The configuration of the feature is described at the link below. It is important to note that these new features are not required (you can continue to use your existing setup) and all of the Output functions remain optional. They are not required for using the BLOX Total CMS client for Adobe InDesign. JIRA INDESIGN-626

Minor UI change for Refreshing Text Variables) The 5.43.08 version was supposed to move the Set Folio Text Variables option to the Documents Menu. But it failed to remove it from the Update and Reset menu. This has been fixed. JIRA INDESIGN-2888

The UI fix for skipped ruleset notification has been extended to also include CS6) The 5.43.14 version replaced a dialog, that the Creative Suite CS 5.5 version could not display, to a text file. QA tested the same dialog with Creative Suite version CS6 and found that it too could not display the dialog. So the text file based warning for skipped rulesets has been extended to CS6 versions as well. This is yet another example of how even though Adobe stopped supporting Creative Suite years ago, subtle changes are happening as the host OSes are updated. JIRA INDESIGN-2913

Page Color Labels Bug Fix with New Document dialog) If a site had disabled the Page Color Labels by using the pageColorLabels.disabled file, then BLOX Total CMS > Documents > New... would not allow the dialog to be opened. This has been fixed. JIRA INDESIGN-2992

Minor Newzware Bug Fix) A user at a site using Newzware for their Ad Layout Format: accidentally selected the BLOX Total CMS > Documents > Advertising > Update/Create .adinfo from Layout file... and the client threw an error rather than the appropriate dialog shown below. This has been fixed. JIRA INDESIGN-2993

+23 
Newzware Requires Enhanced Mode.png

Bug Fix for Keyboard Shortcuts of Utility Scripts) The 5.44.06 release allowed the Utility Scripts to be organized by folders. But it also removed the ability to have keyboard shortcuts. To make matters worse, the old keyboard shortcut scripts remained but were no longer functional. We've added support for the new keyboard shortcut scripts, but because of the technology involved, the old ones should be removed. You can force them to be replaced using the two options in the Keyboard Shortcuts (KS) tab in the dialog found at BLOX Total CMS > Settings and Support... JIRA INDESIGN-2995

+23 
Replace Shortcuts Scripts.png

Bug Fix for Replacing Existing Keyboard Shortcuts) There was a long-standing bug with using the Replace Existing Keyboard Shortcut Scripts in the above dialog. While it worked, it usually wouldn't work until the next launch of Adobe InDesign/Adobe InCopy and then only when 'Build Shortcuts Scripts' was already checked. Now it will rebuild them after clicking the OK button if the option is selected. JIRA INDESIGN-2995

5.44.06 Released 2020.09.29

Improvement for Utilities) The Utility scripts that some sites use have previously been available in a single, long, menu item. That menu now allows for submenus for Adobe Creative Cloud users. To add a submenu, add a folder to your Utilities scripts folder and move the desired .jsx based utility scripts into that folder. Non-appliance Creative Cloud based sites will get this feature when they install this version of the client. Appliance based sites will need to update to Appliance OS 2.28 to get the feature. As with snippet folder menus, apostrophes and certain other special characters can NOT be used on folder names nor on with the folder names. Below is a sample menu and the folder structure that produced it. Note: the subfolders can be multiple layers deep and commonly used scripts don't need any subfolders. JIRA INDESIGN-2690

+23 
Sample Utilities Menu.png
+23 
Renamed Utilities.png

Minor Template Master Change) The Template Masters' function at BLOX Total CMS > Development > Spawn Template now clears the template of any prior template name to prevent issues arising when the templates weren't created properly and Create Pages is subsequently used. Most commonly an esoteric issue could arise from using our very Simple Ad Layout utility and non-standard multi-page templates created incorrectly from other templates. JIRA INDESIGN-2981

Ad Statuses Bug Fix for Page Color Labels) If a user renames a document page in such a way that the .adinfo is no longer available, then the page color labels don't provide much information in the Ad Statuses dialog. The image below shows one. If, however, a user tried to click on that item to determine what it was, an error was displayed. This has been corrected and clicking on it produces no results nor does Ad Statuses scroll to the label as it isn't technically an ad. JIRA INDESIGN-2984

+23 
Ad Statuses with Color Label.png

Minor Page Color Label Change) To speed the generation of segmentation from Adobe InDesign pages with Page Color Labels, the labels will be ignored earlier in the segmentation process. The users won't notice any difference in this minor change. JIRA INDESIGN-2985

Minor Esoteric Bug fixes when using Create/Update .adinfo file from Layout File and Vision Data Ad Layout Format) The BLOX Total CMS > Documents > Advertising > Update/Create .adinfo from Layout File... function had two issues when using the Vision Data. 1) The format wasn't always recognized; and 2) An error occurred if the document had been renamed. Both issues have been fixed. JIRA INDESIGN-2986

Bug Fix) The new Page Color Labels would be examined when using BLOX Total CMS > Documents > Advertising > Override .adinfo file... but it would throw an internal error and shouldn't be added to the .adinfo file through this method anyway. Instead, use BLOX Total CMS > Documents > Set Color of All Pages... to use them to set a page's color. This issue only occurred when using an odd workflow to create pages without existing .adinfo information: aka, using Save As on the existing page, and naming with anything other than a different zone. These Internal errors have been fixed. JIRA INDESIGN-2988

Change to Warnings on misplaced Ads without associated .adinfo files) We had a site that was doing some unique things with sharing pages and causing ads to get placed on documents where they didn't fit. Both Ad Statuses and the Override .adinfo function initially expected that the users would want to be warned uniquely for each serious ad problem such as the ads not being in the live area of the page. But for this one site, that is overbearing. So we have switched from individual dialogs to the standard failures dialog we use elsewhere in the BLOX Total CMS client for Adobe InDesign and InCopy. Note: Because Adobe Creative Suite versions (CS5, CS 5.5, and CS6) have difficulty with the failures dialog, this change only affects Creative Cloud sites. JIRA INDESIGN-2989

5.44.05 Released 2020.09.18

New Page Color Feature) As a further extension of the Page Color support, now when a user uses BLOX Total CMS > Documents > Advertising > Create Edition from Edition file..., if there is no Page Color support in the edition file/layout file the user will be prompted to set the page color. In this case, the dialog will appear with all pages set to na. To ignore setting the page color, click the Cancel button. As with all the Page Color features, sites can add a 'pageColorLabels.disabled' to the root of the code folder to disable the feature for all users. JIRA INDESIGN-532

+23 
Page Colors without Any Known Values.png

New Page Color Enhancement) There is a new feature at BLOX Total CMS > Documents > Set Color of All Pages... that allows the unsplit Edition document, as well as any properly named BLOX Total CMS document to have the page color viewed and/or changed. The menu item and the dialog are shown below. This feature can be disabled, along with all of the Page Color options, with a pageColorLabels.disabled file in the root of the client code folder. INDESIGN-898

+23 
Set Color of All Pages Menu Item.png
+23 
Page Colors with Sections.png

New Suggest Page Color) The Page Color dialog available at BLOX Total CMS > Documents > Set Color of All Pages... and also as an option of both BLOX Total CMS > Documents > New... and BLOX Total CMS > Documents > Advertising > Create Edition from Edition file... has a new Suggest button that uses the following guidelines to suggest the page's color. In all cases, the user can override the suggestions. JIRA INDESIGN-2961

  • If the page has .adinfo information regarding page color, the color will be derived from that.
  • If the page has a color ad, the page is considered a Color page. Black and White ads are ignored.
  • If the page has a page color label frame, including those from snippets, the Page's color will be derived from that frame.
  • If a Page Content Type is applied to the page and if the name of that includes Color or BW, the Page's color will be derived from that.
  • If all those methods haven't lead to a page color then if the page has a known matching page in the press signature, then that will be used to suggest the page's color. For example, if it is an 8-page section pages 2 and 7 will be printed at the same time and if Page 2 is known to be Blank and White and page 7 has no known value, it Black and White will be suggested. This final set of information is only provided when triggered via BLOX Total CMS > Documents > Advertising > Create Edition from Edition file...
+23 
Page Color Suggest Button.png

New Support Feature) The Support tab in Settings and Support now has a new button Show ProtectiveShutdownLog Folder which will open the folder containing Adobe's ProtectiveShutdownLog file. The file is generated whenever Adobe InDesign or Adobe InCopy decides to shut down / quit / crash to protect the database that is the Adobe InDesign or Adobe InCopy document. Even if the file doesn't exist, the folder for it will still be opened when clicking this button. JIRA INDESIGN-2967

+23 
Support Tab 5.44.05.png

Page Color Label Improvements) The internal function to add a page color label to the pages will now reuse an existing label rather than always place a new one. This means that the label can be placed in a different location if desired. The reasoning here is that an existing color label from any page can be modified in any way the site wants and placed in a snippet. Once the snippet is used on a page, the Set Color of All Pages function will recognize the frame as a label and allow it to be reused. It does not, however, recognize the color setting from the label as the page itself needs to be na for the Set Color of All Pages to recognize a change happening to the page's color. The Suggest button in the Page Color dialog will recommend page colors from these revised labels. The frame can be changed from a Text frame to any other frame. And it can be set to use whatever object style you wish and it won't be overridden. JIRA INDESIGN-2968

Template Master Improvement) To further support the page color labels added in client 5.44.x, the Spawn Template function now clears the page color values within the template document. Note, they would not normally be there if the Master Document is created correctly, but because not all sites do things correctly, this improvement prevents a site from accidentally setting the page color from the Template's prior page color. JIRA INDESIGN-2969

Bug Fix) At some point, the legacy BLOX Total CMS > Documents > Advertising > Split Document feature stopped moving the unsplit document to the Backups folder. This then caused it to remain in the live folder and then produced a _02 suffixed version of the single page. All this has been fixed. There is a chance that the problem was related to an OS update. We are unsure if any users encountered this bug or if it was limited to development. JIRA INDESIGN-2973

5.44.04 Released 2020.09.04

New Page Color Labels in for Page Tracker) Pages with known colors now pass that marking to Page Tracker so the Page Tracker users can know if the page is considered a color page. Page Tracker assumes all pages are color pages unless specifically marked. So you might have these color markers unless you disable the feature by placing a pageColorLabels.disabled file in the root of the client code (usually tcms_data) folder. JIRA INDESIGN-897

+23 
Page Color Gallery View.png
+23 
PageColor List View.png
+23 
Page Color Wireframe View.png

Granular Reflow Improvement) When reflowing an image or PDF asset that has the option of having a Standalone Head the value of the title checkbox will now be controlled by the Settings and Support dialogs option for No Standalone Heads. Thus, if you have set the BLOX Total CMS client to not create Standalone Heads when placing image assets, reflowing image via the Granular Reflow dialog assets will automatically uncheck the source of the Standalone head, the title field. This improvement was suggested by a client site. Do you have suggestions for the BLOX Total CMS client? JIRA INDESIGN-2955

+23 
Settings and Support Article and Image No Standalone Heads Driving Granular Reflow.png

Improvement to Documents > New...) There is a new feature of the New... dialog reachable at BLOX Total CMS > Documents > New... that allows users in Enhanced Mode to set the Page Color at the time the document is created. The dialog is shown below. JIRA INDESIGN-2958

+23 
Set Page Color During Document Construction.png

Adobe InCopy Check-In Bug Fix) An earlier version of the client software (5.43.13-1) allowed the asset titles to be changed on image assets in the Adobe InDesign Check-in dialog. But this caused a bug to occur in Adobe InCopy Check-In dialog if the title of any asset was changed. This has been fixed. JIRA INDESIGN-2966

5.44.03 Released 2020.09.01

Updated Feature for Color Markers on Pages) At various times, the BLOX Total CMS client for Adobe InDesign supported automatically placing color labels at the upper right-hand corner of the pages. The color information comes from the Ad Layout Format's Edition file and different formats provide different degrees of success. Ad Statuses will show the Color Mode indication, but will not allow flag missing markers nor create the placeholders if they are missing. If the feature is undesirable, add a file named 'pageColorLabels.disabled' to the root of the code folder to disable the feature for all users. JIRA INDESIGN-250

+23 
Page Color Label B.png
+23 
Page Color Label C.png

The following Ad Layout Formats support the user of Page Color Labels:

  • Ad Base PGL Text
  • Miles 33 XML
  • Naviga XML
  • Vision Data XML

The following Ad Layout Formats appear to provide the information but we do not yet support the Page Color Labels:

If sites want this, please send a request via a support ticket at support.townnews.com

  • APT PageMaster / APT PowerPlan
  • ATEX XML

The following Ad Layout Formats do not provide page color information but do provide Ad Color information

From that, page color can be inferred in as much as a color ad forces the page to be color. But as yet, this is not yet enabled. As above, to request this change please send a request via a support ticket at support.townnews.com

  • Brainworks XML
  • SCS Layout 8000

The following Ad Layout Formats do not provide any consistent color information and the BLOX Total CMS client will not be able to support page color labels:

  • Managing Editor (MEI) Ad Force (note: Managing Editor no longer supports this product)
  • Managing Editor (MEI) ALS
  • Newzware XML

Minor esoteric Bug Fix for MediaPlus sites) If a user attempted to use Create Edition from Edition File when the Ad Layout Format was set to Media Plus while also in Development Mode (very rare since Development Mode is for the Template Masters) an error could be thrown. This has been fixed. JIRA INDESIGN-250

Color Label Improvement) The Create Pages function, available for the Ad Layout Staff using Enhanced Mode will now create the page color labels if the color information is recorded in the .adinfo file. Only certain Ad Layout Formats support these color labels. JIRA INDESIGN-1065

Major New Feature for Multiple Ad Layout Formats) There is a new Development Mode (aka for the Template Masters) function that allows the Advertising staff to switch amongst multiple Ad Layout Formats without having to switch the options in the browser-based preferences and then quit and relaunch Adobe InDesign or swap to a fake domain with a different preference. This new feature is most useful for those sites that are switching from one Ad Layout system to another. For example, since MEI has dropped the extremely limited Ad Force, our clients are smartly switching to other systems. Switching involves testing and that means swapping the Ad Layout Format. This new feature makes it easy to test or just use multiple systems for different publications in the same domain. Start by entering Development Mode and then choosing BLOX Total CMS > Documents > Advertising > Configure Multiple Ad Layout Formats... That will open a dialog where the supported formats are shown. Check the desired boxes and click OK. Then users can pick BLOX Total CMS > Documents > Advertising > Create Edition from Edition file with Specified Ad Layout Format... to choose the active format. From there it sets a temporary default and proceeds with the standard prompts to locate the edition files. JIRA INDESIGN-2283

+23 
Activate Multiple Ad Layout Formats.png

Minor Changes to Advertising Edition File and Layout File Extensions) If you specify in the browser-based preferences an edition file or a layout file extension that is not lowercase, it will be internally be converted to lowercase. There is a possibility at sites not using our appliances for file servers that the file server in use might be case sensitive and also might be configured to export upper case file extensions, most likely for an .XML format, where this could cause some unforeseen conflict. Please test. If you run into problems, just export your edition files and your layout files using lower case file extensions. In addition to this cleanup, we now make sure that any leading or trailing spaces are removed. JIRA INDESIGN-2283

Minor Change to Enhanced Mode) If a user either selects or deselects BLOX Total CMS > Documents > Advertising > Enhanced Mode, the entire menu structure will be recreated. This is because some options are shown and/or hidden as the user switches modes. JIRA INDESIGN-2283

Minor Logging Change when skipping updating Page Tracker) To help to troubleshoot when Page Tracker isn't updated by the BLOX Total CMS client from Adobe InDesign, we log some additional information to find the answer why. Common causes are a recent update or just saving a document that is already at the final process of the Pages workflow. JIRA INDESIGN-2717

Segmentation Bug Fix) It was discovered and reported to us that if assets are merged on an Adobe InDesign page, the segmentation for Page Tracker's Wireframe view, and thus Live e-Editions would be for the first asset placed. Instead, merged frames should be switched to cutouts and this now happens. If, however, you want to produce a link to an asset, produce an Adobe InCopy assignment for the merged items as this will produce a new article asset with full segmentation. This is outlined in the document for best practices. JIRA INDESIGN-2953

https://help.bloxcms.com/knowledge-base/total-cms/technical_users/article_64146b8c-1110-11e5-809b-93167d167373.html

Bug Fix) After numerous bug reports from several sites we finally got some repeatable steps to fix an issue with both the 'Add Selected to' and 'Element Types' menus. It turned out the problems only existed when the sites were using domains that were grabbing rulesets from other domains. The bug was that the list of element types wasn't being built in those cases. This has been fixed and both the 'Add Selected to' and 'Element Types' menus should not function without generating errors. JIRA INDESIGN-2956

Image Statues Bug Fix) If a user logged in without using a listed site from the servers.jsx file (i.e. they are using Manually Entered or the servers.jsx file lists a server address but no site name) then the Image Statuses menu option wouldn't always be available. This bug was introduced in the 5.43.01 and newer versions, but it has been corrected in this version. In addition, Image Statuses now is on by default. It can, however, be disabled via an imageStatuses.disabled file. JIRA INDESIGN-2957

5.44.02 Released 2020.08.13

Stability Improvement) As part of our strong desire to improve the stability of the Adobe InDesign and InCopy client for BLOX Total CMS, we have removed one of the persistent objects from the global namespace and moved it to a standalone function. The users will not notice any changes, but we hope it helps with stability. JIRA INDESIGN-2569

Faster Launching) To speed the Log In process we now skip loading the syndication tool settings until opening the Asset Manager for the first time. This saves at least about 0.2 seconds on fast sites/workstations and more in slower situations such as WANs or hosted BLOX Total CMS environments. JIRA INDESIGN-2691

User Interface Bug for Adobe InCopy Assignments) The Settings and Support user interface had a bug in the Adobe InCopy, or AIC, tab. If the user unchecked the Enable InCopy Assignments, it would disable the Create Assignments Automatically, but it wouldn't uncheck its value. Thus, it would set the default in the Asset Manager to Create Assignments to checked. This has been fixed. And if InCopy Assignments are unchecked in Settings and Support, Create Assignments Automatically will also be unchecked. JIRA INDESIGN-2926

Note: If a site's browser-based preferences are configured for Auto Assignment Creation, this will automatically check both boxes in each user's Adobe InCopy tab of Settings and Support at each launch of Adobe InDesign.

Granular Reflow Bug Fix) An earlier bug fix related to image assets now ensures that the image asset Title gets passed during reflow. That Title becomes the Standalone Head. But a bug in the Granular Reflow allowed the Standalone Head to be unchecked and yet still cause a standalone headline frame to be updated/created with the text of undefined during a reflow. This has been fixed. If title is unchecked, the head will no longer be added to the Adobe InDesign page. JIRA INDESIGN-2929

Bug Fix) Some of the recent changes to fix an issue with sites using the Add Selected Frame To option caused its own error which has now been fixed. If you are having difficulties with that feature, please upgrade to this 5.44.02 client or newer. JIRA INDESIGN-2945

Minor Logging Change) The Adobe InDesign user's Tranlate.log files (and all the various copies that are sent to the tcms_purged directory) now log the output method details in an easier to read fashion. This helps when troubleshooting sites. JIRA INDESIGN-2946

5.44.01 Released 2020.08.10

Bug Fix) We found in a QA log a case where the user was quitting Adobe InDesign while documents were open and an error was thrown because one of the documents wasn't yet saved. The error has been corrected but it wouldn't have caused any user issues. JIRA INDESIGN-2939

Logging Changes) In an effort to make the client logs easier to read, a lot less information is now included in them. This will be an ongoing effort but in this version of the client, there is a new Logging tab in BLOX Total CMS > Settings and Support that, by default, removes the logging of flow-based entries: a log entry that indicates function names being used. In addition, common functions log less information or use fewer lines in the log to log the same information. All of this will speed the client slightly (logging is exceptionally fast) but will make the log files measurably smaller for when a log is needed to be sent to TownNews customer support. JIRA INDESIGN-2940

Improvement) If a user has an account for more than one domain on a non-pooled appliance and without using the servers.jsx pool option, the user will get prompted for all the domains even if the account is set to normal vs. admin access on the other domains. This no longer happens and only domains with full Admin access will be presented as an option to log in to. JIRA INDESIGN-2942

Prior Versions: