Community @ The Turning Gate

Support community for TTG plugins and products.

You are not logged in.

#1 Re: Backlight 2 Support » Update FontAwesome in BL 2 » 2019-01-27 13:27:44

rod barbee wrote:

You kept the rest of the file intact, specifically the code at the very top?

Yes.  Even did it again and got the same result.

#2 Re: Backlight 2 Support » Update FontAwesome in BL 2 » 2019-01-26 23:41:34

As an example, started with  phplugins-pangolin-sample.php and named it my-phplugins.php, and selected  it in the page advanced setup.  The snipped below did not work for FA5.6.3.

// Some example functions are included below. Feel free to delete or modify unwanted functions.
// ****************************************************************************************************

  // put your functions here

function scripts() {

echo '

<script defer src="" integrity="sha384-EIHISlAOj4zgYieurP0SdoiBYfGJKkgWedPHH4jCzpCXLmzVsw1ouK59MuUtP4a1" crossorigin="anonymous"></script>

return false;

} // END

#3 Re: Backlight 2 Support » Update FontAwesome in BL 2 » 2019-01-26 14:47:51

Matthew wrote:

All naming conventions are different in FA5, as compared to FA4.7, meaning that you will not be able to replace preexisting UI elements in Backlight. I simply wouldn't bother, were I you.

The problem arose when I upgraded to Backlight 2.  I lost some of my FA characters with what I assume was FA4.7.  Also, I use MacDown to develop any lengthy text passages, so I need to have it harmonized with Backlight to make sure the FA characters will look the same on the site after I copy and paste the text in Lightroom.  I changed the naming conventions on some pages, but lost MacDown compatibility (MacDown had been using a FA5.0.8 script as I recall).  I re-formatted the FA naming conventions on all pages where I use FA, not too difficult with search and replace using MacDown, and added the FA5.6.3 script to the text of each page.  It all worked, but required a FA5.6.3 script on every page, developed in MacDown or not.  And it allowed me to use some new FA characters.

I have since added the FA5.6.3 script to my first (home) menu item text, and deleted the script from individual pages (except in MacDown).  I use the same menu throughout the site, and it makes all the FA characters work regardless of the page template or contents, and whether the page text was developed in MacDown or not.  So that makes one solution to upgrading FA throughout the site with only one script.

I'm still struggling with PHplugins.  Can't seem to get them working.  Do you have any other on line guidance, tips, etc. that would help?

#4 Backlight 2 Support » Update FontAwesome in BL 2 » 2019-01-25 18:57:36

Replies: 8

Having trouble updating fontawesome to version 5.6.3.  Your hints and tricks refers to CS4 so doesn't seem to apply with BL2.  Got the following script from Fontawesome website; not sure how to install it so it works universally for my entire site.  It does work by adding  it on every page and menu item, but that seems inelegant and tedious to say the least.

<script defer src="" integrity="sha384-EIHISlAOj4zgYieurP0SdoiBYfGJKkgWedPHH4jCzpCXLmzVsw1ouK59MuUtP4a1" crossorigin="anonymous"></script>

#5 Re: Backlight Support » Font Awesome upgrade in Backlight » 2018-03-05 18:07:51

rod:  "Why are you using 15 page templates?
It sounds to me that you’re over complicating this."

OK, followed suggestions and cut down to 10 page templates, mostly by eliminating unused ones.  My site has 9,674 images plus videos and rather long text passages including external links and a bibliography.  I use 3 color schemes (white, dark, black) depending on what I'm doing.  Add pallet positioning/sizing (left, right, none, narrow, wide, etc.) and a few other twists, and it takes all 10 pages to make it work the way I want.

I did get rid of the script in the menu item, and set it up within ttg_head on my phplugin, then activated on every page template.  It works ok.

matthew, thanks for the ideas.  For now, I'll try to keep it simple by using phplugins.

#6 Re: Backlight Support » Font Awesome upgrade in Backlight » 2018-03-04 16:51:52

I had been calling the font-awesome script only on the 2 pages I used for "Bibliography" and "Links".  It worked on those and affected the menu the way I wanted.  None of my other pages called it, and the menus on those pages did not have the font awesome icons I wanted.

I believe what you're suggesting that I should call the script on every one of my 15 page templates.  This will probably work, but seems inelegant, so I tried another approach by calling the script within the menu template.  I added the script in the name box of the first menu item, as follows:

<script defer src=""></script> <i class="fas fa-home" fa-lg></i> Home

