ebr 15490 Posted June 12, 2014 Posted June 12, 2014 I know this was requested way back but I can't find it now. Might have been lost during the time when the FR forum was deleted. Anyway, I think we rejected the idea because of the potential confusion if someone disabled the plug-in and forgot that they did and then couldn't figure out why it wasn't working. Maybe that's valid, maybe it isn't...not sure. Not a slam dunk easy thing to do technically, but it could be done.
Koleckai Silvestri 1150 Posted June 12, 2014 Posted June 12, 2014 Just show it with a different colored background (like red) and the word Disabled in the plugin list. Shouldn't be that difficult to miss. Not sure about the technical issues. As they are load on demand libraries wouldn't the server just not demand that file when it loads everything? 1
Koleckai Silvestri 1150 Posted June 13, 2014 Posted June 13, 2014 Would be nice if there was a way to disable a plugin in the server without uninstalling it completely. I realize it is just one file but reducing steps for troubleshooting makes things easier to use. 2
ebr 15490 Posted June 13, 2014 Author Posted June 13, 2014 The difficulty is that this isn't something we can make an attribute of the plug-in itself because, in order to see the "disabled" attribute, we'd have to load the plug-in and, then, it would be too late. So, as I said, we'd have to maintain a separate list of disabled plug-ins and these would have to be positively IDd by something we can tie back to that particular DLL - without loading it (I guess the dll name). So, yes, it can certainly be done, but it isn't as easy as it might seem - as in simply adding an attribute to a plug-in. All of that is irrelevant as far as whether or not this feature should be added. I just wanted to make the point that it isn't a 5 minute change.
Koleckai Silvestri 1150 Posted June 13, 2014 Posted June 13, 2014 I just figured you would store the attribute in one of the servers sqlite databases.. or in the xml configuration. loadable = true or false. Then you don't have to read the file first. I guess Windows programming is different than anything else but you would think this would be a severe limitation that they would have resolved in 1991.
Luke 38993 Posted June 13, 2014 Posted June 13, 2014 we could just store it in the server config file, and then not load that assembly. of course, enabling and disabling plugins will require restarting the server.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now