# Various Plugins: Tagi Plugins

**URL:** <https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683>\
**Category:** Plugins\
**Created:** [March 14, 2023, 9:12am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683 "2023-03-14T09:12:54Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![aljawaid](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/aljawaid/32/1090_2.png) [@aljawaid](https://kanboard.discourse.group/u/aljawaid)\
**Post date:** [March 16, 2023, 9:20am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/21 "2023-03-16T09:20:39Z")

</div>

agreed, but for github, the repo name IS the folder name… unless you remember to keep renaming your folder before every release.

---

<div class="post-metadata">

**Author:** ![aljawaid](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/aljawaid/32/1090_2.png) [@aljawaid](https://kanboard.discourse.group/u/aljawaid)\
**Post date:** [March 16, 2023, 9:22am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/22 "2023-03-16T09:22:59Z")

</div>

TagiK is confusing for every plugin name to start with. I suggest dropping it. It will confuse users

---

<div class="post-metadata">

**Author:** ![alfredb](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/alfredb/32/1051_2.png) [@alfredb](https://kanboard.discourse.group/u/alfredb)\
**Post date:** [March 16, 2023, 9:36am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/23 "2023-03-16T09:36:05Z")

</div>

> [@aljawaid](#):
>
> but for github, the repo name IS the folder name

Sorry, but I don’t see why. You cannot use the zips created by GitHub anyway.

---

<div class="post-metadata">

**Author:** ![creecros](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/creecros/32/156_2.png) [@creecros](https://kanboard.discourse.group/u/creecros)\
**Post date:** [March 16, 2023, 10:56am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/24 "2023-03-16T10:56:02Z")

</div>

I’m positive that in 2018, [Kanboard.org/plugin.json](http://Kanboard.org/plugin.json) title must match getPluginName in plugin.php to allow update notification in plugin directory.

> <https://github.com/creecros/SendEmailCreator/commit/460467cac188271f0a2afa07bda5dbbeb6e1c5c5>
>
> Corrected to match Kanboard.org/plugin.json to allow update notification in plug…in directory.

and that appears true today. Here is the compare:

> <https://github.com/kanboard/kanboard/blob/ce3e8ca6bb28c6e4ceaee1a5425c2940f71b2443/app/Template/plugin/directory.php#L32>

so…bad things will still happen. Maybe you didnt know what i meant though.

But, you are also correct, folder name matters, repo name means didly squat.

---

<div class="post-metadata">

**Author:** ![Tagirijus](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/tagirijus/32/1528_2.png) [@Tagirijus](https://kanboard.discourse.group/u/Tagirijus)\
**Post date:** [March 16, 2023, 11:17am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/25 "2023-03-16T11:17:02Z")

</div>

> [@aljawaid](#):
>
> TagiK is confusing for every plugin name to start with. I suggest dropping it. It will confuse users

Ouff … well I totally understand and I found it a bit odd myself, to be honest. Still I will look what I can do, but:

1. It took me an hour this morning to rename everything accordingly. 😅
2. I still do not want to have repos named in my Github, which I cannot see directly the connection to. E.g. in this case: it’s a _Kanboard plugin_: TagiKP = TagiKanboardPlugin. So either I find some feature in Github to maybe group such repos … or maybe I will think about it and get used to it in the end anyway.

I will inform you, when I did another renaming!

---

<div class="post-metadata">

**Author:** ![creecros](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/creecros/32/156_2.png) [@creecros](https://kanboard.discourse.group/u/creecros)\
**Post date:** [March 16, 2023, 11:20am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/26 "2023-03-16T11:20:45Z")

</div>

Do you, man.

every name aljawaid suggested to me, i chose the one he hated the most.

Put your mark on the world and be free.

now lets stop shitting up this mans plugin thread.

if it aint broke, dont fix it, and if it is broke, send a PR.

---

<div class="post-metadata">

**Author:** ![aljawaid](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/aljawaid/32/1090_2.png) [@aljawaid](https://kanboard.discourse.group/u/aljawaid)\
**Post date:** [March 16, 2023, 11:49am UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/27 "2023-03-16T11:49:22Z")

</div>

easy sir… I didn’t hate any of your suggestions…

anyhow, it is not up to me, it is not my repo, maybe I am just too open with my suggestions.

---

<div class="post-metadata">

**Author:** ![Tagirijus](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/tagirijus/32/1528_2.png) [@Tagirijus](https://kanboard.discourse.group/u/Tagirijus)\
**Post date:** [March 16, 2023, 12:01pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/28 "2023-03-16T12:01:07Z")

</div>

I just tested on Github to categorize my repos better. The only thing I came up was the _topic_ feature. Still I somehow do not like it to e.g. have a repo called _“HoursView”_ only. Who knows, maybe one day I write a similar plugin for another app and want to call it the same way _(but honestly: very unlikely)_.

Another thing: in the code it’s much better for the eyes to have only _“HoursView”_ instead of _“TagiKPHoursView”_.

What a tiny dilemma, haha. I might still change the names, since it indeed looks a bit more intuitive. There should be an additional _plugin title_ in the `Plugin.php`, which would be used for giving the plugin a more human readable name, after all.

---

<div class="post-metadata">

**Author:** ![creecros](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/creecros/32/156_2.png) [@creecros](https://kanboard.discourse.group/u/creecros)\
**Post date:** [March 16, 2023, 12:02pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/29 "2023-03-16T12:02:06Z")

</div>

sarcasm 101, one day you will pick up on it.

---

<div class="post-metadata">

**Author:** ![alfredb](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/alfredb/32/1051_2.png) [@alfredb](https://kanboard.discourse.group/u/alfredb)\
**Post date:** [March 16, 2023, 12:04pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/30 "2023-03-16T12:04:41Z")

</div>

> [@creecros](#):
>
> now lets stop shitting up this mans plugin thread.

Well said, bro! I’m fully with you.

---

<div class="post-metadata">

**Author:** ![alfredb](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/alfredb/32/1051_2.png) [@alfredb](https://kanboard.discourse.group/u/alfredb)\
**Post date:** [March 16, 2023, 12:06pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/31 "2023-03-16T12:06:23Z")

</div>

> [@Tagirijus](#):
>
> There should be an additional _plugin title_ in the `Plugin.php`

Hell no! There is the description for that purpose.

---

<div class="post-metadata">

**Author:** ![Tagirijus](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/tagirijus/32/1528_2.png) [@Tagirijus](https://kanboard.discourse.group/u/Tagirijus)\
**Post date:** [March 16, 2023, 12:34pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/32 "2023-03-16T12:34:01Z")

</div>

And there I am again, after changing the plugin names (again). Now it should be 100% intuitive. (;

---

<div class="post-metadata">

**Author:** ![aljawaid](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/aljawaid/32/1090_2.png) [@aljawaid](https://kanboard.discourse.group/u/aljawaid)\
**Post date:** [March 16, 2023, 12:53pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/33 "2023-03-16T12:53:20Z")

</div>

throwing clemsonorange oranges at you hahaha

---

<div class="post-metadata">

**Author:** ![FxFx](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/fxfx/32/1358_2.png) [@FxFx](https://kanboard.discourse.group/u/FxFx)\
**Post date:** [March 16, 2023, 12:53pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/34 "2023-03-16T12:53:29Z")

</div>

> [@Tagirijus](#):
>
> Besides that I first have to dig into on how to do configuration sutff: which plugin did you mean?

As far as i understood: this plugin will add “something” directly on the task card. If i’am wrong: never mind 😊

> [@Tagirijus](#):
>
> ## TagiStartedDateOnCard
> 
> This plugin adds the started date on the task card. I used a _play_ symbol for that. If you like to have this play symbol on other places for the started date as well, check out [TagiTaskIcons](https://github.com/Tagirijus/kanboard-TagiTaskIcons) in addition.

> [@Tagirijus](#):
>
> > [@FxFx](#):
> >
> > Is there a difference in sorting compared to this one
> 
> I installed your plugin once and I found it nice! Still I wanted to have the sorting on the **Dashboard** and also I wanted to have two sortings. _1. Sort by due date ASC, while keeping tasks without any due date at the bottom and 2. sort by priority DESC._

I can not judge this. Maybe it makes sense to extened the existing plugin with that function (feel free to contribute if so).

If this is not an option: never mind. Was just an idea, because i fear side effects if both plugins are in use be other users.

Cheers, Fx

---

<div class="post-metadata">

**Author:** ![aljawaid](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/aljawaid/32/1090_2.png) [@aljawaid](https://kanboard.discourse.group/u/aljawaid)\
**Post date:** [March 17, 2023, 12:48pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/35 "2023-03-17T12:48:36Z")

</div>

> <https://github.com/kanboard/website/pull/427>
>
> These are all set to \`remote\_install: false\`

I have added your plugins to the list in the directory. Once merged, they will only show for users of (next release) PluginManager in the new Manual Plugins page.

This way, users will at least have access to your plugins and can decide which ones to manually use if need be.

---

<div class="post-metadata">

**Author:** ![Tagirijus](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/tagirijus/32/1528_2.png) [@Tagirijus](https://kanboard.discourse.group/u/Tagirijus)\
**Post date:** [March 17, 2023, 12:59pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/36 "2023-03-17T12:59:57Z")

</div>

Thank you for adding my plugins to the list. I hope I will remember to update my READMEs then, if the plugins are available via your plugin then! (=

---

<div class="post-metadata">

**Author:** ![aljawaid](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/aljawaid/32/1090_2.png) [@aljawaid](https://kanboard.discourse.group/u/aljawaid)\
**Post date:** [March 17, 2023, 1:26pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/37 "2023-03-17T13:26:38Z")

</div>

Once you are ready to make them into Kanboard releases, you just need to switch `remote_install` to `true` in the `plugins.json` and they will be available to everyone with or without PluginManager.

---

<div class="post-metadata">

**Author:** ![alfredb](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/alfredb/32/1051_2.png) [@alfredb](https://kanboard.discourse.group/u/alfredb)\
**Post date:** [March 17, 2023, 1:39pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/38 "2023-03-17T13:39:10Z")

</div>

> [@aljawaid](#):
>
> Once you are ready to make them into Kanboard releases, you just need to switch `remote_install` to `true` in the `plugins.json`

But the download link has to be fixed first.

---

<div class="post-metadata">

**Author:** ![Tagirijus](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/tagirijus/32/1528_2.png) [@Tagirijus](https://kanboard.discourse.group/u/Tagirijus)\
**Post date:** [March 18, 2023, 8:14pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/39 "2023-03-18T20:14:26Z")

</div>

Which ones and why? When I tested the first link, I was able to get a download at least.

---

<div class="post-metadata">

**Author:** ![creecros](https://yyz2.discourse-cdn.com/free1/user_avatar/kanboard.discourse.group/creecros/32/156_2.png) [@creecros](https://kanboard.discourse.group/u/creecros)\
**Post date:** [March 18, 2023, 10:00pm UTC](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683/40 "2023-03-18T22:00:56Z")

</div>

probably because your download links are:  
[https://github.com/Tagirijus/AddSpentTime/archive/refs/tags/v1.3.0.zip](https://github.com/Tagirijus/AddSpentTime/archive/refs/tags/v1.3.0.zip)

refs to a tag source zip.

this folder structure is incorrect and will not be installable.

you need to make your own zips with appropriate folder structure.

here is an example of a good zip:  
[https://github.com/creecros/Mailmagik/releases/download/1.2.2/Mailmagik-1.2.2.zip](https://github.com/creecros/Mailmagik/releases/download/1.2.2/Mailmagik-1.2.2.zip)

made with Makefile:

> <https://github.com/creecros/Mailmagik/blob/main/Makefile>

alternatively, you could just use 7-zip to make your own archive with appropriate folder structure. I caution the use of windows zip.

when unzipped, your folder structure should be 1 main folder with the plugin name, and all the code and subfolders within that main folder.

```auto
Mailmagik <= Plugin name
    ├── Action  
    ├── Assets  
    ├── Controller  
    ├── Template
    ├── vendor
    ├── LICENSE
    ├── CHANGELOG.MD 
    ├── Makefile 
    ├── Plugin.php   
    ├── README.md
    ├── composer.json
    └── composer.lock

```

the source zips, have `folder>folder>code`

[Previous page](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683.md?page=1)

[Next page](https://kanboard.discourse.group/t/various-plugins-tagi-plugins/2683.md?page=3)
