# Kirby 2.3.0 Beta

**URL:** <https://forum.getkirby.com/t/kirby-2-3-0-beta/3809>\
**Category:** Announcements\
**Created:** [April 8, 2016, 4:13pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809 "2016-04-08T16:13:54Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Adam](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/adam/32/1836_2.png) [@Adam](https://forum.getkirby.com/u/Adam)\
**Post date:** [April 10, 2016, 6:59pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/21 "2016-04-10T18:59:34Z")

</div>

Custom fields for example [http://getkirby-plugins.com/multiselect-field](http://getkirby-plugins.com/multiselect-field) work partly.  
The $assets parts will not load.

---

<div class="post-metadata">

**Author:** ![fvsch](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/fvsch/32/15908_2.png) [@fvsch](https://forum.getkirby.com/u/fvsch)\
**Post date:** [April 10, 2016, 9:37pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/22 "2016-04-10T21:37:21Z")

</div>

Trying the 2.3 beta on my personal site (no panel, blog-like, ten templates, a few tricks, search, Atom feed forked from the Feed Plugins), and so far nothing breaks. 🙂

I’ve started working on a Twig plugin:

> [@Twig plugin (Kirby 2.3+)](https://forum.getkirby.com/t/experimental-twig-plugin/3823):
>
> So I started working a plugin which enables working with [Twig templates](http://twig.sensiolabs.org/). It requires Kirby’s 2.3.0 beta. Code and documentation here: Compatibility Kirby’s chaining API for pages etc. is quite compatible with Twig Page Models and Controllers should be fully compatible (haven’t checked yet but no reason why it wouldn’t work) Helper functions can be exposed to the templates (e.g. {{ snippet('nav') }}) but we need to list them explicitly, which I’m a bit reluctant to do but hey. (Update: so …

Overriding components seems to be a useful approach but it’s completely undocumented and I had to spend my afternoon reading Kirby’s source code, which is instructive but maybe not all plugin developers should have to do it, I don’t know. Some thoughts on what could be documented on this side?

---

<div class="post-metadata">

**Author:** ![jenstornell](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/jenstornell/32/546_2.png) [@jenstornell](https://forum.getkirby.com/u/jenstornell)\
**Post date:** [April 11, 2016, 10:59am UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/25 "2016-04-11T10:59:41Z")

</div>

Nice! Here are my first impressions…

## Thumbnail API

I was not a big fan of it from the start. It was not getting better because of the issues I’ve got. Maybe I will love it later but now, not so much.

[Kirby 2.3 - Thumbs in other language does not generate](https://forum.getkirby.com/t/kirby-2-3-thumbs-in-other-language-does-not-generate/3822/1)  
[Kirby 2.3 - Thumbnail 404](https://forum.getkirby.com/t/kirby-2-3-thumbnail-404/3821/1)  
[Kirby 2.3 - Real strange thumbnail problem](https://forum.getkirby.com/t/kirby-2-3-real-strange-thumbnail-problem/3820/1)

## What I will probably love

I will probably use these things all the time (have not tested all of them yet):

- New Panel Image Field
- New Plugin registry
- Blueprint options
- Global site controller
- Custom pages::$methods
- Custom page::$methods

## Fieldoptions from another field? Why?

Get fieldoptions from another field? Why not just use blueprint global field definitions? It’s probably not a bad feature. I just don’t fully understand it.

## Upcoming docs

Now the url for the docs summery is:

[https://getkirby.com/upcoming](https://getkirby.com/upcoming)

It’s great today. When it’s released, what will happend to that url? Maybe have something like below?

[https://getkirby.com/2.3](https://getkirby.com/2.3)  
[https://getkirby.com/2.4](https://getkirby.com/2.4)  
[https://getkirby.com/2.5](https://getkirby.com/2.5)

Then we could in the future go back to see what happended in that version.

## Summery

Some of the things I’ve been waiting for are in this version, so I’m really looking forward to try it out. However, the new Thumb API is making trouble for me. If that will work it’s probably going to be an amazing release!

---

<div class="post-metadata">

**Author:** ![lukasbestle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/lukasbestle/32/11437_2.png) [@lukasbestle](https://forum.getkirby.com/u/lukasbestle)\
**Post date:** [April 11, 2016, 12:00pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/26 "2016-04-11T12:00:05Z")

</div>

> [@jenstornell](#):
>
> Get fieldoptions from another field? Why not just use blueprint global field definitions?

Not from another field definition, but from another field on another page (content).

> [@jenstornell](#):
>
> [https://getkirby.com/upcoming](https://getkirby.com/upcoming)
> 
> It’s great today. When it’s released, what will happend to that url?

There’s always the changelog, where all changes are listed for all previous versions.

---

<div class="post-metadata">

**Author:** ![bvdputte](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/bvdputte/32/8179_2.png) [@bvdputte](https://forum.getkirby.com/u/bvdputte)\
**Post date:** [April 14, 2016, 9:05am UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/27 "2016-04-14T09:05:05Z")

</div>

Is there a place I can read up about “components” and “registry” and “plugins”?

They all sound very interesting, but are a bit abstract to me.

Thanks!

---

<div class="post-metadata">

**Author:** ![texnixe](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/texnixe/32/5754_2.png) [@texnixe](https://forum.getkirby.com/u/texnixe)\
**Post date:** [April 14, 2016, 9:41am UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/28 "2016-04-14T09:41:09Z")

</div>

We have not managed to update the docs yet, I’m afraid, so currently, there’s only the source code to the rescue and an example plugin file:

Plugin registry: [https://gist.github.com/bastianallgeier/38f895b32b71e8e2b2f3844e38df5489](https://gist.github.com/bastianallgeier/38f895b32b71e8e2b2f3844e38df5489)

For the component architecture, you can have a look at the Twig plugin by @fvsch: [Twig plugin (Kirby 2.3+)](https://forum.getkirby.com/t/twig-plugin-kirby-2-3/3823) as an example.

---

<div class="post-metadata">

**Author:** ![jenstornell](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/jenstornell/32/546_2.png) [@jenstornell](https://forum.getkirby.com/u/jenstornell)\
**Post date:** [April 14, 2016, 9:43am UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/29 "2016-04-14T09:43:48Z")

</div>

Plugin set registry information can be found here as well:

> [@Register plugin with set?](https://forum.getkirby.com/t/register-plugin-with-set/3827):
>
> This is a [gist](https://gist.github.com/bastianallgeier/38f895b32b71e8e2b2f3844e38df5489) about register plugin stuff with set. I don’t understand how to use it. Let’s say I have this in my plugin: /site/plugins/myplugin/myfield/myfield.php /site/plugins/myplugin/myfield2/myfield2.php /site/plugins/myplugin/myplugin.php The first two rows are two fields that needs to be registered and the last is the plugin init file where I want to register the fields. How is that done in this case? Can I do this and it simply “fake” that the fields are in these places, but they a…

---

<div class="post-metadata">

**Author:** ![fvsch](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/fvsch/32/15908_2.png) [@fvsch](https://forum.getkirby.com/u/fvsch)\
**Post date:** [April 14, 2016, 10:04am UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/30 "2016-04-14T10:04:01Z")

</div>

It would be great to have documentation on components (not necessarily what each component type should do, but at least what they are and how to register one and what it implies), registry, and while we’re at it Kirby is sorely missing an “How to write plugins” documentation page which explains how it works and perhaps gives some “best practices”.

For writing my own component (as a plugin) I had to read Kirby’s source code to figure things out, and pick some information from a handful of gists found via Twitter and this forum.  
Reading the source was interesting but not really straightforward.

---

<div class="post-metadata">

**Author:** ![luxlogica](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/luxlogica/32/437_2.png) [@luxlogica](https://forum.getkirby.com/u/luxlogica)\
**Post date:** [April 14, 2016, 12:55pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/31 "2016-04-14T12:55:56Z")

</div>

> [@fvsch](#):
>
> “How to write plugins” documentation page which explains how it works and perhaps gives some “best practices”.

+1

Yes, please! I know writing docs is a chore, but it pays off…

---

<div class="post-metadata">

**Author:** ![simon2017](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/simon2017/32/7442_2.png) [@simon2017](https://forum.getkirby.com/u/simon2017)\
**Post date:** [April 14, 2016, 1:07pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/32 "2016-04-14T13:07:17Z")

</div>

@fvsch or if you have a Template how to add the Kirby Navigation i hope you know what i mean

---

<div class="post-metadata">

**Author:** ![fvsch](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/fvsch/32/15908_2.png) [@fvsch](https://forum.getkirby.com/u/fvsch)\
**Post date:** [April 14, 2016, 1:11pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/33 "2016-04-14T13:11:58Z")

</div>

The answer to that would be those two steps:

1. Write your menu’s code: [https://getkirby.com/docs/solutions/menus](https://getkirby.com/docs/solutions/menus)
2. Save it as a snippet to reuse it in templates: [https://getkirby.com/docs/templates/snippets](https://getkirby.com/docs/templates/snippets)

---

<div class="post-metadata">

**Author:** ![julieng](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/julieng/32/6770_2.png) [@julieng](https://forum.getkirby.com/u/julieng)\
**Post date:** [April 14, 2016, 1:45pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/34 "2016-04-14T13:45:53Z")

</div>

Wow, nice work. I’ll test it soon.

Special thank for that:

> New global site.php controller can now be used for all pages without a dedicated controller

🍻

---

<div class="post-metadata">

**Author:** ![simon2017](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/simon2017/32/7442_2.png) [@simon2017](https://forum.getkirby.com/u/simon2017)\
**Post date:** [April 14, 2016, 6:38pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/35 "2016-04-14T18:38:43Z")

</div>

Thanks you are a genie 😃

---

<div class="post-metadata">

**Author:** ![anon77445132](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@anon77445132](https://forum.getkirby.com/u/anon77445132)\
**Post date:** [April 16, 2016, 1:38pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/36 "2016-04-16T13:38:41Z")

</div>

@bastianallgeier:  
With the new [blueprint options](https://getkirby.com/docs/panel/blueprints/options) we can change the template of a webpage within the panel. That is fine.  
Or we can disallow the change the template, which is also very fine.

But I want to ask you, if someone disallows this change in a blueprint, to display the name of the template furthermore in the panel. In this case only delete the link to the change template form.

---

<div class="post-metadata">

**Author:** ![lukasbestle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/lukasbestle/32/11437_2.png) [@lukasbestle](https://forum.getkirby.com/u/lukasbestle)\
**Post date:** [April 16, 2016, 3:15pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/37 "2016-04-16T15:15:08Z")

</div>

Split this topic on April 16, 2016, 3:15pm UTC

5 posts were split to a new topic: [Kirby 2.3 beta: Thumbnails of Media objects (e.g. avatars)](https://forum.getkirby.com/t/kirby-2-3-beta-thumbnails-of-media-objects-e-g-avatars/3885)

---

<div class="post-metadata">

**Author:** ![anon77445132](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@anon77445132](https://forum.getkirby.com/u/anon77445132)\
**Post date:** [April 19, 2016, 4:16pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/38 "2016-04-19T16:16:33Z")

</div>

Please before the release of final version 2.3.0 consider the issues and PRs of the starterkit, particular [remove size option from textarea fields, use .yml field extension for blueprints #60](https://github.com/getkirby/starterkit/pull/60) and [Fix #42 again #56](https://github.com/getkirby/starterkit/pull/56)

Thanks.

---

<div class="post-metadata">

**Author:** ![mrflix](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/mrflix/32/14443_2.png) [@mrflix](https://forum.getkirby.com/u/mrflix)\
**Post date:** [April 21, 2016, 9:50am UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/39 "2016-04-21T09:50:12Z")

</div>

# Blueprint Options

Can we have this short option to turn of options all at once and hide the whole Page settings section?

```auto
options: false

```

---

<div class="post-metadata">

**Author:** ![flokosiol](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/flokosiol/32/468_2.png) [@flokosiol](https://forum.getkirby.com/u/flokosiol)\
**Post date:** [April 22, 2016, 1:13pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/40 "2016-04-22T13:13:28Z")

</div>

I played around with the **plugin** system and registered a **blueprint** as described [here](https://gist.github.com/bastianallgeier/38f895b32b71e8e2b2f3844e38df5489).  
Everything works fine if I add the blueprint explicitly to other blueprints like this:

```auto
pages:
  template: 
    - my_plugin_blueprint
    - some
    - other
    - blueprints

```

But all pages with the following setting don’t recognize my plugin blueprint …

```auto
pages: true

```

Is this a bug? Any ideas?

---

<div class="post-metadata">

**Author:** ![anon77445132](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@anon77445132](https://forum.getkirby.com/u/anon77445132)\
**Post date:** [May 1, 2016, 12:17pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/41 "2016-05-01T12:17:40Z")

</div>

Kirby 2.3.0 Beta 2 (2016-04-29 13:50:52) on XAMPP (Apache/2.4.9 (Win32) PHP/5.4.27):

The snippet or template code

```php
<?php echo $avatar->resize(50,50)->url(); ?>

```

produces the adress of the thumb

```php
http://127.0.0.1:61080/kirby_basic/thumbs%5Cassets/avatars/username-42x50.jpg

```

in Firefox 46.0. Then the thumb is not visible in the webpage.

Hint:  
`%5C` is the same as “`\`”, where we need “`/`”.

This issue is the same, if I thumb a normal picture from a page.

Something is wrong.

---

<div class="post-metadata">

**Author:** ![lukasbestle](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/lukasbestle/32/11437_2.png) [@lukasbestle](https://forum.getkirby.com/u/lukasbestle)\
**Post date:** [May 1, 2016, 12:43pm UTC](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809/42 "2016-05-01T12:43:24Z")

</div>

Thanks for reporting. This is a Windows-specific issue. I will fix this and send a PR so it will most likely be fixed in the stable release.

[Previous page](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809.md?page=1)

[Next page](https://forum.getkirby.com/t/kirby-2-3-0-beta/3809.md?page=3)
