As there are a couple of locations where plugins can be installed, it would be good to have FileMaker report to the user if one plugin is there in several versions.
Or better maybe just load the newest version only?
Did you ever get despaired when you install a plugin and FileMaker is still loading an older version of the plugin?
It would be nice if FileMaker would detect the duplicate and simply use the newer one or show a dialog with paths to both.
I have noticed that in runtime solutions, if I use the filemaker built in way to update an existing plugin (via new plugin stored in a container field), the new plugin (lets call it update2) is installed in a specific filemaker directory outside of the solution and not under the plugin directory of the solution. Furthermore the original plugin is not deleted or overwritten. This can be a problem if in the future we try to update the plugin via a software installer that rewrites the plugin in the runtime directory. (basically this 3rd update would not work since the runtime is already using the plugin stored in the filemaker directory). The only way to make it work would be by doing a complete update of the solution (basically reinstalling everything). This behaviour over internet updates is not practical and unnecessary. Hope my explaination makes sense. I am voting this up hoping the developers can create a better way to update plugins (specially those that are live).
Retrieving data ...