September 5, 201312 yr Looks like Limetech disembowled our Plugins wiki page! I get that there are new changes coming, (thank you!!!) But all the info and links on that page are important to us maintaining our servers and the plugins. I need to refer back to that page often for links to upgrading, installing, and removing plugins. Until the new system is rolled out, tested, and working, I'd like to see that Plugin Wiki page stay right where it is. Thanks! http://lime-technology.com/wiki/index.php?title=UnRAID_Plugins
September 5, 201312 yr Its not exactly hard to hit the history button http://lime-technology.com/wiki/index.php?title=UnRAID_Plugins&oldid=7799 BUT many of these plugins are either no longer maintained or use pre V5 folder structures. I myself fell into the trap of trying SNAP only to find its both unsuported AND uses the wrong folder structures amongst other things. I suppose it is a question of how long its going to offline for.
September 7, 201312 yr Author You're right, it was easy to hit the history button and see what was there before. And you're also right, I'm sure some of the plugins there had dated information. This sort of thing certainly happens, especially with wiki's and quickly evolving unRaid software. The page was meant to be a one stop shop for plugins. Not only was/is there not a cohesive way to get user customizations and add-ons to unRaid, but the information is scattered all throughout the forums. Many of the most helpful posts are hundreds of pages long - sometimes with important information buried in them too! I think the intention of the Plugins page was to start putting all those links, versions, and data in one place. I certainly did what I could and updated the latest versions and links to all the plugins I use. I would hope and think that others might do the same. The whole thing was a bit of a boondoggle, but the page worked as a stop-gap until the "new plugin architecture" drops. I think it was too pre-emptive to remove the page - especially from a wiki where the users are supposed to be able to write stuff. Between GO scripts, unMenu, simpleFeatures, txz's - it's a lot to wade through.
September 7, 201312 yr Maybe just fork the page to a new page. The crux of the change came from that pages integration into the new webgui. I cant see anyone caring that the old page exists a new url. It does need some more words though and maybe some v5 compliant icons (suspect most dont comply with v5 guidelines). Specifically: * the new strict fodler structure * the new requirement to use 13.1 packages. we need some way of informing users a package breaks from this. IMHO this the most serious problem
September 7, 201312 yr Speaking of scattered plugin information all over the forums....maybe it's time to lock all existing plugin threads and start new ones? Or start a v5.0 plugin subforum. Only actively developed plugins and/or those confirmed to work with v5.0 final would be discussed there?
September 7, 201312 yr Speaking of scattered plugin information all over the forums....maybe it's time to lock all existing plugin threads and start new ones? Or start a v5.0 plugin subforum. Only actively developed plugins and/or those confirmed to work with v5.0 final would be discussed there? As a new user, this would be very helpful.
September 8, 201312 yr Speaking of scattered plugin information all over the forums....maybe it's time to lock all existing plugin threads and start new ones? Or start a v5.0 plugin subforum. Only actively developed plugins and/or those confirmed to work with v5.0 final would be discussed there? As a new user, this would be very helpful. +1
Archived
This topic is now archived and is closed to further replies.