Release 46
A representation of new additional features and improvements that have been released in Codex.
Gjirafa / Codex
New Features
1. Plugin Management via Interface
Codex now features an enhanced interface for managing plugins. Users can seamlessly install, activate, and delete plugins through the Codex interface. Additionally, plugin versioning will be displayed and users can activate any of the plugin versions based on the need. This functionality simplifies the plugin management process for developers, allowing them to efficiently manage plugins for various purposes within Codex. Please refer to the documentation here.
2. Enabling Conditions for Required or Read-Only Fields
New features have been incorporated in field validations, specifically related to Required field and Read-only validation. In addition to making a field required for an entry, users now have the option to add conditions. This empowers users to establish dependencies between fields, ensuring that a field becomes required only under a specified condition. Additionally, a new validation for Read-only fields has been introduced, which also allows users to set a condition under which a field becomes read-only. This feature streamlines the creation of dependencies and conditions between fields, providing users with greater control.
3. Safe Unpublish for Referenced Entries
A helpful feature has been implemented for entries that are referenced in other entries when being unpublished. Upon initiating the unpublish action, a pop-up message appears, informing the user about where the corresponding entry is currently referenced. Additionally, the pop-up provides information on whether the reference field is required. This feature facilitates users in viewing, opening, and managing referenced entries before completing the unpublish action and causing undesired impact in front-end applications.
4. Cloned References as a New Tab in Entries
The side panel of an entry now includes a new tab “Cloned References”. This section comprises two segments: "Cloned to" and "Cloned from". "Cloned to" represents the entry from which the current entry is cloned, while "Cloned from" showcases entries cloned from the current entry. This enhancement simplifies the identification and navigation of cloned entries associated with the current entry.
5. Label as a New Type of Webhook
In response to the improvements related to labels in entries and assets, a new type of webhook has been introduced. Users can now create a webhook of the label type to trigger events when labels are added or removed in entities such as assets and entries. Users can also add filters for the entry entity, specifying the site and model from which labels are changed in corresponding entries. This feature enhances the customization and control over webhook triggers related to label changes in Codex.
General Improvements
1. Publishing an Entry with Required Reference Field
A new improvement has been implemented in the Required Reference Field when publishing an entry. Users are now required to include at least one published entry in the Reference Field, which is validated as a required field. This enhancement prevents potential issues caused in front-end applications in case there is missing value in a required reference field, ensuring that there is a minimum of one entry in Published or Scheduled status.
2. Enhancements to Entry Search Functionality
Several general improvements have been made to the entries listing, particularly in the search and listing processes. In addition to listing entries with the highest scores at the top, the system now also considers the newest and most recently created entries. This refinement facilitates users in finding the most relevant entries, especially in cases with a large number of entries.
3. Specifying Applicable Labels for Entries
Users can now specify labels for assets in the Media Field validation within the model, in addition to specifying labels for entries. This means that assets with the specified labels can be viewed and added to the corresponding Media field in the entry based on label validation in the model. This improvement simplifies the process of adding assets that meet the specified label criteria to a Media field.
4. Specifying Labels for Assets in the Media Field
In addition to specifying applicable labels for entries, users can now specify labels for assets in the Media Field validation within the model. This allows assets with the specified labels to be added to the corresponding Media field in the entry based on label validation in the model. This improvement simplifies the process of adding assets that meet the specified label criteria to a Media field according to their requirements.
5. Possibility to Clone Entries Based on Model Configuration
A new option has been introduced to the customization tab of the model, allowing users to control the possibility of cloning entries created from the corresponding model. Users can now choose to hide the Clone button in the model’s configuration, effectively disabling the option to clone entries created from the model.
6. Bulk Editing of Assets to Add Labels
An enhancement has been introduced to the bulk editing of assets, enabling users to add labels in bulk to their metadata. This bulk editing capability overrides previously assigned labels for each specific asset, providing users with a quicker way to assign labels to multiple assets based on their specific requirements. Additionally, the labels of assets can be observed in the Asset Thumbnail View within the Asset Management Hub and Media Field/Block. This improvement streamlines asset identification based on labels, enhancing internal workflow management.
Bug Fixes
Display of Images in Media Field/Block - Resolved the issue where images in the Media field/block were not displayed properly and in their normal size.
Asset Permissions Specific Actions - Resolved the the issue where specific actions for asset permissions were not working properly, preventing users from editing the metadata of the assets.