Thanks for your reply. What you say about plugins is all very true and the comments I have been making were not meant to sound so critical. But I did want to raise my concern that not everyone is going to as thorough as you might hope. When releasing a plugin to the public a certain level of responsibility should be taken as you never know who is going to end up installing it. If the plugin is intended to be used by people who already know about XY that is fine. But for those that don’t, to read little note saying:
“This plugin is intended to be used by people experienced in XY who understand the potential risks. Those without previous experience might find this a bit of a struggle. You can learn more about XY here”
would be very helpful
Hmm, I can’t say I agree with that, well I agree it might be true. I might be old fashioned but I would like to think when a company selects four plugins from the hundreds they see and writes about them in a newsletter. I always assume they have experienced them enough to share their thoughts.
My mind is a bit blown learning that
I would suggest adding “these plugins are not meant as a rating or recommendation by us” under the article, but that wouldn’t look very good at all
But please, next time you are putting together Kosmos, remember that it is read by people who signed up to it because they trust who it is from and value what they to say.
@digisam: I see your point, and am sorry to disappoint you. In an ideal world, it would be great to be able to give recommendations. In reality, this is impossible for a couple of reasons.
The most important one being that - even if I could test a plugin thoroughly in any kind of environment (which I can’t possibly do) before including it in the newsletter - a plugin can change any day. Something that works today may not work tomorrow.
Also, unfortunately I have no means whatsoever to look into the future to see if developers will continue to develop their plugin or abandon it after the first release. After all, many people develop something for their own use in a project and are kind enough to share it with the world, which is awesome. But if you use it, make sure you do not depend on it to work with the next Kirby release or make sure that you understand enough to be able to update it yourself or hire someone to do it for you.
Plus, Kirby Kosmos is a newsletter, not a test magazine, and as such, we mention stuff that is new and exciting in the Kirby world and which is interesting or might be worth checking out. Of course, I’m cautious about what I include (and if I’m not convinced something is a good idea, I wouldn’t include it), but as I said above, there is no guarantee or even recommendation.
That’s cool, I understand that plugins move on and you can’t extensively test. It a plugin broke the next day, I wouldn’t hold the person who recommended it responsible
Maybe I misunderstood what you initially meant by:
To me it sounded like the plugins are not being installed at all. I apologise if this is not the case.
If someone recommended a film to me, it is not unreasonable to assume it is because they had seen it
I don’t expect a review or a report, as just a few minutes trying anything out (plugins, clothes, music, food, games) is all it takes to decide if you like something or not.
Finally got Kirby CLI working, installed your plugin, used it to install another one. Pluginception! All worked as advertised. I really like this functionality, and I can see it being a great tool for clients, assuming you’d trust your client to not hose their site
