Pre-installed plugins are not detected.
Issue #8
resolved
I had a copy of ArtSmart installed at User Prefs / Plugins / Cineversity / CV-ArtSmart
CV Toolbox installed another copy at User Prefs / Plugins / CV-ArtSmart
The two copies conflicted.
Perhaps run a check for a pre-existing plugin by seeing if an instance of a plugin with the same ID is already running before trying to install.
Comments (9)
-
reporter
-
reporter
-
assigned issue to
Rick Barrett
-
assigned issue to
-
Yeah - it's supposed to be detecting it, but I haven't had a chance to try to reproduce. What was the path for your pre-installed ArtSmart? Was the folder not called CV-ArtSmart or was it nested in the hierarchy? It only looks for the preferred folder in either the user or application path (it does check both). Perhaps we just need a plugin id check as well to be doubly-sure.
-
reporter
It was...
C:\Users\Donovan Keith\AppData\Roaming\MAXON\15.057_AE0D2D8C\plugins\Cineversity\CV-ArtSmart
-
reporter
It was nested in the hierarchy. An ID check would be good as we can't trust users not to rename folders and files. If the installer sees the ID but can't find the plugin's folder, ask the user to manually locate and uninstall the file before installing with CV Toolbox.
-
reporter
Notes: - All installed plugins are stored in a dict by plugin ID - If a plugin is detected that's not in the dict, ask the user to manually uninstall the plugin. Tell them where they might find it (and/or open their plugins directories for them). - Might be best to give them a long list of all plugins to uninstall.
-
- changed version to v1.0
-
Detection in 44045f47
Does not properly report the plugin path. I could find it by walking the install trees, but not sure if it's worth the overhead.
Also, does not currently automatically install those plugins when the situation is rectified. I'll have to build a trigger file for that.
-
- changed status to resolved
Closing this one. The automatic re-installation is in Issue #51
- Log in to comment
Okay, I ran into a plugin install where it detected an existing install and replaced it. It seems that the issue is mostly pre-installed plugins that aren't in the base plugin directory, but I could be wrong.