Kuroco roadmap
Currently, we are focusing on improving the UI/UX of Kuroco's admin panel and developing external integrations.
Jul. Next releases
(Jul 23, 10:00 AM - 1:00 PM)
New Features
Content Management
JSON fields will now be available in content structure.
You will be able to approve multiple pending contents in bulk.
Bulk operations (publish, unpublish, delete, and update sort order) on the content list screen will be compatible with the approval workflow.
A new setting will be added to the approval workflow to prevent users from approving workflows they have submitted themselves.
Member Management
- The email address validation will be configurable to use RFC-compliant rules.
API
It will be possible to sort favoriteX_cnt using order_query.
The
open_flg
field in the Topics::update and Topics::bulk_upsert endpoints will support the value2
(same as the primary language).The Topics::waiting_for_approval_list endpoint will support filter queries.
The endpoint of API::request_api will be able to set path parameters.
Example:/rcms-api/1/external_api/{data_id}
Custom Function
The {sendmail} Smarty plugin will support the parameters to_member_id, cc, bcc, cc_member_id, and bcc_member_id.
- A trigger will be added for "At the time of Github deployment request"
Others
The preview site feature will be added.
You will be able to specify an unauthenticated email address in the Reply-To field only if SendGrid integration is enabled.
UI Changes
The input for identifiers (IDs) in custom trigger settings will become a selection format.
A link to the dashboard will be added to the simplified admin panel.
Content set to 'Higher-ranked display' will appear at the top of the content list in the admin panel.el.
The API list screen will now display the cache settings configured for each endpoint.
Specification Changes
Member Management
- The set of characters allowed in email addresses will be expanded.
- In the local part, the following characters will be allowed: percent (%), exclamation mark (!), hash (#), ampersand (&), asterisk (*), equals sign (=), question mark (?), caret (^), pipe (|), and tilde (~).
- The domain part will require a top-level domain consisting of at least two characters.
Oct. Later releases
The schedule for Later Releases will be announced when the details are finalized.
Support
If you have any other questions, please contact us or check out Our Slack Community.