Skip to main content
Skip table of contents

Summary of Changes v4.0

Version 4.0 brings important new features, improvements and bug fixes, as well as under-the-hood tunings and security enhancements.

For content editors

Removed

  • Data Feed Items REMOVED

    • Replaced by Content Entries.

  • Content Library REMOVED

    • Removed – will be fully replaced in a future release, in which:

      • Content Entries will replace Content Items as the source of all Page content.

      • The Content Entry Library will become the centralised place to manage all items of content.

New features

  • Content Entries NEW FEATURE

    • A Content Entry is a collection of content fields, which together form a single unit of reusable content. You create them from developer-made templates known as Content Types. As a content editor, you fill in these fields, thus creating the actual units of content – for example, hero banners, footers, and blog posts.

    • Content Entries are similar to the Data Feed Items that they replace but with some additional features. For example, they can utilise Locale fallbacks and can be linked together.

    • At this time, Content Entries can’t be used on Pages – they can only be used directly in Consumer Applications. In a future release, however, you will be able to use Content Entries on Pages, replacing Content Items.

    • You can access this new feature under Library → Content entries in the side menu if you have been given the new content editor role by an administrator.

Improvements

  • Search IMPROVEMENT

    • You can now search terms that include spaces and “@”.

  • Default Locales IMPROVEMENT

    • You no longer have to select a Locale manually – one is selected by default.

    • You may have a different default Locale per Project (configured by Forrit).

  • Date Time fields IMPROVEMENT

    • The date and time is now always saved exactly as entered. (Previously, it was converted to UTC, which in some cases could cause the date to change by a day.)

  • Audit History IMPROVEMENT

    • The results table has been reformatted to make finding and understanding changes easier.

    • For clarity, item changes can now be viewed in a separate window, with formatting and colour-coding.

Bug fixes

Audit History

  • BUGFIX When you add a tag to a Task, it is now recorded in Audit History.

Media Library

  • BUGFIX You are now correctly prevented from uploading Media Items with “#” characters in the filename.

  • BUGFIX Image tags and thumbnails no longer sometimes fail to generate when uploading large numbers of images simultaneously.

  • BUGFIX Adding a tag no longer sometimes causes the route field to become uneditable.

  • BUGFIX Editing tags no longer sometimes causes an infinite loading bar to appear.

  • BUGFIX The List View/Grid View button is no longer highlighted by default in some cases.

  • BUGFIX Previously, there were slight differences when filtering in the Media Library versus the Media Picker. This has now been rectified.

Notifications

  • BUGFIX When an item fails to create (e.g. a Page), its notification now includes an error message.

Pages

  • BUGFIX In the ‘Add new page’ window, you are now correctly prevented from saving a Page route that has already been used. (Previously, you would be able to click save, but it would fail and display an error in the Page Tree.)

  • BUGFIX You are now correctly prevented from saving Page routes with invalid characters, such as “#”, “!”, and “:” (Previously, you would be able to click save, but it would fail and display an ‘unknown error’.)

  • BUGFIX In the Page Layout Editor, adding a Component with a long name to a Component Template Slot no longer causes the name to overflow the slot.

  • BUGFIX In the Page Content Editor, adding a Media Item with a long name no longer causes the name to overflow the screen, preventing the thumbnail from displaying.

Picklist Items

  • BUGFIX Picklist Items now correctly update in the Approved Content after completing a Task.

  • BUGFIX Picklist Items being edited no longer sometimes appear duplicated after reordering and pressing undo.

Releases

  • BUGFIX When you delete a Release, the displayed message now correctly includes the Release number (rather than ‘null’) and uses the appropriate terminology (‘release’ rather than ‘publish’).

Rich Text Editor

  • BUGFIX When you click an image inserted via Insert Forrit media item, the tools for image editing now correctly always appear. (Previously, they wouldn't be available unless the Insert Image toolbar button was also enabled via the Enable image edit Client Configuration setting.)

  • BUGFIX Abandoned Translation Jobs no longer appear under “Approved Content” in search results.

  • BUGFIX Fixed an issue preventing Task Review names and descriptions from being searchable.

Task Review

  • BUGFIX When you complete a Task in one browser window it no longer causes the ‘Task completed’ message in others where you may be working on separate Tasks.

Known issues

Rich Text Editor

  • Editing around captioned images KNOWN ISSUE

    • Users are unable to easily edit content around an image if a caption has been added.

  • Edit controls position while scrolling KNOWN ISSUE

    • The floating edit controls can move outside of the expected boundaries while scrolling.

  • Insert image cursor jump KNOWN ISSUE

    • After inserting an image, the cursor jumps to the beginning of the Rich Text area.

  • Video resizing KNOWN ISSUE

    • Users are unable to change the size of inserted videos.

For developers

Removed

  • Data Feed Definitions REMOVED

    • Replaced by Content Types.

New features

  • Content Types NEW FEATURE

    • A Content Type defines a template for a particular type of content – for example, a hero banner, footer, or blog post. As a developer, you create them for content editors, who use them to craft the units of actual content, known as Content Entries.

    • Content Types contain a collection of fields that template similar fields in Content Entries, where editors can insert values. You configure these fields with a specific type that defines the permissible values content editors can enter.

    • Content Types are similar to the Data Feed Definitions that they replace but with some additional features. For example, they can provide localised default values (that the Content Entries will be initialised with), and can be linked together.

    • You can access this new feature under Library → Content types in the side menu if you have been given the new content developer role by an administrator.

Bug fixes

Component Editor

  • BUGFIX Pressing the ENTER key in the markup no longer sometimes clears Picklist default values.

  • BUGFIX Changing a Picklist from multi-select to single-select no longer causes an unknown error on save.

  • BUGFIX Deleting a Component Template no longer causes errors for content editors on Pages where it was used.

  • BUGFIX Editing multiple Variable Types at the same time no longer sometimes causes a validation error that prevents saving.

  • BUGFIX On the Configure variables screen, SVG Media Items no longer overlap text, such as field headings.

  • BUGFIX On the Configure variables screen, long Media Item names no longer overflow and prevent thumbnail display.

  • BUGFIX You can no longer directly reference images (and other resources) uploaded as Media Items using their Azure blob container URLs (found e.g. in image src attributes), as these URLs are intended for internal use only and are highly unsafe for developers to use.

Locales

  • BUGFIX Deleting a Locale no longer causes errors in places where that Locale was selected.

  • BUGFIX Refreshing the page while editing a Locale no longer allows invalid fallback configurations to be selected (though they wouldn’t save).

  • BUGFIX When editing Locale fallbacks, setting a fallback that conflicts with those in another Task now shows the correct Task name in error messages.

Known issues

  • Cutting and pasting in the Component Editor KNOWN ISSUE

    • In the Component Editor, cutting and pasting code deletes Variables and recreates them, deleting all Content Items associated with them and resetting the Variable Type to the default – Text. This affects Page content, not just Component default values. If the containing Task is completed, the Content Items are permanently deleted.

    • You can work around this by copying instead of cutting.

For administrators

New features

  • Content editor permission NEW FEATURE

    • Grants access to the Content Entry Library (accessed via Library → Content entries in the side menu).

  • Content developer permission NEW FEATURE

    • Grants access to the Content Type Library (accessed via Library → Content types in the side menu).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close