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.
Check with 1and1 again so they point your domain to ~/public_html or something link this and not ttg-be!
Then you would place ttg-be and your generated pages in ~/public_html.
Or you could go to the admin panel at 1and1 and select domain center to make this change.
Please comment back how well WP/LR Sync works for you. It looks like it would fit well into my workflow.
Thanks - Daniel
Hey Monte, I like your approach and this is something I have been thinking of doing for a while.
On my site I currently use ''if (ALBUMTITLE == 'Search Results' )'' to detect the search page.
Another thought I had, but never really tried, is locating the search page somewhere else and make a 'gallery' of search pages. Something like this
stock/location <- regular gallery page
stock/location/a <- search page
stock/location/b <- search page
stock/location/c <- search pageWith this scheme, it should be possible to create the page title from the ''CURRENTPAGEURL'' or ''G_PATH''.
Again, these hierarchical search galleries might be wishful thinking.... Search performance might be something else to consider as well.
Best
Daniel
Hmmm....
.profile-image {
margin: 0 auto;
position: relative;
}
.profile-image img {
margin: 0;
}
.profile-icon {
height: nilpx;
width: nilpx;
}
.profile-labels {
position: absolute;
left: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"I would double check what you have entered in the fields of the masthead section. There might be something that breaks the Lr code generation.
Not everything has to be complicated :-)
Best,
Daniel
You can change this in your phplugins file. Just look for the custom.css statement.
Cheers - Daniel
Same here. Doesn't work on Safari on Mac, but works on Chrome. I am wondering if it has anything to do with the umlaut in your filenames (Firmengebäude). Try to change the filename and see if it fixes the Safari issue.
Works fine for me. I like the 'hack' you did to use ArtStoreFronts. This works well!
BTW, when I do hacks like this, I am overzealous and keep a copy of the changes as a separate copy outside of the TTG installation. This way I still can get my changes back even if I overwrote my template file due to a version update... yep, it happened ;-) And then there is always yet another backup.
jstephens576,
The new .htaccces file in ttg-be should just contain this:
Satisfy AnyOr in case you are running on apache 2.4
Require all grantedOnce you have added this and Publisher works, check that you can't access /ttg-be/data.
Ben, the reason to add an .htaccess to ttg-be is because jstephens576 wants to protect his main site. Since Publisher doesn't support authentication credentials, this has to be disabled for ttg-be.
How about adding an .htaccess file w/o access control inside the ttg-be folder? This way you have access control for your site, but disable it for the ttg-be directory where none of your images/content resides?
JC, I am just wondering how many images you have in your film strip? Try to have just one.
The css files inside the Lr plugin are not plain CSS files but they contain LUA markup that is processed by Lr. Once exported, these files become plain CSS and then should pass the W3C validator.
That's really interesting. Thank you for sharing and including the background infos! Please keep us posted on the success of crawlers indexing your paged galleries.
Best
As Rod already hinted, ttg_social_media() is a function that can be added by the user using phplugins. This can be used to either add something to the social media section or replace it all together.
If I look at the source code, there is only one image referenced:
var data = [
{
image: "http://www.emergent-visions.com/test/galleries/pages-gallery/photos/clc_081030_0097_M.jpg",
thumb: "http://www.emergent-visions.com/test/galleries/pages-gallery/thumbnails/clc_081030_0097_M.jpg",
title: "Silhouette",
description: ""
},So this makes sense that there is no slideshow :-(
I see that there are more images in http://www.emergent-visions.com/test/ga … y/photos/, but somehow they don't get picked up....
BTW, you might want to disable directory browsing on your server. You might be able to set this through the control panel or need to use the .htaccess file.
'image' is the name of your subdomain and it looks like your host just places this into your main domain (http://sportfoton.se/image/). Bluehost does the same thing. But in the control panel, I can select a different folder. So I created a subfolder where I have all my subdomains:
..../domains/subdomain1
..../domains/subdomain2
..../domains/subdomain3This way, my main account doesn't get too crowded.
Please post a copy of your code so we can help you get it working.
Don't edit the css files inside the template because they are overwritten with each version upgrade. There is a special facility called custom.css. More on that is in the docs at http://ce4.theturninggate.net/docs/doku … custom_css. In order that this works you need to enable phplugins http://ce4.theturninggate.net/docs/doku … _phplugins.
The single image page is not really hook friendly as I learned a while ago. This is how my single image page looks after some modifications: http://danielleu.com/galleries/united_s … single.php.
In order to avoid that I have to redo too many changes when I install a new gallery template file, I introduced my own hooks. So now I only have to add the hooks to my template file whenever I get a new update.
I have Safari 9.0.1 on my system and the menu items are white and turn gray when I hover over them. I don't see a difference between Chrome and Safari.
Did you try to emtpy your cache?
You put this question in the Publisher forum. So I assumed that you would use Publisher to put publish a new image. But this doesn't seem to be the case and my approach would not work.
CE4 Cart is the shopping cart system for TTG galleries. And no, you could not use your code with that.
There is always the CE4 Cart component....
In order to use your third-party service provider, I would just have the image specific code in Metadata1 and then modify the gallery php file to use that metadata to build the target link. Obviously this change would be lost with each CE4 Gallery update!
Adobe is working on an update to the update..... more at http://blogs.adobe.com/lightroomjournal … lease.html
The G_STYLE identifiers for CE4 changed as well (link).
Did you modify the content of your 'new' site? It might be that your Site Root and PHPlugins path need to be updated to reflect the new location.