Community @ The Turning Gate

Support community for TTG plugins and products.

You are not logged in.

#1 Re: General » CONGRATULATIONS to Matt & Ben! 12 years of TTG! » 2019-04-17 15:17:23


Thanks for the kind words, John! Here’s to the next twelve years.

#2 Re: Backlight 2 Support » sudden death » 2019-04-14 08:41:23


^ That’s very helpful.

This entry in your own php.ini file may work:

mail.log = /dev/null

That sends any logging to the null device, effectively making it disappear rather than try to write to a file.

#3 Re: Backlight 2 Support » sudden death » 2019-04-14 07:12:47


That sounds like a misrepresentation of our software. As I wrote in the other topic,  the issue is a misconfiguration of your host. Backlight does not attempt to write to that location or that file. You’ll need to push harder with your host’s technical support.

#4 Re: Backlight Support » Slow Backlight » 2019-04-13 07:01:53


Hi LeMa, that sounds like they didn't look closely at it.  There's nothing that can be optimised in code to fix the slow speed of static files, which I see as an indicator of poor server performance in general.  Backlight is already heavily optimised, using an efficient caching mechanism and cache headers for files.
Backlight should be performant for sites with tens of thousands of photos.  Do you have that many?

Have you removed Backlight from your server?  I can no longer reach it at

#5 Re: Backlight Support » Slow Backlight » 2019-04-12 07:48:47


Thanks for the access details.  It looks to me as though your host is just slow in general.  For example, static images are taking far longer than they should.  This image took over 4 seconds to load: … D-7949.jpg
A similar sized image on my own site (shared hosting at Bluehost) takes about 0.3 seconds to load.

I suggest taking this up with your host.  There may be more load on your server than there should be.  They would need to either provision more capacity, or move you to another physical server.

#6 Re: Backlight 2 Support » Contact form test email fails » 2019-04-10 13:19:33


Your host is blocking calls to the gmail server. This is quite usual.
Your best option is to send using the ‘mail’ setting rather than ‘smtp’, and setting a from address that matches your domain.

#7 Re: Backlight 2 Support » Select Image Question » 2019-04-02 21:31:58


Hi Michael, that's an interesting approach.  Have you looked at using sessions instead?  Ephemeral data related to site visits shouldn't need to be saved in a database.

#8 Re: Backlight 2 Support » Select Image Question » 2019-04-02 05:05:43


Hi Michael, can you share how you solved this?  My comments about wholesale updates to the Cart don't apply to CR or Backlight as a whole.

#9 Re: Backlight 2 Support » White Screen » 2019-03-31 07:29:39


Hi Patrick, if Rod's suggestions don't solve it, please provide me with FTP access my email so that I can look into it.

#10 Re: Backlight 2 Support » I can't publish photo's from lightroom CC2018 » 2019-03-31 07:07:12


When does this error happen? 

You'll need to take this up with your host's technical support.  This error occurs outside of Backlight code execution.   There's nowhere in our code that attempts to write to that location.

#11 Re: Backlight 2 Support » I can't publish photo's from lightroom CC2018 » 2019-03-27 07:43:17


Sorry I'm late to the party.  The exif_read_data could probably be solved by reinstalling the Backlight Publisher module.  To do so, visit Backlight Modules and click 'reinstall' for the line relating to Publisher.  That should solve it for publishing from LR, but will still leave publishing from Backlight broken, until the exif module is added to your site.

Can you provide me with FTP access via email so that I can look into what's causing the 500 error?

#12 Re: Backlight 2 Support » LR publisher » 2019-03-17 06:56:03


It should be compatible.  I'm not aware of anything in the BL2 Publisher that would break in LR5. 

Some information on the compatibility between our two LR plugins: There are two things that make a Lightroom plugin unique - the install location and the unique internal identifier.  To have two operational Publisher plugins, both need to be unique.  The install location is straightforward.  The plugins have different names so will appear as different sets of files to LR.  We only use two internal identifiers.  One for the CE3 plugin, and another for the CE4, BL1 and BL2 plugins.  That means you can have operational plugins for CE3 and one of CE4, BL1 and BL2.  The BL2 plugin is compatible with CE4, BL1 and BL2 websites, so there is nothing missed from only being able to install one of the CE4/BL1/BL2 plugins.

#13 Re: Backlight 2 Support » Plugin for LightRoom 6? » 2019-03-17 06:47:50


We still endeavour to have CE4 work on the latest version of PHP.  What errors are you seeing?

#14 Re: Backlight 2 Support » How to access Metadata Category field in php plugin » 2019-03-12 18:10:27


The Category is only used for mixed pricing and only saved when mixed pricing is enabled in the associated template.  In that case it can be retrieved with:



Another way of getting this would be to set either the Metadata One or Metadata Two field in your album template to {Caption}, republish the photos and then get the value with either:




