Hi all ,
after updating to 4.7.0 something changed in DT .
I have no more access to the script manger or better said … I can´t find the manger any longer .
The export options has changed , like I can´t export to a collection and / or can’t open the file to an external editor .
Anyone an idea how to solve the script manger issue ???
Your help would be appreciated
THX in advance
Cheers Andreas
Hello, there is not such thing as a released Darktable 4.7.0 version.
Darktable 4.7.0 is the development version that will become 4.8.0.
So, to be able to help, you have to give us the full release version, something like: 4.7.0+1224~gc9dbe75234 , and probably tell us where you got that version from (downloaded, build yourself, …)
To help you understand what is happening, you should also run darktable with lua debugging activated; this means running darktable -d lua from a linux command line, or finding how to do that on other operating systems (using cmd on window for example).
With those informations, we could help finding the root cause of your issue.
In fact 4.7.0 is basically the same as 4.6.0. It’s a line-in-the-sand that’s used to see how many commits there have been since the last feature release, hence the development version is (something like) 4.7.0 +1224 (which would be 4.7.0 plus 1224 additional commits)
Hello Olivier … thank you for your answer !!!
I will try to explain what i did …
I was running DT 4.6.1 and found a 4.7.0 ( Nightly build ) on the web ( darktable-4.7.0+1225.g2ad39238f1-arm64 dmg ) … installed it . I was running a nightly build before … so after installing this morning , i could no longer export the file to PS . Now i have no script manager available to install the lua script !!!
Sadly i am kinda dumb to operate with Terminal etc … no idea what a linux command line is !!!
Hope someone can help me .
How come you feel comfortable experimenting w/ development/nightly builds then?
You can use this if you want to try new features without waiting for releases. From time to time, in development builds, old difficult-to-reproduce bugs are fixed, but it is also true that in the development process with the introduction of new complex code, the stability of the program may suffer compared to official releases, so use it with caution!
Also, new versions can make changes to the database schema, so it’s best to run them with a separate library.
Well I did not think about any consequences… my bad !!
But does your answer help me ??? Not really …
Thx for your answer
There were a few changes committed recently that may have something to do with this:
darktable.css - added css to manage script_manager power button and label:
darktable.css: Add comment about temprary CSS snipet.
If you’re lucky, it’ll be resolved in a few days. If not, please open a bug report at Issues · darktable-org/darktable · GitHub
FAO @wpferguson
Did you back up your config directory before upgrading… if so you might be able to go back until you can sort out the issues… when using a trial/dev version it can be best to run it in parallel with an official release so that you always have access a stable variant…
Looks like you are using a MacOS as your operating system (dmg file).
I only use Linux which is another operating system. So I can not really give you advices how to get the logs.
But since it’s lua related, there is some documentation here: darktable lua documentation - troubleshooting
Hey folks … no I did not backup at all .
I am really struggling to get anything running here .
Right now nothing is working !!!
I am running latest Mac OS on a MacStudio M1 .
Is there a way for a clean install ???
Due to my chaotic actions , I messed up the whole thing .
I even forgot how I installed DT in the first place couple of months ago.
I can see the script manager , but after installing the Lua script … I can´t see the script manger again .
It just does not show up .
Sorry for the hazzle …
Thanks … yes running Mac OS
Will try to look at the Lua documentation
When you installed 4.7, it backed up the database files. They are in the config directory (whatever that is on the Mac; under Linux, it’s .config/darktable/), where you’ll find some files with -pre-4.7 in the name. Just copy library-pre-4.7… to library.db, and do the equivalent for database-pre-....
You could try to run DT with the command-line switch --configdir “path” where path is a new empty folder that will house your config files…this will create brand new clean config files. You could see how that would effect your current status… I am a windows guy so I would modify the run line in the shortcut to add this or run from the command line… I don’t know about program execution on a mac…maybe you can adjust the command line of your icon as you would in windows…
TLDR; It was a bug. It’s fixed. Remove the lua directory in your darktable config directory and run the scripts installer again from darktable.
The plan for 4.8 was to move translation of the lua-scripts into darktable master, so as part of that I went through the scripts and cleaned up the translatable strings and removed the line of code that told the script where to find the translations.
Unfortunately we ran out of time, so will be in darktable 5.0. In the meantime, I went back in and added the line that told the script where to find it’s translation files. Then I tested each script and fixed any problems. I was running the test version of script_manager so it didn’t occur to me to check it before I pushed.
@helgeschneider thanks for testing 
THX folks for your thoughts and suggestions …
Luckily I was able after some back and forth , to get rid of all the crap and installed it fresh .
Now it does work again … with a 4.6.1 version and a 4.7.0 ( last nightly build ) alongside with no issues … so far LOL .
Have a nice day
Cheers Andreas
a pleasure 
Thanks for giving us the opportunity to test by providing weekly Windows builds for people like me.