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 Torsten, we already have something similar in our working code. The FROM address remains as yours, however the REPLY-TO is set to that entered by the client. Clicking reply therefore goes to the client's address.
I don't have a schedule for updating this. We don't have any known bugs and want to avoid unnecessary update fatigue for our clients.
Hi Patrick,
The CE4 cart is found in two files, ttg-be/data/cart/master.sq3 and orders.sq3. I suggest that you copy these over, and see whether everything looks correct. If it doesn't look correct, then simply remove these files on your new instance, and fresh copies will be created the next time the cart is used.
Ben
Hi Patrick,
Sorry, but looking into a case like this will likely take several hours, and I've been running at 200% for the last several weeks.
Friday and Saturday are looking good though, so I should be able to sit down and try to work out what's going on. I'll need to ask you for a few things, some that you've already provided:
1. TTG BE admin login (so that I can see the database structure)
2. FTP access to your server (so that I can see the albums and their locations)
3. Output of your album structure from Lightroom. This will be added to ttg.log by running the following command in Lightroom:
File -> Plug-in Extras -> Output Publisher Structure, and then selecting your Publisher instance and clicking OK.
4. The latest ttg.log file from Documents/My Documents.
Regards,
Ben
You'll need to ask your host to enable the Sqlite module. This is a standard module which your host should provide.
Thanks Norbert. I'll take a look. Who are you hosting with? There is a handful of hosts that publisher is known not to work well on.
Hi Daryl, we have a couple of other things we can try.
I've sent you an updated plugin that should work around the problem. Additional to my email, if the migration still fails (or if it 'succeeds' but misses many or all albums), the following steps may help provide information:
Within Lightroom:
1. Click File -> Plug-in-Extras -> Output Publisher Structure
2. Select your CE3 Publisher Instance
3. Click OK
This will display the structure on-screen, and to the ttg.log file. It will be helpful to send through the ttg.log file after running those steps. If you structure pushes the 'ok' button off-screen, the window can be dismissed by pressing enter.
Hi Kristen, this is a bug in the way that search handles redirects to mobile.php. See this post here for a workaround until we find a better solution:
Hi Mark, I'm glad that solved it. If you're curious, the databases behind TTG can be accessed via the phpLiteAdmin link on the TTG BE dashboard with an additional password of 'admin'. The tables are normalized
No problem. I hope that solves the problem for you. Our focus lately has been on the release of CRG. Publisher had had some quite substantial updates in that period of development, and this search issue had crept through.
The last time I used Access was back in 1997. I remember the date functions were inconsistent in their ordering of the month and day-of-month. One function followed the Access settings, while another followed the settings of the PC the application was run on.. that made for some challenges deploying code on a variety of machines.
FYI, customers can 'enter' CRG galleries in one of two ways:
1. By visiting a CRG gallery with clients managed by CRG. After logging in, your client will be redirected to the gallery.
2. By visiting ttg-be/crg/ on your server. After logging in, your client will see a list of assigned galleries. In the case that only one gallery has been assigned, your client will be redirected directly to that gallery.
Hi Mark, I'm not sure if proprietary is the right word. To me that implies obfuscation and lock-in. The databases use standard SQL and are readable without any TTG code. The data is always yours and in a format that with some technical skill can be taken and used however you like.
Thanks for the link. Looking further into this, there was a bug with searching on metadata. Your keywords are saved in the backend but search wasn't retrieving the results.
I've applied a silent update to the Publisher files that fixes this. To install these:
1. Download Publisher 2.2.0b
2. Replace the ttg-be/publisher/application directory
3. Replace the CE4-Publisher.lrplugin, and restart Lightroom
Your search should then start working, without any need to republish the 10000 Square Meters album. At most you may need to search for another term and then search for fungi again, as the search retains the result of the last searched terms.
Keywords are saved in the back-end irrespective of the metadata settings. That setting only affects the metadata stored within image files.
Hi Daryl, it hasn't been much of a summer lately! We headed up to Mildura for a week and had some decent summer weather.
That error shouldn't happen. Looking at the code, I suspect it's caused by encountering a CE3 album that hasn't been created on the server. A likely culprit is the Default Album which LR adds when a new Publisher instance is created. Do you by chance still have that album in your CE3 instance? If so, try deleting it and migrating again. If you don't have that album, try also removing any albums in the CE3 instance that you know don't exist on the server.
I hope that helps.
Hi Mark, Publisher does not use the embedded metadata found within published photos. It maintains its own database of metadata as pushed in text fields during publishing. Can you give some examples of galleries and keywords that you are expecting to be able to search on but aren't getting the expected results?
I have tested the latest version of Publisher, set to export all metadata. This is keyword data I could find in a Published image. This includes three representations of the four keywords that had been assigned to that photo:
Iptc.Application2.Keywords String 5 "fish
Iptc.Application2.Keywords String 10 bee flower
Iptc.Application2.Keywords String 4 moon
Iptc.Application2.Keywords String 5 yarra
Xmp.dc.subject XmpBag 4 "fish, bee flower, moon, yarra
Xmp.lr.hierarchicalSubject XmpBag 4 "fish, bee flower, moon, yarra
The keyword output was the same for both "All Metadata" and "All Except Camera & Camera Raw Info". Unchecking "Wirte Keywords as Lightroom Hierarchy" omits the Xmp.lr.hierarchicalSubject entry.
Something to consider: Publisher will only re-upload images if the 'Push metadata without updating existing photos' option is *not* checked. If you're trying to update the photos with embedded metadata while leaving that option checked, you will be disappointed.
Technically, feedback from standalone CRG galleries are saved in real time too. However the feedback isn't linked to a client so isn't findable in the CRG admin. It's still there, should we find it useful to add a function for admin to be able to retrieve it.
Hi Jim, thanks for pointing this out. This was trying to process a 'type' field which is found in Gallery and CRG templates but non-existent for Auto Index templates. I have put in a hot fix, which can be found in a new download 2.2.0a. The only component you need to upgrade is the Lightroom plugin.
I'm glad that fixed it. Hopefully you can get your clients off your back now
Hi Norbert, who are you hosting with? Can you email me the log files, using the Email link under my name?
There are two types of files:
1. On your computer, a file named ttg.log, found in Documents or My Documents
2. On your server, the most recent file found under ttg-be/data/publisher/logs/
Hi Jonathan, this was a bug that slipped through on launch day. I take it you downloaded CRG a few days ago?
CRG doesn't need Publisher, but the version we launched with attempted to read in an empty configuration file from Publisher. This error never arose during testing, because all of the testers had Publisher installed.
To fix this, download CRG 6.0.2 and follow these steps:
Replace the CE4-CRG.lrwebengine, and restart Lightroom
Replace the ttg-be/crg/application directory
Replace the ttg-be/crg/lib directory
Login as admin to ttg-be/crg/admin
You'll also need to re-export that gallery and upload it again. I hope that helps.
Hi Marty, it looks like all of your products have been configured to use single prices for the base pricing. 'single pricing' means a given product can only be given one price for a pricing scheme. The customer is not offered any way of choosing options and pays that set price for the product / This means that any additional pricing for attributes and options won't be calculated into the price.
How your products arrived in that state is a mystery - changing to single pricing should remove all attributes and options for a product, and not leave them displayed and unused in pricing. Do you remember changing the base pricing from multi to single pricing?
(In case it's not clear from the instructions, )
Since your products are in an inconsistent state, I don't think this can be fixed from within the Cart admin. I can fix it in the database for you, by changing all of your products back to multi-pricing To do so, I'd need the login details for the full TTG BE admin, since this is the only account that can make changes directly to the database. Consider changing the password to something temporary, and sending it to me by PM or Email (using the link under my photo.)
Also, I recommend making a local copy of the file ttg-be/data/cart/master.sq3 in case something goes amiss with the changes to the database.
Matt uploaded a fix last night. To get your single pages working:
1. Download CE4 Gallery 6.1.4a
2. Replace the plugin
3. Restart Lightroom
4. Re-export the gallery as you setup for the template
5. Replace the files you had previously uploaded to ttg-be/templates/gallery
Hi Chumby, search works across all searchable galleries (i.e. those not password-protected or marked as hidden from search).
Thanks for the further explanation. This has arisen from optimisations for search in Publisher 2.2.0.
Previously, the search results were held between page views, so that if you returned to search/ the old results would still be there.
The new version clears the results if there is no q=searchTerm paramater. The mobile redirect is losing the parameter and therefore losing the search results.
I'll need to look further into this to find a good solution. For now, the problem can be avoided by changing a single line in the file template_index.php within the template used by search.
From this:
window.location.replace('mobile.php'); }
To this:
window.location.replace('mobile.php<?php echo $_SERVER['QUERY_STRING'] ? '?'.$_SERVER['QUERY_STRING'] : ''; ?>'); }
That just passes the search parameter to mobile.php during the redirect.
This is a bug that slipped through in the Gallery plugin. Two missing semi-colons in the single image template.
I suppose with the checked 'enable' password' two login instances are created. The first with the login credentials as given in the album setting, and the other through the 'Edit client' in the Client Response gallery Admin. But the TTG folks may know better.
That's pretty much it. The CRG login and the album password protection are two separate mechanisms. The latter simple shouldn't be in the CRG template, even if enabled in the web module before export. That's something for us to fix.
Hi Mark, the password controls enabled in the template are interfering with the CRG login. This is a bug that we'll need to look into. In the mean time, a workaround is to disable password controls in the web module before exporting the template.