We wrapped up 2.4.1 with a lot of bug fixes and improvements for 2.4. Thanks for all your feedback. It has really helped us tremendously to find undetected issues and add some nice small improvements. We recommend this update to all users. As always you can either download it from our server: https://download.getkirby.com, get it from Github: https://github.com/getkirby/kirby & https://github.com/getkirby/panel, or use the CLI to update by running
Here’s the official change log entry: https://getkirby.com/changelog/kirby-2-4-1
Fixed broken visible/invisible switch
I have upgraded to Kirby 2.4.1 mainly to get this issue sorted.
However, even after the upgrade the “Visible” option is not there.
There is no visible option, to make the page visible, you have to choose a number.
There used to be as far as I remember in previous versions?
Sorry but it is inappropriate to be using such a method. There are over 400 subpages - how would it make sense having to scroll down a list of over 400 entries?
*The website at question is a news portal where categories just keep growing and growing.
Hm, I don’t remember, really, need to check. From which version did you upgrade?
If ordering isn’t important, set the
num option on the parent blueprint to
If it’s an article that you want to sort by date, use
num: date instead.
With these options you’ll be able to simply toggle between visible/invisible without seeing that long list of numbers.
For more info check out: https://getkirby.com/docs/panel/blueprints/subpages-settings#numbering-of-subpages
Thank you for the reply Pedro.
The above would not be a realistic solution as the articles still need to be sorted in the order they are posted rather than alphabetically.
Numbering by date would be more appropriate - however I cannot get this to work.
I have tried both “zero” and “date” and then I’ve added some test articles in a new category.
These, however, are still using the default numbering sorting.
title: Article - Text
*EDIT: You are right Pedro. I’ve misplaced the code. Thank you (ran out of replies)
This option should be added to the parent blueprint. It looks like you added it to the child page.