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.
If enabled, the sales tax applies to both packages and products. Application to Digital Downloads is optional.
Just to keep you updated. We have a fix in our development code: http://ce4.theturninggate.net/docs/doku … _changelog for release with our next maintenance build.
As a test, can you try renaming ttg-be/cart/lib/css/magnific.css to something else and see whether that solves the problem?
Hi Paul, I'm glad to hear. Hopefully it will work well for you from here on.
It works for me. I was able to authenticate with API URL of http://www.natuurismooi.nl/ttg-be/publisher/ and the default API Key. (which you should change). What version of the Lightroom Publisher plugin do you have installed? It should be the CE4 Publisher version 2.1.1.
The directory ttg-be is required. This places everything backend-related into one place.
By self-hosing, I meant is it a server you own or control. It is an odd operating system for a host. The OS version was released in 2005.
Hi Paul,
Publisher ships with a file, .htaccess_disabled. Have you by any chance renamed this to .htaccess? That's the only explanation I can think of for why ttg-be/publisher/api/ works at all. If you have, then either rename the file back again or delete it.
The .htaccess file turns on clean URLs, e.g. /ttg-be/publisher/api/listTemplates/galleries instead of /ttg-be/publisher/?c=api&a=listTemplates&p1=galleries, but that is not fully functional, hence leaving the file named .htaccess_disabled for now.
Hi, I'm not sure how it would work at all with an API URL of
http://www.natuurismooi.nl/ttg-be/publisher/api/Can you try this instead?
http://www.natuurismooi.nl/ttg-be/publisher/Is this self-hosted? It looks like your host is running an old version of Sun Solaris, rather than Linux, which we support. It's possible that the publisher isn't compatible with the OS.
Hi Kristen, these issues are caused by Gallery now using thumbnails-for-mobile instead of thumbnails. Auto Index and Cart now can't find your new thumbnails. I'll discuss this with Matt.
We package all files together as they are used for both a fresh install and upgrades. As always, read the upgrade instructions carefully. It is pretty clear from the readme.txt files, the online changelog and the TTG BE upgrade instructions that only those two should be upgraded and what will happen if you were to replace the entire ttg-be: http://ce4.theturninggate.net/docs/doku … e_versions
We intend to update TTG BE as infrequently as possible. 2.0.2 has been the only update, and we hope to need no more (touch wood).
Auto Index looks for directories within the current directory on the server. If my understanding is correct, FollowSymLinks will only resolve paths of requests coming from the web. It won't have any effect on the directories that Auto Index can see.
Hi Chris, thanks for the suggestion. It would be quite difficult to do. The Auto Index code doesn't know anything about Publisher. It looks for the autoindex.xml files of child albums to determine which to show. Hiding from Auto Index simply removes these files from albums so that Auto Index can't find them, which is a simple and effective solution. Your request would require changes in Auto Index to determine which albums to show, including coding in awareness of the Publisher/TTG BE login status.
That, it is. Here's a post about BOM in Notepad++ taken from http://stackoverflow.com/questions/8432 … thout-bom:
Use Notepad++ instead. See my personal blog post on it. From within Notepad++, choose the "Encoding" menu, then "Encode in UTF-8 without BOM".Found it. Your editor is inserting a Byte-order-mark at the start of the file. You'll need to change the settings in your editor so that BOM characters are not added when you save files. If you're curious, here's the Wikipedia entry on BOMs: http://en.wikipedia.org/wiki/Byte_order_mark
The very start of the first line must read <?php. Do you have a space or blank line before that?
I can see that the file http://kylelucy.com/phplugins/phplugins.php returns something when it shouldn't. That something is 3 bytes long, though invisible and taking no space in a text editor. I'll try to work out what character it is.
What text editor are you using? You may want to try something else.
I can see that the setup.xml file is there now, and that the listTemplates is returning the template name here: http://wheelerimaging.com/ttg-be/publis … tTemplates
You should be able to see the template in the Default Album's settings now.
I added an htaccess file to the templates folder to allow you to see what is inside it now. So should not get the 403 error. Yet, still won't show up in Publisher
If you restrict access to the templates, then we can't view them to help you, and your galleries may not be able to access the files they need. There's nothing to be gained in terms of security by blocking access.
Your server is being weird. For several minutes I was not able to view http://wheelerimaging.com/ttg-be/templa … st081214a/ and now I can. If that page throws a 403 error then that is something beyond our doing.
Now that I can see the directory, I notice that there is no setup.xml file. It looks like not all of the template files have been uploaded. Are you using Export or Upload in the web module? The latter is not reliable.
There's provision for ordering in the back-end (products are retrieved by order then alphabetical). We just need to add a dropbox so that the order can be controlled in admin.
Hi Michael, I'm glad to hear you're back on track. It's always a good idea to keep backups. The data directory is particularly important.
Hi Don, I can't really advise about Wordpress setups as I'm not familiar with it. If you're using the CE4 Theme for Wordpress then you may be able to get advice on that forum (http://community.theturninggate.net/for … wordpress/)
Hi Dave, which version of Publisher are you using? The linked gallery doesn't look like it's been published with CE4.
In particular, this link doesn't show me the album setup as it should: http://galleries.photolens.co.uk/Photo_ … ndon/?data
What slows Publisher down is the time to create renditions. Unlike the web module, which seems to generate multiple renditions from the master file in the one cycle, the Publisher has to create each rendition separately.
Here are some ways to improve the performance:
1. Reduce the number of renditions. If you don't need photos-for-download or photos-for-purchase then don't enable these in the template. photos-for-purchase renditions aren't necessary any more with the CE4 cart, as you can now prepare and upload purchased files as-needed after the order has been placed.
2. Reduce the size of images. In particular, the photos-for-download may be particularly large
3. Render your photos from JPEGs rather than RAW files. This would require you to export as JPEGs, then re-import again, and use the JPEGs in your published collections. This is not at all convenient, but worth considering if you have a very large number of photos to publish.
4. Export from smart previews. If your master files are on an external drive and you use smart previews, then disconnecting the drive will force Lightroom to generate renditions from the smart previews. This can significantly speed up publishing time.
Thanks Kristen. I've hidden the albums from search for now, until I hear back to you regarding the galleries to delete.
I found the initial error in the log: when attempting to delete 'wild' from the server, the server responded that the directory could not be deleted. Unfortunately it doesn't state why this was the case. Had you uploaded any files or galleries into 'wild' manually via FTP? That's the only thing I could think of that could cause the error.
Hi Kristen, Thanks for the further details.. the crux of the problem seems to be that removing the album/s in Lightroom left them untouched on the server. The Lightroom log may shed some light on this. Can you find the file ttg.log in Documents or My Documents, zip it and email it to me?
If you like, I can remove these from your database. To do so I'll need the admin login for your TTG BE setup (change it to something not sensitive first). Am I right that 'wild' and the 'Raptors-Osprey-Eagles-and-Hawks' album both need removing?
It looks like something is amiss with your Wordpress installation. Does the path to wp-content look correct? (that is, does public_html/wp-content exist?)
Hi Don, the final error seems to be that public_html/wp-content/wp-cache-config.php can't be found. Does that file exist on your server at that location?