NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #4129 most downloaded on Packagist
The Kirby core
Latest stable
5.6.3
Last release 17 days ago
05 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
297 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Kirby\Toolkit\V::maxLength() and Kirby\Toolkit\V::minLength() no longer trigger a PHP deprecation for null values.
[!NOTE] You can find the full changelog and docs for Kirby 6 over here: https://getkirby.com/releases/6
$users->findByEmail() method to find a user only by email address #8757Kirby\Toolkit\A::keyBy() always plucks string keys, even if they are also names of PHP functions (e.g. key, count or date) #8715Kirby\Data\Txt::encode() no longer rounds integers with more than 14 digitsKirby\Cms\Page::isMovableTo() returned false)Kirby\Toolkit\V::date() with a null operator now checks the date on its own.Kirby\Toolkit\V::input() keeps % in validation messages.Kirby\Toolkit\V::maxLength() and Kirby\Toolkit\V::minLength() no longer trigger a PHP deprecation for null values.Kirby\Toolkit\A::fill() and Kirby\Toolkit\A::keyBy() no longer call strings as callables, use a closure instead #8715false in a structure field's columns now hides the column instead of showing it with default settings. A string in a field's columns sets the column label, e.g. title: Headline.api, assets, media, panel) are also blocked when Kirby is installed in a subfolder #8746$options argument from new Kirby\Text\KirbyTag(), Kirby\Text\KirbyTag::parse() and Kirby\Text\KirbyTags::parse(). Pass debug: true to Kirby\Text\KirbyTags::parse() instead. $debug is now its third argument.Kirby\Cms\Permissions::for() requires a $category string, does not allow null.Kirby\Cache\Cache::enabled() is abstract. Custom cache drivers that extend Kirby\Cache\Cache directly must implement enabled(): bool. #8734Kirby\Toolkit\Component #8735Kirby\Cms\Responder::json() now has the native return type static instead of static|string.Kirby\Form\Validations::boolean(), ::date(), ::email(), ::max(), ::maxlength(), ::min(), ::minlength(), ::option(), ::options(), ::pattern(), ::required(), ::time() and ::url() now return void instead of true. They still throw an InvalidArgumentException when validation fails.Kirby\Panel\File::dropdownOption(), use Kirby\Panel\Ui\Item\FileItem insteadKirby\Panel\Page::dropdownOption(), use Kirby\Panel\Ui\Item\PageItem insteadKirby\Panel\User::dropdownOption(), use Kirby\Panel\Ui\Item\UserItem insteadKirby\Panel\Site::dropdownOption() and Kirby\Panel\Model::dropdownOption(), use the Kirby\Panel\Ui\Item\ModelItem classes insteadKirby\Cms\Responder::markVolatileHeader(), use $responder->volatileHeaders()->mark($name, $values) instead.Kirby\Text\KirbyTag::option() and Kirby\Text\KirbyTag::$options, use $tag->kirby()->option() instead.Kirby\Email\Body::clone() and Kirby\Email\Email::clone()<k-writer> alias. Use <k-writer-input> instead.restoreSelectionCallback() from <k-textarea-input>. Use restoreSelection() instead.<k-writer-input>: createMarksFromPanelPlugins(), createNodesFromPanelPlugins() and filterExtensions(). Use $helper.writer.availableMarksFromPlugins(), $helper.writer.availableNodesFromPlugins() and $helper.writer.filterExtensions() instead.-container-field-input-padding, -field-input-height, -field-input-line-height, -field-input-font-size: use -input-padding, -input-height, -input-leading, -input-font-size instead-bg-pattern: use -pattern instead-theme, -theme-light, -theme-bg: use -theme-color-700 and -theme-color-500 instead::pickerData() in Kirby\Panel\Model, Kirby\Panel\File, Kirby\Panel\Page and Kirby\Panel\User have been deprecated, use ::item() of Kirby\Panel\Controller\Dialog\ModelPickerDialogController, Kirby\Panel\Controller\Dialog\FilePickerDialogController, Kirby\Panel\Controller\Dialog\PagePickerDialogControlleror Kirby\Panel\Controller\Dialog\UserPickerDialogController insteadplaceholder and icon options work again #8736after and before options work againresettable option is called reset again, as in Kirby 5pagelist and filelist fields now show the field's form value when the column key differs in case from the field name. #8710preview: fields now work as expected instead of copying the whole block or opening the block pasteboard dialog. #8743Your coding agent can read these notes before it upgrades. Set up the MCP server →
Removed code that has been deprecated since Kirby 5 and earlier
[!NOTE] You can find the full changelog and docs for Kirby 6 over here: https://getkirby.com/releases/6
Beta 2 includes all patches from 5.6.2
k-writer-input loads ProseMirror on demand (6.0.0-beta.1), it is registered as an async component. Plugins using extends: "k-writer-input" got the async wrapper instead of the actual component. Plugin components that extend a lazy-loaded component now become lazy themselves. They get resolved once the parent has loaded, so extends: "k-writer-input" works again without workarounds. panel.plugins.components still holds the plain options object, so kirbyup's HMR keeps working. #8657FormDialog/FormDrawer sent an empty value as []. But PHP encodes an empty array as a JSON array. So the actual input in Vue ended up as a named property on an array, and JSON.stringify drops that. ::props() methods now cast value to an object, so props()['value'] is a stdClass on the PHP side. #8652k-input and k-collapsible no longer call listeners like @keydown twice. #8671Kirby\Cms\LazyCollection::data() loads all elements before returning them, e.g. $kirby->users()->data() no longer returns an empty array. #8635panel.request() has a new external option to send plain requests to third-party URLs. #8658k-tag supports color themes (positive, negative, notice, warning, info) as tinted tags #8662GET and POST requests by default. #8659Kirby\Panel\Ui\Item\MissingItem class #8663panel.act() method to act on the message, event, redirect and reload keys of a response. #8660reload: false. #8660fetch() have to send the CSRF token in the X-CSRF header (panel.system.csrf). panel.get(), panel.post() and panel.request() already send it. #8659Kirby\Toolkit\Iterator::key(), Kirby\Toolkit\Iterator::current(), Kirby\Toolkit\Iterator::prev(), Kirby\Toolkit\Iterator::next(), Kirby\Toolkit\Iterator::rewind() and Kirby\Toolkit\Iterator::valid(). Loop over collections with foreach or use Kirby\Toolkit\Collection::first(), Kirby\Toolkit\Collection::last() or Kirby\Toolkit\Collection::nth() instead. Remaining calls like $collection->current() don't throw an error: CMS collections (e.g. Kirby\Cms\Pages) return null, Kirby\Toolkit\Collection returns the element with the key current (or null).Kirby\Cms\LazyCollection::current(), Kirby\Cms\LazyCollection::next() and Kirby\Cms\LazyCollection::prev().Kirby\Cms\LazyCollection (e.g. Kirby\Cms\Users) no longer loads all elements before calling a custom collection method. Inside custom methods, the $this->data property can be empty or contain null values. Use $this->data(), foreach or other collection methods, or call $this->hydrate() first.Kirby\Filesystem\Dir::index() no longer accepts null for the $ignore argument. Pass an array of absolute paths, or false to disable the Kirby\Filesystem\Dir::$ignore list.Kirby\Http\Router::find() no longer accepts null for the $ignore argument. Pass an empty array instead.panel.dialog.successEvents(), panel.dialog.successNotification() and panel.dialog.successRedirect() have been removed, as have the same methods on panel.drawer. Use panel.act() instead. #8660Kirby 6.0.0-beta.1 is an early developer preview. We plan for a final release before the end of 2026. Kirby 6 will be a free upgrade for all Kirby 4 &
Kirby 6.0.0-beta.1 is an early developer preview. We plan for a final release before the end of 2026. Kirby 6 will be a free upgrade for all Kirby 4 & 5 license holders.
[!IMPORTANT]
Don't use Kirby 6 in production yet
You can find all new features, changes and documentation for Kirby 6 here: http://getkirby.com/releases/6
All our security fixes and improvements from our Kirby 5 security releases
Kirby 6.0.0-alpha.3 is an early developer preview. We plan for a final release in the second half of 2026. Kirby 6 will be a free upgrade for all Kirby 4 & 5 license holders.
[!IMPORTANT]
Don't use Kirby 6 in production yet
All our security fixes and improvements from our Kirby 5 security releases
A single place on the user/account view to handle security-related matters, e.g. email, password, two-factor (TOTP) management <img width="948" height="1120" alt="image" src="https://github.com/user-attachments/assets/c0946593-68c6-49c8-8b9e-9d39bbd9768e" />
The login view has been refactored from the ground up to be more driven by the backend. It now features a method picker, a challenge switcher, and centralized loading/error handling. Auth methods can now also authenticate without an email, enabling token/SSO-style plugin methods that don't key on email and plugins can ship their own login method, just like custom challenges. Passkey is coming …
The new auth.passwords option allows you to define a custom password policy for all users.
// site/config/config.php
return [
'auth' => [
'passwords' => [
'minlength' => 12,
'uppercase' => true,
'lowercase' => true,
'digits' => 2,
'symbols' => true
]
]
];
We are collecting all changes in our pre-release changelog, if you already want to dive deeper: https://github.com/getkirby/kirby/blob/6.0.0-alpha.3/CHANGELOG.md
Kirby 6.0.0-alpha.2 is an early developer preview. We plan for a final release in the second half of 2026. Kirby 6 will be a free upgrade for all Kirb
Kirby 6.0.0-alpha.2 is an early developer preview. We plan for a final release in the second half of 2026. Kirby 6 will be a free upgrade for all Kirby 4 & 5 license holders.
[!IMPORTANT]
Don't use Kirby 6 in production yet
✍️ Live editor 📄 Simplified blueprint definition 🥞 New template stacks 🔘 New buttons field
We are collecting all changes in our pre-release changelog, if you already want to dive deeper: https://github.com/getkirby/kirby/blob/6.0.0-alpha.2/CHANGELOG.md
…longer get security updates. There are so far no vulnerabilities that affect you directly. But this could change any time. To keep Kirby secure in the…
Kirby 6.0.0-alpha.1 is a very early developer preview with Vue 3 support, backend refactoring but no new features at this point. If you are not working on third-party plugins or your own custom Panel extensions, you can happily skip this release for now. Pre-releases with features and enhancements will follow in early 2026.
[!IMPORTANT]
Don't use Kirby 6 in production yet
We plan for a final release in the second half of 2026.
Kirby 5 is our latest and greatest release and will be relevant for many more months. We will be releasing new updates and features and there’s absolutely no reason to already think about Kirby 6 at this point if you are not a plugin developer.
According to our license model that we started with Kirby 4, Kirby 6 will be a free upgrade for anyone who bought or will buy a Kirby Basic or Kirby Enterprise license, no matter if you were one of the first with Kirby 4 or if your project just started. You can recognize this if your license key starts with K-BAS or K-ENT. You can buy a Kirby license today and upgrade for free to Kirby 6 at any point later in 2026.
Vue 2 has reached its End of Life in December 2024, which means that it does no longer get security updates. There are so far no vulnerabilities that affect you directly. But this could change any time. To keep Kirby secure in the future, we have to take this step and upgrade to Vue 3. The End Of Life for Vue 2 also means that the Vue ecosystem has shifted to Vue 3 support and it’s getting harder and harder to get good third party libraries and components that still support Vue 2. This is not a good state for the future of Kirby’s ecosystem.
With the upgrade to Vue 3, all third-party plugins for the Panel also need to be upgraded to Vue 3. This is a huge step and we have to prepare it carefully, to provide a good path for Kirby’s ecosystem. We also had our own challenges to migrate to Vue 3 without breaking too much of our own components and APIs. But we feel ready now to take this step to create a solid foundation.
There is no need to worry about security for sites with Kirby 4 and Kirby 5. You can omit the vulnerable parts of Vue 2 by disabling the Vue template compiler.
The easiest way is to install a fresh starterkit and replace the kirby folder with the one from this release (see ZIP download below) The starterkit should already be fully compatible. The alpha label should make it clear enough, but here's a word of warning again. Don't use this release in production and always make backups of your projects and especially the content. We don't take any responsibility for issues that lead to content-loss or other nasty side-effects.
If you are maintaining Kirby plugins that extend the Panel, you need to upgrade them with the latest alpha version of kirbyup. You will have plenty of time to prepare this until the final release of Kirby 6. But the earlier you discover potential problems, the sooner we can work together on fixing them.
Here are the steps to take to migrate your plugin to Vue 3:
npm run buildIf you are writing custom Panel plugins for your clients, you can already try to upgrade one of your plugins and see if you get it up and running with alpha 1. Follow the instructions for plugin developers above in such a case. Otherwise, this first alpha will probably not be very exciting for you yet and you might want to wait some more until we have more features to show or the first plugins are ready to be tested.
Nothing at this point. This really is a developer preview. We will have more exciting Kirby 5 and 6 updates for you in the following months.
We are collecting all changes in our pre-release changelog, if you already want to dive deeper: https://github.com/getkirby/kirby/blob/6.0.0-alpha.1/CHANGELOG.md
…Kirby\Toolkit\Str::studly() no longer trigger deprecation warnings for null #8713
Kirby\Toolkit\Html::email(), ::figure(), ::link() and ::tel() no longer drop '0' as link text or captionKirby\Toolkit\Html::vimeo() and ::youtube() accept URLs with uppercase hosts (e.g. https://Vimeo.com/…, https://YOUTU.BE/…)Kirby\Toolkit\Html::a() handles uppercase MAILTO: and TEL: links like their lowercase versionsKirby\Toolkit\Html::rel() adds noreferrer for uppercase _BLANK targetswhen condition no longer block saving #8724Kirby\Http\Request::headers() now strips only the leading HTTP_ or REDIRECT_HTTP_ prefix, not from the middle of the name.Kirby\Toolkit\Str::accepted() skips items without a value (e.g. Accept: ;) #8713Kirby\Toolkit\Str::camel(), Kirby\Toolkit\Str::camelToKebab(), Kirby\Toolkit\Str::snake() and Kirby\Toolkit\Str::studly() no longer trigger deprecation warnings for null #8713Kirby\Toolkit\A::sort() no longer triggers a warning for rows without the sort field #8713$page->next() and $page->nextAll() (and the same methods of files and users) return null or an empty collection for items that aren't in the given collection.$page->isFirst() and $page->isLast() (and the same methods of files and users) return false for an empty collection instead of throwing an error.Kirby\Image\Location without GPS coordinates to a string returns '' instead of ' '.$model->increment() respects a $max of 0.Kirby\Cms\Blocks::factory() no longer throws a TypeError when called without items.Kirby\Api\Api instances keep their authentication callback, so field and section API sub-requests are authenticated again.Pdo\Sqlite), so driver-specific methods work without PHP 8.5 deprecations. #8669
panel.uploads option sets how many files the Panel uploads at the same time (default: 3)// site/config/config.php
return [
'panel' => [
'uploads' => 5
]
];
Kirby\Image\Svg class to read information from SVG markup #8546imagickdriver are smaller$helper.number.format(value, options) formats numbers in the Panel's interface language. #8674sortBy) is 5–30× faster for large lists. #8675Kirby\Filesystem\Dir::remove() no longer fails when a parallel request removes the directory at the same time #8606<html lang> attribute is a valid language tag (e.g. pt-BR instead of pt_BR). #8674null no longer falls back to the global query function of the same name #8575AND/OR (e.g. page.title == "ORANGE") #8573true, false or null (e.g. page.nullable) #8573width/height attributes render in the Panel file preview #8014viewBox ratio, the viewBox offset no longer reduces the size, decimals are rounded instead of cut off, and comma-separated viewBox values are supported #8546imagick thumb driver resizes and crops all frames of animated GIFs, not just oneimagick or im driver creates a thumb of the first frame, instead of publishing the original GIF and leaving extra files in the media folderim driver keeps all frames intactimagick or im driver creates a small still thumb of the first frame instead of a large file with one image per frameimagick and im thumb drivers create intact thumbs of animated WebPs instead of glitchy frames, and imagick no longer fails to convert them to GIFimagick driver use the brightness of each color instead of its red channel2.5 GB instead of 2.7BB). #8674Kirby\Database\Database::connect() uses PDO::connect() on PHP 8.4+. Kirby\Database\Database::connection() now returns the driver subclass (e.g. Pdo\Sqlite), so driver-specific methods work without PHP 8.5 deprecations. #8669Kirby\Database\Query::count() counts the groups of grouped queries and the distinct rows of distinct()queries with a select list. This also fixes the total Kirby\Database\Query::page(). #8670link field preview inside a table (e.g. a structure field) no longer also opens the row. #8672<select> elements use correct colors for dark Panel theme #8567& #8553Kirby\Http\Uri::idn() and Kirby\Http\Uri::unIdn() no longer drop the host when the IDN conversion fails. #8678Kirby\Http\Idn::decodeEmail() and Kirby\Http\Idn::encodeEmail() keep the address as is when the domain cannot be converted and no longer throw for an empty domain #8678Kirby\Http\Idn::decodeEmail() and Kirby\Http\Idn::encodeEmail() split at the last @, so quoted local parts like "a@b"@example.com are converted correctly #8678Kirby\Toolkit\V::email() validates the value type explicitly instead of catching all errors #8678Cropping thumbnails uses less memory #8497
create blueprint option #8527_globals, _json, _only, _pretty) no longer show up in the Panel URL #85080 #85180 no longer fall back to another language #8523image.ratio option (e.g. in pages/files section) now works with Kirby queries https://forum.getkirby.com/t/custom-cropratio-and-cover-true-for-the-image-settings-in-a-section-generates-an-error/35615/4create: blueprint option no longer converts uploaded files to the global thumbs.format #8489> [!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https:/…
[!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https://getkirby.com/buzz/security-update
Dom::sanitize() - CVSS Score 7.4files, pages and users fields resolve their stored value - CVSS Score 7.1root and dirname parameters - CVSS Score 7.1Thanks to the following reporters for responsibly reporting the identified issues
root and dirname on page creation@import string form in Dom::extractUrls()k-link no longer accept dangerous URL schemes (javascript: etc.).languages.update permission could inject HTML markup into other users' Panels. To override a core string, use the translations extension in your config as before.– and keep their stored value.(date:) KirbyTag keeps cached pages up to date and supports a new optional expiry attribute #7746(date: year) // cache resets at the start of next year
(date: Y-m-d) // no expiry unless set
(date: Y-m-d expiry: tomorrow) // cache resets at midnight
X-Robots-Tag: noindex, nofollowheader and the Panel document includes a matching robots meta tag. #8446Kirby\Template\Template::sanitizeName() methodUrl::normalize() method that brings a URL into the same form a browser parses.<a> tags anymore #5481k-textarea-input: (pre)-selecting works again$helper.string.unescapeHTML() does not unescape entities twice anymore #8345object or toggle #8355Page::create(), File::create() and User::create() use the fields' save handlers again, just like ::update()does. This restores the v4 behavior. Values a field can't handle are normalized or dropped. #8440Page::create(), File::create() and User::create() are checked before the given content is processed, so unauthorized requests are rejected upfront. #8440Sql::joins() returns the bindings collected from its joins instead of discarding them. #8460Sql::insert() no longer fails with a TypeError when called without explicit bindings. #8461Database::connect() throws a clear InvalidArgumentException for incomplete connection options instead of a TypeError. #8463Database::connect() no longer leaves the object with a partially updated configuration; the previous connection stays intact. #8463Sql::unquoteIdentifier() no longer unwraps identifiers whose opening and closing quotes don't match, and no longer mangles the other quote character inside a quoted identifier. #8462$page->changeTemplate() and $file->changeTemplate() no longer delete the existing content before the converted content has been written. If writing fails, the old content stays intact. #8473+ as %2B #8485Kirby\Toolkit\Html::youtube() domains. (thx to @bnomei and Danish Tariq of Laburity for their suggestion and responsible disclosure).kirby.resetPassword session flag now gets cleared on logouta.jpg to b with new extension png no longer overlooks an existing b.png.Kirby\Cms\Inventory class used for page, site and user content dir inventories #8137Uuid classes carry generic type templates, so PageUuid::model(), FileUuid::model() etc. are statically typed as the specific model #8368Database::connect() now takes array $params = [] instead of array|null $params = null, matching the constructor. Passing null was never supported. #8463Kirby\Filesystem\Dir::inventory is deprecated. Use Kirby\Cms\Inventory::for instead. #8137$model->createDefaultContent() has been deprecated, use $model->createContent() instead. #8440Kirby\Sane\Html::options() & Kirby\Sane\Svg::options() are now publicThe Panel is no longer blocked by a deprecation warning when a user blueprint sets an undefined permission #8319
slugs config option in the Panel #8300filename is provided to File::create() #8316> [!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https:/…
[!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https://getkirby.com/buzz/security-update
This vulnerability affects all Kirby sites that are deployed to a server that allows to request URLs with encoded slashes (%2f) such as nginx, the built-in PHP server or Apache setups that have the option AllowEncodedSlashes enabled.
It was possible to create and access thumbnails from media files in arbitrary accessible directories on the server that have a valid thumbnail configuration (JSON job file). It was also possible to detect the presence of files with the .json file extension anywhere on the server.
This vulnerability is of high severity for affected sites.
Server setups running on Apache's default configuration or other servers that have been hardened against encoded slashes in URLs are not affected.
Thanks to Jorge González Milla (@Pig-Tail) for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites where users of a particular role have access to the REST API (access.panel permission is enabled) but no permission to upload any kind of file (files.create, files.replace and user/users.update permissions are all disabled).
It was possible to fill up the temporary directory for chunked uploads with unfinished chunks even as a user without any upload permission.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if you intend all users of your site to be able to upload files. The vulnerability can only be exploited by authenticated users. It was not possible to bypass the actual permission checks for any files that end up in the content or site/accounts folders.
Thanks to @alcls01111 for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites that have not disabled the REST API with the 'api' => false option.
It was possible to trigger a PHP error in the API backend that would expose the full filesystem path of the Kirby installation on the server. This could be used to guess the default content.salt or prepare specialized attacks.
Thanks to Peter Levashov (@petersevera) for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites that are deployed in a way that their index root on the server is next to a second directory that is read-accessible to PHP and shares the same name prefix (such as the site with the index root /var/www/site being next to /var/www/site2).
It was possible to create and access thumbnails from media files within such sibling directories that have a valid thumbnail configuration (JSON job file). This can affect staging sites, site backups or other internal sites.
Thanks to @0x1saac for responsibly reporting the identified issue.
Kirby\Filesystem\Dir::realpath()/Kirby\Filesystem\F::realpath(): Fixed path traversal via prefix match. Now requires an exact match or a DIRECTORY_SEPARATOR boundary.Kirby\Cms\Media::thumb(): Rejects path traversals via filenamesAsset class and asset() helper no longer accept paths with ../ sequences to protect against path traversalsite/cache/.uploads.maxsize consistently across all chunks and reject requests that change the file template or total upload length between chunks.site.preview permission as well as pages.preview permission/option for the home pageModelPermissions::canFromCache() handling of $default argument, incl. proper caching of itsite.preview. The check for the home page pages.preview permission has been deprecated and will be removed in the next major release. Please use the site.preview permission.Added deprecation id for permission deprecate warnings #8253
A (link:) tag with an unresolvable UUID (e.g. deleted page/file) threw an NotFoundException in the previous release, which turned the whole page into the error page. Instead of that drastic exception (added in #6085), we now handle the broken link inline: in debug mode a visible inline error (prefixed with an emoji and a kirby-broken-link class so it can be targeted via CSS, and in production the link is simply dropped (keeping its text). #7426
(link: page://deleted-page)
→ <span class="kirby-broken-link">🚨 The link "page://deleted-page" cannot be found</span>
(link: page://deleted-page text: click here)
→ <span class="kirby-broken-link">🚨 The link "page://deleted-page" cannot be found for the link text "click here"</span>
(link: file://deleted-file text: file) → <span>file</span>
(link: page://deleted-page) → (nothing)
type: html Panel field preview rendering #8242(link:) tag no longer turns the whole page into the error page #8257…Block error message. While this is technically a breaking change, we see this as a debugging enhancement which can clearly go into a minor release wit…
A Kirby site can now be activated as development site when you confirm to comply with the license terms for free development licenses. When the site is not set up locally, Kirby will regularly check that your development site is not publicly accessible. #7832
<img width="536" height="624" alt="Screenshot 2026-07-01 at 16 02 33" src="https://github.com/user-attachments/assets/8304e8f3-e72a-44b7-a22c-cc27a8528c9d" />
New Frontmatter Data handler, which can be used to import or export frontmatter into Kirby. #8019
Decoding
use Kirby\Data\Frontmatter;
$md = <<<MD
---
title: My new article
date: '2026-03-12'
---
# Hello world
This is my brand new article written in **Frontmatter/Markdown**
MD;
$result = Frontmatter::decode($md);
// [
// 'title' => 'My new article',
// 'date' => '2026-03-12',
// 'text' => '# Hello world ...'
// ]
Encoding
use Kirby\Data\Frontmatter;
$result = Frontmatter::encode([
'title' => 'My new article',
'date' => '2026-03-12',
'text' => '# Hello world …'
]);
// ---
// title: My new article
// date: 2026-03-12
// ---
// # Hello world …
Kirby\Content\Version::unlock() methodpanel.content.unlock() method/api/(:all)/changes/unlock routethis.$helper.string.sanitizeHTML() in the Panel to create a clean HTML string with configurable marks and nodes. By default, the sanitizer will only keep inline marks (bold, code, italic, link, strike, sub, sup, underline) #7922this.$helper.string.sanitizeHTML('<p><marquee><strong onclick="alert(\'boo\')">Foo</strong></marquee></p>')
// returns: <strong>Foo</strong>
To set custom writer marks and nodes, you can pass an options object:this.$helper.string.sanitizeHTML(unsanitizedHTML, {
marks: ["bold"],
nodes: ["doc", "praagraph", "text")]
});
// /site/config/config.php
return [
'extensions' => [
'pageModels' => [
// ...
],
'blueprints' => [
// ...
]
]
];
Kirby\Filesystem\F::$types and Kirby\Filesystem\Mime::$types. #8134Kirby\Toolkit\A::flip() method #8132Kirby\Filesystem\F::update($file, $callback) method that reads and updates a file under lock #8187Kirby\Cms\Block::toHtml() by logging suppressed errors and escalating exceptions in debug mode #8085.Kirby\Filesystem\Dir::size() #8131Kirby\Filesystem\Mime::fromSvg() #8130Kirby\Filesystem\Mime::toExtension() and Kirby\Filesystem\Mime::toExtensions() #8133Kirby\Toolkit\Controller #8143Kirby\Toolkit\Html::attr() and Kirby|Toolkit\Xml::encode() #8144Kirby\Toolkit\Str::similarity(), Kirby\Toolkit\Str::startsWith(), Kirby\Toolkit\Str::endsWith(), Kirby\Toolkit\Str::encode(), Kirby\Toolkit\Str::ascii() #8138 #8147 #8145 #8158Kirby\Toolkit\A::without() #8146minWords/maxWords validators for non-single whitespace #8141Dir::remove() with atomic rename #6266panel.request.body(null) does not send "null" to the backend as the request body anymore #8016"false" to the backend anymore but instead omitted from the request. #8016Kirby\Toolkit\DateKirby\Toolkit\LayzValue: fixed passing variadic arguments #8139Kirby\Toolkit\A::implode(): preserve falsy values when imploding array #8140Kirby\Toolkit|Str::toBytes() #8159cookie.key optionI18n::template(): Prevent TypeError when $replace is null #8199[object Object] instead of the formatted link/email text. #7934max limit is reached #8232permissions extension has been deprecated. Those will be ignored in a future release, so make sure to define your custom permissions via the permissions extension. #8070Kirby\Text\KirbyTag::option() and Kirby\Text\KirbyTag::$options: Use $tag->kirby()->option() instead. #8196Kirby\Text\KirbyTags::parse(): $options parameter. Use new $debug parameter instead. #8196Kirby\Cms\LicenseStatus::Acknowledged and Kirby\Cms\LicenseType::Free cases #7832$helper.string.hasEmoji(): simplified regular expression #7966$helper.array #7977, $helper.regex #7976$helper.debounce/throttle #7980, $helper.isComponent #7982, $helper.embed #7983, $helper.keyboard #7984, $helper.isUploadEvent #7985, $helper.queue #7981, $helper.file #7990, $helper.field #7989, $helper.string #7979, $helper.link #7994, $helper.focus #7991, $helper.url #7992, $helper.page #7995, $library.colors #7997, $helper.clipboard #7988, $helper.upload #7996, dayjs plugins #8009, $helper.sort #7993History and Timer as helper class to TypeScript #8010 #8011this.$library, this.$helper and this.$esc are exposed in Vue SFC #8017RedirectError error class with support in panel.error() #8016Permissions::$actions property to $defaults; added separate protected array $actions populated by the constructorPermissions::setAll, Permissions::setCategory, Permissions::setCategories, Permissions::setAction, Permissions::hasAction, Permissions::hasCategory) with 4 cleaner ones: Permissions::normalize(), Permissions::expand(), Permissions::get(), Permissions::has()Permissions::normalize() and Permissions::expand() handle all four input shapes: null, bool, ['cat' => bool], ['cat' => ['action' => bool]], including wildcard at both levels.Permissions::for() now deprecates $category = null via Helpers::deprecated() and throws LogicException if a stored value is somehow not a boolarray_fill_keys(array_keys($defaults), false) instead of array_map(fn () => false, $defaults).<div> tags with <span> tags in <k-input> #8018Kirby\Template\Snippet::hasSlots() method #8178$debug parameter in Kirby\Text\KirbyTags::parse() #8196Html::rel() use #8142Kirby\Cms\Block::toHtml() now throws block snippet exceptions in debug mode instead of returning an inline Block error message. While this is technically a breaking change, we see this as a debugging enhancement which can clearly go into a minor release without negative impact for real-world projects.cpx for pinned composer dependencies shared between local dev and CIjsdom with happy-dom for frontend unit tests #7971> [!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https:/…
[!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https://getkirby.com/buzz/security-update
Kirby internally relies on the following values:
content.salt option is used to generate secure preview and media URLs that should not be guessable by external visitors.Kirby\Http\Cookie::$key property, to sign (or authenticate) cookie values to prevent easy tampering with cookie values that have been set from the backend.We recommend to set the content.salt and Kirby\Http\Cookie::$key values to long random strings for all of your sites.
We have updated the security guide with a section on this topic and added warnings to the Panel system view if Kirby detects the unchanged defaults.
Thanks to @adrgs and Peter Levashov (@petersevera) for their responsible disclosure and suggestion.
Forwarded, X-Client-IP or X-Real-IP headerThis vulnerability affects Kirby sites that have no configured user accounts and are running on publicly accessible servers behind a reverse proxy that sets the Forwarded: for=..., X-Client-IP, or X-Real-IP request header.
It was possible to install the Panel (= create the first admin user) in these setups even from remote IP addresses.
This vulnerability is of critical severity for affected sites.
Your site is not affected if any of the following apply:
X-Forwarded-For or Client-IP header instead of the affected ones.Advisory Details:
Thanks to Peter Levashov (@petersevera) for responsibly reporting the identified issue.
Dom::sanitize()This vulnerability affects Kirby sites and plugins that use the writer or list fields or that use $dom->sanitize(), Sane::sanitize(), Sane\Html::sanitize(), Sane\Svg::sanitize(), Sane\Xml::sanitize(), Sane::sanitizeFile() or $file->sanitizeContents() with untrusted input.
It was possible to inject malicious markup as children of an unknown HTML/XML tag, which would then be passed through Dom::sanitize() without being correctly sanitized according to the provided sanitization rules, causing a cross-site scripting (XSS) risk.
This vulnerability is of high severity for affected sites.
The default file upload protection is not affected, so sites that only validate uploaded files are not exposed to this vulnerability. The vulnerability can only be exploited by authenticated users.
Thanks to Shafiq Aiman (@shafiqaimanx) for responsibly reporting the identified issue.
This vulnerability affects Kirby sites that use the writer field in any blueprint.
It was possible to include a scripting link as the target of a link (or email link). This link target would then be clickable by the user who entered it.
A successful attack commonly requires knowledge of the content structure by the attacker as well as social engineering of a user with access to the Panel. The attack cannot be automated.
In Kirby's default configuration, the vulnerability is limited to self-XSS and cannot directly affect other users or visitors of the site. Panel plugins that are directly using the <k-writer> component may also be affected by stored XSS if they don't sanitize the resulting HTML before saving it to the content.
This vulnerability is of high severity for affected sites.
pages.access permission is not checked in the site/find REST API routeThis vulnerability affects all Kirby sites where users of a particular role have no permission to access pages (pages.access permission is disabled). This can be due to configuration in the user blueprint(s), options in the model blueprint(s), or a combination of both settings.
It was possible to retrieve page information (including full content and metadata) for arbitrary pages via the /api/site/find route without being authorized to access the respective pages.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if you intend all users of your site to be able to access all pages of the site. The vulnerability can only be exploited by authenticated users that know or guess the IDs or UUIDs of pages. Write actions as well as access to draft pages are not affected by this vulnerability.
Thanks to Rizky Muhammad (@EvidentObscurity) for responsibly reporting the identified issue.
Http\RemoteThis vulnerability affects Kirby sites and plugins that use the Kirby\Http\Remote class (including Remote::request(), Remote::get(), Remote::post(), and similar helpers) to send outgoing HTTP requests and that pass untrusted, user-controlled data into the headers option of such a request.
By including newline characters in the value of the header, it was possible to inject a separate, independent header that was not intended to be set.
A successful attack requires that an application or plugin forwards attacker-influenced input into a request header value. Sites that only send static, developer-defined headers are not affected. The attack does not target Panel users or site visitors directly; it targets the remote service that Kirby connects to.
In Kirby's default configuration, the Remote class is not exposed to untrusted input, so a default installation is not affected. The vulnerability becomes relevant for custom code, plugins, or integrations that build request headers from user input.
This vulnerability affects Kirby 5 sites that have the content.fileRedirects option enabled (set to true or a custom closure) as well as all Kirby 4 sites that haven't explicitly disabled this option.
It was possible to access clean file URLs of top-level drafts (e.g. /about-us/team.jpg) without providing authentication, without being authorized to access the top-level draft page, and without providing a valid preview token.
Sites on Kirby 5 using the default configuration are not affected by this vulnerability (the content.fileRedirects option is disabled by default since Kirby 5.0.0). It was also not possible to maliciously access clean file URLs for files stored in page drafts that are not on the top-level (such as /blog/article/resource.pdf).
Thanks to @adamyordan for responsibly reporting the identified issue.
pages.access permission is not checked in the pages picker for parent pagesThis vulnerability affects all Kirby sites that use the pages field and where users of a particular role have no permission to access pages (pages.access permission is disabled). This can be due to configuration in the user blueprint(s), options in the model blueprint(s), or a combination of both settings.
It was possible to confirm the existence of arbitrary pages and to retrieve the value of the title field of the pages found.
The vulnerability can only be exploited by authenticated users. Write actions are not affected by this vulnerability.
link and email marks of the writer field are now protected against self-cross site scripting (self-XSS) from inserted scripting linkspages field now consistently checks the pages.access permission for the provided parent pagesite/find API route are now filtered to only return pages that are accessible to the current user.content.fileRedirects is enabled.Forwarded: for=..., X-Client-IP or X-Real-IP request header with external IP address was provided by a reverse proxy.content.salt option and Cookie::$key default values have not been changed.
<img width="603" height="258" alt="image" src="https://github.com/user-attachments/assets/4efe88bf-c4ed-46a7-951c-3a18084cd265" />$helper.url.hasDangerousScheme(url) JS helper$helper.string.isEmail(string, strict) helpercookie.key option to allow setting the Kirby\Http\Cookie::$key directly from the configKirby\Http\Environment now correctly extracts the for= value from the standardized Forwarded header, fixing ::isLocal() detection behind certain proxies. #8166->where() and ->having() clauses instead of simply dropping non-existing columns from those clauses #8180Kirby\Image\Focus::normalize() #8186(date:) KirbyTag now escapes its output to prevent HTML being injected through special characters in the tag value. Thanks to Peter Levashov (@petersevera) for his responsible disclosure and suggestion.Html::gist() now only embeds Gists from gist.github.com, so it can no longer load scripts from arbitrary URLs. Thanks to Peter Levashov (@petersevera) for his responsible disclosure and suggestion.Kirby\Image\QrCode::toSvg() #8185Kirby\Content\Lock::for() uses current language for fallback) #8173Kirby\Image\Location::num() through malformed EXIF data #8184Html::gist() (and the (gist:) tag) now ignores URLs from hosts other than gist.github.com. Sites embedding Gists from a custom host (e.g. GitHub Enterprise) can re-allow it via Kirby\Toolkit\Html::$gistDomains[] = 'gist.example.com';.Throw exceptions for UUID cache misses when content.uuid.index = false is set only in debug mode #8150
content.uuid.index = false is set only in debug mode #8150After our 5.4.1 release yesterday, the symfony/yaml package had a security release today. This is a patched version with the updated yaml dependency.
After our 5.4.1 release yesterday, the symfony/yaml package had a security release today. This is a patched version with the updated yaml dependency.
Update: After our 5.4.1 release yesterday, the symfony/yaml package had a security release today. There is a patched version with the updated yaml dep…
Update: After our 5.4.1 release yesterday, the symfony/yaml package had a security release today. There is a patched version with the updated yaml dependency: https://github.com/getkirby/kirby/releases/tag/5.4.2
[!NOTE] This release is part of our new monthly security release series. Find out more about those releases and their background on our website: https://getkirby.com/buzz/security-update
This vulnerability affects all Kirby sites on Kirby 5.3.0-5.4.0 and is independent from setup conditions and authentication.
This vulnerability is of high severity for all Kirby sites.
Thanks to @offset for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users.
This vulnerability is of high severity for affected sites and has a high real-world impact.
Thanks to @mojamojam for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites that use the list field or list block, when content is authored by users who may not be fully trusted. The attack requires an authenticated Panel user with update permission to any list field or list block.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if you don't use the list field (or blocks field with the list block) in any of your blueprints, or if every user who can edit content is fully trusted. The attack only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into list field content.
Thanks to @offset for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites that allow the use of the (link: …) KirbyTag, the link: parameter of the (image: …) KirbyTag, the built-in image block with a link or the HTML importer for blocks, when content is authored by users who may not be fully trusted. The attack requires an authenticated Panel user with update permission to any textarea or blocks field, or write access to content files through another vector (e.g. a frontend form or content sync pipeline). Another attack vector is the use of Html::a() or Html::link() with untrusted user input.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if none of the mentioned KirbyTags or block types are used, or if every user who can edit content is fully trusted. The attack only surfaces in the site frontend (i.e. in your templates). The Panel itself is unaffected and will not execute JavaScript that was injected into the textarea or blocks field content.
Thanks to @offset for responsibly reporting the identified issue.
pages.access permission is not checked during rendering of page draftsThis vulnerability affects all Kirby sites where users of a particular role have no permission to access pages (pages.access permission is disabled). This can be due to configuration in the user blueprint(s), via options in the model blueprint(s) or via a combination of both settings.
Your Kirby sites are not affected if you intend all users of your site to be able to access all page drafts of the site. The vulnerability can only be exploited by authenticated users. Write actions are not affected by this vulnerability.
Thanks to @adrgs for responsibly reporting the identified issue.
users.access/list permissionsThis vulnerability affects all Kirby sites that restrict the visibility of users for certain roles via the users.access or users.list permissions. A site is affected if users of a particular role are not allowed to see other users in the Panel, for example because the role's blueprint sets users.access: false or users.list: false as permission for the authenticated user role and/or as option for the target user role.
Your Kirby site is not affected if all authenticated Panel users are permitted to access and list other users. The vulnerability can only be exploited by authenticated users.
Thanks to Matteo Panzeri (@matte1782) for responsibly reporting the identified issue.
Kirby\Sane\Sane::sanitizeProseMirrorFields() method which sanitizes the value and converts non-breaking spaces to HTML entity to match ProseMirrors internal handlingKirby\Http\Url::hasDangerousScheme()accounts directory during user lookup with $users->find()Kirby\Toolkit\BlockAccessAttribute for model methods that must not be used by filterBy or sortBy in Collections.Kirby\Toolkit\Html::link() and Kirby\Http\Url::isAbsolute() do not allow dangerous schemes::filter()/::filterBy() with non-default separators #8062search: false option #8054profiles option #8066Collection::first() and Collection::last() to include null for empty collections #8094Html::link() does no longer accept javascript: URLs. This is a dangerous anti-pattern with many better frontend alternatives and leaves too much space for potential attacks.This vulnerability affects all Kirby sites that use option fields (checkboxes, color, multiselect, select, radio, tags or toggles) with options from a…
This vulnerability affects all Kirby sites that use option fields (checkboxes, color, multiselect, select, radio, tags or toggles) with options from a query or API whose values may not be fully trusted. It also affects direct uses of the OptionsApi or OptionsQuery classes of Kirby's Options package from plugin or site code. The attack requires either an
attacker in the group of authenticated Panel users or user interaction of another authenticated user.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if you are not using any of the mentioned fields or the Options package, if all options are defined statically in the blueprints or if all dynamically gathered options are to be trusted.
Thanks to @offset for responsibly reporting the identified issue.
create permission check via unfiltered blueprint parameterThis vulnerability affects all Kirby sites where users of a particular role have no permission to create pages, files or users (pages.create, files.create or users.create permission is disabled). This can be due to configuration in the user blueprint(s), via options in the model blueprint(s) or via a combination of both settings.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if you intend all users of your site to be able to create pages, files and users. The vulnerability can only be exploited by authenticated users.
Thanks to @offset for responsibly reporting the identified issue.
pages.access/list and files.access/list permissions are not consistently checked in the Panel and REST APIThis vulnerability affects all Kirby sites where users of a particular role have no permission to access or list pages or files (pages.access, pages.list, files.access or files.list permission is disabled). This can be due to configuration in the user blueprint(s), via options in the model blueprint(s) or via a combination of both settings.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if you intend all users of your site to be able to access all pages and files of the site. The vulnerability can only be exploited by authenticated users. Write actions are not affected by this vulnerability.
This vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users.
This vulnerability is of high severity for affected sites.
Your Kirby sites are not affected if you intend all users of your site to be able to list and access the site model and all users and roles, including the content stored within these models. Write actions are not affected by this vulnerability as they were gated by permissions before.
Thanks to @HuajiHD for responsibly reporting the identified issue.
This vulnerability only affects Kirby sites that use the Xml data handler (e.g. Data::encode($string, 'xml')) or the Xml::create(), Xml::tag() or Xml::value() method(s) in site or plugin code. The Kirby core does not use any of the affected methods.
If you use an affected method and cannot rule out input to these methods controlled by an attacker, we strongly recommend to update to a patch release.
Thanks to Patrick Falb (@dapatrese) at FORMER 03 for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites where users of a particular role have no permission to update user information (user.update or users.update permission is disabled). This can be due to configuration in the blueprint(s) of the acting users, via options in the blueprint(s) of the target users or via a combination of both settings.
Your Kirby sites are not affected if you intend all users of your site to be able to upload, replace or delete user avatars. The vulnerability can only be exploited by authenticated users.
changeStatus permission check via unfiltered isDraft parameterThis vulnerability affects all Kirby sites where users have the permission to create pages (pages.create permission is enabled) but not the permission to change the status of pages (pages.changeStatus permission is disabled). This can be due to configuration in the user blueprint(s), via options in the page blueprint(s) or via a combination of both settings.
Your Kirby sites are not affected if your use case does not consider the creation of published pages a malicious action. The vulnerability can only be exploited by authenticated users.
Thanks to @offset for responsibly reporting the identified issue.
This vulnerability affects all Kirby sites that might have potential attackers in the group of authenticated Panel users.
Thanks to @HuajiHD and @0x-bala for responsibly reporting the identified issue.
access permission for the siteKirby\Cms\Site::isAccessible() method checking if the current user has access permission for the siteKirby\Cms\Find::site() method returning the site object or throwingKirby\Exception\NotFoundException if the site is not accessibleerror.site.notAccessible added to i18n/translations/en.jsonaccess and list permissions for users and the current user.Kirby\Cms\User::isAccessible() method checking if the current user has access permission for a given userKirby\Cms\User::isListable() method checking if a user is both accessible and has list permission. Inaccessible users are implicitly not listableKirby\Cms\Find::users() method returning only users filtered by isListable()Kirby\Cms\Role::isAccessible() method checking if the current user has users.access or user.access permission. If the role is the same role as the user's, the user.access permissions are checked. Otherwise users.access.Kirby\Cms\Find::role() and Kirby\Cms\Find::roles() methods returning only roles filtered by isAccessible()error.role.notFound translation key.user.createAvatar, user.replaceAvatar, user.deleteAvatar (including :before and :after)User::createAvatar(), User::replaceAvatar(), User::deleteAvatar()UserRules::createAvatar(), UserRules::replaceAvatar(), UserRules::deleteAvatar(), UserRules::validAvatar()GET /system API route now consistently filters the relevant set of information by current system stateKirby\Cms\Find::parent() now uses Kirby\Cms\Find::site() instead of $kirby->site() for the site model lookupKirby\Cms\Api::site() now delegates to Kirby\Cms\Find::site() instead of $this->kirby->site()config/api/models/System.php the title field now reads directly from $this->kirby()->site() to bypass the site.access permission check, ensuring the title is always availablepage.move dialog now uses Kirby\Cms\Find::site() in the submit handler, when a page gets moved to the top-levelKirby\Cms\Find::user() now enforces isAccessible() on the resolved user, throwing Kirby\Exception\NotFoundException if the user exists but is inaccessibleconfig/api/routes/users.php): all $this->user() / $this->users() calls replaced with Kirby\Cms\Find::user() / Kirby\Cms\Find::users() to apply access control at the API layer. Also cleans up the /roles route and the change-password logic to use Kirby\Cms\FindKirby\Cms\Api::users() delegates to Kirby\Cms\Find::users() instead of $this->kirby->users()Kirby\Cms\UserPicker filters out non-listable users before search/sortKirby\Panel\Collector\UsersCollector filters out non-listable users before role filtering and paginationKirby\Panel\Controller\Search::users() filters by isListable before running the search query. Also moves filter('isListable') before search() in the pages search for consistencyKirby\Panel\User::prevNext() prev/next navigation now filters siblings by isListable so navigation skips hidden usersisListable for prev and next user.Kirby\Panel\ChangesDialog class (::files(), ::users(), ::pages()) will now filter by unlistable models to make sure that they don't accidentally appear in the dialog.Kirby\Cms\UserPicker now filters inaccessible users for the picker dialog.Kirby\Cms\Roles::canBeCreated() and Kirby\Cms\Roles::canBeChanged() to run filter('isAccessible', true) before the existing filter so inaccessible roles are
excluded even if they would otherwise pass the create or changeRole permission checksKirby\Cms\User::roles() to apply filter('isAccessible', true) to the full roles collection before any further permission checks so unauthenticated users and users without user access permissions get no roles.config/api/routes/roles.php: Replaced direct $kirby->roles() calls with Find::roles() so all roles API endpoints enforce access filtering. Replaced $kirby->roles()->find($name) with Find::role($name) for the single-role endpoint. Replaced $kirby->request()->get('canBe') with $this->requestQuery('canBe') for consistencyconfig/api/models/User.php: Added an extra filterBy('isAccessible', true) call on the roles field of the user API model to ensure the API response never exposes inaccessible rolesuser.update permissions are now required to create, replace or delete a user avatar.pages.changeStatus permission now also takes effect during the creation of pages (by preventing the creation of published pages instead of drafts). If you need the old behavior of allowing the creation of published pages but preventing users from changing the status of existing pages, please enable the changeStatus permission and block changes to existing pages in a page.changeStatus:before hook.$page->copy() and $page->changeNum() have been marked as internal. They should only be called after all necessary checks (e.g. permissions) have been performed.$form->values()next/prev) in the page API modelPages section table index resets to 1 on each pagination page #8002
Kirby\Cms\Responder #8013post_max_size no longer causes uploads to fail. #8022Child page content no longer includes parent’s content after using page create dialog #7970
Url::to() strips content representation extension on multilang sites #7965page.create:after hook (Kirby 5.3.x) #7957Using $users->find() with more than one argument or $field->toUsers()/$field->toUser() no longer results in unfiltered collections. #7943
$users->find() with more than one argument or $field->toUsers()/$field->toUser() no longer results in unfiltered collections. #7943$users->find(false) no longer loads an invalid empty user object. #7952$lazyCollection->prepend() and $users->prepend() ensure the intended element order even if the collection was not initialized before. #7952$lazyCollection->empty() and $users->empty() no longer result in populated collections if the original collection was not initialized before. #7952$collection->find(false, false, ...$data) #7952The following cursor-dependent methods of Iterator and collection classes have been deprecated and will be removed in Kirby 6: key, current, next, pre…
[!CAUTION] Unfortunately the Kirby 5.3.0 release introduced a regression in the user handling that leads to wrong results when using
$users->find(),$field->toUsers()or$field->toUser(). All of these wrongly return the entire set of users without filtering.Please update to Kirby 5.3.1 or later.
<k-code-token> component and global styles for inline <code> elements with data-type attribute. The styles for the colored inline elements have been taken from our lab examples and are now available anywhere. The type can either be a generic type (string, float, bool, etc.) or a color keyword from our design system (green, red, orange, etc.) #7765
<img width="934" height="468" alt="image" src="https://github.com/user-attachments/assets/2c013588-af36-4359-b7ae-6b9e7a6fead5" /><k-stack> component to help with horizontal and vertical layouts. Think of it as a flex layout helper component. It's perfect to create equal gaps between elements in a column or row. E.g. different sections or the gap between the headline and contents of a container. #7766
<img width="907" height="1001" alt="image" src="https://github.com/user-attachments/assets/e5dd4ac2-c4f9-4844-abab-45d59a84beb3" /><k-stack>
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
</k-stack>
… or use the k-stack class on an existing wrapper element to inherit the basic stack styles:<ul class="k-stack">
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</ul>
Use the attributes gap, direction, align and justify to control the layout.<k-stack gap="var(--spacing-12)" align="center" direction="row" justify="space-between">
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
</k-stack>
Those are applied as inline styles. If you use the k-stack class on a custom element, you need to set the inline styles manually or with the CSS rules for your element.<k-definitions> and <k-definition> components to build definition lists in the style of our tables. This is particularly useful to show any kind of information in a semantic way. We will use this for our new error dialogs. #7767
<img width="999" height="321" alt="image" src="https://github.com/user-attachments/assets/eab7c249-7a79-4ce4-b3aa-db1742b2ad71" /><k-definitions>
<k-definition term="Term" description="Description" />
<k-definition term="Term" description="Description" />
<k-definition term="Term" description="Description" />
</k-definitions>
Definition items can also be created with custom slots:<k-definitions>
<k-definition>
<template #term><em>Term</em></template>
<p class="k-text">
<a href="<https://getkirby.com>">Description</a>
</p>
</k-definition>
<k-definition>
<template #term><em>Term</em></template>
<p class="k-text">
<a href="<https://getkirby.com>">Description</a>
</p>
</k-definition>
<k-definition>
<template #term><em>Term</em></template>
<p class="k-text">
<a href="<https://getkirby.com>">Description</a>
</p>
</k-definition>
</k-definitions>
<k-checklist> component to create appealing lists of items that are marked as checked, to be noticed or errors. We will be using this in our new error dialogs, but the component is also very helpful for all kinds of scenarios in plugins and other parts of the Panel. #7771
<img width="742" height="881" alt="image" src="https://github.com/user-attachments/assets/8d46262a-04ab-4afa-b5cb-1c26bc6290b7" /><k-checklist>
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</k-checklist>
Applying a theme:<k-checklist theme="negative">
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</k-checklist>
All color themes are supported. notice and negative will automatically change the marker (see screenshot) You can easily add your own custom markers as well.<k-checklist style="--checklist-marker: '💛'">
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</k-checklist>
Kirby\Http\Url::editor($editor, $file, $line) method, to create local editor URLs to open files in a code editor at the given line. #7768<a href="<?= Url::editor('vscode', '/my/local/file.php', 12) ?>">Open in VSCode</a>
scroll-to-bottom and scroll-to-bottom-fill icons #7813LazyCollection class that initializes and loads its data and elements only when they are first needed #7839index.php) are only loaded once when the user object is first created, improving system performance with many user accounts.$visitor->ip() supports new $hash parameter to retrieve a 50 char long hash of the visitor's IP{kirby}, {site} and {index}. This will keep the responses more readable and easier to debug. It will also disguise the filesystem a bit. Although this is not the main intention, since those paths are only visible in debug mode anyway. #7772layout-top + layout-bottom icons #7814Iterator (mostly collections) can now implement a custom iterator and are not pinned to ArrayIterator #7838User::hasPassword() method to provide a solid check for an existing password #7869buttons:
- open
- preview
- '-'
- languages
- '-'
- settings
OfflineError error type in kirby/panel/src/errors/OfflineError.js.kirby/panel/src/panel/request.js now uses safeFetch() and emits offline on network failures.kirby/panel/src/api/request.js uses safeFetch() instead of raw fetch().kirby/panel/src/panel/panel.js catches OfflineError and sets isOffline.Filesystem\F::range($file, $offset, $length) method to only read parts of a fileHttp\Range class for handling HTTP range requests<k-drawer> has new size prop (options: tiny, small, default, large, huge) #7900<k-tag>: support for icon. #7886<k-checkboxes-input>, <k-radio-input>, <k-toggle-input>: support for additional icon alongside text and info for the label #7886Kirby\Filesystem\F::load() has a new cache parameter which will return the file content from cache or add the loaded file content to a cache on the first time its loaded #7920Iterator::has() and the has() method of collections correctly treats an existing but null value as a valid collection element #7838A::get(): Prefer dotted prefix keys to avoid option collisions of full dotted prefix vs. nested array, e.g. with plugin options #6242k-table: #6451(image: ) alt text) #6344Iterator and collection classes have been deprecated and will be removed in Kirby 6: key, current, next, prev, rewind and valid #7838$collection->data property to be populated. Collection methods should use foreach ($collection) instead of foreach ($collection->data). If direct access to the data array is required, call $collection->initialize() (to initialize all keys) or $collection->hydrate() (to initialize all keys and values). During Kirby 5, collection methods still receive a fully hydrated collection for backwards-compatibility. #7839Kirby\Http\Url::to() has been deprecated. Use Kirby\Cms\Url::to() instead #7811Responder::markVolatileHeader() is deprecated in favor of Responder::volatileHeaders()->mark(). The method will be removed in Kirby 6. #7858Str::template() by default also replaces placeholders wrapped in {< >}. #7885Iterator PHPUnit tests #7838The following cursor-dependent methods of Iterator and collection classes have been deprecated and will be removed in Kirby 6: key, current, next, pre…
<k-code-token> component and global styles for inline <code> elements with data-type attribute. The styles for the colored inline elements have been taken from our lab examples and are now available anywhere. The type can either be a generic type (string, float, bool, etc.) or a color keyword from our design system (green, red, orange, etc.) #7765
<img width="934" height="468" alt="image" src="https://github.com/user-attachments/assets/2c013588-af36-4359-b7ae-6b9e7a6fead5" /><k-stack> component to help with horizontal and vertical layouts. Think of it as a flex layout helper component. It's perfect to create equal gaps between elements in a column or row. E.g. different sections or the gap between the headline and contents of a container. #7766
<img width="907" height="1001" alt="image" src="https://github.com/user-attachments/assets/e5dd4ac2-c4f9-4844-abab-45d59a84beb3" /><k-stack>
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
</k-stack>
… or use the k-stack class on an existing wrapper element to inherit the basic stack styles:<ul class="k-stack">
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</ul>
Use the attributes gap, direction, align and justify to control the layout.<k-stack gap="var(--spacing-12)" align="center" direction="row" justify="space-between">
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
<k-box theme="white">Test Box</k-box>
</k-stack>
Those are applied as inline styles. If you use the k-stack class on a custom element, you need to set the inline styles manually or with the CSS rules for your element.<k-definitions> and <k-definition> components to build definition lists in the style of our tables. This is particularly useful to show any kind of information in a semantic way. We will use this for our new error dialogs. #7767
<img width="999" height="321" alt="image" src="https://github.com/user-attachments/assets/eab7c249-7a79-4ce4-b3aa-db1742b2ad71" /><k-definitions>
<k-definition term="Term" description="Description" />
<k-definition term="Term" description="Description" />
<k-definition term="Term" description="Description" />
</k-definitions>
Definition items can also be created with custom slots:<k-definitions>
<k-definition>
<template #term><em>Term</em></template>
<p class="k-text">
<a href="<https://getkirby.com>">Description</a>
</p>
</k-definition>
<k-definition>
<template #term><em>Term</em></template>
<p class="k-text">
<a href="<https://getkirby.com>">Description</a>
</p>
</k-definition>
<k-definition>
<template #term><em>Term</em></template>
<p class="k-text">
<a href="<https://getkirby.com>">Description</a>
</p>
</k-definition>
</k-definitions>
<k-checklist> component to create appealing lists of items that are marked as checked, to be noticed or errors. We will be using this in our new error dialogs, but the component is also very helpful for all kinds of scenarios in plugins and other parts of the Panel. #7771
<img width="742" height="881" alt="image" src="https://github.com/user-attachments/assets/8d46262a-04ab-4afa-b5cb-1c26bc6290b7" /><k-checklist>
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</k-checklist>
Applying a theme:<k-checklist theme="negative">
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</k-checklist>
All color themes are supported. notice and negative will automatically change the marker (see screenshot) You can easily add your own custom markers as well.<k-checklist style="--checklist-marker: '💛'">
<li>Item A</li>
<li>Item B</li>
<li>Item C</li>
</k-checklist>
Kirby\Http\Url::editor($editor, $file, $line) method, to create local editor URLs to open files in a code editor at the given line. #7768<a href="<?= Url::editor('vscode', '/my/local/file.php', 12) ?>">Open in VSCode</a>
scroll-to-bottom and scroll-to-bottom-fill icons #7813LazyCollection class that initializes and loads its data and elements only when they are first needed #7839index.php) are only loaded once when the user object is first created, improving system performance with many user accounts.$visitor->ip() supports new $hash parameter to retrieve a 50 char long hash of the visitor's IP{kirby}, {site} and {index}. This will keep the responses more readable and easier to debug. It will also disguise the filesystem a bit. Although this is not the main intention, since those paths are only visible in debug mode anyway. #7772layout-top + layout-bottom icons #7814Iterator (mostly collections) can now implement a custom iterator and are not pinned to ArrayIterator #7838User::hasPassword() method to provide a solid check for an existing password #7869buttons:
- open
- preview
- '-'
- languages
- '-'
- settings
OfflineError error type in kirby/panel/src/errors/OfflineError.js.kirby/panel/src/panel/request.js now uses safeFetch() and emits offline on network failures.kirby/panel/src/api/request.js uses safeFetch() instead of raw fetch().kirby/panel/src/panel/panel.js catches OfflineError and sets isOffline.Filesystem\F::range($file, $offset, $length) method to only read parts of a fileHttp\Range class for handling HTTP range requests<k-drawer> has new size prop (options: tiny, small, default, large, huge) #7900<k-tag>: support for icon. #7886<k-checkboxes-input>, <k-radio-input>, <k-toggle-input>: support for additional icon alongside text and info for the label #7886Kirby\Filesystem\F::load() has a new cache parameter which will return the file content from cache or add the loaded file content to a cache on the first time its loaded #7920Iterator::has() and the has() method of collections correctly treats an existing but null value as a valid collection element #7838A::get(): Prefer dotted prefix keys to avoid option collisions of full dotted prefix vs. nested array, e.g. with plugin options #6242k-table: #6451(image: ) alt text) #6344Iterator and collection classes have been deprecated and will be removed in Kirby 6: key, current, next, prev, rewind and valid #7838$collection->data property to be populated. Collection methods should use foreach ($collection) instead of foreach ($collection->data). If direct access to the data array is required, call $collection->initialize() (to initialize all keys) or $collection->hydrate() (to initialize all keys and values). During Kirby 5, collection methods still receive a fully hydrated collection for backwards-compatibility. #7839Kirby\Http\Url::to() has been deprecated. Use Kirby\Cms\Url::to() instead #7811Responder::markVolatileHeader() is deprecated in favor of Responder::volatileHeaders()->mark(). The method will be removed in Kirby 6. #7858Str::template() by default also replaces placeholders wrapped in {< >}. #7885Iterator PHPUnit tests #7838Using page title in string template of other fields #7834
> This vulnerability affects all Kirby sites (Kirby 5.0.0-5.2.1) where user permissions are configured to prevent specific role(s) from performing wri…
[!CAUTION]
🚨 Security
Missing permission checks in the content changes API
CVE ID: CVE-2026-21896 Severity: medium (CVSS score 5.8)
This vulnerability affects all Kirby sites (Kirby 5.0.0-5.2.1) where user permissions are configured to prevent specific role(s) from performing write actions, specifically by disabling the
updatepermission with the intent to prevent modifications to site content.If you haven't configured any user permissions that deviate from the default of allowing all actions, your site is not affected.
Remote::json() with single-value JSON content (e.g. a single string, single int) #7806Kirby\Toolkit\Dom for newer libxml versions #7802$collection->group(callable) should accept empty string result as key #7830$_SERVER manipulation in tests #7807Fixed PHP 8.5 compatibility issues around files in the Panel #7773
Removed use of old PHP functions that are deprecated in PHP 8.5 #7556
batch select mode for the checkboxes fieldcreate option for the files sectionPHP 8.5 has been released a few days ago and it's a fantastic release (https://www.php.net/releases/8.5/en.php) Kirby 5.2 is already fully compatible. #7671
For headless setups, proper CORS support is incredibly helpful to speak to your Kirby API, content representations or KQL across domains. Thanks to the help of @johannschopplich, Kirby is now making this very easy out of the box.
'cors' => true to enable CORS with sensible defaults. Check below for additional configuration options.OPTIONS CORS preflight requests automatically receive a 204 No Content response with appropriate CORS headers.Responder::headers() method for all responses. Custom headers set by plugins or user code are never overridden.*): No Vary: Origin header is added (cache-efficient since response is identical for all origins)Vary: Origin header ensures different origins are cached separatelyVary: Access-Control-Request-Headers for preflight requests when reflection is enabledVary: Authorization, Cookie when response uses authentication or cookies'allowHeaders' => true, preflight requests mirror the headers requested by the client while Vary: Access-Control-Request-Headers ensures correct caching. The default [] remains secure-by-default by omitting the header.CORS can be enabled in three ways:
return [
'cors' => true
];
return [
'cors' => [
'allowOrigin' => 'https://example.com',
'allowCredentials' => true
]
];
return [
'cors' => function ($kirby) {
$origin = $kirby->request()->header('Origin');
// Allow specific origins with credentials
if (in_array($origin, ['https://app1.com', 'https://app2.com'])) {
return [
'allowOrigin' => $origin,
'allowCredentials' => true,
'allowMethods' => ['GET', 'POST']
];
}
// Fallback to wildcard for other origins
return ['allowOrigin' => '*'];
}
];
Note: Setting 'cors' => [] (empty array) is equivalent to 'cors' => true and enables CORS with defaults. To disable CORS, use 'cors' => false or omit the option entirely.
| Option | Type | Default | Description |
|---|---|---|---|
allowOrigin |
string, array |
'*' |
Allowed origins (e.g., '*', 'https://example.com', or ['https://app1.com', 'https://app2.com'] for multiple origins) |
allowMethods |
string, array |
['GET', 'HEAD', 'PUT', 'POST', 'DELETE', 'PATCH'] |
Allowed HTTP methods for preflight requests |
allowHeaders |
string, array, bool |
[] |
Allowed request headers. [] (default) suppresses Access-Control-Allow-Headers; true reflects headers from Access-Control-Request-Headers; strings/arrays allowlist specific headers explicitly |
maxAge |
int |
null |
Preflight cache duration in seconds. null uses the browser default (typically 5 seconds) |
allowCredentials |
bool |
false |
Allow requests with credentials (cookies, auth). Cannot be true with wildcard origin |
exposeHeaders |
string, array |
[] |
Response headers exposed to the browser |
'allowCredentials' => true lets browsers include cookies and HTTP authentication with cross-origin requests, effectively granting the external origin the same permissions as the logged-in user. Only enable credentials when the requesting origin is fully trusted and under your control.You can now switch on the select all/deselect all toggles with the new batch option in the checkboxes field to select or deselect multiple checkboxes at once. This is helpful when a checkboxes field has a lot of options https://feedback.getkirby.com/81 #7659
fields:
countries:
type: checkboxes
options:
# lots of countries
batch: true
https://github.com/user-attachments/assets/1d275559-609a-4230-9f5e-79f6de27d9bd
Thanks to this new feature, we now also have the following additions:
select-all and deselect-all iconsselect.all, deselect.all and deselect translation stringsThere are new options to expand or collapse all blocks at once in the blocks options dropdown (if there are collapsible blocks used, e.g. with preview: fields) (thx @dennisbaum) #7555
<img width="210" height="272" alt="collapse-all" src="https://github.com/user-attachments/assets/d3c978b1-dc35-40d2-99df-f595787aed13" />
create option for the files sectionThe new create option for the files section lets you disable the upload button. This is useful if you are using queries in files sections and the upload would not actually show up in the list. It is comparable to the create option in the pages section. #7649
sections:
images:
type: files
query: page.images.filter('customField', 'customFilter')
create: false
We've improved our auto-labelling method for labels, titles and more in various places of the Panel. Here's an example from a blueprint #7656:
sections:
coverImages:
type: files
The files section above does not define a label, but already has a meaningful name, which can now be turned into one. In previous releases coverImages would have been turned into the auto-label Coverimages. Not that nice. Now camel casing automatically turns it into Cover images. This also works if you prefer kebab-casing.
sections:
cover_images:
type: files
This will very often save you from defining additional label/title/name options. This can now help you in the following places: - Blueprint title - Blueprint tab labels - Section headlines - Form field labels - Block field: fieldset names - Block field: fieldset tab names - Block field: fieldset group names - Role titles - Custom panel search labels
This feature is based on our new Kirby\Toolkit\Str::label() method, which you can of course use in your own code, to create nice auto-labels.
We've managed to achieve massive performance improvements for forms. In our test setup we measure two different scenarios:
5.1.4: 00:06.198
5.2.0: 00:03.045
≈ 50.9% reduction in time
≈ 2.04× speed-up
5.1.4: 00:19.390
5.2.0: 00:05.900
≈ 69.6% reduction in time
≈ 3.29× speed-up
Our test sandbox is of course a very theoretical environment, but we still expect to see some serious improvements in real-world setups.
The following steps lead to this improvement:
- New ::emptyValue() method for Kirby\Form\Field and Kirby\Form\FieldClass, which can be overwritten to define the preferred empty value when the field is being reset #7663
- New Kirby\Form\Field::fillWithEmptyValue() and Kirby\Form\FieldClass:reset(), which are used in Kirby\Form\Fields to reset field values without evaluating computed props again if not
necessary. This is the part that leads to the performance improvements. #7663
- Field options are now cached in memory to improve the performance of fields. #7664
- New protected BlocksField::fieldsetForm method to cache forms for each fieldset type. #7665
- Fixes: #7641 and #6734
We've also added a new in-memory snippet cache to speed up snippet lookups and avoid disk access #7369
plugins.getkirby.com directory if plugin is listed there #7243options string supports Kirby query syntax #7566k-dropdown-item supports all button props (esp. dialog and drawer) #7590Kirby\Http\Uri::inherit() methods that copies over query, params and fragment from another URL #7611Kirby\Reflection\Constructor class #7620use Kirby\Reflection\Constructor;
class Reflectable
{
public function __construct(
protected $a,
protected $b
) {
}
}
$constructor = new Constructor(Reflectable::class);
$constructor->getAcceptedArguments([
'a' => 'Test A',
'b' => 'Test B',
'c' => 'Test C'
]);
// will keep 'a' and 'b'
$constructor->getIgnoredArguments([
'a' => 'Test A',
'b' => 'Test B',
'c' => 'Test C'
]);
// will keep 'c'
KIRBY_PHP_VERSION_CHECK constant. This is for very specific cases and comes with risks, please note the code comment in bootstrap.php. #7648Kirby\Image\Gravity enum #7732t() helper accepts array for $fallback #7717default option of the number, date and time fields #7594RequestError JS class is polyfilling error messages stored in the error prop instead of the message prop to create more consistency. #7670RequestError JS class is now responsible for all server errors to add another layer of consistency there. #7670details array from custom Kirby Exceptions is now always properly passed forward in all error responses. #7670panel.notification.error() method is now also passing details forward to the error object. #7670imagick thumb driver #7732Kirby\Image\Image::imagesize() now returns array|falseKirby\Image\Dimensions::forImage() returns 0x0 for invalid imagesKirby\Image\Image::isResizable() checks for zero dimensions earlyk-button supports dialog/drawer objects as props #7590$panel.dialog.open()/$panel.drawer.open() accept a single object argument if it has a url key #7590/panel/lab/internals/errors) for various scenarios (opening views, dialogs, drawers, sending requests, etc.) #7670Removed use of old PHP functions that are deprecated in PHP 8.5 #7556
batch select mode for the checkboxes fieldcreate option for the files sectionPHP 8.5 has been released a few days ago and it's a fantastic release (https://www.php.net/releases/8.5/en.php) Kirby 5.2 is already fully compatible. #7671
For headless setups, proper CORS support is incredibly helpful to speak to your Kirby API, content representations or KQL across domains. Thanks to the help of @johannschopplich, Kirby is now making this very easy out of the box.
'cors' => true to enable CORS with sensible defaults. Check below for additional configuration options.OPTIONS CORS preflight requests automatically receive a 204 No Content response with appropriate CORS headers.Responder::headers() method for all responses. Custom headers set by plugins or user code are never overridden.*): No Vary: Origin header is added (cache-efficient since response is identical for all origins)Vary: Origin header ensures different origins are cached separatelyVary: Access-Control-Request-Headers for preflight requests when reflection is enabledVary: Authorization, Cookie when response uses authentication or cookies'allowHeaders' => true, preflight requests mirror the headers requested by the client while Vary: Access-Control-Request-Headers ensures correct caching. The default [] remains secure-by-default by omitting the header.CORS can be enabled in three ways:
return [
'cors' => true
];
return [
'cors' => [
'allowOrigin' => 'https://example.com',
'allowCredentials' => true
]
];
return [
'cors' => function ($kirby) {
$origin = $kirby->request()->header('Origin');
// Allow specific origins with credentials
if (in_array($origin, ['https://app1.com', 'https://app2.com'])) {
return [
'allowOrigin' => $origin,
'allowCredentials' => true,
'allowMethods' => ['GET', 'POST']
];
}
// Fallback to wildcard for other origins
return ['allowOrigin' => '*'];
}
];
Note: Setting 'cors' => [] (empty array) is equivalent to 'cors' => true and enables CORS with defaults. To disable CORS, use 'cors' => false or omit the option entirely.
| Option | Type | Default | Description |
|---|---|---|---|
allowOrigin |
string, array |
'*' |
Allowed origins (e.g., '*', 'https://example.com', or ['https://app1.com', 'https://app2.com'] for multiple origins) |
allowMethods |
string, array |
['GET', 'HEAD', 'PUT', 'POST', 'DELETE', 'PATCH'] |
Allowed HTTP methods for preflight requests |
allowHeaders |
string, array, bool |
[] |
Allowed request headers. [] (default) suppresses Access-Control-Allow-Headers; true reflects headers from Access-Control-Request-Headers; strings/arrays allowlist specific headers explicitly |
maxAge |
int |
null |
Preflight cache duration in seconds. null uses the browser default (typically 5 seconds) |
allowCredentials |
bool |
false |
Allow requests with credentials (cookies, auth). Cannot be true with wildcard origin |
exposeHeaders |
string, array |
[] |
Response headers exposed to the browser |
'allowCredentials' => true lets browsers include cookies and HTTP authentication with cross-origin requests, effectively granting the external origin the same permissions as the logged-in user. Only enable credentials when the requesting origin is fully trusted and under your control.You can now switch on the select all/deselect all toggles with the new batch option in the checkboxes field to select or deselect multiple checkboxes at once. This is helpful when a checkboxes field has a lot of options https://feedback.getkirby.com/81 #7659
fields:
countries:
type: checkboxes
options:
# lots of countries
batch: true
https://github.com/user-attachments/assets/1d275559-609a-4230-9f5e-79f6de27d9bd
Thanks to this new feature, we now also have the following additions:
select-all and deselect-all iconsselect.all, deselect.all and deselect translation stringsThere are new options to expand or collapse all blocks at once in the blocks options dropdown (if there are collapsible blocks used, e.g. with preview: fields) (thx @dennisbaum) #7555
<img width="210" height="272" alt="collapse-all" src="https://github.com/user-attachments/assets/d3c978b1-dc35-40d2-99df-f595787aed13" />
create option for the files sectionThe new create option for the files section lets you disable the upload button. This is useful if you are using queries in files sections and the upload would not actually show up in the list. It is comparable to the create option in the pages section. #7649
sections:
images:
type: files
query: page.images.filter('customField', 'customFilter')
create: false
We've improved our auto-labelling method for labels, titles and more in various places of the Panel. Here's an example from a blueprint #7656:
sections:
coverImages:
type: files
The files section above does not define a label, but already has a meaningful name, which can now be turned into one. In previous releases coverImages would have been turned into the auto-label Coverimages. Not that nice. Now camel casing automatically turns it into Cover images. This also works if you prefer kebab-casing.
sections:
cover_images:
type: files
This will very often save you from defining additional label/title/name options. This can now help you in the following places: - Blueprint title - Blueprint tab labels - Section headlines - Form field labels - Block field: fieldset names - Block field: fieldset tab names - Block field: fieldset group names - Role titles - Custom panel search labels
This feature is based on our new Kirby\Toolkit\Str::label() method, which you can of course use in your own code, to create nice auto-labels.
We've managed to achieve massive performance improvements for forms. In our test setup we measure two different scenarios:
5.1.4: 00:06.198
5.2.0: 00:03.045
≈ 50.9% reduction in time
≈ 2.04× speed-up
5.1.4: 00:19.390
5.2.0: 00:05.900
≈ 69.6% reduction in time
≈ 3.29× speed-up
Our test sandbox is of course a very theoretical environment, but we still expect to see some serious improvements in real-world setups.
The following steps lead to this improvement:
- New ::emptyValue() method for Kirby\Form\Field and Kirby\Form\FieldClass, which can be overwritten to define the preferred empty value when the field is being reset #7663
- New Kirby\Form\Field::fillWithEmptyValue() and Kirby\Form\FieldClass:reset(), which are used in Kirby\Form\Fields to reset field values without evaluating computed props again if not
necessary. This is the part that leads to the performance improvements. #7663
- Field options are now cached in memory to improve the performance of fields. #7664
- New protected BlocksField::fieldsetForm method to cache forms for each fieldset type. #7665
- Fixes: #7641 and #6734
We've also added a new in-memory snippet cache to speed up snippet lookups and avoid disk access #7369
plugins.getkirby.com directory if plugin is listed there #7243options string supports Kirby query syntax #7566k-dropdown-item supports all button props (esp. dialog and drawer) #7590Kirby\Http\Uri::inherit() methods that copies over query, params and fragment from another URL #7611Kirby\Reflection\Constructor class #7620use Kirby\Reflection\Constructor;
class Reflectable
{
public function __construct(
protected $a,
protected $b
) {
}
}
$constructor = new Constructor(Reflectable::class);
$constructor->getAcceptedArguments([
'a' => 'Test A',
'b' => 'Test B',
'c' => 'Test C'
]);
// will keep 'a' and 'b'
$constructor->getIgnoredArguments([
'a' => 'Test A',
'b' => 'Test B',
'c' => 'Test C'
]);
// will keep 'c'
KIRBY_PHP_VERSION_CHECK constant. This is for very specific cases and comes with risks, please note the code comment in bootstrap.php. #7648Kirby\Image\Gravity enum #7732t() helper accepts array for $fallback #7717default option of the number, date and time fields #7594RequestError JS class is polyfilling error messages stored in the error prop instead of the message prop to create more consistency. #7670RequestError JS class is now responsible for all server errors to add another layer of consistency there. #7670details array from custom Kirby Exceptions is now always properly passed forward in all error responses. #7670panel.notification.error() method is now also passing details forward to the error object. #7670imagick thumb driver #7732Kirby\Image\Image::imagesize() now returns array|falseKirby\Image\Dimensions::forImage() returns 0x0 for invalid imagesKirby\Image\Image::isResizable() checks for zero dimensions earlyk-button supports dialog/drawer objects as props #7590$panel.dialog.open()/$panel.drawer.open() accept a single object argument if it has a url key #7590/panel/lab/internals/errors) for various scenarios (opening views, dialogs, drawers, sending requests, etc.) #7670This vulnerability affects all Kirby 5 sites that might have potential attackers in the group of authenticated Panel users or that allow external visi…
Severity: medium (CVSS score 5.1)
This vulnerability affects all Kirby 5 sites that might have potential attackers in the group of authenticated Panel users or that allow external visitors to update page titles or usernames.
The attack requires user interaction by another Panel user and cannot be automated.
css() and js() helpers #7645Allow specifying the page model class of a Kirby\Cms\Pages collection via PHP DocBlock type tags #7617
Kirby\Cms\Pages collection via PHP DocBlock type tags #7617Page status button in sections received a .k-page-status-icon-option CSS class #7592
.k-page-status-icon-option CSS class #7592users as entry point for Kirby queries #7597$panel.content.isLocked returns false when view does not provide a lock prop #7602Keep original case intact when grouping a collection by callable. #7562.
The im thumbs driver option has been deprecated. Use imagick instead. #6754
We've added a handy page tree navigation dropdown to the preview view. Effortlessly jump to the preview of other pages #7335
<img width="1410" height="1126" alt="Screenshot 2025-08-19 at 10 51 57" src="https://github.com/user-attachments/assets/7d58f045-6882-4cca-8285-930275c3a764" />
Kirby 5.1 adds a number of improvements to the Kirby Query language. Since the query language plays such an essential part for Kirby's blueprints, the new query improvements will push the possibilities for blueprints even further.
The improvements are based on a new AST-based query parser and runner that has been added in addition to the previous (legacy) parser. The legacy parser will remain the default parser for now. We aim to replace it with the new runner in Kirby 6. Consider the new runner as a beta state during Kirby 5.x releases. #6788
The new AST-based runner (thanks to @rasteiner for starting off the work on this) runs not only more reliably and performant, but also allow us to add more functionalities. Those are not supported by the legacy runner.
AND/&&/OR/||)==, !=, >, <,<=,>=)+, -,* , /, %)page[site.pageMethodName]query.runner option to switch to the Kirby\Query\Runners\DefaultRunner::class to activate the new AST-based runner (see docs below for more information how to create a custom runner)The new query runner is stricter in parsing queries. In some edge cases, this will require you to access an array/object via subscript notation - in rare cases on the top level via the new this keyword, e.g. this["identifier.with dots and spaces"].
New batch mode for structure fields to delete multiple rows at once. You can activate it by using the new batch option in your blueprint (#7400):
structure:
batch: true
fields:
text:
type: text
https://github.com/user-attachments/assets/6f5f2cee-c96e-4e12-9f2c-abbea5263def
You can now search through the info in a multiselect field by enabling the search > info option. (Thanks to @aofn) #7089
fields:
multiselect:
type: multiselect
options:
...
search:
info: true
<img width="275" height="177" alt="Screenshot 2025-07-21 at 13 26 02" src="https://github.com/user-attachments/assets/09ae369d-7b8f-49ca-aa89-953df567d857" />
We’ve turned the stats section into an additional new field. The stats section keeps existing, but with the new stats field there are more layout possibilities and options for simpler blueprint setups. The field has the exact same options as the stats section (https://getkirby.com/docs/reference/panel/sections/stats). #7392
title: Shop
fields:
stats:
type: stats
size: huge
reports:
- label: Revenue
value: €29,682
info: +112.5%
link: https://getkirby.com/shop
theme: positive
- label: Orders
value: 265
info: +82.8%
theme: positive
- label: Avg. Transaction
value: €112.01
info: +16.3%
theme: positive
- label: Refunds
value: €15.20
info: +10.5%
theme: positive
- label: Discount sales
value: €1,422
info: n/a
New imagick thumbs driver, using the Imagick class instead of the convert command line command #6754
// /site/config/config.php
return [
'thumbs' => [
'driver' => 'imagick'
]
];
panel.themeYou can now set the default Panel theme that is used when the user has not set any custom setting in their account view. Supported values: "light", "dark" or "system" (default, matches the user's operating system) #7341
// site/config/config.php
return [
'panel' => [
'theme' => 'light'
]
];
Collection::join() methodThis new method is available in all collections #7340 (thx to @adamkiss)
$venues = $page->children()->join(' | ', fn ($child) => $child->venue());
$venues = $page->children()->join(as: fn ($child) => snippet('venue', ['page' => $child], return: true));
session.cookieDomain optionThe option allows to share the session cookie across subdomains with a shared sessions folder feedback.getkirby.com/628
[!NOTE] You can read more about the behavior of the
domainattribute for cookies in the MDN docs.Note that setting the
cookieDomainoption disables Kirby setting thepathattribute to the cookie (relevant in subfolder setups).
return [
'session' => [
'durationNormal' => 7200, // default: 2 hours
'durationLong' => 1209600, // default: 2 weeks
'timeout' => 1800, // default: half an hour
'cookieDomain' => 'getkirby.com', // default: automatic browser behavior
'cookieName' => 'kirby_session',
'gcInterval' => 100 // default: cleanup every ~100 requests
]
];
The dialog search input has a new button to clear the input #7513
https://github.com/user-attachments/assets/1a6e9df4-9609-4f67-8bb9-0bbb0e566aa7
The license dialog now includes a button to remove the license file #6962 #6960
<img width="688" height="245" alt="Screenshot 2025-08-19 at 11 07 21" src="https://github.com/user-attachments/assets/f9ba2d22-bf32-4eeb-8d3b-cab01f3c1b78" />
We've added history support for panel.dialog for nested dialogs #7519 Dialogs can now correctly open more dialogs which will be stacked on top of each other and close correctly.
We've improved the UI when the structure field is disabled that allows to open drawer to see all fields as well as navigate through all entries when paginated https://feedback.getkirby.com/687
Our language detector will now correctly detect languages based on locales. You can now easily set up two English locales (en_GB and en_US) for example and the detector will pick the right one and redirect correctly. (thanks to @tobiasfabian) #7178
You can now set the Panel interface translation on demand with the new translation query parameter. E.g. https://example.com/panel/login?translation=it #6616
We've added a link to the PHP version support table from the fatal view that is displayed on unsupported PHP versions
skeleton theme for itemsWe've added a new sekeleton theme for the k-item component to represent a loading state #7521
<img width="543" height="164" alt="Screenshot 2025-08-12 at 11 20 14" src="https://github.com/user-attachments/assets/74e14860-c3b4-42f2-ab72-120e52549783" />
With Kirby 5.1 you can create a small plugin that enables support for snippets and block controllers: one can add a controller for e.g. the snippet site/snippets/header.php to site/controllers/snippets/header.php. And since blocks are also just snippets, e.g. site/controllers/snippets/blocks/video.php.
As there can be many snippet calls within a single request, checking for the existence of a controller for each of these can impact your site’s performance.
<?php
use Kirby\Cms\App;
use Kirby\Template\Snippet;
use Kirby\Toolkit\Str;
class SnippetWithController extends Snippet
{
protected static $controllers = [];
public static function controller(
string|null $file,
array $data = []
): array {
if (
$file === null ||
str_starts_with($file, static::root()) === false
) {
return $data;
}
if (isset(static::$controllers[$file])) {
return array_replace_recursive(
$data,
static::$controllers[$file]
);
}
$name = ltrim(Str::before(Str::after($file, static::root()), '.php'), '/');
// if the snippet has a name, we can load the controller
// and merge the data with the controller's data
if ($name !== null) {
$data = array_replace_recursive(
$data,
static::$controllers[$file] = App::instance()->controller('snippets/' . $name, $data)
);
}
return $data;
}
public static function factory(
string|array|null $name,
array $data = [],
bool $slots = false
): static|string {
$file = $name !== null ? static::file($name) : null;
$data = static::controller($file, $data);
return parent::factory($name, $data, $slots);
}
public function render(array $data = [], array $slots = []): string
{
$data = array_replace_recursive(
static::controller($this->file, $data),
$data
);
return parent::render($data, $slots);
}
}
App::plugin('getkirby/snippet-controllers', [
'components' => [
'snippet' => function (
App $kirby,
string|array|null $name,
array $data = [],
bool $slots = false
): Snippet|string {
return SnippetWithController::factory($name, $data, $slots);
},
]
]);
stats field and section as well as the k-stats/k-stat components) now support passing a drawer instead of a link or dialog #7472<k-stats-field> component #7389Kirby\Cms\License::delete() and Kirby\Cms\License::root() #7211
github.com/getkirby/kirby/issues/6960)LanguageVariable::language() method #7379Kirby\Panel\Ui\Stat and Kirby\Panel\Ui\Statsbackend components, which are used to create the correct information for the <k-stat>/<k-stats> Vue component #7373 #7374controller class name or closure hat returns an object with ::load() and ::submit() methods that will be used then as load/submit event actions. Ideally used with returning a Kirby\Panel\Controller\Dialog/Kirby\Panel\Controller\Drawer object. If the named class also defines a static ::for() method, it will be used to create an instance of the class.<k-label> component now also accepts false for the input prop. This will switch the label element to an h2 and also remove the <abbr> for the invalid state. All fields that don't store any values will need this. We can also use it for the info field, which did still create its own headline.Kirby\Panel\Collector\PagesCollector classKirby\Panel\Collector\FilesCollector classKirby\Panel\Collector\UsersCollector classKirby\Panel\Ui\Upload class to handle upload settings in sections and potentially also in fields #7436<k-item> component for a model, such as text, info, image, link, etc. #7456
Kirby\Panel\Ui\Item\FileItemKirby\Panel\Ui\Item\ModelItemKirby\Panel\Ui\Item\PageItemKirby\Panel\Ui\Item\UserItemUuid::toUrl() method that returns the model's absolute URL and includes query and/or fragment that was included in the UUID uri #7484Page::uuid(), Site::uuid(), File::uuid() and User::uuid() #7484closed listener for Panel dialogs and drawers that gets called after the dialog has been closed #7519Kirby\Uuid\Uuid::is() now accepts an array of multiple types to test against #7543Kirby\Http\Query::merge() and Kirby\Http\Params::merge() methods #7546currentColor isn't enforced as fill for all SVGs anymore (only for .k-icon) #7297Kirby\Panel\Ui\Component::render() now only filters out props that are null, not empty arrays #7384h2 that easily bled into component rules.Kirby\Http\Response would falsely converted to a Kirby\Http\Response object #7478max value #7417link KirbyTag when using a UUID #7477translate) are working properly again #7570Exif::iso() now returns the first array item if ISOSpeedRatings is an array #7569::url() method of PageUuid and FileUuid has been renamed to ::toPermalink() and will be removed in a future release. #7484im thumbs driver option has been deprecated. Use imagick instead. #6754Kirby\Http\Router::find(): Passing $ignore = null has been deprecated (pass an empty array or omit the argument instead) #7547App::controller() to return controllers nested in subfolders inside site/controllers #7368<k-stats-section> to <k-stats> #7376<k-stats>stats field uses the new Kirby\Panel\Ui\Stat and Kirby\Panel\Ui\Stats classes to clean up the props generation for the frontend.Kirby\Form\Mixin Traits for after, autofocus, before, help, icon, label, placeholder and width props #7396list settings for table layouts in Kirby\Panel\Model::image() #7449::pickerData() methods and in the Kirby\Panel\Controller\Search controller to clean up all places where such item props are created. #7457Kirby\Http\Response object to Kirby\Cms\Responder::send(). #7478splitVendorChunkPlugin. #7354$mock->addMethods() in unit tests #7356Kirby\Database package #7318<k-stats>Kirby\Http classes #7547query.runner config option
Kirby offers a new runner for its query syntax based on parsing the query as abstract syntax tree. This runner is more reliable and efficient than the rudimentary legacy runner (which in Kirby 5 remains the default). The new runner is currently in its beta phase. You can activate it by setting the query.runner config option:
<?php
use Kirby\Query\Runners\DefaultRunner;
return [
'query.runner' => DefaultRunner::class
];
Query syntax
When using the new query runner, you can also use logical, comparison and math operators in your queries as well as receive arguments in closures:
// new operators
$query = new Query('age > 25 && name != "John"');
$query = new Query('price + vat');
// arguments in query closures
$query = new Query('(foo) => foo.homer');
$data = [];
$bar = $query->resolve($data);
$bar = $bar(['homer' => 'simpson']);
$this->assertSame('simpson', $bar);
Queries will still be tried to resolve first directly from the data context, e.g. when your query is null and your data ['null' => 'foo'] the result will directly be 'foo'. Same for user.username and ['user.username' => 'foo'].
The im thumbs driver option has been deprecated. Use imagick instead. #6754
We've added a handy page tree navigation dropdown to the preview view. Jump effortlessly to the preview of other pages #7335
<img width="1410" height="1126" alt="Screenshot 2025-08-19 at 10 51 57" src="https://github.com/user-attachments/assets/7d58f045-6882-4cca-8285-930275c3a764" />
Kirby 5.1 adds a number of improvements to the Kirby Query language. Since the query language plays such an essential part for our blueprints, the new query improvements will push the possibilities for blueprints even further.
The improvements are based on a new AST-based query parser and runner that has been added in addition to the previous (legacy) parser. The legacy parser which will remain the default parser for now but we aim to replace it with the new runner in Kirby 6. Consider the new runner in beta state during Kirby 5.x releases. #6788
The new AST-based runner (thx to @rasteiner for starting off the work on this) runs not only more reliably and performant, but also allow us to add more functionalities. Those are not supported by the legacy runner.
AND/&&/OR/||)==, !=, >, <,<=,>=)+, -,* , /, %)page[site.pageMethodName]query.runner option to switch to Kirby\Query\Runners\DefaultRunner::class to activate the new AST-based runner (See docs below for more information how to create a custom runner)The new query runner is stricter in parsing queries. In some edge cases, this will require you to access an array/object via subscript notation - in rare cases on the top level via the new this keyword, e.g. this["indentifier.with dots and spaces"].
New batch mode for structure fields to delete multiple rows at once. You can activate it by using the new batch option in your blueprint (#7400):
structure:
batch: true
fields:
text:
type: text
https://github.com/user-attachments/assets/6f5f2cee-c96e-4e12-9f2c-abbea5263def
You can now search through the info in a multiselect field by enabling the search > info option. (Thanks to @aofn) #7089
fields:
multiselect:
type: multiselect
options:
...
search:
info: true
<img width="275" height="177" alt="Screenshot 2025-07-21 at 13 26 02" src="https://github.com/user-attachments/assets/09ae369d-7b8f-49ca-aa89-953df567d857" />
We’ve turned the stats section into an additional new field. The stats section keeps existing, but with the new stats field there are more layout possibilities and options for simpler blueprint setups. The field has the exact same options as the stats section (https://getkirby.com/docs/reference/panel/sections/stats). #7392
title: Shop
fields:
stats:
type: stats
size: huge
reports:
- label: Revenue
value: €29,682
info: +112.5%
link: https://getkirby.com/shop
theme: positive
- label: Orders
value: 265
info: +82.8%
theme: positive
- label: Avg. Transaction
value: €112.01
info: +16.3%
theme: positive
- label: Refunds
value: €15.20
info: +10.5%
theme: positive
- label: Discount sales
value: €1,422
info: n/a
New imagick thumbs driver, using the Imagick class instead of the convert command line command #6754
// /site/config/config.php
return [
'thumbs' => [
'driver' => 'imagick'
]
];
panel.themeYou can now set the default Panel theme that is used when the user has not set any custom setting in their account view. Supported values: "light", "dark" or "system" (default, matches the user's operating system) #7341
// site/config/config.php
return [
'panel' => [
'theme' => 'light'
]
];
Collection::join() methodThis new method is available in all collections #7340 (thx to @adamkiss)
$venues = $page->children()->join(' | ', fn ($child) => $child->venue());
$venues = $page->children()->join(as: fn ($child) => snippet('venue', ['page' => $child], return: true));
session.cookieDomain optionThe option allows to share the session cookie across subdomains with a shared sessions folder feedback.getkirby.com/628
[!NOTE] You can read more about the behavior of the
domainattribute for cookies in the MDN docs.Note that setting the
cookieDomainoption disables Kirby setting thepathattribute to the cookie (relevant in subfolder setups).
return [
'session' => [
'durationNormal' => 7200, // default: 2 hours
'durationLong' => 1209600, // default: 2 weeks
'timeout' => 1800, // default: half an hour
'cookieDomain' => 'getkirby.com', // default: automatic browser behavior
'cookieName' => 'kirby_session',
'gcInterval' => 100 // default: cleanup every ~100 requests
]
];
The dialog search input has a new button to clear the input #7513
https://github.com/user-attachments/assets/1a6e9df4-9609-4f67-8bb9-0bbb0e566aa7
The license dialog now includes a button to remove the license file #6962 [#6960](https://
<img width="688" height="245" alt="Screenshot 2025-08-19 at 11 07 21" src="https://github.com/user-attachments/assets/f9ba2d22-bf32-4eeb-8d3b-cab01f3c1b78" />
We've added history support for panel.dialog for nested dialogs #7519 Dialogs can now correctly open more dialogs which will be stacked on top of each other and close correctly.
We've improved the UI when the structure field is disabled that allows to open drawer to see all fields as well as navigate through all entries when paginated https://feedback.getkirby.com/687
Our language detector will now correctly detect languages based on locales. You can now easily set up two English locales (en_GB and en_US) for example and the detector will pick the right one and redirect correctly. (thanks to @tobiasfabian) #7178
You can now set the Panel interface translation on demand with the new translation query parameter. E.g. https://example.com/panel/login?translation=it #6616
We've added a link to the PHP version support table from the fatal view that is displayed on unsupported PHP versions
skeleton theme for itemsWe've added a new sekeleton theme for the k-item component to represent a loading state #7521
<img width="543" height="164" alt="Screenshot 2025-08-12 at 11 20 14" src="https://github.com/user-attachments/assets/74e14860-c3b4-42f2-ab72-120e52549783" />
With Kirby 5.1 you can create a small plugin that enables support for snippets and block controllers: one can add a controller for e.g. the snippet site/snippets/header.php to site/controllers/snippets/header.php. And since blocks are also just snippets, e.g. site/controllers/snippets/blocks/video.php.
As there can be many snippet calls within a single request, checking for the existence of a controller for each of these can impact your site’s performance.
<?php
use Kirby\Cms\App;
use Kirby\Template\Snippet;
use Kirby\Toolkit\Str;
class SnippetWithController extends Snippet
{
protected static $controllers = [];
public static function controller(
string|null $file,
array $data = []
): array {
if (
$file === null ||
str_starts_with($file, static::root()) === false
) {
return $data;
}
if (isset(static::$controllers[$file])) {
return array_replace_recursive(
$data,
static::$controllers[$file]
);
}
$name = ltrim(Str::before(Str::after($file, static::root()), '.php'), '/');
// if the snippet has a name, we can load the controller
// and merge the data with the controller's data
if ($name !== null) {
$data = array_replace_recursive(
$data,
static::$controllers[$file] = App::instance()->controller('snippets/' . $name, $data)
);
}
return $data;
}
public static function factory(
string|array|null $name,
array $data = [],
bool $slots = false
): static|string {
$file = $name !== null ? static::file($name) : null;
$data = static::controller($file, $data);
return parent::factory($name, $data, $slots);
}
public function render(array $data = [], array $slots = []): string
{
$data = array_replace_recursive(
static::controller($this->file, $data),
$data
);
return parent::render($data, $slots);
}
}
App::plugin('getkirby/snippet-controllers', [
'components' => [
'snippet' => function (
App $kirby,
string|array|null $name,
array $data = [],
bool $slots = false
): Snippet|string {
return SnippetWithController::factory($name, $data, $slots);
},
]
]);
stats field and section as well as the k-stats/k-stat components) now support passing a drawer instead of a link or dialog #7472<k-stats-field> component #7389Kirby\Cms\License::delete() and Kirby\Cms\License::root() #7211
github.com/getkirby/kirby/issues/6960)LanguageVariable::language() method #7379Kirby\Panel\Ui\Stat and Kirby\Panel\Ui\Statsbackend components, which are used to create the correct information for the <k-stat>/<k-stats> Vue component #7373 #7374controller class name or closure hat returns an object with ::load() and ::submit() methods that will be used then as load/submit event actions. Ideally used with returning a Kirby\Panel\Controller\Dialog/Kirby\Panel\Controller\Drawer object. If the named class also defines a static ::for() method, it will be used to create an instance of the class.<k-label> component now also accepts false for the input prop. This will switch the label element to an h2 and also remove the <abbr> for the invalid state. All fields that don't store any values will need this. We can also use it for the info field, which did still create its own headline.Kirby\Panel\Collector\PagesCollector classKirby\Panel\Collector\FilesCollector classKirby\Panel\Collector\UsersCollector classKirby\Panel\Ui\Upload class to handle upload settings in sections and potentially also in fields #7436<k-item> component for a model, such as text, info, image, link, etc. #7456
Kirby\Panel\Ui\Item\FileItemKirby\Panel\Ui\Item\ModelItemKirby\Panel\Ui\Item\PageItemKirby\Panel\Ui\Item\UserItemUuid::toUrl() method that returns the model's absolute URL and includes query and/or fragment that was included in the UUID uri #7484Page::uuid(), Site::uuid(), File::uuid() and User::uuid() #7484closed listener for Panel dialogs and drawers that gets called after the dialog has been closed #7519Kirby\Uuid\Uuid::is() now accepts an array of multiple types to test against #7543Kirby\Http\Query::merge() and Kirby\Http\Params::merge() methods #7546currentColor isn't enforced as fill for all SVGs anymore (only for .k-icon) #7297Kirby\Panel\Ui\Component::render() now only filters out props that are null, not empty arrays #7384h2 that easily bled into component rules.Kirby\Http\Response would falsely converted to a Kirby\Http\Response object #7478max value #7417link KirbyTag when using a UUID #7477::url() method of PageUuid and FileUUid has been renamed to ::toPermalink() and will be removed in a future release. #7484im thumbs driver option has been deprecated. Use imagick instead. #6754Kirby\Http\Router::find(): Passing $ignore = null has been deprecated (pass an empty array or omit the argument instead) #7547App::controller() to return controllers nested in subfolders inside site/controllers #7368<k-stats-section> to <k-stats> #7376<k-stats>stats field uses the new Kirby\Panel\Ui\Stat and Kirby\Panel\Ui\Stats classes to clean up the props generation for the frontend.Kirby\Form\Mixin Traits for after, autofocus, before, help, icon, label, placeholder and width props #7396list settings for table layouts in Kirby\Panel\Model::image() #7449::pickerData() methods and in the Kirby\Panel\Controller\Search controller to clean up all places where such item props are created. #7457Kirby\Http\Response object to Kirby\Cms\Responder::send(). #7478splitVendorChunkPlugin. #7354$mock->addMethods() in unit tests #7356Kirby\Database package #7318<k-stats>Kirby\Http classes #7547query.runner config option
Kirby offers a new runner for its query syntax based on parsing the query as abstract syntax tree. This runner is more reliable and efficient than the rudimentary legacy runner (which in Kirby 5 remains the default). The new runner is currently in its beta phase. You can activate it by setting the query.runner config option:
<?php
use Kirby\Query\Runners\DefaultRunner;
return [
'query.runner' => DefaultRunner::class
];
Query syntax
When using the new query runner, you can also use logical, comparison and math operators in your queries as well as receive arguments in closures:
// new operators
$query = new Query('age > 25 && name != "John"');
$query = new Query('price + vat');
// arguments in query closures
$query = new Query('(foo) => foo.homer');
$data = [];
$bar = $query->resolve($data);
$bar = $bar(['homer' => 'simpson']);
$this->assertSame('simpson', $bar);
Queries will still be tried to resolve first directly from the data context, e.g. when your query is null and your data ['null' => 'foo'] the result will directly be 'foo'. Same for user.username and ['user.username' => 'foo'].
Add the correct mime type for the markdown extension in Mime::$types #7502
Mime::$types #7502ModelWithContent::save() now consistently uses the current language, not default language, if not provided explicitly #7487Add support for refresh-based redirects in Panel #7429
k-items when general sortable prop is true but individual items do not specify their own sortable key #7390Export Vue’s reactive method for Panel plugins #7352 (thx @johannschopplich)
Updated translations: fr, is_IS, pt_BR, pt_PT
fr, is_IS, pt_BR, pt_PTsortable state of files sections to the file dropdown to correctly disable the sorting option. #7334@ #7315Panel::url() throwing when called with default args #7344 (thanks to @rasteiner)Kirby 5 is here! 🚀 Full release notes: https://getkirby.com/releases/5
Kirby 5 is here! 🚀
Full release notes: https://getkirby.com/releases/5
https://getkirby.com/releases/5
https://getkirby.com/releases/5
$kirby→root('licenses')) (Thanks @nilshoerrmann) #6767IsFile::assetFactory() method to create a new asset instance based on the file type, but without adding it to the property cache. This enhancement is related to the bug fix for #7289F::type() does no longer interpret .tmp as valid file extension, but uses mime detection to get the correct type.File::create() does no longer throw a missing extension error #7289File::create() does no longer remove the content file of an existing file if a duplicate error is thrown.WeakMap for VersionCache to avoid cache collisions due to a behavior in spl_object_hash that will sometimes reuse cache ids for new instances. #7302https://getkirby.com/releases/5
https://getkirby.com/releases/5
$force argument for Kirby\Form\Fields::submit() and Kirby\Form\Form::submit() to submit any value, even if the field is disabled, inactive or not translatable. #7283 This enhancement is related to the regression fix for disabled fields (see below)Cmd+S doesn't re-submit the dialog when its already submitting #7258false as label value to <k-field> will no longer throw a console error. We use this in the new <k-entries-field> to disable labels for nested fields.<k-entries-field> checks for a valid array as given value and will no longer throw a console error if null is passed. #7265extends #7253Kirby\Cms\ModelWithContent::update() will accept disabled fields again, unless $validate is switched on. #7268You can use Kirby\Content\Content::update() again to update a content object in memory. As before, this will not write anything to disk, but will only assign temporary content values that might be useful in a template, controller or other parts of your code. With this change, updating content in structures, blocks or entry fields will work as expected. With our new v5 content architecture, you have to adapt your code slightly though if you update content objects of models (pages, users, files, site). The content objects in models are longer cached and you can only keep on working with the updated objects if you assign them to a variable and work with that. #7285 #7250
$page->title();
// Foo
$page->content()->update([
'title' => 'Bar'
]);
$page->title();
// Bar
$page->title();
// Foo
$content = $page->content()->update([
'title' => 'Bar'
]);
$page->title();
// Foo
$content->title();
// Bar
https://getkirby.com/releases/5
https://getkirby.com/releases/5
The following enhancements have been made to fix file upload regressions:
TextareaInput.restoreSelection() methodpanel.upload.announce() method, which sends the success notification and model.update event after uploads have successfully completed.file.upload.error event for every file that could not be uploaded.insertinsertFileinsertUploadprependtogglewrappanel.content.save() now calls panel.content.cancelSaving() to make sure that any old scheduled save requests are properly
cancelled. This could have lead to potential race conditions before.FilesField no longer sends unnecessary file.upload and model.update emitters after upload. Those lead to duplicate section reload requests so far. After uploads, the panel.upload.done() already takes care of reloading the current view and all its sections.TextareaInput.insertUpload() method now uses await panel.content.update() to push text value changes directly to the changes API and to reload the view correctly. This fixes #7249file.upload event directly when a file has been uploaded and passes the file object correctly. Before this change, the file.upload event was only called in the FilesField and FilesSection components when all uploads finished.upload.done() and upload.cancel() handlers now properly emit the complete event if there are any completed uploads.HasMethods::hasMethod() public again #7266TextareaInput.restoreSelectionCallback() Use TextareaInput.restoreSelection().TextareaInput.selectionRange and TextareaInput.restoreSelection() are used to replace the old restoreSelectionCallback method in dialog events for better async control.FilesSection. The upload module already takes care of the notifications and events.> This breaking change is not adding to the list of breaking changes in the final release notes. This change was necessary to fix the new preview URLs…
https://getkirby.com/releases/5
Uri class now properly serializes URIs of the form /subfolder/. #7255Change the underlying logic for preview tokens (breaking preview URLs created in previous v5 pre-releases). #7256
[!NOTE] This breaking change is not adding to the list of breaking changes in the final release notes. This change was necessary to fix the new preview URLs before the final release. You are only affected if you used a v5 pre-release in production.
https://getkirby.com/releases/5
https://getkirby.com/releases/5
page.changeTitle and page.changeSlug hooks receive a new optional $language parameter, which passes a full Language object. #7227$filename arguments for Asset::mediaPath(), Asset::mediaUrl() and Asset::mediaRoot() to keep the Asset class consistent with the v5 changes in the File class #7241_preview param for preview iframe URLs. This new parameter can now be used in the frontend to adjust the UI for when being shown inside Panel preview view. #7225Page or the Site or the slug for a Page (in a secondary language) , the ::changeTitle() and ::changeSlug() methods will check for an existing changes version and store them there as well. Otherwise, the changed title or slug would get reverted as soon as the changes version is published. #7227File, the File::changeSort(), the method will check for an existing changesversion and store it there as well. Otherwise, the changed sorting number would get lost as soon as the changes are published. #7230Asset::mediaDir() method. Thumbnails for assets can now be generated properly again. https://github.com/getkirby/kirby/issues/7238Kirby\Form\Field and Kirby\Form\FieldClass normalize type and name attributes and set the name to lowercase. This will now bring back the default column setup in structure fields if you use camelCase or anything else than lowercase for field names. #7236Support for named parameters in Form constructor. Passing the $props array is still supported but deprecated. #7166
https://getkirby.com/releases/5
We are only listing the differences here from previous betas. For the full changelog for v5, please check out: https://getkirby.com/releases/5/changelog
Model::versions() method, which returns an array with the two versions latest and changes. If there's no changes version, the latest will be used. #7153Version::sibling() method to fetch a different version for the same model #7161Fields::passthrough() will resolve closure values (just like fill and submit) #7164$props array is still supported but deprecated. #7166Form::for(). Passing the $props array is still supported here as well, but also deprecated. #7166panel.content.changes() has been renamed to panel.content.diff()panel.content.hasDiff() method.panel.content.version(versionId) methodpanel.content.versions() methodcontentand original props have been removed from all model views.versions prop has been added instead with latest and changes as child objects.changes property in the <k-model-tabs> component has been renamed to diff.https://github.com/user-attachments/assets/8f98d08d-c149-4e8a-89c9-7591323f6ae3
false to disable view buttons ****[#7139](https://github.com/getkirby/kirby/issues/7139)Fields::passthrough() method no longer supports passing an empty array to reset all passthrough values. [#7164](https://github.com/getkirby/kirby/pull/7164)LC_MESSAGES constant check [#7224](https://github.com/getkirby/kirby/pull/7224)content prop has been removed from all model views.Kirby\Content\Version::prepareForContent() again [#7192](https://github.com/getkirby/kirby/pull/7192)preview as icon and Preview as text. [#7220](https://github.com/getkirby/kirby/pull/7220)OpenButton instead of the PreviewButton and the refactored PreviewButton in addition to that. [#7220](https://github.com/getkirby/kirby/pull/7220)PreviewDropdownButton has been removed [#7220](https://github.com/getkirby/kirby/pull/7220)Kirby\Panel\Model::content() is deprecated. Use Model::versions()[’changes’] instead. [#7153](https://github.com/getkirby/kirby/pull/7153)Form::content() is deprecated. Use Form::toStoredValues() instead. [#7166](https://github.com/getkirby/kirby/pull/7166)Form::data() is deprecated. Use Form::toStoredValues() instead. [#7166](https://github.com/getkirby/kirby/pull/7166)Form::strings() is deprecated. Use Form::toStoredValues() instead. [#7166](https://github.com/getkirby/kirby/pull/7166)Form::values() is deprecated. Use Form::toFormValues() instead. [#7166](https://github.com/getkirby/kirby/pull/7166)$defaults argument from form and field methods wherever possible, to clean up default value handling [#7134](https://github.com/getkirby/kirby/pull/7134)
Field::toFormValueField::toStoredValueFieldClass::toFormValueFieldClass::toStoredValueFields::toFormValuesFields::toStoredValuesForm::toFormValuesForm::toStoredValuesFields::for method to simplify the ModelWithContent::createDefaultContent method and get rid of the Form class usage. [#7149](https://github.com/getkirby/kirby/pull/7149)Version::errors() method [#7155](https://github.com/getkirby/kirby/pull/7155)Version::isValid() method, which is now used in ModelWithContent::isValid() instead of the Form class. [#7155](https://github.com/getkirby/kirby/pull/7155)Pre-release notes: https://getkirby.com/releases/5
Pre-release notes: https://getkirby.com/releases/5
Fields::validate() methodForm::validate() method, which is a proxy for Fields::validate()Form::validate() in ModelWithContent::update()::isTranslatable($language) method for Field and FieldClass::extendModels() method in HasModels trait.::isSubmittable method for Field and FieldClassFieldClass::fill() now returns static instead of void. This no longer introduces a difference to the Field class and also makes ::fill() chainable, which can be handy.Required methods and properties are now moved to the Validation mixin::fill() is no longer setting a null default value, which makes no sense.Field::fill() method when no computed properties exist. #7113:fill() method call #7113App::$events initialization #7121Kirby\Blueprint classes have been removed. Those classes never were involved in rendering Blueprints. We used a small part of it for the field options, but had them mostly in there in preparation for a Blueprint code refactoring that never happend as planned. The removal should not cause any damage, because the code was internal and never useful for plugins. But we still want to mention it here. #7119value and default. Public access to properties has not been documented or encouraged anywhere, so it technically should not have been used anyway. #7123::isSaveable has been renamed to ::hasValue in the FieldClass class. #7125k-panel-menu: simplify gap #7108::isSaveable has been renamed to ::hasValue in all form classes. #7125Pre-release notes: https://getkirby.com/releases/5
Pre-release notes: https://getkirby.com/releases/5
Vue bundle accessible as JS Import map #7107A::get() instead of the is_array check. Results in a 2% improvement of total execution time according to tests by @bnomei https://github.com/getkirby/kirby/issues/7096A::get() no longer accepts a first argument that is not an arraycircle-outline. Use circle insteadcircle-funnel. Use filter insteadheart-outline. Use heart insteadimage-outline. Use image insteadKirby\Content\Content::update() is actively deprecated and must no longer be used. It will throw an exception to find usage early on.
Pre-release notes: https://getkirby.com/releases/5
::toEntries() field method #6993 for the new Entries field.<ul>
<?php foreach ($page->myEntries()->toEntries() as $entry): ?>
<li><?= $entry->upper() ?></li>
<?php endforeach ?>
</ul>
ExceptionField class #7002accessibilityaicloudinfo-cardkirbyrocketrssshieldshut-downterminalwallet$model->versions() method returning a versions collection (currently changes and latest) #7059Language::is() method to compare Language objectsVersion::delete('*')PlainTextStorage::isSameStorageLocation() implementation, which compares text file locations for more accurate results.ModelWithContent::changeStorage() has a new second, boolean $copy argument, which is false by default. Storage is thus moved by default, but can be copied on demand.ModelWithContent::save() and ModelWithContent::convertTo() use that new $copy flag to create a fully in-memory copy for the old instance.k-item: fix non-selectable state #7024User::delete() will now properly call file.delete hooks for deleted user files.::update calls in hooks #6869pages.preview permission againKirby\Form\Form::exceptionField() #7002$page::translation() returns a single translation in single language mode. This is also included in the $page::toArray() method$page::translation() returns a new Kirby\Content\Translation object instead of the old Kirby\Content\ContentTranslation object.Kirby\Content\ContentTranslation class has been removed and repalced with Kirby\Content\Translation$page::translations() returns a new Kirby\Content\Translations collection instead of a generic Kirby\Content\Collection It will always include at least one language - even in single language mode.Kirby\Content\Content::update() is actively deprecated and must no longer be used. It will throw an exception to find usage early on.ModelWithContent::$content and ModelWithContent::$translations cache props have been removed.User::create() does no longer accept null as argument.User::update does no longer have any effect. Use User::changeName() instead.HasMethods::hasMethod() and HasMethods::callMethod() are now protected methods #7058ModelWithContent::versions() is no longer available as direct field accessor. You need to use $model->content()->versions() instead if you are using a field with the name versions. #7059$originalEvent parameters for App::apply() and App::trigger() have been removed as they are no longer used in the core.ModelWithContent::readContent: Use $model->version()->read() instead #7013ModelWithContent::writeContent Use $model->version()->write() instead #7013Page::factory() method is always lowercasePage::model() is always lowercase::setBlueprint in Model constructors before setting contentPage::updateParentCollections in the ::commit method and remove redundant calls.::updateParentCollection methods to FileActions and UserActions and use them in their commit methodsUser:: with static:: in user actions.Pages/PagesMethodsTest.phpHasModels traitApp::setSite() is now public and can be used to overwrite the current site instancePage::normalizeProps()File::noramlizeProps()User::normalizeProps()ModelWithContent::changeStorage() method.Kirby\Cms\ModelCommit classKirby\Cms\ModelState classModelCommit class in all action classesKirby\Cms\Collection::update($object) methodKirby\Cms\Events class that handles low-level hook executionKirby\Content\Translation have been undeprecated because they turn out to be useful
::code()::content()::exists()Kirby\Content\PlainTextStorage handlerUser::delete(), Page::delete() and File::delete() to delete the Versions properly@see tag consistency in the core codeColor field: the text => value notation for options has been deprecated and will be removed in Kirby 6. Please rewrite your options as value => text.…
Pre-release notes: https://getkirby.com/releases/5
entries fieldNew option for pages and files sections, to delete multiple files or pages at once https://kirby.nolt.io/38
In addition to audio and video files, we've now also added a PDF preview to the core:
site.rss.php #6950Kirby\Cms\Pages::delete(array $ids) and Kirby\Cms\Files::delete(array $ids) methods to handle batch delete for multiple files in a collection.selectable property for the <k-item> and <k-items> components. When set to true, the items show checkboxes and emit an select event, when the checkbox is clicked.files and pages sections introduce new delete API endpoints. Those endpoints can take a set of page or file ids and will delete each one. Errors will be caught and sent back in the details array of the final thrown exception.name: true notation #6928date handler for changes timestamp #6937api.methodOverwrite option has been renamed to api.methodOverridetext => value notation for options has been deprecated and will be removed in Kirby 6. Please rewrite your options as value => text. #6913panel.favicon option throws deprecation warnings for url option (use href instead) and for rel key (use reloption instead)
Pre-release notes: https://getkirby.com/releases/5
buttons: falseApp::storage(ModelWithContent $model) methodstorage component, which can be overwritten in plugins or the app instance setup.// How to create a new default storage instance component:
use Kirby\Cms\App;
use Kirby\Cms\ModelWithContent;
use Kirby\Content\PlainTextStorage;
class MyCustomStorageClass extends PlainTextStorage
{
}
// on app initialisation
$kirby = new App([
'components' => [
'storage' => function (App $kirby, ModelWithContent $model) {
return MyCustomStorageClass($model);
]
]
]);
// in a plugin
App::plugin('my/storage', [
'components' => [
'storage' => function (App $kirby, ModelWithContent $model) {
return MyCustomStorageClass($model);
]
]
]);
$app->role() method that works like $app->user() to return a specific role or the role of the current user. #6874Panel\Ui\Button: i18n support for text and title propsPanel\Ui\Buttons\ViewButtons and Panel\Ui\Buttons\ViewButton have new optional $model propertyPanel\Ui\Buttons\ViewButton for link, dialog, drawer, icon, text, theme propsbuttons:
- preview
retour:
text: Retour
This first looks up k-retour-view-button and falls back to k-view-button.inline: true in their button definition are displayed as inline buttons in toolbar (instead inside the dropdown) #6902this.$helper.object.filter(object, predicate). #6902title #6911link, dialog and drawer props #6896Str::ucfirst() behavior, now behaves like PHP default #6834isEmpty() usage #6898Str::ucfirst() method no longer lowercases all but the first letter of the text, it only capitalizes the first letter. #6860ModelPermissions need to set their category with the const CATEGORY or static function category() instead of protected string $category and use the static user() method instead of $user and $permissions properties #6880<k-item>: Removed data-only-option attributes<k-dialog>: Removed data-has-footer attribute<k-toggles-input>: Removed data-disabled attribute<k-writer-input>: Removed data-toolbar-inline attribute<k-bubble>: Removed data-has-text attribute<k-header>: Removed data-has-buttons attribute<k-tag>: Removed data-has-image and data-has-toggle attributes<k-tree>: Removed data-has-subtree attributerequired: true on checkbox and toggle fields now enforces that these fields need to be checked/toggles (active state)panel.favicon option throws deprecation warnings for url option (use href instead) and for rel key (use reloption instead)ModelPermissions now also supports Language objects as quasi models #6876LanguagePermissions class that inherits the existing logic from LanguageRules for consistency with other models #6876access and list permissions per permission category, model type and user role to reduce code duplication #6881$app->roles() method to the AppUsers trait to increase the overviewPre-release notes: https://getkirby.com/releases/5
Pre-release notes: https://getkirby.com/releases/5
Pre-release notes: https://getkirby.com/buzz/v5-alpha
Pre-release notes: https://getkirby.com/buzz/v5-alpha
Pre-release notes: https://getkirby.com/buzz/v5-alpha
Pre-release notes: https://getkirby.com/buzz/v5-alpha
Pre-release notes: https://getkirby.com/buzz/v5-alpha
Pre-release notes: https://getkirby.com/buzz/v5-alpha
Pre-release notes: https://getkirby.com/buzz/v5-alpha
Pre-release notes: https://getkirby.com/buzz/v5-alpha
## 🚨 Security - Updated Symfony YAML library
> [!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https:/…
[!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https://getkirby.com/buzz/security-update
This is a backport of our security release for Kirby 5. For all details and vulnerabilities see: https://github.com/getkirby/kirby/releases/tag/5.6.0
We recommend all users upgrade to Kirby 5. If an upgrade is not possible, this security release is the alternative solution.
> [!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https:/…
[!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https://getkirby.com/buzz/security-update
This is a backport of our security release for Kirby 5. For all details and vulnerabilities see: https://github.com/getkirby/kirby/releases/tag/5.5.2
We recommend all users upgrade to Kirby 5. If an upgrade is not possible, this security release is the alternative solution.
> [!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https:/…
[!NOTE] This release is part of our monthly security release series. Find out more about those releases and their background on our website: https://getkirby.com/buzz/security-update
This is a backport of our security release for Kirby 5. For all details and vulnerabilities see: https://github.com/getkirby/kirby/releases/tag/5.4.4
We recommend all users upgrade to Kirby 5. If an upgrade is not possible, this security release is the alternative solution.
One column per quarter.