Serviio

You seem to have missed my point.

I did not expect my 8/13 updates to be included. My note was specific to the 3 that you distributed that showed an update date that did not reflect their latest updates prior to 8/13, and therefore were obsolete, and led to user errors.

I dont know how you track changes but I not only update the first post for each groovy, but also label each download with version and date, and also add a post for the update so the groovy thread will pop to the top of the list. It would therefore seem you process to ensure you are distributing the latest groovy's needs to be improved. Checking every plugin thread that has been posted since your last pack update would certainly find all mine.

WildRushSykes,

I notice that each time a new version of Serviio comes out that the "Subject" line of this thread changes. Does this mean these plugins are compatible from Serviio 0.6.0 through 1.0.1?

zip,

Let's take the "Serviio Plugins Pack" out of the Serviio forums and place it right here:

http://www.serviio.org/download

There should be an SVN or Git repository setup for Serviio plugin developers and "WildRushSykes" should have access to this repository and access to the "http://www.serviio.org/download" site (so the "Serviio Plugins Pack" can be updated - for users to download).

Also, this SVN or Git repository will be expanded to include other Serviio products that developers are working on.

The "Available plugins" forum should be renamed to "Plugins" and within that "Plugins" forum should be a thread for each developer's plugin. All questions for a particular plugin would be posted in the corresponding thread.

Now make that happen!

AFAIC plugins are only supported on the latest Serviio release. Why would you expect a plug-in developer to maintain back level copies of Serviio just to be able to test problems that people are having with them?



That's the way it works now but the name should still be "Available Plugins" to distinguish it from "Plug-in Requests". Personally I don't use Packs or Repositories because that just injects a middle man and their typical errors, resulting in user posts asking why a plugin does not work, or how to make it work. I prefer to go straight to the authors source to get the latest and the details on how to exploit the power of each plug-in as well as the latest features which an aggregate download cannot do.

Quote from jhb50: "AFAIC"

The quote (above) is the problem.

We have some developers creating plugins for all versions of Serviio (aka: 0.6.0 - 1.0.1) and other developers too lazy to test their plugin against older versions. These plugins are all over the place when it comes to compatibility with Serviio 0.6.0 and 1.0.1.

There are "valid" reasons why some users cannot upgrade to the newest version of Serviio. Some developers either don't care or have such shallow thinking of this concept.

Wow, some attitude!!

Perhaps those lazy shallow thinking developers should just stop sharing their personal plugins with the community.

...with all the time you spend "yapping" in these forums, you could of tested your plugin with the following Serviio versions:

0.6.0
0.6.1
0.6.2
1.0.0
1.0.1.

Enough said...

Testing takes time for a single version, let alone the time to install and switch between different versions. However, the problem often isn't a case of testing, it's that the plugin may require features / fixes in a new version of Serviio.

Some people just like to point out issues rather than working towards resolving them. Lloyd why don't you make it your responsibility to test each plugin with every version of Serviio, and then you can work with the plugin developers to ensure that the plugins work with each version.

This would definitely help the entire user base.

Zip already mentioned when he launched plugins, developers should assume users should be using the latest Serviio build
If a user finds their new build not working right then this should be addressed separably in the Support section

As Zip said plugins should be using the latest build of Serviio, there no reason a user should be an old build of Serviio

Guess the best advice for users who are unable or unwilling to upgrade Serviio to 1.0.1 is not to upgrade to a set of plugins labeled "For Serviio 1.0.1".

Even better advice is to read the individual plug-in updates and only install those that have no version pre-reqs.

Kinda obvious advice

Hi there
Just to report that SC2Casts doesn't work it should be either updated or removed
Ty

This is an excellent bit of kit, thank you very much

Thanks for the feedback chuckle its good to hear from someone that appreciates it Ruis I've left the plugin in for now but marked it as not working until its fixed

Are all of these plugins compatible with earlier versions, or does this pack require the 1.01 version ?

its recommended to have the latest serviio version as some plugins are only compatible with 1.0.1 but if you are using older version then certain plugins may not work or behave correctly so please be prepared for that

OK => Thx.. it sure is convenient to have all the needed plugins in one spot..

just a followup = would u know if the 0.6.2 version of the TuneIn plugin needs to be upgraded ? It doesn't appear that I can get Internet radio anymore in the latest 1.0.1 version..

only zip will be able to tell you that as he was the plugin creator if you have not done so already please bring this to his attention in the plugins thread

So i am trying to understand and make this work.

From my understanding there should be each RSS feed for every groovy file in this thread, right?

so after unzipping all groovy files in C:\program files\serviio\plugin, i have to add the RSS in the serviio console for every groovy, right??

thanks guys

yes
- unzipping all groovy files
- add the RSS or Webresource you want
- serviio will automatically find the proper groovy plugin to parse the RSS/Webresource

Is this tounge in cheek or is LLoyd being a dick? I can't tell. Might be the latter. If it is that case then LLoyd should ask for all the money back that he has paid the lazy small minded developers of the plugins he is using. Oh wait ... !

Sheesh