Kirby 2.2 public beta

After weeks of work the public beta for Kirby 2.2 is finally available.

It’s a pretty massive new release with a totally rewritten frontend and backend architecture for the panel. I decided to go this way in order to make the panel more extensible and easier to maintain in future releases and put more focus on stability and security. This rewrite is basically the reason why it took so long, but I’m very happy with the result and sure that it has been worth the wait.


It’s the first release for which I managed to make a little video demo of some of the new features. I hope you enjoy it :slight_smile:


You can find the full set of changes in this temporary changelog: Consider the changelog work in progress. I will extend it with examples, docs and code snippets in the next days until the final release.


All testers are very much welcome! Grab it and tear it apart :slight_smile: Especially if you have written a custom form field for the panel, please make sure to give it a try and let me know if something breaks. In case of any bugs or issues, please post it on Github:

How to update/test


The most easy way is to grab the latest version here: and replace your kirby and panel folders. With our updated htaccess file you should also replace that if possible.

Use Git

If you want to use Git and start with a fresh beta version of the starterkit, langkit or plainkit, you can do this:


git clone -b develop --recursive


git clone -b develop --recursive


git clone -b develop --recursive

Updating submodules

If you use Git submodules you can move to the beta like this:

cd kirby
git checkout develop
git pull
git submodule foreach --recursive git checkout develop
git submodule foreach --recursive git pull

cd ../panel
git checkout develop
git pull



I’m super happy about any kind of positive or negative feedback, so please just let me know how you like it or what you don’t like about it.

Thank you

A huge “thank you” to @distantnative for his help over the last weeks!


Sorry about the video quality. Quick Time somehow compressed the video too much and I don’t have time today to reupload it. I will do so tomorrow.

Sorry for bothering: The link keeps downloading 2.1.1. Not 2.2. I know I am too old school for Git.

I’m an idiot :slight_smile: It should be of course :slight_smile:

Congrats @bastianallgeier! Looks like an awesome update!

1 Like

@bastianallgeier looks the video link stopped working. “Page not found.”

The video link works for me …

I re-uploaded the video. Should be working again. Just also realized that I made a ridiculous mistake right in the first sentence. I’m probably not going to become a demo video pro :slight_smile:

@bastianallgeier I wouldn’t have even noticed the mistake. :slight_smile: I just wanted to say that I really appreciate the videos. It’s great to see live demos in addition to change logs and documentation. Super helpful!


Seems like a great update. Will try it out as soon as i have some spare time! And as @iancox already mentioned, I also really like the videos. Great to have a quick overview over the new features!

1 Like

Great update and cool video :slight_smile: Many thanks for all your effort!

Looks really great, but I’m missing permissions for the Panel? :smile:

Hooray, looks awesome!
Just updated my current project in dev and the first thing I recognized in the panel is that fixed save button! Such a win! :slight_smile:

Can’t wait to dive deeper next week! <3

Hm… So I updated the submodules as shown above - But the structure field is missing the nice table layout from the preview video. Anyone else having this issue?

The table layout is an option:

    label: My Structure Field in Table Layout
    type: structure
    style: table

D’oh :laughing: As always thanks @texnixe

This looks like an awesome update :slight_smile: Only thing: The “You have unsaved changes!\n Discard” takes far to much vertical space @bastianallgeier. Maybe you could put the discard-button on the right on the same baseline as the save button, that would be very cool!

If you want, you can do that yourself by setting a custom panel stylesheet in your config.php

c::set('panel.stylesheet', 'assets/css/custom-panel.css');
1 Like

Thanks @texnixe for this tip :slight_smile: But I knew this before. I just thought this should be default, because there are many devices with very limited viewport-heights out there.