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'm not sure I understand what you're wanting from the layout. They are coded differently, and album entries in Backlight 2 are designed to e more responsive than those in CE4.
Maybe if you post pictures to illustrate the difference, it will be easier to understand what you're asking.
There has been no update. I need to take my laptop in for repairs later this week, and I'm hoping to find some time to start getting into some of the development tickets I've collected once I get it back.
Hi Pete,
In the sample PHPlugins file for pangolin, included in the /backlight/custom/phplugins folder of your installation, you will find this sample function:
function main_top() {
echo '<ul style="background-color:#FFF9C4;color:#000;margin:1.5rem 0;padding:24px 36px;">';
if (PASSWORD_ENABLED) {
echo '<li><strong>This gallery is private</strong>.</li>';
if (LOGGED_IN) {
echo '<li><small>The user is logged in</small>.</li>';
} else {
echo '<li><small>The user is logged out</small>.</li>';
}
} elseif ( $this->isManaged() ) {
echo '<li><strong>This gallery is client managed</strong>.</li>';
} else {
echo '<li><strong>This gallery is public</strong>.</li>';
}
echo '</ul>';
return false;
} // END /**/
This is the most up-to-date syntax, and demonstrated how to use the logged-in/out conditions. You'd want to use this logic to display the logout button, and perhaps change the "main_top()" location to reflect the location at which you'd like the code to appear.
And I'm not seeing any issues with transitions.
Backlight's page template has a menu assigned. If there's no menu in Wordpress, then it will display. If you have a menu in Wordpress, the Backlight menu is overridden.
Backlight menus do not show in Wordpress' admin.
Syntax.
function main_top() {
include 'someFile.php';
return false;
}
Honestly, probably not going to happen. Cluttering the thumbnails UI on a small display just makes it more difficult to do everything, especially for fat-fingered people, or other who struggle with touch-screens. It's too easy to miss the checkbox and hit the thumbnail instead, or vice versa. The symbols make thumbnails more difficult to see. And no one should be judging images based on mobile-size thumbnails anyway.
If you need to indicate to viewers they should make selections, then include a call-to-action in the gallery description.
Got it. I've replied via email.
We typically post update to the blog when updates are available. You can get notifications via email when we post to the blog. I've just re-enabled the subscription sign-up in the blog's sidebar, at http://theturninggate.net
^^^^ What Daniel said.
And the video demonstrates a fresh install, not an upgrade.
Password recovery?
http://backlight.theturninggate.net/doc … _passwords
On mobile, you will see empty checkboxes on large images, and filled checkboxes on thumbnails and in the large view. Images should be selected while navigating the large image presentation.
Hi Jon,
These days, I think the WP REST API is probably the way to go for this stuff. It was first packaged into Wordpress in the 4.7 release. Here's an example. This function will get five posts from your blog.
function main_top() {
$curl = curl_init();
curl_setopt_array($curl, array(
CURLOPT_RETURNTRANSFER => 1,
CURLOPT_URL => 'http://yourdomain.com/blog/wp-json/wp/v2/posts',
CURLOPT_USERAGENT => 'User Agent X'
));
$posts = curl_exec($curl);
curl_close($curl);
$posts = json_decode($posts, true);
if(is_array($posts)){
echo '<ul>';
for ( $i = 0; $i < 5; $i++ ) {
if (isset($posts[$i])) {
echo '<li><a target="_blank" href="' . $posts[$i]['link'] . '">' . $posts[$i]['title']['rendered'] . '</a></li>';
}
}
echo '</ul>';
}
return false;
} // END /**/
Resources:
cURL:
https://stackoverflow.com/questions/277 … n-http-get
PHP 5 For Loops:
https://www.w3schools.com/php/php_looping_for.asp
Convert and Loop through JSON with PHP
https://jonsuh.com/blog/convert-loop-th … s-objects/
WP REST API Handbook:
https://developer.wordpress.org/rest-api/reference/
And you can visit the URL in the code above to view the post data, so that you can see how to pick it apart.
You should also install the JSON Formatter extension for Chrome:
https://github.com/callumlocke/json-formatter
Looks good, and I'm glad to see you've successfully made the jump to Backlight 2.
Out of curiosity, what issues did you have with Lightroom 8?
Pierre, see my response to your other post, about Backlight location and publishing galleries to named folders.
I've replied to your email.
Backlight is fully separate from our old Lightroom plugins. So while you may be tempted to compare your experience to the older CE plugins, please resist that urge. Backlight 2 operates very differently, and by its own rules. We advise that you adhere as closely as possible to documentation, rather than assuming it will work the same as those things from years ago.
With Backlight 2, you may, of course, publish albums privately. Backlight should be installed at the root of your site, i.e. pideja.com/backlight. But you can then create albums at pideja.com/noces, if that's what you want to do. You may password protect those albums, hide them from view, etc.
Brilliant. You should have received codes for everything you have for Backlight 1, so get in touch with me if you think you've not received something you should have.
Are the index.php and .htaccess files in their proper locations?
I suppose so
Hi Chris,
Are you able to verify this? The .htaccess file may be invisible by default, so you would need to set your FTP client to show invisible files. This is usually done via the View menu or Preferences, depending on the FTP client.
I can see that /backlight is accessible on your site, so it would seem to be the case that the problem is with either or both of the index.php file, or the .htaccess file. Please ensure both are in place; or maybe just upload fresh copies.
Have you tried to publish any galleries yet, either from Lightroom or from within Backlight? Have you had any problems with that?
Just set the page breakpoint to a higher value.
Ah, I see. Short album descriptions do not support Markdown. That copy gets used in unformatted places, SEO, social media blurbs, etc.
All software has bugs. Lightroom is full of them, and many of those bugs have been in the software and have gone unfixed for years on end. And that's Adobe, with loads of funding and countless engineers around the world. We're two guys building software out of our homes.
And we have a solid track record of fixing bugs in a timely fashion when we find them. And one of the big wins in Backlight 2 is the automated update system, which allows us to fix bugs and roll out fixes more quickly than ever before, while making it dead simple for customers to update with released changes.
We provide this forum as a venue to assist our customers, and provide a direct line of communication between those using of the software, and those building it. Also something you don't get from Adobe. So, what I do not appreciate is someone coming in here with an attitude, being entirely uncooperative with the support process, and implying that we're releasing half-baked software, which is an entirely false and disrespectful statement.
If you come in here for help, we'll help you. If you find a bug, we'll fix it. But if you come in here and you're rude to our team, or to our community members, then I frankly do not care whether you continue to buy into our product.
Maybe something to do with Backlight being in a subfolder, .../noces/backlight.
Typically, should be at pideja.ca/backlight.
Markdown should be working. Exactly where are you trying to use it, and can you please provide a link to your gallery?
The metadata for the one-image album you've linked to is configured to display the Filename and image Caption on the thumbnail. The filename is correctly displaying, and the image has no caption.
There's no problem here, in that the page is displaying exactly the metadata it has been configured for. If you want to display other metadata, then change the template config and republish your image.
And maybe learn to use the software before you start complaining that it doesn't work. Because it totally does work, and totally IS working in your example.