What plugins do you miss?

[bnomei]

the deed is done: Plugin: InstagramAPI – Endpoints access (BETA)

edit: fixed link. thanks @luxlogica

[distantnative]

Global panel media – something like this, @jenstornell?

First proof of concept: https://github.com/distantnative/panel-media

[jenstornell]

Yes. I have already created a plugin like this myself, but I never released it because of a Kirby bug https://github.com/getkirby/panel/issues/959.

My plugin is a field to be used in site (panel options). It looks like you have taken a different approach, maybe a better one.

Anyway, when I built my plugin there was two things I thought about:

• Cache 300 nested pages with 10 images on each page is 3000 images scatterd through folder. Could it be slow? It needs to search for all the files in all the pages on every refresh. I was about to create a kind of an index using hooks when a file was changed or a page was renamed/deleted. Do you see the need for a cache or is it fast enough?
• Sorting. You sort by page which is great as a default. It could also make sense to sort by filename and modified. Filename is good when want to find duplicates of images visually (even if there are other tools for that as well). Modified is good to see which images was added recently. What do you think about a sorting feature?

Anyway, it looks like a really good start and it would be nice to kill my proof of concept and let you build this thing.

[distantnative]

@jenstornell

My plugin is a field to be used in site (panel options). It looks like you have taken a different approach, maybe a better one.

Indeed, I used this one as a case study for a plugin’s custom panel view (and it worked!). You do not need to add anything to a blueprint as with fields. Only I could not yet find a way to add a button to the dropdown menu and hence need to rely on widgets as buttons/ways to the panel view. I used it for the new config panel view of the panelBar.

@jenstornell

Cache 300 nested pages with 10 images on each page is 3000 images scatterd through folder. Could it be slow? It needs to search for all the files in all the pages on every refresh. I was about to create a kind of an index using hooks when a file was changed or a page was renamed/deleted. Do you see the need for a cache or is it fast enough?

There would definitely be the need for something like this. Calling $site->index()->files() gets slow quite easily, with much less pages and files then you mention.

@jenstornell

Sorting. You sort by page which is great as a default. It could also make sense to sort by filename and modified. Filename is good when want to find duplicates of images visually (even if there are other tools for that as well). Modified is good to see which images was added recently. What do you think about a sorting feature?

Reasonable ideas, in my view. Good thing with this solution: you get your custom panel view, which really is like a blank slate in the panel. You can do pretty much anything you want. Include custom CSS, JS…

Given my limited time, I am not sure if I will manage to work on any of these features. Priority lies on my plugins. But of course I would be happy to see PRs. I think this proof of concept shows in a quite simple way how to create and use such a custom panel view (workaround, since it is not really easily supported, but this workaround works pretty well so far).

[jimbobrjames]

Off the top of my head, I would like the following in Kirby:

1. Batch content modification - deletion, status changes, moving content between sections
2. Easier way to build menus without going through several each loops.
3. Ability to add metadata to multimedia files from within the panel.

[flokosiol]

@jimbobrjames

Ability to add metadata to multimedia files from within the panel.

This is possible with file fields. Or do you mean something different?

[jimbobrjames]

Ah HA! I did not know you could do that. I understood from the docs that adding information like captions to videos and images was limited to manually add text files outside of the panel. Thanks for the tip.

[texnixe]

@distantnative

custom panel view (and it worked!)

Nice, my logger plugin uses a custom panel view as well (as do two or three other plugins), but I have now refactored the code base based on yours, looks a bit cleaner now.

Yes, would be nice to be able to add such custom views to the menu instead of having to create a widget every time.

[jenstornell]

@texnixe @distantnative

It seems to be very useful. A long time ago I made a very simple admin page. @flokosiol updated it a bit.

Proof of concept - Panel admin pages

It is currently not possible to change the sidebar, main or add a new admin page to the panel. Admin panel page workaround It is possible to add an admin panel page like the image below by using a panel field. Create a page in the panel Add a blueprint for it Add a field with your tool (or what it might bee) Hide stuff with CSS if needed [image] Blueprint <?php if(!defined('KIRBY')) exit ?> title: Home pages: false files: false fields: title: label: Title type: text page: …

Anyway, maybe it will be a panel core feature in the future, who knows. Until then, maybe it could be nice to have some kind of a boilerplate plugin that only includes custom panel views?

If there is not time for it it’s fine, just wanted to drop the idea.

[texnixe]

