View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007269||MediaMonkey (current)||Framework: Scripts/Extensions||public||2011-01-31 07:54||2011-01-31 13:27|
|Status||resolved||Resolution||no change required|
|Target Version||Fixed in Version|
|Summary||0007269: Uninstall of old version of scripts/skins during installation of new version doesn't work always|
|Description||It doesn't work if you want to install the new version into different folder than before, e.g. you have installed the old version in the global folder and now you want to install the new version into local folder -> you will end up with two installed version of the same script.|
During installation of the new version of script/skin, the program itself should uninstall the old version of the same script/skin, not matter if it is previously installed in local or global folder and not matter of the current user choice of the installation folder.
|Tags||No tags attached.|
|Fixed in build|
I think that the current approach is OK.
As implemented in 0006710: If the same plugin is presented in both plugin folders then the plugin from the LOCAL user's folder is loaded and the GLOBAL is ignored. This is all right, don't forgot that user needn't to have enough rights to uninstall the GLOBAL plugin.
The problem here is, that the approach doesn't work for auto-scripts, reported as:
0007273: If an auto-script is presented as both local and global script then it is running twice
||I don't think that scripts from global folder are ignored. If I put Magic Nodes or Play History & Stats scripts in global and local folders I would get those nodes twice in the Tree panel. I think that Eyal had similar problem with its script described on the mentioned thread which is not related to Tree panel.|
||yes, it is tracked as 0007273|
Well, I saw just now that you edited your comment.
How could you call such approach "resolved" if it doesn't work with auto scripts? You approach none of existing installation packages for auto script would be compatible with MM4, all such packages would require modifications of Install.ini file.