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.
Interesting.
In this case I think he could probably just use it in his page source where he currently inserts the hearts to insert two (or more) different sized ones and wouldn't need to use any CSS.
I like the HTML <picture> tag for doing things like this but it is not supported in older browsers so you have to make that decision before you use it. In browsers where it is not supported it will just continue to use the default image and not resize, it won't break anything. I use this to have two different sized banner images for desktop and mobile.
<picture>
<source media="(max-width: 440px)" srcset="/backlight/custom/images/Short_Logo.png">
<img src="/backlight/custom/images/Regular_Logo.png">
</picture>
Since this is for mobile, I don't think there are many phones out there with browsers that don't support this.
you need to enclose the code within the function with
echo '
... code here ...
';
Excellent description of how sorting works.
Ah, sorry.
design > templates > template name > layout > breakpoint
I understand you can have multiple page templates with different phplugins files, I just wasn't sure that what he was looking for rather than do things differently on an individual album by album basis. And I wasn't sure you could get the album name in phplugins. Live and learn.
I think phplugins will apply to every gallery and not really show if a particular person has viewed a particular gallery?
You can add page copy to an album via Lightroom (edit album > page content) but I don't know what would happen if you tried to insert HTML via that route.
I'd also suggest that, once you get things working with just markdown and before you start tweaking with HTML you 'clone' your pages in Backlight to 'pagename-save' or something so you have a stable point to get back to if things go sideways. Go to designer > pages and click on the page name and you will see the option to clone the page.
BBEdit is a decent MAC editor fwiw.
I think you can also use
echo <<<SCRIPT
...
SCRIPT;
in place of
echo '
...
';
That way you don't have to escape single quotes. I'm no expert, though, so I could be mistaken.
I can get to: http://www.artofthewild.co.uk/backlight/admin/?a=login
but obviously don't know your login credentials.
No problem, obviously the folks who are legally required take precedence and there is always phplugins for those who want more granularity. Thanks.
add width="nn" inside the src tag.
my uploaded images are of the form "/backlight/designer/?c=page&a=image&p1=xx"
but I'm no web designer so I don't know what the significance of the difference in format is.
Look under designer > uploaded images and click on the image name and you will see the URL to use listed.
This does slightly decrease the accuracy of geographic reporting in analytics, so if anyone cares about this aspect it would be nice to have a way to turn it on or off rather than having it one way or the other by default. For what it's worth.
Turn off "Display Breadcrumbs" in your album set in Lightroom.
In your album template under Image Renditions you specify the size and quality of the jpegs that Publisher uses to 'publish' the album assigned to that template.
I wonder if uploading that album to the 'root' replaces the .htaccess file?
Did you try just "Spectral" as a prepend?
Instead of using Pages to display your albums create them under an album set and then use Menu Sets to have a menu item point to your main album set and the menu items for the individual albums will be generated.
I use an inline vegas slideshow on my main page and don't have any problems with navigation but I don't have any experience with the other slideshow types. Looking at the page source I see your slideshow has "cover : true" and mine has "cover: false" but I don't know if that means anything.
You might experiment with inline vs full screen and then just shrink and grow the width of your browser window to see how the menu behaves as it gets down to mobile size and see if that makes a difference.