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.
there are two places that can come from, the page itself and the contact form’s “Invitation” field. Try editing the contact form.
you can add the code to either hook, along with your existing code. you just can’t call a hook more than once.
were you already using the album_bottom hook for something?
have you tried adding the escape character to your translation?
I’ve reported the issue
should be. just use the appropriate hook. See the phplugins file for a list of them all.
can you post a link to the album displaying the problem?
"Admin users may navigate public, protected, and private albums freely while logged into Backlight's admin."
This is true only when I am using Internet Explorer. If using Chrome, I do not have unrestricted access to the protected galleries. I have not checked any private galleries yet.
This should work under all browsers, it has for me. Try clearing browser cache perhaps.
I think Ben will need to address the second issue
Master Access code can be found in the main settings under Publisher
custom thumbnails is the answer to face cutting
there are border-radius and border-radius of image settings in the template. Those will round the corners.
There is no current way to use just a select number of images. The image shown is chosen just like the cover image. So all those limitations apply.
You're probably ahead of me on understanding JSON
I was just looking at the TTG documentation on that. Looks like it's only meant for accessing albums, sets, and photos.
https://backlight.me/docs/json-api
So no contact forms.
There are plenty of contact form plugins available for WordPress though.
I too loathe the Gutenberg block editor. I'm using the Classic editor too.
You shouldn't need a special JSON plugin for WordPress.
seems like you're doing everything right.
no
well....maybe? Using the new JSON API perhaps?
Tom, have you enabled the https browser redirect feature in Backlight Settings?
hi Ben,
I've assigned a cover image. Still no hero image in a page with inserted album.
I thought you did fix that. Something to do with the big blank area showing up in a search page using a Hero enabled album template. I can't get the hero to appear in an inserted album on my test site.
The only control is to control the number of characters and the color. If you don't see the description color changing, try clearing template cache. (did you save the template?)
Or you could use custom css to not display the description. Right click on the element and Inspect Element. Should take you right there.
I'm splitting this off to its own topic
- Rod, I think you are right again about the album-titles. Not only the boxes are very small, but Backlight does not seem to take well to the HTML code. It takes it for part of the title. And that code you corrected was to be used to try to get the multi-language effect for the titles but sadly, it does not work.
Yep, you can't use html markup in css
I think I correctly identified the album set template but I'm not too sure how to use this. My album-set identifier is
marcogalleryset. I want to keep the thumbnail images, of course. So, for now all I have is.album-set-template-identifier-marcogalleryset #albums
but of course, it doesn't do anything yet.
this is your css:
/* Album titles */
.album-set-template-identifier-marcogalleryset #album-title
<div data-lang="en"></div>
<div data-lang="fr"></div>
first, there is no bracket after the selector
Second, you have html after the selector, not css.
what are you trying to do?
How can I apply this with the multi-language album titles?
As far as I can tell, you can't
I don't think the album title fields can take html
So the solution is to not use a div in writing the multi-language code for the form labels. Instead, use this:
<label for="contact-field_1" data-lang="en">Telephone-en</label><label for="contact-field_1" data-lang="fr">Telephone-fr</label><label for="contact-field_1" data-lang="de">Telephone-de</label>
You'll need to identify contact-field_1, etc. I assume they're in order.
This also solves the asterisk issue. I'm assuming that since divs are block level elements, they're pushing that asterisk down. Labels are inline elements.
what I see happening is this:
For forms that use multiple languages in added fields:
the font-weight for the default fields of Name and Email is coming from the form label styling
The font-weight for added fields is coming from the body styling
I'm also seeing a difference. It seems that the default fields of Name and Email are having a font-weight of 700 applied while the added fields are having a font-weight of 400 applied
This seems to only happen when multiple language code is added to the additional fields.
Whereas a form label that does not have multiple languages in the added fields gets a font-weight of 700 applied, just like the default labels.
One other thing I noticed is that if an added field that uses a label with multiple languages is also set to be required, the asterisk is pushed away from the text and ends up in front of the text box.
This one got a little lost where it was in the larger topic of multi-language support. So I'm giving it it's own topic.
The issue seems to be that fonts aren't being applied in the same way for all field labels
That feature has been a part of Backlight for a while now. I just wrote a post about it, in fact
https://ttg-tips-and-tricks.barbeephoto … -your-css/