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.
I have a fix for the Video ID in our working code. This had been lost during refactoring - the same Page Content section is currently used for Albums, Album Sets and Top-level Galleries, with Video ID not being applicable to the latter two. This will be released with our next maintenance update.
Thanks for the explanation. This can be done in Backlight's Publisher in the following steps:
1. Click Publisher in the main menu
2. Click Edit for the entry for JCHS Galleries
3. Under Base Settings, change the value for Top-level Gallery Directory
4. Click Save
I don't think your approach is the best way of doing it though. Top-level Galleries are limited in functionality and not intended for managing access, or even for renaming on an ad hoc basis. I would instead recommend keeping a common Top-level Gallery Directory and giving each client an Album Set underneath it. To lock the client out, you could then add an access code for the Album Set without giving the client the access code. Or alternatively, you could set up an access code from day one, and then change it to prevent further access.
Hi David, which image would you want to show up as the Hero in a search result?
Hi Patrick, it already is using that template, and it's appearing to me as a light background that matches the rest of your site. Perhaps logging out of admin will let you see the correct template in that browser?
FYI, I determined the template/s being used by looking at the Search page source and reading the <body> class attributes:
<body class="pangolin type-album template-id-48 album-template-id-68 cart-unready crg-unready" data-layout="1col right">48 corresponds to the page template "PJL LT1" an 68 to the page template "PJL LT1 Galleria Search"
I notice though that the search field doesn't render properly in that template. I don't know whether that's because of any incompatibly with using Galleria as a search template or not.
We'll look at automatically disabling the hero image when a template is used for Search.
It's generally a bad idea to remove gallery files via FTP. Backlight is meant to manage these in conjunction with the database entries so that the data and physical files are consistent. Can you post details about what you're seeing and what you're expecting to see, with URLs? I realise you've posted some links above, but it would be good if you could post current links along with what you're expecting to see.
Along with that, can you email me a Backlight admin login so that I can see what's happening there.
Which search page is it showing and which do you want to change it to? I’ll have a go in your admin and see what I can find.
Thanks, Patrick. I've cleaned up the Publisher database. Can you see whether changing the search template now works correctly?
Let me know here if there are any further issues when working with the Publisher.
Hi Rutger, that could be an issue in the contact form determining your current page address. Can you please email me a Backlight admin login so that I can look into this?
Hi David, I don't think there's a way to. Hero images draw an image from your album, and the Search is not an album. Matt should be able to confirm that. Which image/s would you want to use as the Hero for Search?
Can you please email me a Backlight admin login? I'll see if anything's amiss and try to create a hidden album to see what issues I can find.
That's great. Do you have 2FA working? I prefer to use it as it gives that extra peace-of-mind.
Hi Patrick, I can see what looks to be the problem - some settings remain in the Publisher database that should only exist in the Admin database as of Backlight 2. That means that the value you're saving for the template will be ignored with the old settings taking precedence. I can remove these old settings for you if you like. Let me know.
What has been your upgrade path for this site? e.g. BL1 to BL2 and then Bl2 to BL3? This issue of old settings shouldn't be happening any more.
Hi Xevi, I thought we had a setting to bypass 2FA, but that doesn't seem to be the case. Can you see whether you can reset your password with the instructions on this page: https://backlight.me/docs/password-retrieval
In particular, look at the steps for "In the event that you are not able to receive the email ..." Note also, that the 2FA codes are also logged in the same log file, so that may be useful as well to get a code that you can't receive by email.
It’s on our to-do list to provide this feature within the Backlight admin. No ETA on this.
/backlight/admin/admin/login is actually a valid URL, although that's not a URL that Backlight should send you to.
The first 'admin' refers to the main application you're in, and the second to the 'admin' controller of the application. BL2 and 3 suppress the second so that it should not appear for aesthetic reasons. In other cases, something like the 'admin' controller of the 'publisher' application looks more presentable, at /backlight/publisher/admin.
Can you provide access at all? As it stands, a site that we can not see on a server that you manage, I don't know what you expect us to be able to do to help.
Are you running the latest version of the LR Publisher? It should say 5.0.1 in the Plug-in Manager (available under LR's File menu).
If you are and still get that error, then can you dig out the log file from your PC and email it to me? It's called ttg.log and should either be directly under your Documents directory, or in a subdirectory called LrClassicLogs.
Perhaps. One more thing to forget during deployment and any version number wouldn't be updated until module updates had been run. We make a note in our blog posts when LR Publisher needs updating, which is seldom.
Hi Mark, further from my last comment. I have looked into this and there was an issue in the upgrade script that caused BL1 to BL3 upgrades to miss some necessary BL2 upgrades for Publisher. I have fixed this on your site by changing the version number of Publisher back to the pre-BL2 upgrade version. That has successfully completed all upgrade steps.
I have released a fix users who have yet to upgrade from BL1 to BL3. Sorry for the trouble this has caused you.
Hi Mark, due to the sensitivity of albums that should not be visible, I have run a query on your database to mark all albums that have usernames as protected. This appears to have worked across a number of galleries I've tried.
Thanks for the suggestion. Added to the list of possible enhancements.
I'm afraid I can't offer advice on a local site that we can't see. The error is unknown to me.
As the message suggests: invalid reCAPTCHA client ID. Please check you entries for your reCAPTCHA Site and Secret keys in the Backlight settings.
Hi Jan, Backlight needs the 'exif' module to be installed. This should be a standard module. Can you see whether there is a setting in your cPanel to activate this module (somewhere in your PHP settings). If not then you'll need to ask your host's technical support to enable it.