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.
Hi Alex, PayPal keeps shuffling things around. The credentials can be created using 2. REST API Integration.
Hi Rod, that link works for me without issue from the page https://www.fotograafdonald.nl/2019/. Tried in Safari and Chrome. The redirect code above shouldn't impact the behaviour of outgoing links.
Hi Theo, it looks like the URLs are not being mapped correctly. All URLs are being picked up as the home page, even one's that should result in a 404 Not Found: http://www.theomolenaar.nl/broken/
I'll have a look via FTP to see what I can find.
I noticed that your host is running a 14 year old version of SunOS, and not Linux. The software running on it looks to be up-to-date, so I'm not sure whether the OS and age of it is a factor.
I'm not really following what's going on. Is there a specific URL where links aren't working?
Hi Ben, problem solved, thanks for your support. Tech support from my hosting company enabled the exif module.
Just curious, since I didn't have this problem before: is this because of the update of BL2 or is it something that went wrong on the server side of my website?
I'm glad you're able to get back on track. What's happened in Backlight is that I added code in version 2.0.6 to check for image orientation and to rotate images if needed. This fix largely applies to uploads through the Backlight uploader, but affects the LR uploader because the code is common between the two upload processes. Since LR produces images that don't need rotating, this check is redundant for images uploaded from LR, so I'll be looking to skip the rotation handling for this scenario.
While that should fix the error you've encountered, exif* functions are used by the Backlight uploader, for image rotation and extraction of metadata, so enabling the exif module on your server is best for the long term. I'm looking to add a check for the availability of the exif module and clear messaging and instructions for when it's needed but not found.
Hi Donald, can you try clearing your browser cache? Your browser might be loading the older JavaScript
While this isn't a solution, the latest changes don't touch the pricing schemes.
Thanks, Mark. I'm glad to hear.
Hi Jean-Paul, this is caused by missing support for the 'exif' module in PHP. Can you enable this PHP module or request your host's technical support to enable it?
The resizing is performed by completely different image engines between LR and Backlight, so the file sizes produced by the two will differ. That includes the way that each handles the JPEG quality setting.
The "etcetera" might be useful in seeing what the issue is. Make sure to update your LR Publisher from the Backlight Modules page, so that it's version 4.0.7.
The simplest test is to upload the content below into a new file called test_connection.php and call it with a URL like
http://yoursite.com/test_connection.php?url=https://get.theturninggate.net
(changing yoursite.com with your actual site URL)
This code strips out all other Backlight code to demonstrate that your host is blocking the connection.
<?php
if (!isset($_REQUEST['url'])) {
die('usage: test_connection.php?url=[URL]');
}
$url = $_REQUEST['url'];
$body = @file_get_contents($url);
if (!isset($http_response_header)) {
die('Unable to connect to the server: '.$url);
}
die('Connected and retrieved: '.$body);
?>
See our document on similar errors: http://backlight.theturninggate.net/doc … ule_errors
Step 3. is a workaround if you're host's technical support doesn't help.
Hi Bernard, it's HTTP access via the URL https://get.theturninggate.net
Further to the above, the ordering is working as-expected based on alphabetical filename ordering. This ordering is done at the database level, so doesn't provide us with an opportunity to add smarts to it.
Thanks for raising this. I've added it to our todo list to look into.
Strato websites seem to have intermittent issues in accessing our server at https://get.theturninggate.net. This may just start working for you. If not, I suggest asking their technical support to investigate why your web server is not able to reach https://get.theturninggate.net
Hi Xevi, you have a duplicate filename in your album. The latest Backlight update, version 2.0.6, addresses this. Make sure to update both your Backlight Modules and the LR Plugin.
I'm not sure what the cause was, but I logged in to your Backlight admin and cleared the Template Cache. The problem has gone away.
Hi Bernard, that's a very odd error. It looks like URLHelper is being loaded twice, when it should only be possible to load it once. Not an easy one to debug but I'm looking into it.
Hi Jim, the error on missing Framework is because your site is still looking for Backlight 1 files. Running the command "Update Album Files" under special links on the Backlight admin landing page should fix that.
Your listing of the directories shows that Backlight 1 files are still on the server. These will interfere with Backlight 2 and need to be removed. In particular, the /backlight/publisher/ directory should not exist. In Backlight 2 this is a virtual directory handled with URL Rewriting via backlight/.htaccess
See these steps in the upgrade process: http://backlight.theturninggate.net/doc … acklight_2
I would also take Wordpress out of the equation until you get past all of these issues. I have seen that Wordfence in particular can interfere with interactions with the backlight/ directory. You might find a hidden file within backlight/ that injects a call to WP and Wordfence before continuing to call backlight/
Something's not right then. As Rod commented, it should just work by changing the sorting criteria. Can you create a test album that exhibits the ordering problem (if you don't still have one on your server) and provide me with a link and Backlight admin via email?
Thanks. I've received it.
Hi Andrew, it looks like your host has disabled that function. We use it to determine whether sessions can be saved under backlight/data/, using an exclusion list of hosts that have caused problems. Can you ask your host's technical support about whether this has been disabled?
I haven't received anything. Did you send it to [redacted]?