Resolved issues in Experience Space

This topic describes previously documented known issues in Experience Space that are now resolved.

Resolved in Tridion Sites 10

Resolved issues with publishing and deployment
  • An issue with intrusive publish notifications is resolved.
  • Users can now specify a valid time when scheduling deployment.
  • Default publish priorities defined on target types are no longer ignored.
  • Default priority can now be overridden when unpublishing.
  • Scheduling deployment now sets the correct time for users with a time zone offset to UTC.
Resolved issues with RTF and plain text fields
  • In the rich text editor, inserting a component link around a selection (image or formatted text) no longer deletes the selection.
  • Line spacing for rich text fields in read only view is now correct.
  • An issue where pressing Enter in a rich text field would scroll the entire page is resolved.
  • An issue with some user interface strings for the rich text editor only being available in English is resolved.
In both plain-text and rich-text fields, Experience Space did not display red underline highlighting for misspelled text. Spell checking now results in highlighting of misspelled text, provided that your browser is configured to enable spell checking for your default browser language.
Resolved issues with external items
Navigation to an external item that is not shown in the parent folder due to item limits

To avoid performance issues with large lists of external items, Experience Space limits the number of external items that can appear in a list to 1000 items. The limits can have unexpected results when a user clicks a link to an item with the intention of viewing that item in the list view, and that item happens to be one that is not shown in the parent folder due to the limit.

Previously, an error would appear saying that "We were not able to navigate you to the item with ID {number}." To get to the item, the user would need to copy the item's ID from the error message and use Experience Space's Search feature to locate it. Now, Experience Space will automatically navigate the user to the item's parent folder and show the item as a search result. Note that if the parent folder is also not available because of the limit, you will be navigated to the first available folder in the path.

History for External Components failed to load when the item was checked out and the current user lacked permission to read minor versions
Previously, when an Experience Space user tried to view the history for an External Component (an ECL item), the History list failed to load if the item being viewed was checked out by another user AND the current user did not have permissions to view minor versions (as is the case for a checked out item). This issue no longer occurs.
Incorrect dates for external taxonomy concepts
When using external taxonomies from Taxonomy Space, Experience Space shows summary information for the external concepts, which includes the date the concept was created and date it was last modified. In Tridion Sites 9.6, Experience Space showed the date and time the Core Service Rest API last updated the list of concepts rather than showing the actual create and modify dates. The correct dates now appear.
Resolved issues with GUI extensions
  • Extension field values are now correctly updated when using `renderField` as an input.
  • Extensions now have access to items selected in the table.
"Translation From" information appearing where it does not apply
In Tridion Sites 9.6, Experience Space displayed the Translated from section in the Translation panel where it was not relevant. This specifically occurred when viewing items in a Publication that were configured as both a source and target for translation but where the language of the Publication was the same as the language of its parent Publication (the source). Since there is no actual translation between the two Publications, you should not have seen the Translated from information when viewing items in the source-target Publication. This issue no longer occurs.
The content of rich text fields appear to be gone after the user tries to navigate away but cancels
Previously, users who of Google Chrome or Microsoft Edge sometimes experienced the following behavior: when they tried to navigate away from an item editor showing rich text fields and subsequently canceled out of the confirmation dialog that popped up, the user returned to the item editor, but all content in rich text fields in the item editor appeared to have vanished. The data was not lost but it was no longer displayed. This issue no longer occurs.
Experience Space entered an infinite loop when trying to synchronize against a modified Schema
Under certain conditions, opening a Page based on a Schema that had recently been modified could lead to an infinite loop (resulting in a spinner on the screen that never stopped spinning).
This issue was resolved.
Indefinite attempts to open Classic UI links in new window or tab
In numerous places, Experience Space provides links to other related Content Manager items. If the item type cannot be opened in Experience Space itself, such as for Schemas, then Experience Space opens the item in the Classic user interface.
In Tridion Sites 9.6, there was an issue if your implementation was also using Tridion Access Management for user authentication. When the context menu was used to open a such a link in a new tab or browser window, rather than opening the link in a single new window or tab, the browser opened two new windows or tabs and repeated this over and over again. This issue no longer occurs.
A temporary internet outage required a browser refresh and, in some cases, caused data loss
In the event that a user's internet connection drops temporarily, some operations may require a browser refresh. For example, when creating a Component, if the connection drops just as the user is about to open the Schema dropdown, an error is reported (correctly), but in Tridion Sites 9.6, Experience Space was unable to repopulate the dropdown, even after the connection was restored. In certain scenarios, similar behavior resulted in data loss. For example, you had a Component with a large number of fields, one of which was a mandatory Component link field. It this case, it was possible for the user to be unable to set the Component link field and would need to refresh their browser. All content in all other fields was then lost. This issue no longer occurs.
Other fixed issues
  • Experience Space now indicates when there are licensing errors.
  • The Insights panel now correctly show data for the parent of selected item.
  • The Items in progress list now loads correctly after a refresh.
  • Keyboard shortcuts for item actions now work properly.
  • Correct editing buttons are now displayed for components in workflow.
  • A linked multimedia schema defined on a folder is no longer ignored when creating multimedia components via upload.
  • Filtering of numeric values in a select control now works as expected.
  • Users can now open/edit components based on a schema that does not have a major version.
  • A possible text overflow issue when displaying search results is resolved.

Resolved in Tridion Sites 9.6

Browser Back button could not be used to go back to a previously selected node in trees
The Back button in your browser lets users navigate from one screen back to another screen, but going back to a previously selected node using the Back button was not possible. Similarly, users also could not use the Back button to go back to a previously visited tab in a tabbed screen or dialog. This issue no longer occurs.
Experience Space reporting a successful finish of a batch of items even if an item in the list was deleted in the meantime
In a scenario in which a number of items are selected to be finished, then one of those items is deleted by another user, and then the batch finish action is performed. Experience Space previously claimed that all items were finished when, in fact, the deleted item was not. This error no longer occurs.
If a user tried to link to a never-checked-in item, its title and text fields were not populated automatically
In a scenario in which a user is setting the value of a Component link field, and is selecting a Component that has not yet been checked in for the first time, the fields of that Component should be displayed. Previously, the fields failed to display, but now this issue no longer occurs.