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.
Not able to check right now, but does the footer text not accept Markdown?
Jon, can you please email me your order numbers?
Well, This is embarrassing!
I have the same issue. Bought Backlight3. Clicked the Update link and site says it is still Backlight2. Tried the change email link as above and no deal. Link to screenshot below....
Your Backlight 2 and 3 orders look to have a matching email address. Try this, maybe?
https://backlight.me/docs/updating-order-details
Do you have cookies disabled on your iPad?
In Backlight 2, I think not possible.
In Backlight 3, this would be a perfect use case for the new JSON API. See this conversation for a bit of a start:
http://community.theturninggate.net/vie … 417#p65417
I don't know what "terrible banner" you're talking about. I also don't think your comment is strictly relevant to this thread. Perhaps you'd better open a new topic.
I think the new JSON API is likely to supplant the embed. Once things settle down a bit, I'm looking forward to flexing it a bit.
Yes, I'm seeing the same issue. I've fixed it for our upcoming 3.0.1 update. Thank you.
Padding will probably need to wait until 3.0.2 at this point.
The way I think about embedded albums is that they ought to just serve up the image grid, and that the page being embedded into will already have a content area for text, static images, etc.
The embed feature was never meant to be very robust, and it trickier than we'd like it to be. The intent was just to allow people to use an album on their home page, basically.
Well that's not great. Something to fix then. I don't want the hero image to embed.
And now there's a feature video:
http://theturninggate.net/2020/05/04/he … cklight-3/
Patrick,
I found your orders. Indeed, you had an email address mismatch. I've change your Backlight 3 order to use the same @pkriner email address as your Backlight 2 orders, and you should now be able to install the upgrade.
If you'd prefer all your orders to use your Gmail address, please contact me via email and I can update all of your orders.
Well, I've never seen that before. Did you provide the correct order number and email address?
You're still running Backlight 2, so try doing this:
https://backlight.me/docs/updating-order-details
Enter your order number and email address used to purchase Backlight 2. I'm hoping we'll then see modules again, and can upgrade from there.
Weird. I'm not seeing the issue opening your site in Safari. What version of MacOS are you using? I'm on Catalina, so the latest Safari.
loadHTML strikes again. Seems no matter how much we try to put guards around this piece of code, someone trips on it. It's been fine in our most recent rounds of testing, but whatever. I guess your host's PHP config doesn't like it.
I'm going to gut it for the next update, which should be coming along very soon. The code in question is to do with lazy-loading images in blog posts, which is something I've not been entirely happy with anyway, and have been wanting to rework.
My apologies for the inconvenience. If you can hold off on making new posts until 3.0.1, that'd be great. If your need is more urgent, please contact me via email and we can get you fixed up in the meantime. In which case, I'll need FTP access to your site.
I was also mistaken above, when I said that albums would have the Site feed in their head. We're working on some RSS feed improvements for our first update to Backlight 3, and I can see that albums do present their own feed in the head, and non-album pages then use the Site feed. My apologies for the misinformation above.
Behind: "site.com/set/album/feed" you have to add ".php" to make it actually work in the RSS reader
The part: "[Album RSS Feed](./feed/)" makes no difference , not that I noted...
That might be a quirk of your specific reader. I haven't had to do that in any of the ones I've tried.
The arrows are 50% opacity, regardless of color. They are never gray; they are black, and 50% opaque. When you mouse over them, they become 100% opaque.
If you want them to be otherwise, then you can override the CSS.
Edited above. The trailing slash -- "/feed/", not "/feed" -- is important.
First thing to decide, whether you intend to work in JS or PHP. Either way, the top bit of the documentation, "The API", defines the available endpoints. The endpoints are the same, regardless, but you're meant to understand already how to use them.
I'm not a PHP guy. If using PHP, I don't know the extent of your options, but cURL is one way you should be able to interact with the API. In phplugins-pangolin-sample.php, look for the function with "Get a list of blog titles from Wordpress JSON API", and that's an example how to use cURL, and then how to utilize the response to render HTML.
In JavaScript, I've provided two convenience libraries that allow you to interact with the API without having to write the fetch requests yourself. The library api.js is written in ES6 JavaScript, and should be used if you're only targeting modern web-browsers. If you're concerned about supporting older browsers, including Internet Explorer, then you should use jquery.api.js instead.
The simplest starter I can give is this, in PHPlugins:
function scripts() {
if ($this->hasAlbum()) {
$albumId = $this->album->getId();
echo '
<script src="/backlight/modules/module-publisher/lib/js/jquery.api.js"></script>
<script>
var backlight = new Backlight()
backlight.getAlbum('. $albumId .', {
done: function(data) {
console.log(data)
},
})
</script>
';
}
return false;
} // END /**/
And that will just log the response to the console. You'll need to figure out what to do with it.
Make sure you go into the Settings and enable the JSON API. That was a late addition, and I've just now added it to the docs.
Upgrading from Backlight 2 to Backlight 3, you shouldn't upload anything. Once Backlight 3 is purchased, the upgrade is performed like any update to Backlight 2. Please watch the video on this page:
http://theturninggate.net/2018/09/12/in … cklight-2/
The problem isn't with opening the correct image. The problem is that the preview image for the album is defined -- necessarily so, else there would be no preview image -- and so let's say the representative image for the album is image #1, and you share image #5 to Facebook.
On Facebook, people will see a link to the album and the previewed image will be image #1. The preview's description will be whatever the description for the album, not for the shared image.
So if you share 10 images from the same album, then you will have 10 identical posts on Facebook, all of which open different images.
Feel free to read up on Facebook's Open Graph Protocol if you'd like. Single-image pages exist, in part, so that we can provide image-specific OGP information to social media, so that when you share an image, you're actually sharing THAT image.
And yes, scaling on the y-axis is possible. but that would require a total overhaul.
Hi Graceson,
Just to make sure you've got it, the JSON API documentation is here:
https://backlight.me/docs/json-api
Some base knowledge of JavaScript or PHP is assumed, so it's not fully exhaustive.
In JS, you can interact with the API via the provided libraries, or you could use whatever your preferred style for making XHR requests. For modern browsers, that's the Fetch API; for supporting older browsers, then probably jQuery's AJAX. These are the two things being used by our libraries, so again, I'd recommend using them rather than writing your own.
In PHP, you should be able to make API requests using cURL. I am personally less familiar with PHP.
Either way, I would put the work into a PHPlugins function. There's already examples there how to inject JS, and I believe there's some use of cURL in one of the Wordpress-related samples.
Because the API is more intended for advanced users, I doubt I'll be blogging tutorials about it. But I will like cobble together some examples at some point, and we'll start to leverage it more within Backlight itself in future updates.
Thank you.
There's not much research to be done. You'll just want to create new templates using the pangolin modules, then reassign your albums, sets and pages to use them. Backlight 3 has a Reassign feature that makes that pretty easy to do. Or, if you delete an Okapi template, you'll be asked which template to use to reassign everything that was using it.
To get started, I'd create a new page or album, and make it private, hidden from view. Then use that while you design your new templates. When you're satisfied with the new template, then reassign your public pages, albums, etc.
Either is fine. Okapi still works in the meantime, and you'll just want to spend some time transitioning your site to the newer templates. The downside of staying on Okapi, of course, is that they haven't been updated in ... I don't know ... three years or something? Pangolin is where all the new features and improvements are.