gsettings comes preinstalled on ubuntu, so this is one way which doesn't need sudo privileges.
In the meantime, please let me know how you get on with the plugin on your Windows system.Google Chrome and Chromium obey the environment proxy variables ( http_proxy, no_proxy, etc.) and the proxies set via gsettings. If you'd like me to do this for you, then please let me know. This would drastically reduce the number of times that Lightroom regenerates the gallery's 'config.xml' file for the preview and should help with the problem (although you'd not see the changes you make to the gallery instantly). Instead, the live preview window would be updated only on demand (Cmd+R (Mac), Ctrl+R (Windows), 'Web -> Reload').
However, if it will help, I could compile a version of the plugin for you which would not update the live preview window automatically when each configuration option is changed in the interface. I'm glad you've found a workaround (even though it's not ideal).Īs I mentioned, if the problem is with the way that Lightroom handles the generation of the gallery files (either a timing or multi-threading issue), then there is perhaps little that can be done from within the plugin to counteract this. Please let me know if refreshing the live preview window when the error message appears (Cmd+R (Mac), Ctrl+R (Windows), 'Web -> Reload') helps. In the plugin's manifest file, the plugin requests that the 'config.xml' template be processed before the 'index.html' template so, unless there is some kind of threading issue or asynchronous activity (which, as far as I am aware, the plugin has no control over), I'm really not sure what might be causing the problem. Maybe my notes in these forum threads will at least help to explain this issue in greater detail:Īs I mentioned in the forum threads above, the problem could be some kind of timing problem with the way that Lightroom generates the files for the preview (perhaps the 'config.xml' file is sometimes not ready in time for the gallery to be displayed by the 'index.html' file).
From the limited information I have, it seems that the problem may affect only a limited number of Mac users. Two of these users are known to be using a Mac (the third user's system is unconfirmed) but I've never been able to replicate the problem myself on a Windows PC. Over the course of a year and a half, only three other users have reported the " Config file not found." message appearing in Lightroom's live preview window. If the error message appears in Lightroom's live preview window then the try forcing a refresh of the page (by pressing Cmd+R (Mac), Ctrl+R (Windows) or by selecting 'Web -> Reload' from the drop-down menu at the top) to see if this clears the problem without having to move away from the Juicebox web engine and lose your settings.
Once I am able to see your gallery and its code, I should be able to determine the cause of the problem and propose a solution.
How do I fix this?Īlso, if possible, please upload the gallery to your web server and post a link so that I can take a look at the problem for myself and hopefully help further. When I view my gallery I see the message 'Config file not found'. If the error message appears in your Chrome browser, then please see this FAQ which refers to the error message and might help. I'm not sure if you are referring to the " Config file not found." message appearing in your Chrome browser or Lightroom's live preview window (or both). But in the past 3 hours the program has crashed at least 4 times with the "Config File not found" error.