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.
Backlight doesn't know which version of the LR Plugin you have installed, so there isn't a straightforward way of determining whether it needs updating.
Updates to the LR Publisher are few and far between and to-date have not been required. We make a note of new versions in our blog posts and in the change log.
In this case, there isn't a real dependency between the LR Publisher 2.0.6 and the latest Backlight update. This error arose because of a bug in Backlight that tried to log a variable that wasn't there if you were using the older LR Publisher. I've since applied a silent update to module-publisher that addresses this.
Just switch it off it it annoys you.
Can you provide me with a Backlight admin login and FTP access via email. Also, which albums or sets are only visible within LR, and which are only visible within Backlight?
I'll leave that to you guys. I'd also not want to crap up the UI by adding more complexity. The LR to BL interactions are already complex as it is.
The setting would be under the Publisher settings of Backlight's settings, reachable via the Admin > Settings menu. There wouldn't be any changes to the LR album dialogues.
I'm not keen on making new functionality like this only available to the PHPlugin. Users should not have to use that technical approach for basic functionality.
This is caused by a combination of the Backlight publisher code assuming that the value for the existing Photo ID (i.e. the id of the photo used internally within Backlight) is being passed from the LR Publisher. That would only be the case for the latest LR Publisher.
The remedy is (as you're aware) to update to the latest LR Publisher. I have also put in a hot fix in the Backlight publisher code to remove this dependency, which shouldn't have been there in the first place. If you've already managed to update the LR Publisher then it won't be necessary to update the Backlight publisher. To do so, visit Backlight Modules, then click on "Reinstall" for the line for module-publisher.
Hi Charles, the session folder is there to manage everything related to your session. If it wasn't then the page wouldn't remember anything about your visit from one page to the next - things like which language you've chosen, whether you're logged in, etc. The only thing we doing different from the norm is to save the sessions within our data directory rather than in the default location (which would be some system folder configured in the system PHP settings).
I made this change to avoid a common issue of hosts misconfiguring their servers in ways that caused the default system location to not work.
Are you getting this alert for all files within the data/sessions directory?
Some remedies:
1. Whitelist that directory with ImunifyAV
2. If this is an isolated case for a single visitor, then email me that exact file so I can take a look -- perhaps somebody has attempted something malicious with your site, with the contents of that attempt being part of the file
3. Edit our session handling file so that it uses the default system location for sessions (I can advise on that if that's what you want to do)
4. Disable the custom session directory via a setting in env.php (this functionality does not yet exist so would require an update to the code from me)
Fetching the exif data from the image itself is new functionality in Backlight 2. This is to allow handling of images directly within Backlight so that images can be handled outside of LR.
I need to add checks for the EXIF module before attempting to use the function, and also review whether accessing exif_ functions can be avoided when images are coming from LR.
Hi Don, it looks like the exif module is missing on your server. Can you see whether that can be enabled within your host’s control pane or ask your technical support to enable it?
Hi Markus, you should be able to just download the entire backlight directory. The SQLite files reside within subdirectories of backlight/data.
I missed uploading the latest LR Publisher to our release stream. Please try downloading again.
The only way to get the latest PHPlugins samples is by downloading the Installer again and accessing them in the backlight/custom/phplugins/ directory.
Good catch, Steve! I had missed updating that on our release stream. Please download it again.
Hi Donald, can you find the file ttg.log in your Documents directory and email it to me?
Ben, if you add a filename-to-Title function, then slugToTitle should be updated too, shouldn't it?
slugToTitle accepts a string no matter where it came from. That's just an example of code or similar code that's already there.
Hi Jim, from a Backlight perspective that could probably be done by adding a new setting within the Publisher section of Backlight Settings, e.g. Single Image Page Title Format with options such as Image Title (the current behaviour), Filename (forced to used the filename, whether the Title metadata existed or not) and Filename Converted to Title (for want of a better name - where Backlight code would convert any textual part of a filename to a Title, as you've described).
The filename-to-Title functionality would be easy enough to code. We already have similar conversions in other places such as a slugToTitle utility function.
Does that sound like it would fit the bill?
Go into the Cart settings and change the Sales Tax Country to Netherlands. That will change the 'home' country for shipping from USA to Netherlands.
There’s no functionality to do so. Are you receiving multiple contact submissions from an individual user? Have you enabled reCAPTCHA?
I've been working on this. There are a couple of issues, and it's proven a difficult fix so far.
Hi Martin, sorry for the delay in getting back to you. I've only now had a chance to go through my emails. I'm glad that you've solved it.
* IIS is absolutely not recommended. That removes two requirements from the installation: Linux and Apache. IIS handles things differently.
* I would not recommend 777 except as a last resort. 755 should usually do.
* phplugins is a protected directory by design. Files from there are intended to be loaded by the server and not called from the web. You can unprotect it by modifying phplugins/.htaccess to remove or disable the Deny line. Modifying Backlight to do things it's not intended to is at your own risk.
* Allowing uploads from the public is an inherently dangerous operation. You would want to make sure they are saved to a benign location (e.g. a /tmp directory with noexec) with some kind of antivirus to protect against malicious files.
I'm looking into this. The backend creates in ID for each photo, but sees the duplicate as the same photo and returns the same ID as used for the earlier image. The error arises when LR tries to register that ID for a photo, when that ID has already been assigned to the earlier photo.
The fix will be to detect that the second photo is a different photo and produce a different ID in the backend, and set a distinct filename so that the second image doesn't overwrite the first.
Try logging out of Backlight admin or visiting in a different new browser.
There isn't anything for me to find by looking into this. If something like that happens, just go in and remove the album in the Backlight Admin login.
We have a fix in testing that we'll fast-track once we confirm it's working. This was caused by a regression in the most-recent maintenance release.
We have a fix in testing.
Hi Paul, which limit is that? The number of images per upload? That is configurable in the Admin settings within the Publisher section.