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.
Hi Pierre and Torsten, this was included in 6.0.3, which came out last week. See the changelog for the updates and upgrade instructions: http://ce4.theturninggate.net/docs/doku … _changelog
Further from what Matt said. The products with databases (CRG, Publisher and Cart) automatically perform database upgrades for all of the intermediate versions. So if there were database changes for 6.0.2 and 6.0.3 (which there aren't), then replacing the 6.0.1 files with 6.0.3 would perform the database changes needed for 6.0.1 to 6.0.2 and then 6.0.2 to 6.0.3.
It sounds like you're making progress. I've sent you a link to help check the structure of your galleries in Lightroom. It's a tool that I use to help solve issues like these. The idea is to compare this structure with what you're seeing in FTP.
To view the structure:
1. Run the command File -> Plugin Extras -> Output Structure (or similar name)
2. Find your ttg.log file under Documents.
3. There should be a line at the end with 'inspected' near the start. Copy everything from [[ to ]] including the square brackets.
4. Click on the Convert gallery... On the page I messaged you
5. paste the [[...]] text in
6. Visit the List gallery xml files link on the page I messaged you
7. Click View Structure on the most recent entry (probably with 20150211 in the name)
The number next to each can be ignored for now. If the structure matches what you're seeing in FTP then you should be fine. If not, please pass me your TTG admin login so that I can see if this can be fixed in the database. It would also help to have ftp access so that I can compare the file structure as well.
The migrator function is meant to handle everything database-related. After migrating, the galleries directory should remain intact, with all ce3-specific files moved aside. For example the file galleries/galleries.xml is renamed to galleries_ce3.xml. At that point, the ce3 instance in Lightroom should no longer be able to manage anything under galleries on your server.
Have you changed the structure of the albums and album sets in either the ce3 or ce4 Lightoom publisher instances since migration?
I suggest you disable your phplugins and try migrating again. We cannot provide support for code you've added to phplugins.
The output publisher structure is a command that we sometimes ask customers to run in order to work out issues. The output is capture in a file called ttg.log, found in your Documents directory.
Who are you hosting with? It can help to make sure the address you're using for the vendor email has been added as an account in your control panel.
That's correct, Rod.
Hi Tom, thanks for pointing this out. Do you the order email with that message? If so, please forward it to my email address (available via the Email link under my picture), redacting any confidential client details. I'll then see what can be changed in the Cart to work around it.
This should be the cause of the email issue: https://code.google.com/p/android/issue … l?id=63538
A persistent bug in Android, that has been affecting users for over a year. It's probably worth reading through the comments to see if there's a suitable way to solve this by updating your browser and/or email client.
The various text items can be customised in the CRG Admin. Look for the Localisations menu item under settings and click Manage Localisation for the language that your CRG is set to use, which is probably US English.
The CRG client login is an entirely different mechanism to the non-CRG password setup. CRG isn't aware of the master password.
At this point, your only way to view the galleries is to do so via a client login. You could create one with your own email and assign the albums to yourself. Of course this isn't ideal, and something we'll put more thought into.
Have you tried adding the attributes and options in the order that they should appear?
Make sure you are generating the gallery with the latest plugin.
Hi, for some reason the top-right cart icon isn't in the generated Publisher gallery. It can be found in http://caddinfo.com/photo-now/ttg-be/te … /index.php but not in http://caddinfo.com/photo-now/ttg-be/te … _index.php
The first thing to try is to re-upload both index.php and template_index.php in your template. If that doesn't help, can you zip up your no_download_gallery_template_2015-02-02a template and email it to me?
Hi Geoff, I'm glad to hear the emails are working for you now.
To help other 1&1 customers, can you help confirm what you did? I'm assuming:
1. Setup an email address in the 1&1 control panel
2. Set your vendor email to use that address
3. Set the mail send type to 'mail'
Is that correct?
Hi you said that an email went through. Was that sent using 'mail' rather than 'smtp'?
Was the sender address on your received email the one you specified or some host-specific address (e.g. user1234@host.godaddy.com - completely made up, I have no idea what GoDaddy would use as senders addresses). If it's something like that then it may help to set up your sender's address in the cpanel of GoDaddy. You don't have to use GoDaddy for your email. Such as account is just a dummy account, but it will help inform GoDaddy that it's a real email address, and so GoDaddy will be more likely to use that as your sender address when using 'mail'. A more legitimate address is more likely to make it through to the receiver's inbox.
Hi Geoff, sorry to hear it's still not working for you. All I can suggest at this point is that you set CRG to demo mode (which means both vendor and client emails are sent to the client), and try using a variety of email addresses that you're able to check for the client's email. Then check all of the inboxes and spam folders. The idea here is to at least try to find one positive case of the emails actually going out, so that you can eliminate sending from 1and1.
Regarding the other smtp-related configuration fields. If set to 'mail', these are unused and have no bearing on the mail sending process.
Unfortunately post-processing filters won't work with Publisher. The reasons are technical:
Lightroom provides a default rendition loop that outputs one rendition for each photo in a published collection. Publisher needs to generate multiple renditions per photo (photos, thumbnails, etc.) and so can not use the default rendition loop. In code we are calling the same rendition functions that the default rendition loop calls, which in theory means that any post-processing filters should be applied for every rendition. Due to reasons unknown, Lightroom ignores post-processing plugins for renditions generated explicitly in this way.
This is one of many unexplained limitations of the Lightroom SDK that we have had to contend with. Very little, if anything, is ever fixed or improved with the SDK, which has remained almost unchanged since Lightroom 3.
We have pondered changing Publisher to generate one rendition per photo, and have other renditions generated dynamically on the server. This raises a couple of issues: Firstly, converting images on web servers is memory intensive, so the chances are high that this will exceed the maximum memory usage allowed by hosts. Secondly, this would mean that all renditions on a gallery would have the same watermarking and color modes.
Hi Geoff, most hosts block attempts to send via smtp, so you may be out of luck with that.
Some hosts don't like to send out from mail(), or do so with a system address that may get picked up as spam, unless the host knows the from address you are sending from. For example, I host with Bluehost. Let's say I was using vendor@my-site.com as the sender address. Bluehost was happy to send emails out as from vendor@my-site.com only after setting up the email address in my Bluehost cPanel. That doesn't mean I'm using Bluehost for my email, but only that Bluehost has an account for that email.
Hopefully this will be a one-off. Had you had anything go wrong prior to that error, such as Lightroom crashing while using Publisher? Also, had you manually changed any files in your galleries using FTP? That can confuse Publisher.
If this happens again, it will be helpful for me to be able to look at your file structure and database.
The search folder can sit pretty much anywhere. The restrictions are that ttg-be doesn't reside in a sub-directory that search isn't in, and that search be no more than 20 levels deeper than ttg-be.
These pairs are okay:
/ttg-be
/search
/ttg-be
/my-site/search
/my-site/ttg-be
/my-site/search
/one/two/three/ttg-be
/one/two/three/search
/one/ttg-be
/one/two/three/search
This is not:
/one/ttg-be
/search
You could in theory copy search/ to multiple locations, if that made sense for your site navigation.
Hi Kristen, no worries I'm glad that it's working for you again.
Hi Kristen, is that a CE3 template? If so then the $mobile_php variable should already include the query string without you needing to edit the file. I don't know how well CE3 templates would work with the CE4 Publisher.
Can you email me the template files so I can take a look?
For ordering, make sure the collection's Sort field is set to User Ordering, and that the album's 'Photo order' field is set to 'Managed by Lightroom'. You'll then need to publish a photo for the ordering to take effect. Right-clicking a single photo to republish and then clicking Publish will suffice.
Regarding editing album sets, there was a bug in Publisher. Please update to the latest version, downloadable with the 2.2.0b zip file. That bug resides in the LR plugin. There shouldn't have been any side effects other than not being able to edit an album set.
Your other problems will need some investigation. Can you please provide me with your TTG BE admin login (changed to something you can share if needed), and preferably grant me FTP access? It's best to send those details via Email using the link under my name. Also, what is the URL of the gallery you are trying to update?
Search replaces the block text section with the search form or album results, so there's no way of configuring the template to include copy there (without editing the template manually). That said, I am working on adding a Publisher setting to provide page copy to be inserted above the search field. This should be in the next significant update, I hope to get out in February.