Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
It sounds like something has changed on your server. Can you email me a Backlight admin login and your API Key so that I can look into this?
Hi Paul, the code has a limit of 1,000 thumbnails that will be returned in that list. Does it look like you're seeing that many?
If you think it's hitting that limit, then the limit can be changed by doing the following:
1. Rename the file backlight/env.php.skel to backlight/env.php
2. Edit that file, and add an entry near the top of the file for THUMBNAIL_THRESHOLD so that the top of the file looks like this:
<?php
define('THUMBNAIL_THRESHOLD', 10000);3. Restart Lightroom
Hi Régine, this is the same problem that your host had but then resolved. Can you take this up with them again, perhaps asking them to run a traceroute again?
I couldn't find it anywhere - who are you hosting with?
Hi Andreas, Backlight uses SQLite and not MySQL. One way to check would be to create a file on your server called info.php with the following contents, then share the link here for me to look at:
<?php phpinfo(); ?>It's on the radar to provide more helpful messaging. Did Rod's suggestion fix it?
Thanks for raising this Régine. I'll look into it.
Thanks for the suggestion. It's been something I've been wanting to implement. I can't yet provide a timeline for this feature.
Clearing the cache should have fixed it. I wasn’t able to log into your Backlight, but achieved the same effect for the search page by visiting
https://www.keylightphotography.us/backlight/search/?reCacheNormally you would do this via the Designer menu in Backlight.
Please provide me with FTP access and a Backlight admin login via email so that I can look into this.
Thanks, Daniel.
Hi Charles, this error has come about from an update to PHP on your server that the TTG BE is not compatible with.
I've put in a fix in the file CE4-TTG-BE-205b.zip in the shop. Can you download that zip file and upload this single file from the zip to your server?
ttg-be/framework/helpers/SimpleHTMLTag.php
Hi John, can you post the URL where this error comes up?
By the look of it, one of the older Backlight 1 index.php files is still on your server.
Do you know what error message you were seeing? If so, please copy and paste it here.
An update on the original post, above. In this case it looks like Strato has performance issues with SQLite. It takes over four seconds for just one of the database queries, which is about 50 times the time it should take.
So for anyone fighting with Lightroom, restart it every time you change something.
That's not necessary. It may be advisable to restart Lightroom after changing the API Key on the server, that's all. I have yet to investigate this.
I have noticed the same effect since updating to Backlight 2.0.5. I didn't notice that before.
Hi Markus, I doubt that anything in Backlight 2.0.5 would have affected performance like this. Who are you hosting with?
Can you share a Backlight admin and provide FTP access via Email so that I can look into this?
You don’t need to update the plugin. The LR Publisher plugin is stable and rarely needs updating. We’ll make it known via our blog if the plugin needs updating.
That's right. It's a limitation of Lightroom. The "Name" field is fixed and relates to the name that appears in the left-hand album collection. We don't have any control over its behaviour. All other fields are specific to TTG Publisher.
That is a limitation of Lightroom. The solution is to use the Album Title field for the title you want to appear on your website.
Hi Bernard, the LR Publisher for BL2 is designed to also work with BL1 and CR4. There should be no harm in leaving the CE4 plugin there and deactivated.
Hi Oliver, I found the problem and fixed it. It was some debugging code I had put in one of the module-framework files when woking out the issue with the connection to get.theturninggate.net. The modules page is now working.
Hi Oliver, I believe I may have broken something when looking at your server. I will log in again this evening Melbourne time and fix it. Sorry for the trouble.
Hi Scott, can you share a Backlight admin login via email? I will then try to create and publish to a hidden album to see whether I can find the problem.
Hi Scott, you can use it for any sites that you own on a 'fair use' basis. What we do not allow is for a single purchase to be used for multiple entities, especially where you are selling the construction of sites as a service or another party is running a business.
Examples of what we allow:
* Sites that you own and control. e.g. a site for your photography business, a site you may have for a personal interest, any test sites you may have
* Sites that belong to direct relatives that are not businesses. e.g. your partner's hobby site
Two examples that would NOT be allowed under a single purchase:
* Setting up a site for yourself then using the same Backlight purchase for a friend's business, or sharing it for your brother-in-law to use for his business
* Using Backlight as a design tool for a web business and selling implementations of multiple sites. e.g. building sites for local businesses that you act as the designer/site builder
If in any doubt, then please just ask us.
Hi Regine, I'm glad that it's working.
We have made no change to our server to fix this. We have not to date been able to isolate where the network connection has been failing (e.g. on your/customer's servers, in the network, or at our server), but it appears that it's now working for users on both OVH and Strato. It could be that both of those hosts share the same infrastructure, and that the issue has been resolved there.
Hi Anthony, the PHP version should not play a part in this. It may be the case that certain hosts provide different feature sets from one version of PHP to another, but that doesn't mean that we depend on any version (so long as it's 5.4 or newer).
We are looking into this ongoing issue. So far we have only limited information to go by, until one of the hosts that can not connect is able to run a traceroute test.