This seems to call the script every time for the menu, and doesn't require phplugin activation on individual pages.  The script ensures that pages that use it work properly.

If there's a better way, I would like to know it.  It would be nice if phplugin and css activation were included in menu templates.  Perhaps in some future upgrade.

#7 Re: Backlight Support » Font Awesome upgrade in Backlight » 2018-03-04 01:20:07

After some struggle, I finally figured out the phplugins route with the following:

// Basic structure for a PHPlugins function
function ttg_scripts( $style, $path ) {
    echo '
    <script defer src=""></script>

    return false;
} // END /**/

That's OK for pages, but how do I get menus to accept it?

#8 Re: Backlight Support » Font Awesome upgrade in Backlight » 2018-03-04 00:11:33

I'm not using phplugins or hooks, only the script posted in my original post.  That is the function that works as long as I add it in the Page Copy of the Page I'm using.  I tried using custom phplugins, but no couldn't seem to get it working.  I need to know how to set it up properly.

I understand if I got it right somehow, I could call the phplugin from the individual page template.  That's helpful since there are currently only two pages where I want to use the updated Font Awesome.  But I want to use it in menus also.  How can I do this?  There doesn't seem to be a way to call phplugins from menu templates.

#9 Backlight Support » Font Awesome upgrade in Backlight » 2018-03-03 19:52:29

Replies: 10

Font Awesome has some new icons I want to use, and I can access them by putting their script in the page contents:

<script defer src=""></script>

I want the new 5.0.8 version available across all Backlight, rather than just individual pages one by one.  Tried several approaches in custom PHPlugins and CSS, but can't seem to get it working.  Just how can I accomplish this upgrade?

#10 Re: Backlight Support » Galleria Album Won't Load on iPad » 2018-01-29 19:37:56

Matthew, Will stop chasing the holy grail, and not worry about WebOS browsers.  Now that I have an excuse to buy a new iPad, will probably do so and confidently render more albums with Galleria.  It's a very nice add-on, thanks, and I hope development will continue.

The idea of fewer descendent levels for the small screen hamburger menu is still a neat idea, and it would be nice to see it somewhere in a future upgrade.

#11 Re: Backlight Support » Title Metadata » 2018-01-28 15:44:01

Rod, I think I got it using LUA (not LUF as I mistakenly typed in a previous entry).  In this case, I decided to insert the Folder name if the Title field is empty.  Tried to do it with simple = sign, but that didn't work.  So, thought it through backwards by using the not equal sign ~= and it worked.  Here's the text:

{LUA=if Title ~= "" then return Title else return Folder end }

Always had to remember to re-publish the metadata in LR every time I tried a revised LUA statement.  Slow going, but finally got it.

Thanks for the help.

#12 Re: Backlight Support » Galleria Album Won't Load on iPad » 2018-01-28 12:49:23

FWIW, a postscript.  Discovered that my Galleria albums also won't load on the built in WebOS browser on my LG television.  Perhaps choking on the image size like the old iPads.

#13 Re: Backlight Support » Title Metadata » 2018-01-28 00:54:43

Rod, What I'm trying to do is have the Title display when there is something in the field, but show either nothing or some alternate field or text when individual photos within an album have an empty Title field.  This is conditional for each photo.

One way to do this might be to select all the photos in lightroom that have a blank Title and put something like a single space in that field.  This seems inelegant and forces me to add the space to new images even when I don't want anything in the Title field.

Another way might be to disable the Title field and put {Title} {Caption} in the captions field.  I like the 2 separate lines, so would have to figure out a line break between the tokens to get it.  But this leaves the same font size, color, etc. for both lines.  I like to have a slightly smaller font for the 2nd Caption line and may want other options in the future.  Again inelegant and not what I'm looking for.

It seems to me that there must be a way to suppress the file name display when the Title is empty.  I tried the LUF token command without any success; perhaps I was using it wrong.  Alternately a css might do it.

#14 Backlight Support » Title Metadata » 2018-01-27 17:05:29

Replies: 4

From a template:  "Title metadata being absent, image file name will display instead."  How do we just change this to a blank or some other text when the Title field is empty?

#15 Re: Backlight Support » Font style in image captions » 2018-01-27 00:08:10

Matthew, Got it, thanks.  Works now.

#16 Re: Backlight Support » Font style in image captions » 2018-01-26 15:50:46

rod barbee wrote:

Looks like the selectors for Galleria would be:

