Terminalfour: 8.2.16
- Date Released:
- December 6 2018
General
This release focused mainly on resolving issues for Workflow, Packages and Form Builder.
Under the ongoing Performance theme, we reduced the HTML generated for the site structure (RDSM-27335). This has had some good results:
- For a single collapsed section the HTML size has been reduced by 52%
- For a full Site Structure with 720 Sections the HTML size has been reduced by 49%
The following bugs were impacting many clients and priority was given to resolve them:
Key | Summary |
---|---|
RDSM-23477 | Workflow emails are not sent to the step moderators on step start |
RDSM-28725 | Workflow inheritance does not extend past children |
RDSM-26728 | Workflow (step) in approve content table is empty for inherited workflow |
RDSM-29080 | Step emails are sent to step moderators who cannot approve the content |
RDSM-29078 | When workflow content is rejected and then edited, it does not use the workflow |
RDSM-28262 | Section/Content links prepend the microsite site root for all links |
RDSM-28031 | Form fields stuck together when drag and dropping |
RDSM-28468 | When a submission cannot be imported due to special characters the stack trace should be suppressed |
RDSM-28656 | Data Object: Does not support TLS1.1 or TLS1.2; Many servers now require TLS1.1+ |
RDSM-20626 | Duplicate content shows the incorrect breadcrumb on the approval page |
RDSM-27412 | Fully formed microsite not generating absolute paths for channel links |
RDSM-29193 | SAML login appending 'null' to URL, leading to 404 |
Supported Systems
Include Linux - CentOS 7
Changes
Component | Summary | Priority | Key |
---|---|---|---|
Authentication | SAML login appending 'null' to URL, leading to 404 | P3 | RDSM-29193 |
Channels / Microsites | Upgrade task is needed to set output dir to an empty string for micro-sites and correct null base_uri and base_href values | P3 | RDSM-29734 |
Channels / Microsites | Fully formed microsite not generating absolute paths for channel links | P3 | RDSM-27412 |
Channels / Microsites | Cannot access microsite which has incorrect root section | P4 | RDSM-29686 |
Content | Performance: it takes circa 20 seconds to delete 24 pieces of content with attached file | P3 | RDSM-22709 |
Content | Mirrored content: HTML tags appearing in mirrored location for content | P4 | RDSM-21975 |
Content Approval | History tab, versions of content are not displayed for comparison | P3 | RDSM-23512 |
Content Approval | Duplicate content shows the incorrect breadcrumb on the approval page | P3 | RDSM-20626 |
Content Syncer | No columns to select in type mappings, when a csv with spaces in its filename is selected | P3 | RDSM-25492 |
Content Types | Recycle content, deleted content type layout(s) appear on inactive & orphaned content tabs | P3 | RDSM-23048 |
Data Object | Data Object: Does not support TLS1.1 or TLS1.2; Many servers now require TLS1.1+ | P3 | RDSM-28656 |
Database | Events should use a defined thread pool | P3 | RDSM-29171 |
Form Builder | Reduce number of stack traces and shorten them that are caused to write lock on submissions index | P3 | RDSM-29894 |
Form Builder | Using nested dependencies with fields that are mapped to an existing list causes the content type to be created each time | P3 | RDSM-29313 |
Form Builder | Viewing the Form builder config page after upgrade throws an error if not connected to Form bank | P3 | RDSM-29136 |
Form Builder | When a submission cannot be imported due to special characters the stack trace should be suppressed | P3 | RDSM-28468 |
Form Builder | Form fields stuck together when drag and dropping | P3 | RDSM-28031 |
Form Builder | If you drag and drop CC info field to change location in the form, the field above it is also moved | P4 | RDSM-25173 |
Form Builder | Not possible to remove part of a dependency | P4 | RDSM-21795 |
Form Builder | Unwanted warning is displayed in dependencies when creating new form | Trivial | RDSM-23482 |
Hierarchy | Verbose HTML markup in Site Structure attributes leads to slowdown of page rendering | P3 | RDSM-27335 |
Hierarchy | Cannot find content version pops up in logs when you create new section on client dataset | P3 | RDSM-25678 |
Hierarchy | Mirrored child sections missing correct icon on package import | Trivial | RDSM-29094 |
Installer/Upgrader | CSS custom styles file from TinyMCE disappears from a non standard TinyMCE profile on upgrade | P3 | RDSM-29642 |
Navigation | Top Content navigation object (and likely others) have incorrect DB values post upgrade | P3 | RDSM-29965 |
Navigation | Fully formed microsite using navigation objects not publishing media files from another microsite or channel | P3 | RDSM-29669 |
Packages - channel | Section Package Import fails when it contains content with a link to a purged section | P3 | RDSM-29385 |
Packages - channel | Channel packages import fails when it contains a content asset which has a list element populated with a list value id that no longer exists in the list | P3 | RDSM-28311 |
Packages - channel | Content type set to "Branch" instead of "Section" on imported section | P3 | RDSM-26803 |
Packages - general | Media referenced more than once being added to package graph with no links to files | P3 | RDSM-29487 |
Packages - general | Media referenced in a package as both link text of a section/content link and as regular content results in media with no actual files to be imported | P3 | RDSM-29455 |
Packages - general | Media referenced in a package only as link text of a section/content link causes package error on import | P3 | RDSM-29454 |
Packages - general | Media variants resolved twice as part of package creation but only one reference contains link to file | P3 | RDSM-29301 |
Packages - general | Channel packages assigns incorrect file to variants on import | P3 | RDSM-29130 |
Packages - general | Media is imported to parent category with broken images when Media archive package is imported with Language set to English | P3 | RDSM-26962 |
Publish | Publish failing when caching is disabled | P3 | RDSM-29117 |
Publish | Section/Content links prepend the microsite site root for all links | P3 | RDSM-28262 |
Publish | PublishCache doesn't cache failure to load page/content layouts, etc. causing performance issues | P3 | RDSM-26868 |
Scheduler | Successful scheduled email notifications are being sent even though they are disabled | P3 | RDSM-29484 |
TinyMCE | Plugins for TinyMCE editor are unchecked after upgrade to V8 | P3 | RDSM-29648 |
Upgrader | Upgrade 0594 fails to deal with corrupted legacy data in media tables | P3 | RDSM-29844 |
Workflow | Content cannot complete a workflow if other pieces of content, in same workflow, have active workflow steps | P3 | RDSM-29778 |
Workflow | Inactive users receiving workflow emails | P3 | RDSM-29650 |
Workflow | Contributors receiving workflow emails | P3 | RDSM-29649 |
Workflow | Content in a workflow skipping required approval step | P3 | RDSM-29634 |
Workflow | Assigning a workflow to a section with existing content does not add the content to the worklfow | P3 | RDSM-29632 |
Workflow | Step emails are sent to step moderators who cannot approve the content | P3 | RDSM-29080 |
Workflow | When workflow content is rejected and then edited, it does not use the workflow | P3 | RDSM-29078 |
Workflow | Workflow inheritance does not extend past children | P3 | RDSM-28725 |
Workflow | Workflow (step) in approve content table is empty for inherited workflow | P3 | RDSM-26728 |
Workflow | Workflow: Able to bypass a step in workflow | P3 | RDSM-26727 |
Workflow | Workflow emails are not sent to the step moderators on step start | P3 | RDSM-23477 |
Workflow | Skipping steps/going to the wrong step when you have the reject settings set to content owner | P3 | RDSM-23460 |
Workflow | Duplicate content is not associated with workflow | P3 | RDSM-23096 |
Workflow | Workflow name not displayed in grandchild section when workflow is set to inherited | P4 | RDSM-26732 |
Workflow | No way of identifying from the UI what order workflow steps are in | P4 | RDSM-22944 |
Workflow | UI issues on create workflow and step pages | P4 | RDSM-17779 |
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.