Community @ The Turning Gate

Support community for TTG plugins and products.

You are not logged in.

#1 Re: Backlight Support » Publishing large photo sets aborts with server 12152 code » Today 08:32:15

this may be a case where you need to increase the upload limit in your php.ini file.
see: … hp?id=8117
and: … hp?id=7032

Otherwise, it could be the issue where GoDaddy thinks it's a denial of service attack, discussed here: … 197#p48197

#2 Re: Backlight Support » Download product missing from cart » Yesterday 23:30:31

never mind. I figured out that the guest username was simply "guest"

Looks like the problem could be that you may not be supplying the images for download. See the documentation: … _purchases

#4 Re: Backlight Support » Download product missing from cart » Yesterday 22:04:04

are all prices and shipping charges filled out?
How are you supplying the downloads: are they being created by Publisher? Uploaded manually?

If you can set up guest access to Backlightf and post the credentials, we can take a look and give better responses.

#5 Re: Backlight Support » Download product missing from cart » Yesterday 09:04:57

the album linked to is using the "default" pricing scheme. Does your default pricing scheme include a digital product?

#6 Re: Backlight Support » Cart and Client respond in one album. » 2017-10-15 23:45:17

Probably not going to happen. Matt's addressed this several times over the past few years.
For example: … 045#p45045

#7 Re: Backlight Support » Pinterest Share Buttons » 2017-10-15 12:24:44

Just the Pinterest button? Then custom css is the answer.

