Community @ The Turning Gate

Support community for TTG plugins and products.

You are not logged in.

#1 Re: Backlight Support » Backlight 2 » 2018-08-13 06:19:14


Backlight 2 and plugins will come with discounts for existing customers. Bear in mind that this project has been going for 18 months with hundreds if not thousands of hours put into it and that what we charge so covers support and feature upgrades for the life of the product.

#3 Re: Backlight Support » backlight not working yet please help » 2018-08-07 08:21:20


There's something not right there.  That error message should not be happening at /backlight/ and may cause other problems.  Can you provide me with FTP access via Email so that I can look into this?

#4 Re: Backlight Support » https » 2018-07-22 18:16:31


Strangely, I'm still getting the insecure message on your search page at
The identity plate is also still coming in over http, not https.  Looking at the code, the base URL is taken from the Site URL value in Backlight's settings.  If that setting does include https, then clearing the cache should remedy the problem.  Based on your above comment and the fact I'm still seeing it come over http and the warning, for some reason that doesn't seem to be the case.

Looking at your home page, the identity plate is coming over https.

#5 Re: Backlight Support » https » 2018-07-22 08:18:45


I suspect that the warning on is due to this warning in the console:

The page at '' was loaded over HTTPS, but requested an insecure image ''. This content should also be served over HTTPS.

Can you try temporarily assigning a template that does not use a banner image, to see whether the 'unsecure' warning goes away?

#6 Re: Backlight Support » https » 2018-07-22 07:40:04


I’m looking into this.

#7 Re: Backlight Support » Trouble with contact us email setup » 2018-07-20 08:37:57


Are there any errors in your Nginx error logs?  Are you running selinux, which may disallow a web server from making server requests?

#8 Re: Backlight Support » Trouble with contact us email setup » 2018-07-20 07:13:30


The method to contact Google first tries to use curl, if it's installed on your server, and then attempts to use file_get_contents.  Backlight expects false to be returned from those attempts.  While curl behaves nicely and returns false on being unable to call the URL, file_get_contents throws an exception.  I've modified my working code to catch the exception and return false, so that the Backlight will instead return the (slightly more) friendly message "Unable to contact reCAPTCHA service", along with continuing to show the contact form.

#9 Re: Backlight Support » Trouble with contact us email setup » 2018-07-20 07:08:16


