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.
Between major versions like CE to CE2 you can't, unfortunately.
From the FAQ:
Q: Can I transfer all my TTG Pro or CE settings to CE2?
A: No. Templates for CE version engines are not compatible with CE2 engines. You'll need to start over. Sorry, that's just the nature of things. But, once you've designed for one engine, like TTG CE2 Pages, you can create a template and port those settings to templates for other engines, saving you tons of time and reducing any errors that might occur. Read Matt's tutorial for sharing engine settings.
have you tried shutting down and restarting Lightroom?
It probably means that you don't have any images in your filmstrip.
Or in the Lightroom Toolbar you have Use: ____ set to "Flagged Photos" and none of your photos are flagged, or you have it set to "Selected Photos" and none of the photos are selected
I've been bitten by that too. It's counter-intuitive to those of us who shot slides for so long, like we'll put finger prints on the thumbnail or something
be sure you're clicking inside the thumbnail when you want to drag pictures, not just on the frame around the thumbnail. It's not a preference setting, it's just the way Lightroom works
Hi Ed,
Most pages output by ttg plugins are php (Pages, Stage, etc). The Highslide gallery can be output as html if you don't use any of the features that require php. If you do, then they're output at php. (that may be true as well for Photoswipe and Horizon, I haven't checked)
The Highslide, Photoswipe, and Horizon galleries are all customizable. If you want to use the cart, you'll need at least one of those.
take a look at the Orientation. There's also a link in that document to a Beginner's guide that should go a long way in answering your workflow questions
Use the Template Browser to save a template of your work.
Also, use the Save Web Gallery button at the top right of the preview area.
It's best to use Export and then upload the results of the Export to your site via FTP. Lightroom's upload feature can be unreliable. See this: http://wiki.theturninggate.net/doku.php … ctionality
LR 4 (the current release is 4.2) handles collections differently than LR3, which stores your web settings in the collection. LR 4 does not, it saves them in saved web galleries. So be sure to create templates i LR3 of every single gallery, autoindex, stage, Pages, or whatever else you have. When you upgrade to LR4, your templates should all be there and you can apply them to the collections holding your galleries and then save them as Web Galleries in the Web Module.
Other than that, just the standard backing up of stuff.
Upload the contents of the Pages folder you exported (assuming you named it Pages). Not the "pages" folder itself, but its contents. You should end up with several files and folders in the root of your site including index.php, galleries.php, about.php, etc. and folders such as galleries/, resources/, photos/, etc.
Matt's beginner's tutorial has a screen shot of all the files you should see in the root
Open your FTP program. Connect to your web server using the credentials supplied by your host. Each FTP program is different so you'll have to read the documentation for yours to see how to enter your FTP address, username, and password.
Once connected to your server space make sure to navigate to the root of your site (usually the public_html folder). this is often done on the right hand side of the interface.
On the other side of the interface navigate to the location on your computer where you've placed your TTG export.
Highlight the files and click the upload button or whatever your FTP program uses
You use an FTP program to transfer your exported TTG files to your web server. You'll need the credentials from your host.
Couldn't you just password protect the index and not password protect the galleries?
Or maybe use .htaccess and .htpasswd to protect the index folder?
Matt recommends Bluehost: http://wiki.theturninggate.net/doku.php?id=bluehost
I switched to them a few months ago and have been very pleased. Their control panel makes it easy to find what you need, to create subdomains, to redirect urls, etc.
And all the ttg things work just fine.
that's all Matt. I just poke my nose in here as a procrastination strategy to keep me from working on what I really should be doing....
Looks like a server problem. Looking at the results of the autoindex verification it shows a php realpath() failure:
http://www.timpacker.com/resources/autoindex/verify.php
this thread might help:
http://community.theturninggate.net/post/157/#p157
try this:
##Gallery on the Lake
31 Gallery on the Lake Road
P.O. Box 130
Buckhorn, Ontario, Canada, K0L 1J0
<a href="http://www.galleryonthelake.com/" target="_blank">www.galleryonthelake.com</a>
e-mail: info@galleryonthelake.com
Tel: 1- 888 - 242 - 7475
Post a link to your site
never did get the PM. you can email me directly though if you like
hmm. I noticed earlier that you could see the text: &midot; in your menu. The color of the font was different, it was a lot darker.
Try highlighting the area in the browser around the menu items. You'll see the dot show up. It's small, but it's there. You might need to do a search to investigate what kind of css or other php coding you might need to get what you want.
I'm not up on that stuff and Matt is gone for a few days.
take a look near the top of this thread. Matt initially wrote that code as: · (2 d's)
but it looks like there's a typo in the expanded phpplugins code he included.
Try adding that 'd' back in.
As the documentation states,
"To get the server path, upload published content containing a /phplugins/ folder to your web server, then ping the path.php file in your web-browser at that address. For example: http://www.yourdomain.com/phplugins/path.php"
What this means is that you need to enable phplugins (Site Info> PHPlugins), export, and upload the contents of the exported folder to the root of your site. In your case, you don't have Pages yet so you've uploaded the phplugins/ folder to the folder you've indicated. Then you enter the url shown, (modified with your domain name/folder_location) and the result in the browser page is your server path.
Enter that server path in the "Server Path to PHPlugins without trailing slash" window.
I was able to correct things by changing the gradient angle in the css from 0 to 90
For my menu:
background-image: linear-gradient(90deg, #000000,
#744814 50%, #000000);
and leaving all the others at 0.
and I also changed the angle accordingly for the Page background gradient:
background-image: linear-gradient(90deg, #000000, #2C2C2C 650px);
This makes things look correct in Firefox 16. And since I only changed the last background-image: setting it hasn't seemed to effect other browsers like Chrome or Safari. And since IE9 doesn't do gradients...well, who cares about IE9 anyway. I haven't looked at it in any other browsers yet so I may have messed things up a bit elsewhere.
This code can be found in the resources/css/core-elements-body.css file of an exported gallery (or Pages). Look for the Page Settings section for body for the page background gradients and look for the Navigation section for the .menu-container settings.
The gradient angle setting can be changed there, but it would have to be changed in every exported gallery, autoindex, stage, or other page you might have. The easiest thing to do is to implement these changes with a custom css file using phplugins.
If anyone needs to implement these changes but is intimidated by the code, simply copy and paste the relevant code from the exported css file into a custom.css file to be used by phplugins (see above link to the tutorial). Then just make the change from 0 to 90 where needed.
Yikes. The gradients on my web site just took a 90 degree turn! Although the menu bar looks kinda cool, I'd rather be the one in control of things
Everything looks like it should in other browsers but the latest version of Firefox is having some interpretation problems or something.
Thought it might be a problem with my pc so I checked my laptop and all looked fine in Firefox 13.x but when I updated to 16.0.1, the gradients took that same hard right turn.
That's the only issue I've seen so far but I wouldn't be surprised if other css related problems cropped up. I did send in a report on this but it wouldn't hurt if others did the same, assuming you're seeing the same things I'm seeing.