This looks more like a broken build then a bug, is the addon included anywhere in the "scripts" ?

Such problemmy with all the addons that I try to include. If I try to turn off the addon (tick off, deactivate) the program also gives eror and then the addon is not possible to include more.

Yesterday put version 2.64 it works without problems. but if I put 2.69 Problem with addons does not disappear.

Does this happen with 2.69 release?

Can you check if this problem is specific to the build you downloaded.

Yes, this problem only in version 2.69 to version 2.64 no such problems.

Now I have two versions.
Because on the disabled addons 2.69 can not convert files to OBJ this can only 2.64.

Version 2.69 downloaded from your official website.

@Andrey (K_Studio): Did you test with the 2.69 release downloaded from blender.org? (4b206af is not a release)

Yes.

Couldn't reproduce the issue with neither official 2.69 release nor current development builds.

@Andrey (K_Studio) please try downloading latest build from http://builder.blender.org/download/ and provide us exact stesp how you reproduce the issue, starting from how/where you unpack the archive.

It might also be permission issue, so try unpacking to locations different from c:\program files

◀ Merged tasks: T38499.

Can confirm the problem on official 2.70win32, affecting various addons.
OS is WinXP, using the portable .zip-version, unpacked to different location than C:\Program Files\.
Please let me know if any more informations are needed.

@Campbell Barton (campbellbarton) I followed the steps, and it worked - once. The second script produced the message described above, as I tried to activate it.

A few days ago I achieved a similar effect, forgot to mention that in first place: An IRC user recommended to rename my %appdata%/../2.70- folder, and then not pick "copy previous settings" on next start. With the fresh created new settings folder, I had the similar effect of being able to install&activate one external script.

Just to clarify: All the addons shipped with blender can be activated fine. Problems just arise from self-downloaded ones.
Also, I am always using the "install script from file" button and point it to a .py or a .zip.
The installationpath I picked was "C:\Portable".

I found an even simpler solution, if it helps someone in future:

1.Install script
2.Activate (doesnt work, gives error)
3.Close & reopen blender
4.Search script again in user settings, activate again - now it should work.

If you want several scripts as once, batch the process - first install all of them, 1x close&reopen, then activate all of them, works too.

Thanks @Campbell Barton (campbellbarton)!

@riidom (riidom)

Can you please let us know what the error is, Run blender with the console before installing a script and copy&paste the entire message here. or attach a text file if its large.

Activate should work first time, if not - then its a bug, but you dont give us any information as to what fails.

It is pretty much the message the OP quoted at end of his first post. I add 2 screenshots:

Edit: 3rd one, the console after restarting, going to userprefs, finding addon, activate it successful:

note: release/scripts/modules/bpy/utils.py, refresh_script_paths is supposed to make sure the addon can be imported after installing.

It looks like this isn't working in some cases.

Just tried on windows7, and I can't redo this bug.

I can't see why refresh_script_paths would fail, afraid I would have to use a system with this problem to be able to investigate the bug.

If someone likes to debug, This is whats happening:

• User installs addon: WM_OT_addon_install (from wm.py)
• WM_OT_addon_install creates the target directory (if it doesn't exist)
• After the file is copied bpy.utils.refresh_script_paths() is called to ensure any newly created addons paths are in sys.path.

To debug this I would try print this before and after installing the script.

print("Addon Paths:", __import__("addon_utils").paths())
print("Sys Paths:", __import__("sys").path)

Heres a diff:

diff --git a/release/scripts/startup/bl_operators/wm.py b/release/scripts/startup/bl_operators/wm.py
index 86ae8fd..faa5d10 100644
--- a/release/scripts/startup/bl_operators/wm.py
+++ b/release/scripts/startup/bl_operators/wm.py
@@ -1846,6 +1846,9 @@ class WM_OT_addon_install(Operator):
         import shutil
         import os
 
+        print("Addon Paths:", __import__("addon_utils").paths())
+        print("Sys Paths:", __import__("sys").path)
+
         pyfile = self.filepath
 
         if self.target == 'DEFAULT':
@@ -1945,6 +1948,9 @@ class WM_OT_addon_install(Operator):
         # in case a new module path was created to install this addon.
         bpy.utils.refresh_script_paths()
 
+        print("Addon Paths:", __import__("addon_utils").paths())
+        print("Sys Paths:", __import__("sys").path)
+
         # print message
         msg = tip_("Modules Installed from %r into %r (%s)") % (pyfile, path_addons, ", ".join(sorted(addons_new)))
         print(msg)

@Andrey (K_Studio)

Could you apply these changes to your wm.py, install an addon (get the output), then install it again after restarting blender?

@Campbell Barton (campbellbarton) should we close this at some point due to lack of feedback ?