note the file path in the config, which is incorrect:
Note also that for some reason, the repo path in my working example above has to be typed as file://xxx, NOT file:///xxx - maybe a Windows only thing? Should be three slashes normally?
Actually the initial problem is that you have a trailing
comma inside your list. But yes, you also need to use windows-x64 instead of amd64. And Blender should have given you a proper error.
Unfortunately none of the suggestions work (tried all of them), the error is related to how the data is interpreted in Python. It makes sense, the code in blender_ext.py reads:
platforms = [platform for platform in manifest_dict.get("platforms", "").split(",") if platform]
and throws the error 'list' object has no attribute 'split'
which is correct, given that manifest_dict.get("platforms", "") already returns a list as defined in the .toml. If it were a str instead, the code that tries to split it would make sense.
For the records, I think the only “problem” here is that the generated html has repository=“./index.json” for all the entries.
Short of suggesting people to manually search/replace the index.html, this could be an option --html-repository where you specify the entry point for the json.
On a different subject, how would one now enable Add-ons via command line?
I used to do for example this in Blender 4.1: blender -b --factory-startup --addons "f2"
to load an unbloated Blender and just activate the f2 Add-on (as an example). If I provided a wrong Add-on name, e.g. blender -b --factory-startup --addons "foobar", Blender would report back: Add-on not loaded: "foobar", cause: No module named 'foobar'
With 4.2 I can’t activate any of the Add-ons at the moment with such mechanism. Furthermore, the error message isn’t telling me much, and is always the same:
Traceback (most recent call last):
File "<string>", line 1, in <module>
ModuleNotFoundError: No module named '_bpy_internal.addons.cli'
@RainerTrummer hi, enabling add-ons on the command line is working in my tests.
The issue with reporting bugs here is I end up needing to ask follow up questions and try to find out what your doing on your system that’s different to mine, so please just report bugs in the tracker because it adds noise to these threads & risks developers missing reports before release.
In the end, since we implemented the simpler way to download the missing add-ons from within Blender (and the system local repository to make portable installations), I decided to leave the backwards compatibility bundle only on the wiki release notes.
You should be able to prepare such directory, and either use it for yourself, or use it in a more controlled environment for all Blender users in a studio with internet restrictions.
Quite sure it is only the “parent” add-on which will be showing up in the list. but maybe someone closer to the project can confirm this. That section is about avoiding creation of panels/operators with the same identifier.
P.S. I was thinking where is the good place for such sort of questions would be. In a way, it is not really announcement, and doesn’t really fall under “contributing to Blender” category. Perhaps #python room on the Blender chat is where there are plenty of developers who can more instantly share knowledge and such?