January 13, 201610 yr I hope you didn't let out a bit of wee.... Luckily I caught my mistake before I reached that level of excitement.
January 16, 201610 yr With the new release of 6.1.7 I can only guess this is now Obsolete until you release the next Bleeding edge updates?
January 16, 201610 yr Author With the new release of 6.1.7 I can only guess this is now Obsolete until you release the next Bleeding edge updates? Indeed, you need to uninstall this plugin and upgrade to unRAID 6.1.7.
January 20, 201610 yr holly cow bonienl, you are using the original ancient tablesorter plugin.. you really should check out Mottie's fork (https://github.com/Mottie/tablesorter) which improved on it greatly (then there is even yet the successor past that, but thats for another conversation). you will find a ton of goodies that prob would work out well for this... http://mottie.github.io/tablesorter/docs/#Examples also your on jquery 2.1.4, may want to look at upgrading to 2.2.. some performance gains with certain selectors. http://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/
January 22, 201610 yr Updated and now I'm getting "404 File not found". Reboot did not help. I am running 6.1.7, and all my other plugins were up to date.
January 22, 201610 yr Updated and now I'm getting "404 File not found". Reboot did not help. I am running 6.1.7, and all my other plugins were up to date. Not sure I understand why you are posting to this thread. Do you mean you are using this plugin with 6.1.7? You are supposed to remove this plugin when you upgrade to 6.1.7 as it says in the first post.
January 22, 201610 yr Because before I posted, I read it too fast and thought it meant if you weren't on 6.1.7, there was a bug and you needed to uninstall the plugin. But I found the thread because the damage was already done. I simply did a "Check for updates" in my plugins page, saw it was available, and updated it. It broke, and then I came looking for help. So now that my system is busted, how would I go about manually fixing this?
January 22, 201610 yr Author Because before I posted, I read it too fast and thought it meant if you weren't on 6.1.7, there was a bug and you needed to uninstall the plugin. But I found the thread because the damage was already done. I simply did a "Check for updates" in my plugins page, saw it was available, and updated it. It broke, and then I came looking for help. So now that my system is busted, how would I go about manually fixing this? Delete the file /boot/config/plugins/dynamix.bleeding.edge.plg Delete the folder /boot/config/plugins/dynamix.bleeding.edge Reboot your system
January 22, 201610 yr I don't have that in my plugins folder root@Tower:/boot/config/plugins# ls -l total 320 drwxrwxrwx 2 root root 16384 Mar 10 2015 OpenELEC/ drwxrwxrwx 5 root root 16384 Oct 22 2014 dockerMan/ drwxrwxrwx 3 root root 16384 Jan 22 13:51 dynamix/ drwxrwxrwx 2 root root 16384 Dec 29 15:40 dynamix.active.streams/ -rwxrwxrwx 1 root root 3023 Dec 29 15:40 dynamix.active.streams.plg* drwxrwxrwx 2 root root 16384 Jan 21 19:27 dynamix.cache.dirs/ -rwxrwxrwx 1 root root 5564 Jan 21 19:27 dynamix.cache.dirs.plg* drwxrwxrwx 2 root root 16384 Apr 27 2015 dynamix.kvm.manager/ -rwxrwxrwx 1 root root 1762 Jan 22 13:51 dynamix.plg* drwxrwxrwx 2 root root 16384 Dec 29 15:40 dynamix.system.info/ -rwxrwxrwx 1 root root 3528 Dec 29 15:40 dynamix.system.info.plg* drwxrwxrwx 2 root root 16384 Jan 21 19:27 dynamix.system.stats/ -rwxrwxrwx 1 root root 4691 Jan 21 19:27 dynamix.system.stats.plg* drwxrwxrwx 3 root root 16384 Jan 6 2015 powerdown/ drwxrwxrwx 3 root root 16384 Sep 30 20:09 unassigned.devices/ -rwxrwxrwx 1 root root 10431 Dec 29 15:40 unassigned.devices.plg* drwxrwxrwx 2 root root 16384 Apr 27 2015 virtMan/ drwxrwxrwx 2 root root 16384 Dec 2 2014 vmMan/ drwxrwxrwx 2 root root 16384 Oct 22 2014 webGui/ drwxrwxrwx 2 root root 16384 Oct 22 2014 webvirtmgr/ root@Tower:/boot/config/plugins#
January 22, 201610 yr Author I don't have that in my plugins folder root@Tower:/boot/config/plugins# ls -l total 320 drwxrwxrwx 2 root root 16384 Mar 10 2015 OpenELEC/ drwxrwxrwx 5 root root 16384 Oct 22 2014 dockerMan/ drwxrwxrwx 3 root root 16384 Jan 22 13:51 dynamix/ drwxrwxrwx 2 root root 16384 Dec 29 15:40 dynamix.active.streams/ -rwxrwxrwx 1 root root 3023 Dec 29 15:40 dynamix.active.streams.plg* drwxrwxrwx 2 root root 16384 Jan 21 19:27 dynamix.cache.dirs/ -rwxrwxrwx 1 root root 5564 Jan 21 19:27 dynamix.cache.dirs.plg* drwxrwxrwx 2 root root 16384 Apr 27 2015 dynamix.kvm.manager/ -rwxrwxrwx 1 root root 1762 Jan 22 13:51 dynamix.plg* drwxrwxrwx 2 root root 16384 Dec 29 15:40 dynamix.system.info/ -rwxrwxrwx 1 root root 3528 Dec 29 15:40 dynamix.system.info.plg* drwxrwxrwx 2 root root 16384 Jan 21 19:27 dynamix.system.stats/ -rwxrwxrwx 1 root root 4691 Jan 21 19:27 dynamix.system.stats.plg* drwxrwxrwx 3 root root 16384 Jan 6 2015 powerdown/ drwxrwxrwx 3 root root 16384 Sep 30 20:09 unassigned.devices/ -rwxrwxrwx 1 root root 10431 Dec 29 15:40 unassigned.devices.plg* drwxrwxrwx 2 root root 16384 Apr 27 2015 virtMan/ drwxrwxrwx 2 root root 16384 Dec 2 2014 vmMan/ drwxrwxrwx 2 root root 16384 Oct 22 2014 webGui/ drwxrwxrwx 2 root root 16384 Oct 22 2014 webvirtmgr/ root@Tower:/boot/config/plugins# You still have a couple of outdated plugins installed, below folders are not needed anymore drwxrwxrwx 2 root root 16384 Apr 27 2015 virtMan/ drwxrwxrwx 2 root root 16384 Dec 2 2014 vmMan/ drwxrwxrwx 2 root root 16384 Oct 22 2014 webGui/ drwxrwxrwx 2 root root 16384 Oct 22 2014 webvirtmgr/
January 23, 201610 yr Hmm. Deleted those and a few others like stats and info, but the issue persists. Can I delete everything from that plugins folder?
January 23, 201610 yr Fixed. I had to delete dynamix-2016.01.22.tar.gz from /boot/config/plugins/dynnamix Thanks for the help, guys! I never would have found it without you!
January 23, 201610 yr Thanks deleting dynamix-2016.01.22.tar.gz from /boot/config/plugins/dynnamix worked for me too. :) I must admit that I did not take any notice of this thread, as I only thought it related to people using test drivers
Archived
This topic is now archived and is closed to further replies.