Kuroco roadmap

Currently, we are focusing on improving the UI/UX of Kuroco's admin panel and developing external integrations.

2025

Apr. Next releases
(Apr. 21st, 11:00 AM - 1:00 PM)

New Features

Content Management

• The content list and API support sorting by all default items.

API

• Multiple favorite_action_type can be specified in the Topics::list endpoint.
  favorite_cnt: Total count of all types
  favorite1_cnt: Count of favorite_action_type = 1
  favorite2_cnt: Count of favorite_action_type = 2
  ・
  ・
  The response will include the number of favorites for each specified action type.

• You will be able to select the type of security when adding an API structure.

• The order_query parameter will be added to the Member::list endpoint.

• Filter functionality will be added to the Topics::draft_list API.

• You will be able to specify index as a query parameter for the Topics::increment API.

• The image display control for private content has been improved, allowing images to be viewed even if they are private when ignore_open_flg is set.

• The following endpoints have been added:

  • Endpoint for updating saved drafts
    Topics::draft_update
  • Endpoints related to spiders (crawlers)
    Spider::insert
    Spider::update
    Spider::webhook
    SpiderHistory::details
    SpiderHistory::list
    SpiderHistory::logs

Custom Function

• The following trigger will be added:

  • After logging in using External SSO

• The trigger after adding content will now also be executed when "Copy including secondary languages" is selected.

External System Integration

• A new setting will be added to allow specifying a private URL (e.g., http://localhost:3000/) as the return URL for SAML SP.

EC Features

• Multiple settings for the same product will be possible in stock linkage.

UI Changes

• The input for identifiers (IDs) in custom trigger settings will become a selection format.

Specification Changes

API

• For multilingual content with repeated items where some items have primary language content but no secondary language content, the response behavior when using ext_group=true will change:
  • Before: Empty data for secondary languages would be added at the end of the repetition.
  • After: Secondary language data will be arranged in the same order as the primary language.

Custom Function

• The method of specifying the return value $data changes for the trigger "When copying content."
  • Before change: To modify the value of an extended item during copying, specify the value using data.ext.1.
  • After change: To modify the value of an extended item during copying, specify the value using data.ext_1.

Members

In previous releases, when an administrator without group update permissions added a new member, the initial registration group was not reflected. However, the expected behavior is that the "initial registration group is reflected" even if the administrator does not have group update permissions at the time of new addition. Therefore, this behavior has been restored.

• Before the September 2024 release: When a new member is added, the initial registration group is reflected even if the administrator does not have group update permissions.
• From the September 2024 release onward: When a new member is added, the initial registration group is not reflected, and the group settings remain empty if the administrator does not have group update permissions.
• From the April 2025 release onward: When a new member is added, the initial registration group is reflected even if the administrator does not have group update permissions.

Apr. Later releases

The schedule for Later Releases will be announced when the details are finalized.