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.
So, to recap:
in order to re-publish albums already published from Lightroom to a "new" instance of Backlight, you must "edit" each album set and album (which literally means change something, seems like any change will do) and and after a change is made, that album (or Album set) can be republished.I hope this helps someone else. What a maze of workarounds
The other day I found a Lr plugin that allows you to mark album trees for publishing. I think that's exactly what you need. Unfortunately, I don't remember where I saw it ![]()
You still have this strange frameset on your site.
If Backlight 2 doesn't work with a current or future PHP version, it will be fixed. Earlier this year, Ben even did an update to CE4 to get it running with PHP 7!
My test site uses PHP 7.2 and I don't see any problems with the cart.
And it works ! Thanks.
![]()
I just looked at some older messages and an updated version of CE4 works uner PHP 7 (http://community.theturninggate.net/vie … 692#p51692).
You need to download TTG BE again and then replace ttg-be/framework/lib/Parsedown.php and lib/php/Parsedown.php on the server.
If you assign a title to the image, then the title will show instead of the filename.
ok. many thanks Rob. I have one running on CE4, the rest on backlight. I guess Ill extend support for that pho version until I update that site to BL. Cheers!
rod barbee wrote:Depends on the php version and the site. If you've got CE4 sites running, php 7 might mess them up.
But if it does, you should be able to revert to an earlier version of php. I'm currently running 5.6 and my Backlight sites (on one CE4 test site) are running fine.I think there have been some discussions in the CE4 forums about this. You could try searching there.
You can set the php version in the cpanel. I would select version 7 and give it a try. If there are issues, you can revert back to 5.6. Report here if something doesn't work. I think that Ben did some updates to fix some issue that came up in the past.
Try this:
#crg-widget {
width: auto;
}BTW, your page shows an error with '<script src="jquery.min.js"></script>'. AFAIK, jquery is already loaded by BL2. It might be better to use the scripts hook with phplugins to insert your custom javascript code.
I think I noticed the same thing when I played with CRG and Backlight. The fix was some custom CSS. Do you have a link to your test site?
Sorry, it looks like PayPal changed its interface since I set up my cart years ago.
When I look at 'NVP/SOAP API integration (Classic)', I see my previous settings. So you might want to try that, although I'm hesitant to disagree with Ben because he knows this stuff in and out.
I tried to find the pages, but they are not there as URL's. So it is the backlight database or whatever that makes the translation (I guess). But I culd not fin any of that.
The pages are all handled via the .htaccess file. I would suggest to copy the .htaccess file from the installer to the root of your site as you might have edited in the past (different thread).
never mind, found it, thanks!
![]()
backlight > cart > settings > list settings. The PayPal settings are in the Checking Out section.
As you have noticed, the button is there. It uses white text on a white background.... You need to check the colors you are using.
no idea what that is for and where it is from Daniel????
Somehow you defined that the 2019 folder is the root of your site I guess. Who are you hosting with?
I noticed this in the past and was wondering why.... Your page setup is strange since your photography site is embedded in a frameset:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
<html>
<head>
</head>
<frameset rows="100%,*" cols="*" >
<frame name="subdom" src="index.php" marginwidth="0" marginheight="0" scrolling="auto" frameborder="NO">
<frame src="dummy.html">
</frameset>
<noframes>
</noframes>
</html>Going to https://www.fotograafdonald.nl/2019/, the links work properly. I would get rid of this top-level frameset thingy.
I send you an email by clicking on the Email link in your profile...
Could you DM me your email address please? Thank you.
I received the email today and replied to it.
Did you got my mail Daniel?
No, I haven't received anything. The spam folder is empty too.
Jim, did you try the find & replace plugin? It looks like you can achieve a populated Title field in two steps: 1) copy filename to title field followed by 2) replacing unwanted characters by spaces.
Obviously this takes a bit more time than having an automated solution. But this way, you could have your title field populated within 'minutes'. Don't forget to select 'publish metadata only' in Lr Publisher when updating your images.
Daniel Leu wrote:How about a simple phplugins function that overwrites the value currently used? This way, one could even include the album title, if desired.
For clarity, are you suggesting a PHPlugins hook to replace the page's TITLE element in the document head?
The title could easily be replaced via Javascript, using document.title via the existing PHPlugins hook for scripts.
https://developer.mozilla.org/en-US/doc … ment/title
Ben proposed a new Publisher setting which would mean a hardcoded implementation. So instead of going this way, I think that a phplugins hook would be more versatile. AFAIK this would affect <title> as well as og:title and twitter:title. Having a matching crumb would make sense to me as well. This is a feature request from Jim, so he might be better to specify/clarify this.
I don't know whether one approach or the other would yield greater SEO benefit. Google is supposedly good about parsing JavaScript for SEO. Supposedly ...
I'd rather have my page ready on load and not depend on Google's capability to parse my JavaScript code.
Hi Jim, from a Backlight perspective that could probably be done by adding a new setting within the Publisher section of Backlight Settings, e.g. Single Image Page Title Format with options such as Image Title (the current behaviour), Filename (forced to used the filename, whether the Title metadata existed or not) and Filename Converted to Title (for want of a better name - where Backlight code would convert any textual part of a filename to a Title, as you've described).
The filename-to-Title functionality would be easy enough to code. We already have similar conversions in other places such as a slugToTitle utility function.Does that sound like it would fit the bill?
Ben, if you add a filename-to-Title function, then slugToTitle should be updated too, shouldn't it?
How about a simple phplugins function that overwrites the value currently used? This way, one could even include the album title, if desired.
Daniel wrote:Jim, can you provide a link to what you refer to as "photo page"?
What I'm calling the "photo page" is the page with just the one photo on it. It's the page with the unique URL to the one photo.
I'm using albums with slide shows, which show as a gallery. From there I can do into the slide show, get to the sharing bar and select the permalink. That URL is the type that ends with ...single.php
I thought that you were looking at a different page since my titles are propagate (as long as I put a title in there).
I was able to reproduce the same look and feel from my CE4 days.
A few comments, and yes, I'm going for the low-hanging fruits:
- Your logo is now 60px high vs 40px with CE4. To make the masthead smaller, you could remove the top and bottom padding from 24px to something smaller (.masthead-primary {padding: 24px 0 24px;}).
- The font you use is bigger than the one from CE4.
BTW, the links should be http://jwlimages.com/Temp/Backlight_on_iPad.PNG
Jim, can you provide a link to what you refer to as "photo page"?
Do you have a link to your site?
There is a small error: /wp/wp-content/themes/backlight-child/styles.css should be /wp/wp-content/themes/backlight-child/style.css
style.css and functions.php are used by Wp. You will not find any references to them in Backlight.