I recently migrated my Backlight site to a new server. After a few tweaks (changing the SQLite Journal Mode to PERSIST, changing SQLite Synchronous to Off, and reloading all the latest modules, including the Lightroom plugin) most features are working. However, I had to change the API URL in Lightroom to: /backlight/?m=publisher to regain Lightroom connectivity and, more importantly, I have lost the ability to upload custom cover images directly in Backlight.
The original custom cover images still reside in the backlight/data/designer/image_uploads directory and the correct reference numbers show in the Publisher Base settings for each album. But the image is represented by a broken link icon. Trying to re-upload the image results apparently uploads another copy to the image_uploads directory, but also results in a broken link with no cover image visible.
Note, I have been successful in using Backlight to restore a cover image that exists in the album.
Any suggestions how to restore custom image upload in Publisher would be appreciated.
Hi @Richard, this would be caused by URL rewriting not working. Can you check that there are two different .htaccess files, one at the top of your site and one within backlight/? If not then copy them over from the Backlight installer zip file.
Another potential issue is that the mod_rewrite module is not enabled in your Apache instance. If you are managing your own server then make sure this module is enabled and that AllowOverride is set to On for the directory that your site resides in.
Hello Ben, yes I was missing the .htaccess file within backlight/ directory. Adding it back seems to have fixed the problem. Note that the Backlight files are installed on the server in a /photos folder and that is where the “site” Backlight .htaccess file resides (not at the website root). Should this pose a problem? The website root .htaccess file only contains some :“AddType video/mp4 .mp4” entries for video support elsewhere on the site. I changed the SQLite Journal Mode and SQLite Synchronous settings back to default.
Installing Backlight into a folder imposes some restrictions on using pages, but should otherwise not be a problem. We document such a setup for running Backlight when using WordPress as a main website, in our WP Theme documentation.
Using WordPress or not, these instructions should hold up for any use case where Backlight is not at the top-level of your website.
As an aside, I should probably extract this concept into a separate piece of documentation so that it’s not so closely associated with WordPress, which we’re moving away from …