@jenstornell

could be nice to have some kind of a boilerplate plugin

The Panel Media plugin in its current state is actually the perfect boilerplate as it does not have any complex logic in it yet.

@jenstornell

Anyway, maybe it will be a panel core feature in the future, who knows.

I think it will be at one time or the other.

[jenstornell]

You are probably right @texnixe. Maybe break it out and place it in a new repo before it gets complex then @distantnative?

[bnomei]

just in case someone wishes for newsletter plugin with panel support but did not dare to speak up. here it is…

Plugin: Mailjet

This php helper class allows you to send transactional emails, as well as test and publish newletters. In combination with my Kirby Opener Plugin you can do all that from within the Panel. An example template and controller are provided to help you getting started with styling your own emails using Tim Ötting’s Kirby Builder @timoetting , the responsive email markup language mjml and the logic-less templating language Mustache PHP. But if you have your own toolchain to create responsive HTML…

[jenstornell]

Even if this post is great to see what everyone wishes for, it’s a bit hard to follow. Some write in the wiki-post and others write ideas in the comments. On top of that there is a discussion. I’m not judging anyone but I think that it could be improved.

Kirby Plugin Wishlist - Released!

Today I’ve released the repository Kirby Plugin Wishlist. I’ve copied all the plugin ideas into that repository so everything exists there as well. Some plugin ideas was solved so I added these as closed issues.

I think it will be much easier to maintain similar to Kirby Plugins.

It’s using Github issues which has many benefits:

• One plugin idea is one issue
• Open/closed depending on if the idea is still relevant
• Tags for filtering
• Search
• Comments on each plugin idea

[jenstornell]

Good start for Kirby Plugin Wishlist repository

I really think the new repository Kirby Plugin Wishlist got a good start.

It has interesting discussions like the one about menus.

New plugins

It also got birth to new plugins, a table field #20 and a social button plugin #14 (screenshots inside).

The new plugins are called Kirby Tablex and Kirby Sharingbuttons.

Nice work guys!

[krisa]

Hold on Jens. Now i have to update the docs and screenshots! Ouch

[flokosiol]

Yes

I really liked the idea of having a Github repo for plugin wishes instead of having one large topic at the forum. You can easily search and find proposals and stuff like that.

But

But I think it moves the discussion away from the forum. Discussing on Github is great and important (in principle) when it comes to technical stuff concerning plugins or issues, but I think it would be better, if the initial discussion about new plugins and ideas takes place here.

So

In my opinion it would be great if there would be a new subcategory “idea” inside the plugins category, just like the discontinued one. We could then open a topic for each new idea and start discussion without mixing topics.

Please don’t get me wrong @jenstornell – I really appreciate your effort. But I think it would lead to better discussions because more people would be involved (I guess).

What do you think?

/cc @texnixe @lukasbestle

[texnixe]

That’s actually a pretty good idea, @flokosiol.

[jenstornell]

@flokosiol Yes, I’ve noticed that too. I tend to agree with you but I want to see how it works out first, but I think we could try.

What I think we could lose with the forum is:

• The possibility to close a topic. Only the crew can lock conversations. That’s needed if the case is solved and the idea became a plugin. A solution for it is to have like Plugin - Idea - Solved or something but I guess it’s too much?
• Search. While we can search the forum it’s a bit harder to narrow down to plugin ideas than on Github because on Github everything is plugin ideas.
• Filter with tags does not exists in the forum as far as I know.

But I agree on the main reason that it’s nice to have all involved in the discussion.

I think we should try but I will keep my repository until I’m sure that this is a good idea.

[texnixe]

Hi everyone,

the new Plugin ideas category - as suggested by @flokosiol - is born. I also think that it makes more sense to have discussions regarding plugins here in the forum…

Sonja

[jenstornell]

Alright. I’ll keep my repo until I’m sure this is the best way. To get started I looked into the advanced search and here are some findings for the lazy people…

To list all the plugin ideas, the search query looks like this:

#plugins:ideas

or https://forum.getkirby.com/search?q=%23plugins%3Aideas

It’s also possible to search by keywords like this:

#plugins:ideas relationship

…or by user

#plugins:ideas @ola

The most important thing that I miss compared to Github is the option to close a post when the plugin idea is developed into a plugin. That plugin would probably have an own post and the plugin idea post would not be needed anymore. With my access I can’t close or lock posts. I have no idea to solve that problem yet.