Release 48
A representation of new additional features and improvements that have been released in Codex.
Gjirafa / Codex
New Features
1. Permissions for managing Labels on Entries
A new permissions section has been introduced to the team's permissions management, focusing on the addition and removal of specific labels on entries. This Labels permissions section allows for the creation of rules targeting specific fields, which can either permit or restrict team members from adding or removing labels on entries within certain models, sites, or specific labels themselves. This enhancement in label permissions is designed to streamline the workflow of users who handle various entries and labels, enabling them to more effectively work on their assigned content.
2. Ability to clone Assets when cloning an Entry
A new functionality has been introduced in the process of creating mappings for content models, specifically to facilitate asset cloning. When creating a mapping between a model and a target model, an additional option is now available that enables the cloning of assets along with the entry into the target model. Furthermore, users have the option to select a target folder where the cloned assets will be stored upon cloning the entry. This added functionality, available during the model mapping setup, simplifies the cloning process.
3. Improvement in handling References during Unpublishing
A new improvement has been implemented in the unpublishing process for entries. Now, when attempting to unpublish an entry, if it is referenced in Required Fields of published or scheduled entries, the "Unpublish" confirmation button will be disabled in the popup window. Users will need to manually navigate to these referencing entries and remove the dependency from the Required Fields before the "Unpublish" button becomes enabled. This enhancement is designed to safeguard against the removal of entries that are crucial references in published content, preventing potential errors on the frontend.
General Improvements
1. Display of System Fields in Entry Version History
A new improvement has been introduced to the preview feature of Entry Version History. Now, in addition to displaying the entry editor fields upon previewing an entry version, the system fields of the entry will also be shown. These system fields include the status of the entry version, labels added to the entry version, and, when applicable, the Published/Scheduled Date, Unpublished Date, and First Published Date. Additionally, it's important to note that any change in these system fields will result in the creation of a new version. This enhancement will assist users in more easily recognizing and locating a specific version based on the system fields, facilitating a quicker and more efficient preview process.
2. Improved Formatting control in Rich Text field
A recent update enhances the functionality of the Rich Text field, especially concerning the copying and pasting of formatted text. Now, when users copy text with formatting from external sources and paste it into a Rich Text field, the pasted text will adhere to the field's configuration as defined in the model. For instance, if the Bullet List option is disabled in the model for the Rich Text field, and the copied text includes a bullet list, then this portion of the text will be converted to plain text upon pasting into the Rich Text field of the entry. This update ensures consistency within the field and streamlines the process for users who are integrating external text into the Rich Text field.
3. Automatic removal of Expired Entries from the List
A new functionality has been introduced to the Entries Lists, specifically targeting expired entries. Users can now effortlessly remove expired entries from the List by simply clicking a dedicated button. This applies to entries that were previously active but have since expired due to reaching their specified expiration date. This enhancement streamlines the process, allowing users to efficiently clear expired entries from the List without the need to manually verify and remove them post-expiration.
4. Enhancement in filtering entries with Predefined Field values
A new enhancement has been introduced to the entry filtering mechanism, particularly for fields that contain predefined values in the model. Now, when users attempt to filter entries using Text or Number fields with predefined options, they can conveniently select from these predefined options to filter the entries. Only entries that match the selected value will appear in the search results. This improvement significantly streamlines the process, allowing users to filter entries based on predefined options effortlessly, without the need to manually input the value into the field.
5. Addition of a 2:3 Ratio Preset for Image cropping
A 2:3 ratio preset has been newly added to the ratio options in the Image Crop Tool within the Asset Management Hub. Users can now easily crop images using the 2:3 ratio by selecting this newly added custom ratio from the list of presets. This addition simplifies the process for users who frequently use this specific ratio for cropping images, eliminating the need to manually configure these dimensions under the fixed ratio settings.
6. Preventing the Deletion of Tags used in Entries
An enhancement has been made to the Tag Management page, which now prevents users from deleting tags that are currently in use within entries. To proceed with the deletion, users must first manually remove the tag from the Tag field in each entry where it is used. This update ensures a safer approach to deleting tags that may be required in published entries, potentially preventing errors on the frontend.
7. Added validations for Custom Fields in the Model
New validations for custom fields in the model have been introduced, specifically for the JSON type. Now, users can apply validations such as Required field, Read-only, and Limit number of properties when adding custom JSON fields to their model. These additional validations function similarly to those for Codex fields, enhancing the ability of users to validate these fields effectively.
Bug Fixes
Customization columns not being saved in Content Views - Fixed the issue where the customization columns changed and were not being saved in Content Views when sharing them with a new team.
Issue when comparing the Rich Content field of an entry - Fixed the issue where, when comparing two different entry versions, the Rich Content fields were not displayed properly, making it impossible to compare the content within them.
Users with permissions couldn't use the Photo Editing Tool - Fixed the issue where users, even though they had permissions to edit assets, couldn't click on the Photo Editing Tool on images at the entry level.
Prevented users could click on Boolean field in entries - Fixed the issue where users didn't have permissions to edit a Boolean field but still could change the value, specifically for the Boolean field of Toggle switch appearance.
Denying rule for editing content of a specific label - Fixed the issue where users were denied the ability to edit content on entries of a specific label, but this affected being prevented from editing all entries.