Community @ The Turning Gate

Support community for TTG plugins and products.

You are not logged in.

#1 Re: Backlight Support » Publishing large photo sets aborts with server 12152 code » Today 09:29:32


GoDaddy has unsophisticated security rules that incorrectly detect Publisher traffic as a denial-of-service attack.  Traffic is then blocked for 60 seconds.  This has been the case for up to a decade, and affects Publisher and similar plugins from other vendors such as Gallery.

What hosting plan are you on?  If you have a dedicated virtual machine (or similar non-shared hosting), then you may be able to have the security rule that affects this removed (it should be a mod_security rule, but which rule I don't know).  You'd need to contact GoDaddy's technical support to ask how to do this.
If you're on shared hosting, then you may have luck in asking GoDaddy's technical support to upgrade your cPanel version.

Unfortunately, there is no universal advice that I can offer that will fix this with any certainty.

#2 Re: Backlight Support » pilot error: after upgrading things not working » Yesterday 12:21:24


And... a takeaway for the Backlight developers is to add some smarts to completely ignore modules that don't meet the naming rules.

#3 Re: Backlight Support » pilot error: after upgrading things not working » Yesterday 12:19:46


Backlight modules operate on consistent naming conventions.  You've renamed standard-page to tmp-standard-page.  Backlight then treats that as a module, and attempts to load a non-existent file called TmpStandardPageEngine.php file.

The take-away from this is not to try renaming folders in the modules directory.  Either keep them ore remove them, but don't rename them.

#4 Re: Backlight Support » Sub-domain problems » 2017-10-15 09:58:05


Pick one domain and configure Backlight and Publisher for that domain and that domain only.  Backlight does a lot of work to calculate paths and needs everything to point to the same place.

If you must have it available at two locations, then I would suggest configuring Backlight at and using your events subdomain as a vanity URL that redirects to

#5 Re: Backlight Support » Advantage - more than one publisher instance » 2017-10-13 05:37:25


It’s hard to advise without an answer to my question above.

One option for two exact copies would be to maintain one through LR and use a sync function of a good FTP application. The directories to sync would depend on whether you plan to duplicate the galleries or entire Backlight site.

#6 Re: Backlight Support » Advantage - more than one publisher instance » 2017-10-12 20:43:27


Hi Rainer, the approach would depend on what you're trying to do.  Are you planning to maintain copies of your site at two separate locations, or are you moving from one location to the other?

#7 Re: Backlight Support » Quick Setup in Backlight » 2017-10-09 18:28:28


It's probably worth following the step 1. anyway.  You may find that you have settings to disable the modules. 

If that doesn't help, then whether you take it up with tech support or try step 3 is up to you.  The former may be more trouble, but the latter may just be putting a bandaid over a bigger problem.

#8 Re: Backlight Support » Quick Setup in Backlight » 2017-10-08 19:25:24


We have a document about this on Bluehost.  Have a look at the section on modules: … ule_errors

#9 Re: Backlight Support » Gallery Set Hierarchy match Folder Hierarchy in Catalog? » 2017-10-08 19:12:46


Thanks for explaining.  I also don't have a lot of trust in the longevity of Lightroom.  The development of Backlight's Design tools was largely prompted by uncertainty of ongoing existence for the Web module.

In your case are you only focussed on Collections rather than Folders?  I can't at this point think of a good way to automate what you're looking for.  Perhaps others more experienced as users in Lightroom will be able to offer suggestions.

#11 Re: Backlight Support » Gallery Set Hierarchy match Folder Hierarchy in Catalog? » 2017-10-08 08:16:50


Very little chance.  It may be technically possible to build something like this but at a lot of effort for little reward.  You're the first person to suggest this feature, which suggests it wouldn't be of wider interest.  In practical terms, I'd imagine that few of our customers would want their entire catalogs published, or would have catalogs far too large to push in entirety to the web.  Our back-end is geared to thousands of photos, and not tens or hundreds of thousands of photos.

#12 Re: Backlight Support » Restrict metadata published with images? » 2017-10-07 19:03:25

rsamco wrote:

So sorry for my error ... so glad that I didn't keep you from enjoying a beautiful afternoon. We had a beautiful day today here in Oregon as well ... but Autumn, not Spring :-(

No problem.  There are many moving parts to Backlight and many technical decisions made over the years with accumulated code that can make it hard to understand what's going on.

A lovely day here, with plenty of colourful birds as we walked along the river.  All was good till I got the family lost and we had to scramble up an escarpment, rendering me the worst dad ever apparently.  Fixed with ice cream sundaes.

#13 Re: Backlight Support » Restrict metadata published with images? » 2017-10-07 10:07:32


It's a lovely Spring day here, and we're heading out for the afternoon.  If the above steps don't resolve it, and you see no change in the 'enable_maps' setting on the above link, then can you zip up your ttg.log and email it to me, using the link in my signature?  This can be found in your Documents directory on your PC or Mac.

#14 Re: Backlight Support » Restrict metadata published with images? » 2017-10-07 09:53:18


Thanks for the links.  Interestingly, the first album shows that maps are still enabled: … test/?data  (named as 'enable_maps')

Can you try toggling that setting in the album settings, clicking the 'Edit' button to save the setting and refreshing the above link to see whether the setting change takes effect?

#15 Re: Backlight Support » Restrict metadata published with images? » 2017-10-07 09:35:24


Let's not assume a bug until we're all on the same page.  What do you mean by 'geolocation'?  Specifically, where are you seeing the photo's location info?

Can you provide a URL of an album you think should not be showing location info?

#16 Re: Backlight Support » Restrict metadata published with images? » 2017-10-07 08:03:41


I think I've worked it out.  The Metadata option in Lightroom pertains to the information embedded into the published JPEGs.  Can you confirm that you are seeing location metadata saved within the images themselves?  To see this you will need a tool that can view the image metadata.  I use the command line application 'exiv2' like this to view Exif metadata:

exiv2 -PE 20150706-0604.jpg

For an image with location info, the relevant entries look like this:

Exif.Image.GPSTag                            Long        1  736
Exif.GPSInfo.GPSLatitudeRef                  Ascii       2  South
Exif.GPSInfo.GPSLatitude                     Rational    3  36deg 50.71500' 
Exif.GPSInfo.GPSLongitudeRef                 Ascii       2  East
Exif.GPSInfo.GPSLongitude                    Rational    3  146deg 22.27380' 
Exif.GPSInfo.GPSAltitudeRef                  Byte        1  Above sea level
Exif.GPSInfo.GPSAltitude                     Rational    1  743.5 m
Exif.GPSInfo.GPSTimeStamp                    Rational    3  02:35:44.1
Exif.GPSInfo.GPSSpeedRef                     Ascii       2  km/h
Exif.GPSInfo.GPSSpeed                        Rational    1  0/1
Exif.GPSInfo.GPSImgDirectionRef              Ascii       2  True direction
Exif.GPSInfo.GPSImgDirection                 Rational    1  16367/181
Exif.GPSInfo.GPSDestBearingRef               Ascii       2  True direction
Exif.GPSInfo.GPSDestBearing                  Rational    1  48947/181
Exif.GPSInfo.GPSDateStamp                    Ascii      11  2015:07:06

Backlight also saves metadata, separately in the database in accordance with the template and album settings.  This is not controlled by Lightroom's Metadata controls.  For example, tokens such as {Title} used in captions.  When the Album's Enable Maps option is checked, the location information will be saved in the database.  If you want to hide location information for photos, then disable this feature for the album.

Does the above explain the behaviour you're seeing?

#18 Re: Backlight Support » Restrict metadata published with images? » 2017-10-06 19:41:03


Thanks for confirming.  Have you checked that the file modification times have been updated after re-publishing?

#19 Re: Backlight Support » Restrict metadata published with images? » 2017-10-06 09:44:10


Which file rendition are you looking at?  e.g. thumbnails, photos, photos-for-download.  What version of the Publisher LR plugin are you running?  The latest should be 3.2.2.

#20 Re: Backlight Support » Restrict metadata published with images? » 2017-10-06 09:38:19

rsamco wrote:

Therefore my conclusion that the "TTG Publish Service" is completely broken w.r.t. metadata filtering. But I still can't believe that I'm the only one to have experienced & reported this problem (i.e., I'm still questioning my own sanity).

Your conclusion is wrong.  This works as expected for me and always has, so it can not be 'completely' broken.  Are you by chance reviewing metadata on images that are cached in your browser?

#21 Re: Backlight Support » pages issue » 2017-10-04 05:16:31


I had missed that you’re attempting to run Backlight on nginx. Had you seen our article on this? … web_server

#22 Re: Backlight Support » New error on previously working site » 2017-10-03 19:07:59


I see that your site is now blocked by Wordfence.  This post suggests it is an issue with the Endurance cache on Bluehost and provides suggestions: … st-8809398

#23 Re: Backlight Support » New error on previously working site » 2017-10-02 04:50:20


The version of Parsedown in /lib/php would have been from a CE4 install. We have since updated CE4 to include a version of Parsedown that is compatible with PHP 7 (which didn’t exist during development of CE4).

The easiest solution would be to backup lib/php/Parsedown.php and upload the version from Backlight into that location.

#24 Re: Backlight Support » New error on previously working site » 2017-10-01 21:04:50


I see that you still have the SQLite error.  Try changing your PHP version to something else.  7.0 single php.ini works for me.

#25 Re: Backlight Support » New error on previously working site » 2017-10-01 20:49:32


What is the 'mismatched API issue'?  What errors if any are you seeing now?

Board footer

Powered by FluxBB