Loading a plugin set doesn't lead to the expected result, if the plugin names in the
plugin set file don't match the current name properties. This will become a problem
on localized installations if the plugin set file isn't self-created but provided
by another user/maintainer.
| Submitted | rschwenn - 2010-02-17 - 22:37:35z | Assigned | nobody |
|---|---|---|---|
| Priority | 5 | Category | plugin manager |
| Status | Open | Group | None |
| Resolution | None | Visibility | No |
| 2010-02-19 - 16:39:34z ezust |
Yeah, I think the whole concept of a pluginset is probably going to be redesigned
in 4.4. We need to remove the buttons from the plugin manager install/manage pane and create a new dialog/pane for managing/installing pluginsets and disabling old/obsolete plugins, which will run on startup or something. |
|---|---|
| 2012-12-28 - 17:19:20z ezust |
I think the reason I needed to put the name in the pluginset file in the first place
was because I was searching through the .xml file for plugins that matched the name
that I found from the pluginset.xml file. If that name changes depending on the localization, but not on the server side, then I need to use something else to compare against. |