thx for getting involved.
in the meantime the "module/attribute"-part of the problem seems to have been resolved.
it was a little generator plugin, that i set up a year ago while i had been trying to learn python for a few weeks, a kind of practice if you wish. (unfortunately didn't keep going back).
ppl that used it in r19 now wanted me to look into it, since it did not work in r20 anymore.
so i tried to remember stuff :)
well, after changing a thing concerning instances it actually worked on my systems on r20, but not on other people's.
they were getting this "...AttributeError: 'module' object has no attribute...". - message, which i did not get.
on another forum outside of this one, i have been made aware of a "symbol cache"-problem, stating that whenever a plug-in had been updated and things in it's ressources had been changed, the symbolcache-file in the "prefs"-folder should be deleted.
turns out, doing that made the "...AttributeError: 'module' object has no attribute...".-message go away for those ppl (as mentioned, i myself did never get that AttributeError: "'module' object has no attribute 'BESPLINE_SOURCE_OBJECT'", pointing to the line "obj_sel = op[c4d.BESPLINE_SOURCE_OBJECT]".
so, that part's been solved by deleting the symbol cache file.
since i did not know about this solution, i had to keep an eye on the other part of the problem, which is the plugin-id-collision topic.
i also tried and got a new plugin id for that plugin (old one: 1040388, new one: 1050856) but that didn't change anything.
but it also had to be independent of my little plug, since it occurs with every plugin, that is installed.
so, when i go ahead and delete all plugins, but one, out of the plugin-folder, the one that is still installed shows the same message:
for example, the one plugin, that is in the folder right now is drop2floor, showing the message in the console:
"RuntimeError:The plugin ID '1041642' collides with another plugin ID in 'Drop2Floor'.You have to use a unique ID for registering your plugin!You can get a personal number for free from PluginCafe at www.plugincafe.com"
no matter, which plug, i'm getting this message.
when it comes to:
"Did you set an environment variable like g_additionalModulePath that loads additional plugins?"
no, it didn't. frankly, i didn't know about that. i thought, the builtin-possibility would take care of that. was not aware, that one would additionally need to set the paths manually wihthin the system's settings.
within r20 i had defined a custom folder as a plugin-folder. most boringly, it's the "old" plugin-folder in the user-prefs folder, that i use as a custom folder.
habits die hard, i guess.
since you made me aware of the need to setup the additional env.variable, i tried it. no luck, unfortunately.
but: during this process, i realized that, if i put the plugin (whichever) into the plugin-folder within the main application structure, the collision-messages do not appear anymore.
well, that's the status.
at the end, it's not that big of a deal, since all plugins, while showing this message, do work as expected. the collision does not seem to have any impact.
@s_bach said in R20, Python - "RuntimeError:The Plugin ID 1234 collides with another plugin ID in 'Xyz'.", no matter what.:
Hello and welcome to the PluginCafe.
Can you be a bit more precise in your description? What exactly is the plugin ID that causes the error? What is the name of the plugin; what does Xyz stand for?
What exactly is the attribute error?
..AttributeError: 'module' object has no attribute...
What attribute exactly is missing? The Python console should print out the number of the line causing the error. Can you share the code that is causing the error?
Did you set an environment variable like g_additionalModulePath that loads additional plugins?
If you post questions, please make sure to use the Q&A system.