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.
Pages: 1
Yes. That's what's so odd. The settings are updated. Everywhere I can find them, that is. I publish to the new location/domain name and I have made several test changes to the content to verify that. Yet, the "Go to published album" still goes to the old location/domain name.
Thanks. I'll give it a try.
Is it possible to protect an album set? Eg, if I have multiple albums (projects) for a client, can I put them in a single album set only accessible by that client? In Backlight 2? in Backlight 1?
If so, how would I do it?
Thanks.
My web sites including my galleries were recently move to a new, upgraded, server by my ISP and to differently named subdomains. All files were copied over by the host system analyst. Everything that I have tested on the new server works fine. All my web sites work just as they always did.
In Lightroom, I edited the publisher settings and re-established the connection between the existing publisher galleries in LR and on the web. The galleries have been republished.
But when I "right click" on a gallery in LR and select "Go to published album", LR goes to the old domain name and server. I do not see any setting anywhere that controls this behaviour. I assumed that this would correct itself once I had republished the galleries, but it did not.
Any ideas of the cause of and how to fix this (relatively minor) problem? Is there a file within LR that I can edit?
(BTW, although I am engaged in updating Backlight to Backlight 2, I have not yet made any changes that affect the existing galleries.)
I have run into a somewhat similar issue. I get these error messages:
For Publisher:
Backing up databases...
Backed up master.sq3
Upgrading to version 3.2.2...
Updating settings table
Unable to upgrade to version 3.2.2
Error message: SQLSTATE[HY000]: General error: 1 no such column: title
Designer
Backing up databases...
Backed up master.sq3
Upgrading to version 1.2.0...
Configuring localizations
Unable to upgrade to version 1.2.0
Error message: SQLSTATE[HY000]: General error: 1 no such column: sort_order
I tried Ben's work around (ie reinstalling the modules) but that didn't resolve the issue. Funnily enough, both the cart and client-response modules updated with no apparent problem (although I have not dipped into those areas yet).
My site is running PHP 5.6.37.
Any suggestions greatly appreciated.
Thanks, Jon
Went to add an album to one of my backlight galleries, but got this message:
Unable to perform action: Getsetupfortemplate.
What has changed since the last time I was working on my site? How do I fix this?
Thanks, Jon.
Oops. I must have done something wrong. I just recently changed the login name on all my backlight installs to the same name but different from the name I used to log into my blogs. Just to make things easier for me but perhaps a bit more secure I thought. I'm sure they all worked fine yesterday.
I'm still able to access the other backlight installs, but when I went to access backlight on my blog subdomain just now, I got an error:
--------------------------------------------
Unexpected error: unpack(): Type V: not enough input, need 4, have 0 in file.php on line 318
--------------------------------------------
How do I fix this?
Thanks.
Thanks Matt, very diplomatic.
As a matter of fact, I tweaked it this morning. I simplified the menu and demonstrated to myself another value of top level galleries. I moved content from some of my information pages to the appropriate top level gallery. Not only was I able to get rid of three pages, I could combine two submenus. Now visitors won't usually have to go to more than one place for the information they need.
Once again I have to say that I love Backlight. It is so easy to use. CE4 and previous versions were great products but being tied to working within the lightroom web module, they were, in comparison, so clunky. Backlight with its web interface and easy publisher tie in...Wow, that's really all I can say. Thanks team!
Yes, my backlight site is out of development and into production. Does that mean it's finished? Of course not! Backlight is so easy to tweak, I'll probably keep on doing it just for the fun of it. Remember the In Search of Excellence management fad back in the 80s? One of their adages is so easy to apply now with Backlight: "Do it, try it, fix it." So, I'm not finished, not by a long shot. But you can see the current incarnation here: http://hummingbirdphotographics.com.
A significant change for me was moving from thumbnail/still image galleries to theatre galleries for almost all my work. This change began in my head with CE4 Stage of course, that I used for my home page (repeated with Backlight) but didn't really seem to me feasible to implement wholesale until Theatre. So now I have a Vegas style theatre for the home page and a flickety style theatre for the presentation galleries. Of course this evolution coincided with a revised business model too. I'm no longer offering a lot of different options for every image. Instead I am selecting only a subset of images to sell and only in specific forms. The rest are just to, I hope, inspire the visitor.
Another major change for me is moving to the top level gallery concept. Funny. For years I insisted on being able to get right to each gallery through the menu. This meant I needed to code a multi-level menu in phpplugins, and recode every time I added a new gallery. So now that Backlight has made multi-level menus so darn easy, I'm moving away from them. How ironic is that?
The look is new too. Trying more of a minimalist approach. In development, it was even more minimal, but I guess I'm not just there yet. I relented, or maybe repented, made a final tweak just before transfer to production and brought a masthead image back. So easy, I couldn't resist. But it's an image that doesn't draw the attention as much, at least I hope. I want people to look at the galleries, not admire the web site. But by the same token, I don't want them hating the environment in which they are viewing the images. A fine line between the two in many ways. Not sure I've got the right balance yet. But hey, do it, try it, fix it!
At the moment I don't know how to do that. But it sounds like something interesting to explore when I have some spare time.
Might this be included in a future update? Matt? Ben?
Does Backlight Wordpress add-on support the use of "widgetized" footers?
I am considering moving to a full page blog with my widgets in the footer. But I can't figure out how to do that. If I change the page template to a full page I lose the widget panel in WordPress. Am I missing something?
Or is this something I could easily do with custom php?
Thanks.
I've read the older posts (well, those I could find) related to SEO and backlight. None of the comments mention the Theatre add-on. I forget, perhaps it came out after these discussions. The discussions I read seem focused on thumbnails and single images. Or perhaps I am just confused.
So, while I hesitate to re-tread old ground, I am wondering if captions, keywords, etc associated with images in a theatre gallery are still visible to the internet search engines. Images do get identified when I search within the site, but this doesn't give me confidence that Google and other search engines will find them.
Put more succinctly, does using theatre galleries make the images invisible to the internet search engines?
I've really gotten to like the theatre galleries, but if they are invisible to the search engines, I probably won't make such extensive use of them.
Thanks.
Thanks for figuring that out, Ben. Good to keep in mind. Or do I detect an update coming?
I tried the main_bottom hook and it seems to work for everything, including full page theatre galleries. I kept the code I received from Statcounter in a separate html file and just added an include line in the php file within that hook.
Thanks again Rod.
These are great resources, Rod. Thanks.
Thanks Rod. I saw all the new hooks in the phpplugins file, but couldn't tell what each actually did. As far as I know, my Backlight is up to date. Whenever a new version comes out, I update. I'm using 1.1.1.
I'll give those hooks a try and report back.
I have been using Statcounter with the CE plugins for awhile. I put the statcounter code into the ttg_body_bottom function in the phpplugins file. That worked fine, except I think with the full stage gallery. I never got around to try solving that one.
With Backlight, this body_bottom tag doesn't seem to exist. I tried it in the ttg_scripts function, but it doesn't seem to do anything there. I have tried it in some other function areas, I forget now what ones I have tried, but the mast_head and navigation related ones I remember, but they either break the page, ie the page doesn't load, or it does nothing.
Which is the proper function to include it under?
Is there anything special I need do to have it work with "in-page" theatre templates and full-page theatre templates?
Thanks.
Sorry the delay. I got distracted by events yesterday.
The problem was occurring on my development site, development1.hummingbirdphotographics.com.
As Matt suggested, I had the search album set to a slight variation of the standard album template, a one column page instead of the two column page. Changing back to the standard album template has seemed to correct the problem.
Thanks.
While testing the various facets of my backlight site, I discovered that the search function fails to present a larger image of found photos. I get this error message:
"Something went wrong
Unable to find view with name single in GenericEngine.php on line 441"
So, I agree something went wrong. Can anyone tell me how to figure out what and correct it?
Thanks.
I would like to offer a product for which I prefer to only ship on a custom, pre-arranged basis. My other products can use a standard shipping scheme.
Is there any way to not have the shipping option come up for just for this one product? I am guessing not, that it is a cart-wide setting, but thought I would check to see if anyone has a work around.
Thanks.
Yes. Matt's right. 99%, it seemed, of the transfer worked fine. But there were some problems that I had to try fixing with custom css or even getting into the functions.php file. And I think I managed to fix them, but I thought I would try Rod's suggestion of loading backlight and the wordpress module into my blog domain and transferring the page template from my web site. Then in the blog instance of backlight, I created and exported the wordpress theme. I created a child theme in case I had to do other tweaks, but there was no need (well at least so far!). Other than, as Rod reports, having to repopulate the side bar with the widgets. Still having a child theme might prove of value some day. So I have left it as is.
Useful learnings. Thanks.
Update. Instead of downloading to my hard drive and re-uploading, I simply copied over the files from one subdomain to the other through my Parallels Panel (website administration). Piece of cake. I see it in my Themes on my blog and have been looking at through the preview function in Wordpress and everything looks good.
I was slowly coming to Rod's idea when I got his reply. And I understand Matt's point perfectly. It's sort of like having to upload a lightroom gallery to a password protected server directory. You need a whole authentication routine which I presume is pretty involved.
What did I do? I simplified things a bit. Rather than going to the trouble of installing wordpress, I simply faked the directory path. I created wp-content and theme folders on the same domain as backlight. Didn't need any content in those folders. Defined my blog in backlight settings as existing on the backlight domain (even though it doesn't). And voila! an exported theme. All the export wordpress theme function needs is a path, it apparently doesn't check to see if there is actually a wordpress installation.
Now all I have to do, I think, is download the backlight theme and then upload to my actual blog site.
Thanks.
I've developed my backlight site and now I'm working on my blog. However, way back, when I first started a blog, I made a decision to run my blog on its own subdomain. I have the wordpress add-on installed on my development domain where my backlight site is. But I am having trouble exporting the wp theme to my blog site. It's probably an access issue, but I don't know where or how to resolve it.
Suggestions anybody?
BTW, I am ecstatic with Backlight. I've been using TTG plugins since before CE, almost from the beginning I think. I've been used to the tediousness of building templates and so on in the Lightroom web module. But wow! Backlight is so much easier and faster. I rebuilt my whole web site in no time at all. And the CE4 cart imported easily. It's not on my production site yet. But all I need do now is test the cart, which I don't think will be a problem and get my blog looking the same as the galleries.
Thanks Matt and everyone else involved in its development.
Jon
Pages: 1