Community @ The Turning Gate

Rod, thanks.  I was having trouble using the iframe html from Google.  Whenever I try to publish the Google provided html in Tray 01 (copy), I get an error message returned from Lightroom: "Can't rename the published collection.  Error performing function. (Code: 406)"  This happens only when I try to use iframe html in an album, otherwise the album publishes normally.  And I was not trying to rename anything.  I even tried to publish other albums, some with names I never used before anywhere.  I still got the error message.  Here's a typical Google html, and I've tried different html with other maps:

<iframe src="https://www.google.com/maps/d/embed?mid=1ykplgKvev-BFGpW6910nXHIahsQ" width="640" height="480"></iframe>

Anyway because of the error, I decided to try the pym approach.  Apparently, that won't work for what I want to do.  If there's a way to do it with iframe, that's OK.  But I need to know how to avoid the error problem.  If you have any ideas, please advise.

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

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?

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.

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="https://use.fontawesome.com/releases/v5.0.8/js/all.js"></script>

    ';
    return false;
} // END /**/

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

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.

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.

Matthew, Got it, thanks.  Works now.

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.

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.