Bugzilla – Bug 5934
Can't disable plugins
Last modified: 2008-12-18 11:12:53 UTC
I have tried to use the Settings->Extras page to disable some plugins. After I click "Disable", if I refresh the screen, they are reported as still disabled. However, when I restart the server, I see messages in the log indicating that the plugins are being loaded, and when I view the settings, they are Enabled. I have tried to disable the Snow Screensaver, and also a couple of third-party extras.
I think this needs more work, and to be more specific. bug 5900 reports plugin state being reset after upgrades, because disabled plugins got re-enabled. Clearly plugins CAN be disabled under some conditions. I've just disabled RadioTime and ShadowPlay, and Snow as a test. On restart, they are still disabled. Check the plugin-data.yaml file in the cachedir. the value for "state" should change to 0 when disabling plugins. Is this a problem for you with all skins, or just default with the new settings pages? Are you seeing any changes in the plugin-data.yaml file? Are you getting any info from the log when you set prefs to DEBUG? If so, lets get those details in the report.
The JS on the Default settings pages was broken. Change 14193 should fix this.
I am still seeing an issue with this. If I disable any single item, save the settings and refresh the page, it does show the "Enable" option (indicating it is disabled). But, when I restart the server, it changes back to "Disable" (indicating it is enabled).
I can't reproduce this. Can you make sure you're not loading a stale copy of the page from cache? Could you please check the plugins cache file as indicated by kdf?
This does appear to be working now, at least the plugins that I wanted to disable are now remaining disabled.
Having cleared my cache and restarted, most plugins have been enabled again. Eg. I disable Pandora, Rhapsody, Slacker and other stuff, but these have just come back. It appears that plugin state is stored in the Cache folder, so plugin state will be lost if the cache is cleared. It should be persisted in the prefs settings.
plugin-data.yaml stores the plugin states. If you wipe the hard drive cache, you will reset to the default for each plugin, but ensure that no old templates or js is still stored elsewhere. You then need to test the disable without wiping plugin-data.yaml. Erasing the cache folder shouldn't have to be done at any time, but clearing the browser caches (clearing private data for FF) is needed often, especially when using svn. plugin-data.yaml might do better if it were relocated, with all this folder shuffling, going on and evangelism over persistent data, read/write, etc.
change 14931 - moving state to preferences instead of cache file. Please reopen bug 6210 if needed.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.