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.
This is a PHP code incompatibility. There is no need to change to PHP 5.6 to upgrade Backlight.
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?
I've fixed this in my working code. This will be included in our next maintenance update.
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:
ttg-be/framework/helpers/SimpleHTMLTag.phpBernard, 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.
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.
That's by design. You can't use Paypal with zero amount, so the button is not shown.
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. http://127.0.0.1/info.php)
<?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 get.theturninggate.net 443or if telnet is not available:
wget https://get.theturninggate.netSimilar 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.
Backlight does use cookies to maintain user sessions. The browser stores a unique session ID that is sent to the server on every request. The server matches this to session data, which in most cases is information about the selected language, and the settings and language entries themselves. This is mostly for performance reasons, so that the back-end doesn't have to fetch the settings and language entries from the database for every page load. The chosen language would not work without a session and related cookie.
This use of a cookie is fairly typical across the web and is benign. There is no user data stored and nothing shared through other services.
Logging out of the admin in that browser should reset it for you. Adding ?destroy to the site url should achieve the same effect, e.g. http://yoursite.com/?destroy . That function will completely remove your user session (but won't destroy the universe or anything like that).
Looking at the source code for the LR Publisher, the URLs should be updated in the following scenarios:
1) Editing an album will update the URL for the album and the photos within the album
2) Moving an album from one album set to another will update the URL for the album and the photos within the album
3) Republishing a photo with metadata-only switched off, will update the URL for the photo
Item 3) is a weak point - the URL should be updated whether it's the metadata-only setting is checked or not.
I'm not sure why the third of your four scenarios happens.
Hi Dave, your host's technical support sounds very helpful. pdoextended.php is the file that accesses the database. The databases reside in seperate files. In particular, the file that's causing an issue is data/publisher/master.sq3.
I suspect that the file has not been corrupted but that there is some other system issue. Can you find that file and email it to me so that I can check whether there's anything wrong with it?
Hi Dave, what message are you seeing? Can you locate the file ttg.log under your Documents directory on your PC, and email it to me?
A longer answer. I'm keen to get this fixed so it's on the top of my list.
Hi Dave, who are you hosting with? If you're with GoDaddy then they may be blocking your uploads. If that's the case, have a look at your Publisher instance settings (by double-clicking the "TTG Publisher" bar in Lightroom) and see if there's a "Delay API Requests by n seconds" option under "Other Publisher Options". Enabling that will slow down the pace of requests and help avoid being blocked by the host.
It hasn't.
500 errors are difficult to diagnose. All it means is that 'something failed' on your server. Can you provide me with the exact steps to see the error, FTP and any TTG admin access needed via email.
Hi Bernard, thanks for confirming too.
The only thing I can think of is that there is something between the hosts at Strato and OVH and our server at theturninggate.net that does not like the IP address of that server. We have worked closely with the host of TTG and are confident that there is nothing at our end that blocks requests. There is definitely nothing on our server that blocks requests, as the traffic from Strato and OVH doesn't even reach our server.
This new server is at a different hosting company and on a different IP address. The application running on the server is identical to the old sever.
It works (for me).
Thank you
Great! Thanks for confirming.
Hi Bernard and Régine, can you please try to access the Backlight Modules page again and let me know if it's working?
I have set up https://get.theturninggate.net on a new server at a different host.
Good question. If you're using a non-virtual copy to edits come through, or only an unmodified rendition?
As above, however there are reasonable limits based on our pricing model. I wouldn't expect to be updating Backlight 1/2 to PHP 7.8, 8.0, whatever it may be, based on one-time purchases made ten years prior.
Many, or most hosts should allow you to specify a PHP version that your site uses. As an example, PHP 5.6 has been out since 2014 and has only just become unsupported after the 40th iteration (version 5.6.40). I would hope that many hosts will or do provide a similar option to fix your site to version 7.2 or similar, so that you don't need to worry about them upgrading the version and breaking compatibility with existing code.
This should have been addressed in a Backlight upgrade. Can you update your site to the latest version?
Hi Donald, I assumed that you wanted https://www.fotograafdonald.nl/ to show the contents of https://www.fotograafdonald.nl/2019/ without redirecting?
If that's not the case, then removing or renaming the index.html file at https://www.fotograafdonald.nl/ should fix it. Then index.php should function as a redirect and take users to https://www.fotograafdonald.nl/2019/
I'm not sure why, but it looks like the frame is causing the links to be unclickable.