Skip to content

Kaleta 3.24.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 07:22
· 220 commits to main since this release

The first step towards a website your whole team works in: shared enquiries, a responsible person for every page and item, and one screen with your own work. Update when convenient.

Working together

  • My work – one screen with your open enquiries, new ones nobody has taken yet, your pages and items that need a look (review date, unpublished changes, comments on the draft) and your requests Claude has answered. It is first in the menu for everyone except administrators.
  • Responsible person for pages and collection items (products, services, documents), with a Mine tab in Pages and in collection items. It means responsibility only – it does not limit who may edit.
  • Whoever gets an enquiry, a page or an item gets an e-mail with a link – never the enquiry itself, and never when you take it yourself. The dashboard shows Assigned to me.
  • Review reminders go to the responsible person, at most one e-mail a day.
  • When someone leaves, Users shows what they are responsible for and hands it all over in one step, also when you block or delete the account.

Faster site

  • The public page cache is no longer emptied by work that does not change the site – answering enquiries, notes, requests, mail and report settings. Visitors keep getting fast pages while the team works.
  • Reminders and mail retries now also run while people work in the administration, so they do not wait for visitors on sites without cron.

Builder

  • A new page starts in the builder: choose an empty builder page, a ready-made layout or a simple text page. The page title is no longer offered twice.
  • Pages, the builder and Waiting for you show who edited a draft and when.

For Claude

  • New tools my_work and assign; update_enquiry can set who handles an enquiry. The lists of pages, items and enquiries say who is responsible. The basic tool list is unchanged, so existing connections keep working as before.

One database change (a responsible person on pages and items), applied by the update. No setting, MCP tool or parameter renamed. Audited before release.

Full Changelog: v3.23.1...v3.24.0