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
Update:
Thanks to Matt it has been discovered that it was double quotations marks causing the text to come up on the thumbnail and the <br/> html doesn't seem to be problematic. I found it interesting that it has something to do with the combination of double quotes and having more than 1 paragraph. Another photo with caption had double quotes too, but no problem until I added another paragraph to it to see if that was it. So for those interested use single quotes instead and all will be good.
I wanted to let people know that I have found a way to get images to always open in their fully expanded view. Having captions on images can make images usually open up quite small. I didn't like the aesthetics of that and discovered that by adding hs.allowSizeReduction = false; to the custom.js file the issue seems solved and I have not noticed any problems on viewing from desktop or mobile devices.
If anyone knows if this could be bad for some reason please inform.
2.Also I was wondering if anyone knows why one photo I have always comes up with caption text over the thumbnail. The text is blue and looks look it might be a hyperlink and changes red when clicked. No other photos of mine do that. I'm guessing there might be something with text formatting, but haven't figured it out yet. I have noticed that it at Least goes away in LR thumbnail previews in HSGallery when I remove<br/><br/> from the captions to divide paragraphs, but upon exporting the text is still there. Other photos are formatted with similar html in captions and have no problems though, so it doesn't make sense. Any thoughts or similar experiences?
Thanks!
Sounds good. Thanks for the rundown of new features Rod.
One thing I was referring to was how Boje mentioned in a post that he missed being able to align title and caption separately now in CE3. If this is the case that is too bad. Centering titles and having captions align to the left looks good, but centering both or having titles to the left not so much. I think its good to take away unneeded options, but that is something that would be good to keep.
I figured I am fine with CE2 until Cart is available, so didn't bother to upgrade yet. I didn't know that shared resources is now available in CE3. That is a huge improvement.
Aren't the text options even more limited in CE3 though? That would be my only concern. I recall people talking about not be able to do various things with text in CE3.
Thanks Rod,
So by using phplugins and shared resources one doesn't need to copy the style settings from Pages and paste it into HSG, CRG, Cart, AI, etc if one wants to make a basic change like add a new link to the nav bar or change the masthead, etc? How does one enable shared resources?
Yes I tried uploading photos using Pub with simple html things like <p> & <br/> and it is like mobile in that it makes the code visible and doesn't break lines.
Yes I know for most people short descriptions are sufficient, but for anyone wanting to explain stories and meanings behind things it isn't very functional without html.
Thanks for the possible work around Rod and feedback Matt.
If Matt or someone else who might know could answer the other 2 main questions (in bold) I had I would be very grateful.
Is there a way to make photos with captions default to opening full?
Couldn't one include a line of code for that?
Does Publisher's metadata tokens usage differ from a normal export of galleries and thus not allow html? Regardless of whether HTML should work or not it DOES WORK in normal exports of galleries. It is very important to me to be able to explain the stories behind images and I'd guess at least a few other users. I am willing to overlook the mobile not using html if at least people on computers can read about images in nicely formatted text. If Publisher's use of metadata tokens makes the html code in titles & captions not work viewed from computers I think it should be explained upfront to people that their metadata functionality is a little different.
This lack of basic text formatting support seems to be TTG's weakest link (besides not having one unified way to update a webpage and all plugins at once, Those 2 additions would make TTG almost flawless IMHO). To say basic html in captions & titles it is beyond the scope of LR & the TTG plugins doesn't make sense as it DOES WORK on basic export, except for mobile and apparently Publisher. I would like to try solving this html functionality issue with mobile if at all possible. I wouldn't mind having some people look at the file and paying for coding it to work if that is at all possible. Could someone point me to which file/s would be needed to look at for this? Perhaps the mobile.php & or mobile_template.php for a gallery?
I think it should be explained upfront to people that using TTG they can't describe photos with even basic line breaks because I feel some users may save a lot of time not working to figure out how to use and creating a site with TTG and then learning that text is so limited. Besides this I love TTG and would really like to see TTG flourish & improve. And like I said, I'm happy that at least it works on computers and if I can figure out how get photos with captions to open up full than that will be great.
Much Appreciated
I need to be able to explain individual photos in length with captions. I understand that for mobile the photoswipe code doesn't allow for the captions to be formatted for html presently, but viewing from a computer captions with line breaks are possible with html and look good from my tests.
I've asked before, but never received an answer; Is there any other possible way to describe individual photos with TTG plugins besides captions? The ability to describe photos with html is IMHO one of the most important features needed to make TTG completely functional. This really needs to be worked on as it seems crazy to have all the functionality of TTG, but not have the basic ability to describe photos other than one big hard to read block.
Something else related to captions is that when viewing exported images with captions that are vertical/portrait in composition the photo and captions come up on a computer very small. Landscape/Horizontal images are a little smaller than normal too, but not really small like verticals. Pressing the enlarge photo icon will solve that problem, but some people visiting websites won't know to do that and it seems annoying to have to do such anyway. It also isn't consistent with the other photos without captions which default opening full and thus looks unprofessional. Is there a way to make photos with captions default to opening full?
Also, recently I've started using Publisher and have noticed that captions don't look right (aren't formatted with html) even on the computer for some reason. I know that Publisher uses the metadata tokens, but does such use not allow for html? If so that would be disappointing.
Thanks
Well you know what I want for Xmas. Is HTML for mobile possible in future updates?
Is there any other way to have paragraph descriptions of individual images?
Surely this is an important function for photographers.
Thanks
BEST WAY DISCOVERED
I just discovered that line breaks can be inserted directly from within LR by adding <br/><br/> or partial breaks with <br/> or <p> depending on desired style in the caption or title metadata fields.
For editing already exported galleries the above method can be done, but it is obviously much more of a pain in the a$$, so better to do it in the Library module within LR and then export.
Hello Everyone,
I was wondering how to break lines/paragraphs within captions & or titles and saw there were a few posts on this topic already asked by kristenwestlake and hulsebos58 and that people were saying there doesn't appear to be a way to do it. After trying a few things and figuring out how to do it I thought I'd share.
Go to the index.php file of the gallery with the image/s that you want to have paragraph breaks within and edit the section of an image that has <p>your text example</p> in it. In between sentences that you want to have a paragraph line break enter <br/><br/>. So it will look like this-<p>your sentence. <br/><br/> another sentence.</p>.
This works for either titles or captions.
And if one just wants to have a partial line break with the next sentence starting from the next row down (instead of a complete line/paragraph break) just enter one <br/> or even just <p>.
Just make sure you are editing the text within the <p>...</p> section as there are other similar looking areas with the same caption or title text, but that won't be applied to the actual area wanted.
Hope that helps
It may be possible to create a multilingual site with php. See link below. Being a complete newb to website building I don't know specifics about implementing such script into the present files, but I will try to figure out how to do it.
http://jacksonengineering.net/proj_phplanguage.php
Example of script.
<?php session_start();
// session start must be first statement
// do not leave any white space before the php declaration
//the url ? language declaration should have preference over the page name
$pagename = basename($_SERVER['PHP_SELF'],".php");
$pagenamearray = explode(".",$pagename);
if (count($pagenamearray) == 2){ //there is currently a bi-lingual site page loaded
$_SESSION['language'] = $pagenamearray[1];
$urllang = $pagenamearray[1];
}else{ //this page must be a non bi-lingual page
$urllang = 'en';
}
//check for a language selection on the url
if(isset($_GET["lang"])){//language has been passed via url
$_SESSION['language'] = htmlspecialchars($_GET["lang"]); //set it what was found
}
///if there still is no language set, go with english for a default
if(!isset($_SESSION['language'])){
$_SESSION['language'] = 'en';
}
//now we think we have the session language figured out
//
//now check for a version of the current page in the desired language
//lets make some things clear first
//the current page url is either en or de from $urllang
if($urllang != $_SESSION['language']){ //if the url isn't the same as the $_SESSION
if($_SESSION['language'] == 'en'){//if it should be english then load the english
header("Location: $pagenamearray[0].php");
exit;
}
if($_SESSION['language'] == 'de'){
//construct the name of the file if it existed filename.de.php
$deVersion = $pagenamearray[0] . ".de.php";
//we have to check if a de version actually exists of this page
if(file_exists($deVersion)){//redirect if it exists
header("Location: $deVersion");
exit;//stop executing things
}else{$pagelangnotfound = ture;}
}
}
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!-- do not change the doctype languages as these don't refer to the content language -->
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<!-- again, do not ever change "xml:lang" property.
however one should set the "lang" property to reflect the content language -->
<head>
<title>PHP Language Simple Demo</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<!--The charset declaration is very important here-->
<meta name="description" content="This is the multilingual php website Demo" />
<meta name="keywords" content="php language simple example code" />
</head>
<body>
<?php
if ($_SESSION['language'] != 'en'){
echo 'Sprache: <a href="'. $_SERVER['PHP_SELF'] . '?lang=en">English</a>';
}else{echo 'Language: English';}
?> |
<?php
if ($_SESSION['language'] != 'de'){
echo '<a href="'. $_SERVER['PHP_SELF'] . '?lang=de">Deutsch</a>';
}else{
echo 'Deutsch';
if($pagelangnotfound){
//if the user has selected german but the current page is not found, this text is displayed
echo " (Leider gibt es noch keine Übersetzung für diese Seite.)";
}
}
?>
<p><a href="./../../proj_phplanguage.php#simpex">back</a></p>
</body>
</html>
I've been wanting a dual language site as well and have been thinking about the most elegant way to do it.
So far I've only come up with.
1.Write the other language under the text of the other where necessary.
This would make the pages longer and perhaps annoying to some.
2.Could one make another nav bar for the other language? At first I was thinking about the footer and that might be a good compromise if possible, but that wouldn't seem possible bec it just copies the main nav bar, unless their is a hack to separate them. Matt or someone else know a hack for this? Or would it be possible to create a two-tiered top level nav bar instead of just having to make all the labels unpleasantly small on one long nav bar?
Any other ideas?
Much Thanks
Pages: 1