That approach would be independent of any cart settings.

#15 Re: Backlight 2 Support » credentials not recognized » 2019-03-12 17:51:37


Hi Pierre,  please check your email.

#16 Re: Backlight 2 Support » credentials not recognized » 2019-03-09 05:51:09


Backlight 2 does not store plain text passwords, so is unable to retrieve passwords.  All it can do is provide links to reset the password.  When you visit the Forgotten Your Password? link, if the Username and Email are found, then an email is sent out, and also, the reset link is logged to the latest file under backlight/data/admin/logs/.  For example, after trying it on my development environment, I have the file:


containing the following contents:

[08-Mar-2019 20:38:13] TRACE: To reset your password, visit the following link: http://backlight2.local/backlight/admin/reset/339c22e403d7063cd630fa2f1b279da4d1c25b18/

The logging is useful as a fallback when emails aren't going out or being received.

Of course, that won't help if Backlight doesn't recognise your username or email.  Have you set an email address for your admin account?  After installing or upgrading to Backlight 2, you should have been prompted to update settings on the next login, including adding an email address to your admin account.  If you hadn't set that, then there probably isn't an email address associated with your admin login. 
If that's the case then the only way to solve this is to edit your database directly.  I can do that for you if you can provide me with FTP access via Email.

#17 Re: Backlight Support » Cannot login Backlight » 2019-03-07 08:33:15

Daniel Leu wrote:

Oh, I forgot that with Backlight 1 there is no need to login in order to upgrade..... Installing the latest version should fix this issue.

Another trick, in Backlight 2, is to visit backlight/installer/ again.  Doing so will fetch the latest core modules (e.g. admin, framework, designer, publisher, pangolin-* modules) and install them over the versions of the modules that are already there.  That should help recover from any code issues within the Backlight admin that prevent logging into the Backlight admin in order to update modules.  That of course assumes that the installer code doesn't have issues on that server.

#18 Re: Backlight Support » Cannot login Backlight » 2019-03-07 05:00:12


This is a PHP code incompatibility. There is no need to change to PHP 5.6 to upgrade Backlight.

#19 Re: Backlight 2 Support » Change Order Button not functioning correctly » 2019-03-04 13:51:49


Hi Michael, thanks for the encouragement!  The fix turned out to be quite simple, but was hiding from me.  One of those situations where I was going blind looking at a single line that looked correct.  Can you visit the Backlight Modules and upgrade the Cart module to version 5.0.5?

#20 Re: Backlight 2 Support » Small bug in Backlight Admin » 2019-03-04 13:24:22


I've fixed this in my working code.  This will be included in our next maintenance update.

#21 Re: CE4 Publisher » CE4 website suddently broken » 2019-03-03 12:30:21


CE4 should work in version PHP 7.  That particular incompatibility has been addressed, and can be fixed on your server by downloading the latest version of TTG BE and updating it.  In particular, replacing this single file should fix it:


#22 Re: Backlight 2 Support » Strange problem with migration from test to final site » 2019-03-03 06:23:38


Bernard, just to confirm what Rod asked: is this issue limited to the "Go to published..." function from LR?  The important thing is that your site is fully functional on the new URL and that updates are correctly being applied to your site.

#23 Re: Backlight 2 Support » Unexpected error: Module 'SourceGuardian' already loaded... » 2019-03-02 13:14:43


Hi Gary, The advice is applicable beyond Bluehost. I would be having the conversation with your host - why did they switch you to a PHP version with a broken configuration. We can’t help if hosts do that to customers.
On that, the only unstable thing is the host’s configuration and not the version of PHP they are providing.

#24 Re: Backlight 2 Support » Cart Behavior with $0 amount on checkout Paypal does not appear!!! » 2019-03-02 12:21:38


That's by design.  You can't use Paypal with zero amount, so the button is not shown.

#25 Re: Backlight 2 Support » Newbie....Backlight 2 install error on Synology NAS » 2019-03-02 10:34:19


Hi James, Backlight requires a well-configured and supported Linux server.  As you've found, a Synology NAS doesn't fit the bill out of the box.
Can you check that the Curl PHP module is installed?  If you add a file called info.php on your server with the following contents, then view the file in your browser (at e.g.

<?php phpinfo(); ?>

There should be a section for curl with a bunch of settings.  If it's not there then you'll need to install the module. If the PHP Curl modules is already installed, then there's something in the PHP, Apache or server configuration that's blocking requests to external servers.  A first point of diagnosis would be to run the following command from your terminal:

telnet 443

or if telnet is not available:


Similar commands exist for the curl linux command.  Whichever one is available should be able to connect to the server.  That will at least indicate whether your server can connect to ours or not.

Board footer

Powered by FluxBB