Version 1.0.0 - 2016-04-16
What is it?
Kirby Jumplist adds a menu in the upper-right corner of Kirby’s panel, allowing you to quickly jump from page to (sub-)page - thus allowing you to change, edit, copy / paste very quickly between individual pages.
More info about Kirby can be found at http://getkirby.com
- Download the .zip and extract it to the root of your site.
- The jumplist acts as a field, simply add it to every blueprint where you want the jumplist to show up.
\site\blueprints\jumplist_example.php for the basic set-up.
- At default the list shows a maximum of 10 pages per row. You can change this number in
- At default the list shows submenu’s for every page. You can change this behaviour in
\site\config\config_example.php for the setup of those preferences.
Kirby Jumplist - version 1.0.0
very cool! i think this is a good Feature for Kirby i think, thanks a lot for that plugin
I made it the day before yesterday, and can’t do without
I even don’t use the “old” route anymore (click on dashboard, click on page, click on save, click on dashboard, etc…).
do you have create more Kirby Plugins?, i dont find you on GitHub
I created about 25 plugins, but did remove them when Kirby was updated from 2.2 to 2.3 (it broke most of my plugins).
So the plugins on GitHub are the ones that truly works
Does Kirby-Jumplist work with Kirby 2.4.0 ?
I’ve got an error message, Kirby doesn’t find the jumplist field.
I did a quick test and works for me. Have you moved the
jumplist folder from the repo to
I did not test it, yet, with 2.4.0 - still stuck on 2.3.0
But I’ll upgrade tomorrow and let you know.
BTW. you need to include the “field” on every blueprint - it’s a strange mix between a plug-in and a field… so that’s why
(it’s a plug-in, acting like a field - or vice versa)
- edit - Will also update the background-color of a subpage pulldown; it interfierces now with the parents background-color.
The “field cannot be found” error message appears if the field does not exist in the fields folder, or is not registered via a plugin.
The “old” way of creating and adding a field was via the fields folder. Newer fields are often added as a plugin in the plugins folder that registers a field.
I’ve pasted the jumplist folder in /site/fields/
And I’ve added the jumplist field in a blueprint like this:
And I’ve got an exception: “The jumplist field is missing. Please add it to your installed fields or remove it from your blueprint”
That’s weird. Does your folder structure now look like this:
Stupid I am :-/
I pasted all the “jumplist” repository folder.
It’s ok now
I’ve updated the plug-in (it still uses the “old” way of activating plug-ins, 'cause it’s… old )
- Fix where submenu’s could overlap
- Compatibility check with Kirby 2.4.0
- Minor visual adjustments to seperate the (sub-) menu’s
I use your Jumplist menu in a project, some of my pages are hidden (blueprint> hide: true) but these pages appear in my Jumplist menu.
Is there an option to hide these hidden pages in the Jumplist menu ?
good question, I will see if I can fix that
Have you found a solution to hide hidden page in the menu ?
I tried to find a specific class to set a display: none but without success.
Sorry - Kirby development is on some lower level - here
In order to apply some “hidden” tags to the jumplist, I must iterate over the blueprints - I guess.
Those one are the only files that hold this kind of meta-data, and the jumplist does not interact with the blueprints right now.
But feel free to fork / copy / delete my code, it’s free for all / to all!
I understand Thanks for your answer.
It looks like it’s simple to make invisible pages not visible in the jumplist.
foreach($site->pages()->visible() as $page):
I can filter them with
->visible() and the jumplists hides them.
I will update the thing with an optional setting, were one can force hidden pages to be shown, or not.
The update, once ready, will be posted here.
Sorry for the delay, Kirby’s API string is so complex, that I didn’t realize this (well, this chained string is simple - but it has so many options that are not fully or badly documented that I stopped using it…).