Knowledge Base

Terminalfour: 8.1.9.6

Date Released:
April 14 2017

General

This minor release has a fix for issues mainly with Packages. Other fixes include resetting content on a Channel, multiple language media publishing, Content Syncer and navigation improvements.

Changes

Component/sSummaryPriorityKey
Caching, Content Resetting content does not work until the cache is rebuilt, causes all content to become unselected from the channel P2 RDSM-26324
Access Control Access Control changes don't cascade down to child sections P3 RDSM-13033
Content Types Cannot create content type if elements start with digit and the same word after P3 RDSM-26050
Form Builder, Languages Form submission in the submission report links to the submission in the language the UI is set to P3 RDSM-26270
Content Syncer, Hierarchy If the content syncer is configured to create a separate section for each content item and imports into a mirrored section/branch, the sections are not created in the "mirror" (only in the source) P3 RDSM-24852
Installer/Upgrader Login error when upgrading from 7.4.0004 to 8.1.9.4 P3 RDSM-26355
Media Library, Preview / Publish Publish fails with NullPointerException because it tries to get a version of media using the wrong language P3 RDSM-26410
Navigation Content type name inside a nav object is left blank if the power user does not have access to the content type set initially P3 RDSM-26099
Navigation If a power user doesn't have access to content types set for Keyword search, on saving the navigation object, the selected content types are lost P3 RDSM-26112
Navigation, User Experience (UX) PTOF: data loss when configuration contains non-accessible assets P3 RDSM-26223
Navigation, User Experience (UX) Pagination nav object: data loss when configuration contains non-accessible assets P3 RDSM-26221
Packages Media packages that contain variants cause the import to hang P3 RDSM-25753
Packages T4 tags for media within selective output are not parsed when process format is not set or set to false P3 RDSM-25911
Packages Importing a content type package fails with a package exception P3 RDSM-26004
Packages Section link for a piece of content has changed after importing a channel package P3 RDSM-26006
Packages Files with query params can cause duplicate content to be picked up when creating an HTML package P3 RDSM-26198
Packages Cannot import a package if content has a populated file element P3 RDSM-25971
Packages Variants are missing from TinyMCE after importing channel package P3 RDSM-26435
Packages Channel package: Related content navigation object loses selected content type on import P3 RDSM-26005
Packages Channel package: ID in navigation object t4 tag written in CSS file is not updated to the ID of the imported navigation object P3 RDSM-26019
Packages Channel package: Not importing content with image element populated P3 RDSM-25979
Packages Content link set in TinyMCE is overridden by a content link set in a link section content type after importing a channel package P3 RDSM-25989
Packages Importing a media archive from a media category package imports 0B media files P3 RDSM-25948
Packages Selected media layout for media element is set to "Default" media layout on import P3 RDSM-26002
Packages Radio button, select box, checkbox and cascading list selections are no longer selected when importing a package P3 RDSM-25985
Packages T4 tags in predefined list names and values should be resolved when importing a package P3 RDSM-26040
Packages Packages fail to import if a section link element and an html element with a section link are included in a channel package P3 RDSM-26432
Packages Packages: Link sections are imported as normal sections P3 RDSM-25915
Packages If the html element that was imported is empty the ReplaceLinks task can fail with a null pointer P3 RDSM-26191
Content Syncer, Scheduler, User Interface & XHTML Compliance When scheduling the content syncer the sync type is always "Initial sync" P3 RDSM-24756
Packages, User Interface & XHTML Compliance "Parse for t4 tags" is deselected in custom css media type layout P3 RDSM-26018

Before upgrading

In advance of the upgrade please view the information and Technical Roadmap. Please contact us prior to upgrading we can provide you with the pre and post-upgrade tasks.

Priority

Please note that the priorities assigned to bugs differ from those assigned to Client Support tickets:

  • P1 - Major rework of product.
  • P2 - Major performance change. 
  • P3 - Regular priority change. 
  • P4 - Minor change. 
  • Trivial - Very minor UI changes.