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.
Yep, what they said. Just hook into Fancybox to launch whatever modal content you have. There's zero reason to install your own modal library. We've already taken care of it for you, such that you won't need to use PHPlugins, custom stylesheets, or any other advanced features. Just drop the right markup into your content and you're good to go. It's as simple as this:
#About
Lorem ipsum dolor sit amet, consectetur adipiscing elit ...
<a href="#myModal" data-fancybox>MyModal</a>
<div id="myModal" style="display: none;">Modal content</div>
Oooooookaaaaaaay ... I found your messages in my spam folder, Tom. Along with other messages I have apparently missed. And a bunch of crap about my @theturninggate mailboxes having been hacked. So that's just great.
I will try to look at this within the next few days, but I apparently have some catching up and some damage control that I need to do. =/
Hi Tom,
Sorry, I haven't checked in in a few days, and have been off of my computer most of the weekend. I haven't received your emails. Can you send relevant info to mjcampagna at gmail?
Hero image is not ideal for custom thumbnails, unless you make your thumbnails the size of a full image ... which would be just fine, I think.
Backlight forms are not meant to work in Wordpress. You should checkout Wordpress plugins. Contact Form 7 is the one I've always used.
Did you clear the template cache? Embedded albums don't refresh their settings as their standard views do.
So, you want the hero image to display on the Home page?
If so, trying clearing the template cache.
Hero images should display with embedded albums. This was unintentional, but hurray for unforeseen side-effects. My first inclination was that I should fix it, but it looks like people like having hero images included, so now I'm thinking I'll try to put some options around it instead.
I think the lazy-loading throttle has got nothing to do with it. It's just a browser issue.
also worth checking, are you able to use the regular [gallery] Wordpress shortcode, or does it fail as well?
If I'm going to debug, I'll need access to the Backlight and Wordpress admin areas, and maybe FTP access (so that I can look at the files created by the WP theme). You can email me.
Looks great, Nico!
The only suggestion I have is in regards to the cookies notice. You've changed the label on the "Opt-out of Google Analytics" checkbox to just read "Google Analytics". In doing so, you've changed the polarity of the messaging. Now, enabling the checkbox looks like an opt-in, when it is, in reality, an opt-out. And so, people wanting NOT to tracked by Google Analytics would leave the box unchecked, and then WOULD be tracked.
Yeah, I'm aware. Thing is, that's all coming from YouTube, so it's out of my hands. If there's a fix, I haven't been able to find it yet.
Why not embed a galleria slideshow, and just add a new image to the album every month?
It's not an oversight. There is intentionally not a font-size slider for body text. Maybe once in a year someone raises it as an issue, so I haven't felt bad at all for not having it. Also, people no longer publish content with WAY TOO SMALL TEXT, the way they regularly used to do with the Lr plugins. That's a win.
You should probably wrap the whole thing in a condition to determine whether or not you're dealing with an album.
if ($this->hasAlbum()) {
...
}
You can see other examples of this being used in the samples.
Yes, and no. There are no options to customize the quick search directly. Colors are inferred from your template settings.
Re: Lr/Mogrify2, Lightroom doesn't allow us to route our export through another plugin.
Search pages should always use a pangolin-album template.
Everything Daniel has said above is accurate. Highslide could be implemented either using PHPlugins or via JSON API. You will just be subject to all the same limitations that were reasons we dropped Highslide. Lack of mobile suitability and no updates since 2011 being high on that list.
I've found your orders and updated you Backlight 3 order to match the existing Backlight 2 orders. You should now be able to perform the upgrade. If you'd like me to update all orders to use a new email address, please email me directly.
Having to use an iframe is most often symptomatic of doing something you shouldn't be doing, or doing something that might be achieved in a better way. Valid use cases for iframes are few and far between.
We have never advised using iframes (except maybe with the Pym support in Theater, but that's really an odd duck), and still consider it to be generally bad practice. We have not made any changes in Backlight 3 to improve the iframe experience, as there's really nothing for us to do in that regard. Most problems you would have with iframes are inherent to iframes, are often intentional limitations due to security concerns that the browser is attempting to protect you against, and there's nothing we can code to change that.
Otherwise, I'm not entire sure the specific "problem(s)" you're referring to.
You're mixing PHP into JS. You can't do that.
Basically, your entire "done:..." function, you're writing as PHP.
To be more specific, we only have a Publisher plugin for Lightroom Classic.
But you can export JPGs from any software, and upload them into Backlight. I personally use Capture One Pro as my primary processing software.
Okay. Maybe we wanted to limit markup getting thrown into it. PHPlugins it is then.