The error is as stated.  The server is not able to contact Google to confirm the recaptcha, after clicking submit.  That error line is only reached in the codebase from the attempt to contact Google for recaptcha.  You may get the tick from clicking the recaptcha but that is not the end of the recaptcha mechanism.  The proof of the pudding would be to create a simple test php page called from your browser (so that it's via your web server and not command line) and see what results when attempting to run this line:

$output = file_get_contents('');

The expected result from that call is a response like:

"success": false,
"error-codes": [

It sounds like sending email is another issue you need to solve.

#10 Re: Backlight Support » Trouble with contact us email setup » 2018-07-19 19:43:40


Hi Bill, that looks like your server is unable to connect to the Internet.  The line of code is called with an attempt to contact Google to verify the contact form recaptcha.  That URL starts with (and includes parameters specific to the account associated with your recaptcha and the current request).

Can you ping on the command line of the server?  Can you connect to 443?  (curl should make a good test).
If not, you'll need to fix your server's network settings to allow this.  If you can connect on the command line, another potential blocker is selinux.  If so, you'll need to allow your web server to make contact to the Internet.  Another potential blocker is any iptables or other firewall that may be blocking outgoing requests from your server.

#11 Re: Backlight Support » PHP & MySQL - web host upgrading to new versions » 2018-07-18 14:25:04


Hi John, as above.  We keep Backlight updated for compatibility with the latest versions of PHP.  Unfortunately, each version of 7 has made changes that have broken our code in minor ways, that being 7.0, 7.1 and 7.2.  We endeavour to do our best to fix these issues as they crop up.

#12 Re: General » Website down » 2018-07-18 14:22:47


I would guess your host has changed the server software in some way.  This isn't related to a PHP version number, but instead to a PHP misconfiguration on the server.

#13 Re: Backlight Support » Site tries to use port 8443 » 2018-07-16 11:40:03


No worries. I’m glad to have been able to help. The proxy port issue is a discovery that will lead towards better code.

#14 Re: Backlight Support » Site tries to use port 8443 » 2018-07-16 11:13:45


That rewrite rule from our documentation looks to be incorrect. Can you try changing that from photos to photos-for-purchase?

#15 Re: Backlight Support » Site tries to use port 8443 » 2018-07-15 07:53:15


It looks like HTTP_HOST may be useful in determining whether the incoming port was specified in the browser URL or not.  I'll keep this in mind for any future solution.

Here is an example URL that fails to load an image:

Does that image exist at that location?  Are you running any URL rewriting that could be tripping it up?

#16 Re: Backlight Support » Site tries to use port 8443 » 2018-07-15 07:26:15


PHP Info gives me "phpinfo() has been disabled for security reasons"

In addition to the disabling in my earlier comment, also disable lines 181-185 in URLHelper, like this:

/*$cpuOld = URLHelper::currentPageURLOld();

if ($cpu != $cpuOld) {
	die('currentPageMismatch: '.$cpuOld.' !=. '.$cpu);

#17 Re: Backlight Support » Site tries to use port 8443 » 2018-07-14 18:54:54


Backlight attempts to construct URLs in a couple of places, using the PHP variable $_SERVER['SERVER_PORT'] and adding in the port number to the URL of not set to 80 or 443.  It looks like this is picking up the port from the web server (as I'd expect it to) and not the proxy server.

A workaround to avoid this would be to disable the two lines of code that add the port numbers to the URL.  These are line 400 in backlight/publisher/application/helpers/PublisherHelper.php and line 199 in backlight/framework/helpers/URLHelper.php.  They can be disabled by prepending // to the start, e.g.

//$host .= ':' . $_SERVER["SERVER_PORT"];

Can you provide me with a Backlight admin login via email so that I can see what the URL/port settings look like in PHP Info?  This may help work out a longer term solution.

#18 Re: Backlight Support » Backlight admin screen errors » 2018-07-12 10:23:01


Looking further into this.

* QUERY_STRING error.  It looks like your server does not set this variable when there are no parameters in the URL, e.g. nothing like  I'll put in a hotfix in the code for this.  In the mean time, if you want to make this error go away and are happy to edit files, the fix is to change line 72 of backlight/framework/helpers/AuthHelper.php from this:

if (preg_match('/a=phpliteadmin/', $_SERVER['QUERY_STRING'])) {

to this:

if (isset($_SERVER['QUERY_STRING']) && preg_match('/a=phpliteadmin/', $_SERVER['QUERY_STRING'])) {

* For the Internal Server Error, try changing the permissions from 777 to 755 for backlight/data/designer and everything under that, and any other directory you may have applied 777 to.  If that doesn't help, then please provide me with FTP access via email.

#19 Re: Backlight Support » Backlight admin screen errors » 2018-07-12 06:10:24


777 permissions are possibly the cause of the internal server error. We don’t advise to use 777 unless 755 failed.

Can you provide me with an FTP login via email so that I can look into these errors?

#20 Re: Backlight Support » Correct PHP version? » 2018-07-06 13:16:56


We support up to version 7.2. Each of 7.0, 7.1 and 7.2 have caused issues with Backlight in general that we’ve patched as we’ve gone along. It’s likely that you don’t have the latest version of the Cart. If you do want to try 7.2 again, I suggest first downloading the latest zip file for the cart and replacing module-cart.

#21 Re: General » Backlight - The future? » 2018-07-04 08:26:00


Backlight 2 is well into development and near to being ready for internal testing.  Stay tuned.

#22 Re: Backlight Support » Pallet/Column2 Not Formatting HTML » 2018-06-23 15:08:15


I've found that the LR Publisher hadn't included the Tray 2 field in the 'allow HTML' list.  I've changed this.  Please try downloading the latest copy of Backlight and replace the Lightroom Publisher plugin.

#23 Re: Backlight Support » Solved: Publisher can't publish new album - Disk Error » 2018-06-23 10:58:16


Hi Michael, that's positive that they were able to get your site going again.  Although it's owned by GoDaddy, it may still be under a different set of infrastructure.  If you haven't encountered the request blocking, then I would leave the delay disabled.  I haven't heard back from any users about which values they've found to work.

Do you have extra galleries that have been created?  If so, the best approach is to try deleting them from Backlight.  Visit Backlight > Publisher > Top-level Galleries, then Albums and click on the album name.  At the bottom of the View Album page is a Delete Album link.

I haven't heard of any customers with  Are you looking to move to them?

Thanks, wishing you a fine weekend too!

#24 Re: Backlight Support » unable to perform action : CreateAlbumSet » 2018-06-22 06:55:02


Hi Audrey (is that right?), is this a new site or updates to an existing site?  Can you provide a link to your site, and email me a Backlight admin, using the Email link in my signature?

#25 Re: Backlight Support » Solved: Publisher can't publish new album - Disk Error » 2018-06-20 22:04:50


Hi Alfred and Michael, that sounds like some promising progress on the issue.  Michael, are you able to ask your host for a similar change, or ask where in your control panel or files you could make a similar change?  I can't see it being a change anywhere in Alfred's hosted files.

EDIT: Michael, looking at your phpinfo page, it looks like the TMPDIR is already set in the same way as it has been for Alfred.  Is this the result of you contacting support?  If not, they may have provided a global fix.  Are you still getting errors?

To be honest, I'm not impressed with your host's remarks on this.
A properly-configured PHP environment should have SQLite writing to the correct locations, without any need to configure this.  This "one time courtesy" is fixing something that should not have been broken.
We have been very pleased with SQLite as a technology, which has exceeded our expectations.  It is fast and robust.  We have had thousands of supported installations over the years, with some sites having tens of thousands of photos, without any noticeable degradation of performance, or any loss of data integrity.
MySQL would be a more performant and robust solution, but I see nothing lacking in SQLite for what we need in Backlight.  The huge benefit of using SQLite is that the data is managed through files, and requires no setup of databases and users through the control panel, which would be a massive headache for us to advise across the various hosts that our customers use.

Board footer

Powered by FluxBB