.galleria-info-title for the title field
.galleria-info-description for the caption field


Tried the selectors.  The former had no effect; the latter changes the entire Title and Caption display.  Example -- set the title to red and description to yellow:

http://www.michaelrichardsphotography.c … ey/ankara/.


#17 Re: Backlight Support » Font style in image captions » 2018-01-26 01:02:12

Rod, Thanks.  I really wanted this for a Galleria large image presentation.  I guess it can't be done.  I'm relived that I wasn't brain damaged.

#18 Backlight Support » Font style in image captions » 2018-01-25 18:36:46

Replies: 6

It seems simple, but couldn't figure it out, so asking help for my brain freeze.  I want to display image captions in italics or underline, but mixed in the display.  Specifically, I want the Title in normal text and Caption in italics.  Is there a way to do this?

#19 Re: Backlight Support » Galleria Album Won't Load on iPad » 2018-01-23 18:46:08

In the meantime, I cut the menu descendent levels from 3 to 1, a simpler menu setup that cuts down the hamburger menu overload.  I had it at 3 levels mainly for my own convenience, anyway; even the full screen menu would confuse a guest visitor.  They should have a better experience now.

#20 Re: Backlight Support » Galleria Album Won't Load on iPad » 2018-01-23 02:49:13

Thanks for the inputs on this.  It seems you get the display ok on your iPads.  I was getting an all black screen only on both Safari and Chrome.  I Googled "iPad won't display some websites," and got a long list of hits.  Tried some of the recommendations -- free up more memory (even though it has 30 GB free anyway) clear caches, reset, cold start, etc.  No help.

Since I load the album ok on my iPhone, I'm going to assume it's an IOS and hardware problem.  My old iPad is IOS 5, and my new one (to me) is IOS 9.3.5.  Software update says it's current, so apparently my iPad won't update to IOS 11 due to outdated iPad model.  (my iPhone is IOS 11.2.2 and works fine).  I'll not be chasing this issue any further till I get a new iPad.

Regarding the blue hamburger menu TomO mentioned, I have almost 700 albums and album sets on the website, so it doesn't surprise me that the menu is unworkable.  It would be better for me to be able to choose a top-level only menu or perhaps only a shallow level of album sets instead of a long list of albums. Perhaps one could choose a different menu set or descend levels for the hamburger menu.  Don't think this is doable right now, but something you might want to consider it for Backlight upgrade.

#21 Backlight Support » Galleria Album Won't Load on iPad » 2018-01-22 20:21:39

Replies: 8

I have Galleria albums that won't load on iPad, but work nicely on iMac, iPhone, and Windows 10 machines.  The iPads load other non-Galleria albums OK.  Same problem on an old (IOS 5) iPad as my new one.  Anyone experienced this problem?  Have I got a bum setup in my template?  Here's are a couple of the URLs; about 5 different Galleria albums act the same:
http://www.michaelrichardsphotography.c … days-2018/
http://www.michaelrichardsphotography.c … -festival/

#22 Re: Backlight Support » Creating Custom 404 Error Page for specific templates » 2018-01-19 15:21:01

I'll bet a clever programmer (which I am not) could present a different 404 page display by album just by HTML coding in the "Page not Found Message" and perhaps making a few other CSS/PHP adjustments.  I suspect the effort required to do this would exceed it's worth.

#24 Re: Backlight Support » Panorama » 2018-01-18 19:38:01

PaulQM wrote:
richam wrote:

I used Vegas Strip pano settings: Gutters, Border, Slide Padding and Slide Margins to 0.

Hi, fantastic idea but where would I find the Vegas Strip pano settings?


First, you need to have a Pangolin Theater album to work on.  If necessary, start a new album.  Then select "Filmstrip" in the "Presentation Type" section.  The controls should appear.

#25 Re: Backlight Support » Using an image as a link » 2018-01-16 18:40:41

Rod, I agree.  Attempting to improve the presentation for smaller screens, I tried some smaller slice size panos.  But they brought on their own problems of shaky presentation and unwanted gaps without improving small screen display.  Here are some examples you can see for yourself.  These are the Columbo panos with slices halved to 480, 240, and 120 pixels, as indicated in the URL:

http://www.michaelrichardsphotography.c … -pano-480/
http://www.michaelrichardsphotography.c … -pano-240/
http://www.michaelrichardsphotography.c … -pano-120/

If there is a solution, I'd like to know, but for now will keep slice size the same as image width.

Board footer

Powered by FluxBB