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 am in the process of reorganizing and updating our existing documentation, and writing up some new topics for Backlight 2 and its add-ons. This is a work-in-progress, as you might imagine. A part of this process is reviewing docs from under Backlight, updating and moving them up into the Backlight 2 section; some of it is just writing all new docs. Therefore, expect to see docs disappearing from lower on the page as I move them up, or break them apart.
I've just spent the last few hours specifically working on docs for the Client Response Add-on:
http://backlight.theturninggate.net/doc … t_response
I realize this is not comprehensive. There will be more. I'd like some feedback, though, on what aspects of using Client Response you feel could particularly benefit from more documentation.
You might have a better experience using Galleria to run your full-screen.
I also see there's a newer version of Vegas Slideshow available than the one currently included in the Theater add-on. I've opened a ticket for myself to make that update.
The default shadows are subtle in that their purpose is to ensure that white UI elements remain visible against light areas in underlying photos. They are simply a tool for legibility, such as in this example:
http://theturninggate.net/galleries/01- … a-default/
What do you mean by "selected"? Is that just the image that's been clicked to open the slideshow, or are you asking about an image that has been marked as a selection in the client response features?
Nice looking site, Thom.
I have one piece of feedback, though, and it's that the navigation menu is very difficult to read, being white on tan. I'd use higher contrast colors to improve legibility.
Backlight 2's Publisher works just fine with Lr6.
Unfortunately, it's not possible to insert HTML into album title or description, or image titles or captions. This is due to a variety of limitations, such as code structure, data sourcing (from Lightroom's metadata, for example), and in how we use this information (oftentimes in places where HTML cannot be embeddings, such as in IMG alt attributes, the document's TITLE element, social media Open Graph Protocol, etc.)
Re: #1
You can also use PHPlugins to create a custom image loop, and could theoretically let you create galleries of whatever style you like. However, you say you're "not a code-guy", so ... just worth pointing out, the functionality is there to allow you to do these things.
You can disable the breadcrumbs. Or you can implement some custom jQuery to move them elsewhere on the page. But the built-in options won't do what you're asking about. The gallery presentation and the breadcrumbs are separate components on the page.
The latest version of our phplugins-pangolin-sample.php includes two examples of note, beginning on lines 492 and 510. These show how to call up album information and create a custom image loop in an album. That's about the extent of what I am prepared to support for album customization. You are, of course, welcome to be as ambitious as you like with things, but I can really only support what's "in the box", so to speak.
I could recommend trying to keep your customizations within albums, rather than trying to over-complicate things with pages and album embeds.
By "... current latest versions of Backlight and its add-ons," I was of course referring to Backlight 2.
Instagram apparently does not allow sharing from web sites ...
Instagram is very much focused on users posting their own images from camera phones, and seems to actively discourage sharing of found images.
Might be that I'm tired, but I'm not quite following this. What's going on on the page/album without PHPlugins, and then what does the PHPlugins function look like?
This is splendid. Really digging it!
If you have any thoughts to share, I'd love to hear about how you've gotten along with the language/localization features in Backlight 2.
It's been a little while, but revisiting this issue to see where we stand on things. I am NOT seeing this issue in our examples of Cart or Client Response here on The Turning Gate, running the current latest versions of Backlight and its add-ons.
Anyone else?
Nice work! Looks great.
I've just written a helper script in our working code to solve this. Ended up being a bit more complicated than I was originally thinking, but it should do the job.
- if hitting a single-image page from the gallery, no change. The Back button will return to gallery.
- if hitting a single-image page from a page-embedded gallery, Back button will return to the page.
- if previous, and navigating to next or previous image, track the original referrer using a URL parameter. The Back button will return to the page.
- if referrer is an outside address, the Back button will behave as a Close button, and will return to the gallery (i.e. clicking a link to image page on Facebook, the Back button will NOT return the traveler to Facebook).
This should go out with the next update.
I have similar gripes with iOS Safari's UI.
Regardless of thumbnail layout, though, the default slideshow should give you as close to a full-screen viewing experience as can be had in iOS Safari.
I personally think the slideshow in pangolin-album gives the best mobile experience can be had in Backlight. I prefer it to the Theater or Galleria presentations.
If you had Theater for Backlight 1, then the version for Backlight 2 is also a free upgrade using the discount code we sent you.
The logic kicks in whenever the caption height is larger than 18px. You've increased the caption size from 0.75rem to 1rem in your custom CSS, which is causing the problem. If you want larger caption text, while preserving the intended behavior, try this as a compromise:
.fancybox-caption-collapsible .fancybox-caption {
font-size: 0.875rem;
line-height: 1.125rem;
}
Can you provide a link to your videos?
I spend an afternoon trying to get Paver to work, and it wasn't working out. It's tabled until I have time to research alternatives. Still on my mind, though.
The button is only supposed to be there when a caption needs it, which is when the caption overflows a single line. Recent changes to Fancybox have required some rewriting in this area; last I looked at it, it was passing my tests. But if it's exhibiting buggy behavior, then it will need another pass. Examples would be helpful.
Thank you, Oliver.
Unfortunately, I personally have no experience with the Unlimited Sitemap Generator, so cannot advise one way or the other.
Ah, deleting the preferences file. The magic fix for all sorts of Lightroom ailments