li.share-pinterest {

#8 Re: Backlight Support » Sub-domain problems » 2017-10-15 08:51:01

this has always worked for me:

In my host's C-Panel I create a sub-domain and give it a name. A folder by that name is created on the server.
So if I was creating an "events" domain, the url would look like this: and on the server there would be a folder named events/ (
Backlight would be installed in

In backlight, the Site url would be
The Publisher API URL would be

#9 Re: Backlight Support » Cart and Client respond in one album. » 2017-10-13 04:22:21

You can't.
Cart and Client Response are two different things and can't be used together.

Here are a couple of options:
What you can do is, after getting the feedback from your clients, remove all images from the album except their selects and then assign a cart enabled album template to the album.
If you want/need to keep the CR album up, create a new album using a cart enabled album template.

#10 Re: Backlight Support » Can not see thumbnial on "album set" page » 2017-10-13 01:05:14

Edit the Album Set in Lightroom. At the bottom of the Basic tab, click on Cover image and choose an image.

And if you want to use the "Random" setting, see this conversation: … hp?id=8094

#11 Re: Backlight Support » Advantage - more than one publisher instance » 2017-10-13 00:42:23

I don't think there's an automatic way of doing it, you'll need to create each one individually. Maybe someone else has some ideas. (lots of into online about using smart collections. Smart albums are created the same way as smart collections)

But you can create a smart album based on the name of an already published album. Smart albums only populate the album with images. You'll need to fill out all the album details like name, template, album copy, etc.
But it will populate the album with images.

I don't see any way of duplicating album sets though. I think you'll need to do that manually.

I've not looked, but perhaps there's a Lightroom plug-in out there that can duplicate the album-set/album structure of a Publisher instance.
Lightroom Voyager will transfer published collections from one catalog to another catalog, preserving the album-set/album structure. I don't see anything about it being able to duplicate a Publisher instance within a catalog though.
But it might be worth asking them.

#12 Re: Backlight Support » Error upgrading from 1.0.2 » 2017-10-11 00:37:22

However I then went to the .../backlight page and logged in. This resolved the issue, which may have been the solution all along.

After most updates you'll need to log in and visit various sections of Backlight so that the databases are updated. You'll also need to clear the template cache. This is always the last step and is outlined in the readme.txt files included with the download.

A follow up question: I have spent limited time with Backlight until now and have only a small test site. I now but plan to re-do my CE2 based site that is a commercial site that I need to keep running until the new one is debugged. To make the new site live, do I simply copy the content from "test.mysite" to "mysite" and edit the backlight settings page? If there is a better way, is there a writeup on how to switch?

That's should do it.
But to be sure, I suggest running a migration test into another subdomain. Get your new site created and include only a few albums. Then download everything from your test site to your computer and upload it to the migration test subdomain. Log into the migration test site and make the needed url changes in Settings and then visit the site to see if everything is working correctly.
If so, you should be ready to finish off your test site and then migrate it to your main site.

#13 Re: Backlight Support » 360 Panorama whit Backlight 1.2.2 » 2017-10-11 00:25:06

Take a look at the index.html file included with the pym download. There are a number of lines of code in there that you're not using in your html document.
I'd suggest first including all those meta tags:

<meta charset="utf-8" />
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<meta name="apple-mobile-web-app-capable" content="yes" />
	<meta name="HandheldFriendly" content="True" />
	<meta name="MobileOptimized" content="320" />
	<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no, shrink-to-fit=no" />

and especially the css:

<link rel="stylesheet" type="text/css" media="all" href="normalize.css" />

	<style type="text/css">

		/* base styles */
		html { -webkit-text-size-adjust: none; /* prevent font scaling in landscape */ }
		#page__body {
			background-color: #fff;
			color: #333;
			margin: 0;
			padding:12px 24px;

also, the sample index.html file uses a div with id="page-body" to contain the content. You might try wrapping your content in a div with that id.

#14 Re: Backlight Support » Pangolin Theater - controls position and image size » 2017-10-10 23:56:29

About the image size: on the workstation it's ok, but on the iPhone, it is a bit big. Any way to control the page size on the mobile phone?

Sorry, I don't know.

#15 Re: Backlight Support » Error upgrading from 1.0.2 » 2017-10-10 05:01:31

Don't delete the old folders just yet. Those folders contain the necessary files for pages, albums, etc you've created so far (the Backlight "Okapi" stuff)
You'll need them for your existing albums and pages to still work.
For more on the move from Okapi to Pangolin, see this blog post: … available/
specifically the part near the end titled: Moving from Okapi to Pangolin

Ben will need to comment on the error though.

#16 Re: Backlight Support » Pangolin Theater - controls position and image size » 2017-10-09 06:53:58

You're locating the controls in the top pallet and they're actually being aligned center in the list item that the controls are placed in. The top pallet uses list items, and it looks like it's using a few list items so it's likely going to need some tricky css to center the controls in the top-pallet. If it's even possible to center them in the top pallet.

If you want the controls centered above the slideshow, you'll be better off positioning the controls using "In" or "Above" and using something like this for the css:

#vegas_controls {
text-align: center;
top: -50px

an example: … w-olympic/

#18 Re: Backlight Support » Pangolin Theater - controls position and image size » 2017-10-08 00:09:06

Hi Matt,
I'm using the inline layout but still not seeing the difference between the two.
Here's one with the controls set to "In": … -or-coast/
and one with the control set to "Over": … rols-over/

I've double checked the templates being used.
the #vegas_controls css looks the same for both.
Theater 1.2.4

#19 Re: Backlight Support » Pangolin Theater - controls position and image size » 2017-10-07 08:30:58

You have three choices for positioning: In, Over, and Top Pallet. Frankly, I'm not seeing any difference between "In" and "Over" (this might be a bug for Matt to look at).
You could use In or Over along with some custom css to center the control in the top of the image:

#vegas_controls {
text-align: center;

If you don't want the controls on the image, you can try adding top: -50px; to the css to move them above the image.

How much larger do you want the slide show? Hard to advise without seeing something. Generally, I think the max-width control along with aspect ratio and image size will control the size of the show.

#20 Re: Backlight Support » Restrict metadata published with images? » 2017-10-07 06:59:39

Well, I'm stumped. Looks like this is Ben's territory.

#21 Re: Backlight Support » Restrict metadata published with images? » 2017-10-07 06:24:38

Created & published new album to my BL sandbox website with "Include: Copyright & Contact Info Only" checked in TTG Publisher's  settings.

Did you also check the Remove Person Info and Remove Location Info boxes?

#22 Re: Backlight Support » Fancybox Slideshow » 2017-10-07 01:35:26

I don't see any mention of changes in Fancybox in the Backlight 1.2.2 release 3 readme.txt file.

The slide transition looks smooth to me. It's fast, but it's not jittery or anything.

#23 Re: Backlight Support » Clear Template Cache - a wish » 2017-10-06 20:39:18

Are you saying that you're making manual changes to the files themselves rather than changes in the Backlight interface?
If so, I don't see how Backlight could "know" you've done this so that it could automatically trigger template cache clearing.

#24 Re: Backlight Support » Client Response Gallery broken » 2017-10-06 06:25:52

you tried deleting and then replacing the client response module at backlight/modules/module-client-response/, correct ?
you might also try replacing the backlight/client-response/ folder as well

could you perhaps have somehow deleted your client-response album template? If that happened, I believe another template gets assigned automatically, in this case perhaps a regular pangolin album.

otherwise, Ben will need a url and probably Backlight admin credentials

Board footer

Powered by FluxBB