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.
I am encountering a strange effect. After a rather long time I have pulished a new gallery in a nested structure (Locations/Australia/Long Reef) and discovered that the published album is not visible, in fact none of the albums in that structure are visible anymore.
A link to the Autoindex is here:
http://www.fotowarkstee.de/galleries/locations/
where this album should be accessible when selecting New Zealand:
http://www.fotowarkstee.de/galleries/lo … th-island/
but it is not shown - but is was before
The albums themselves still exist (if I go there directly from Publisher in Lightroom via " Go to published Album" it is there. Just the links in the Autoindex are not there anymore. If I create a new Location, it appears, but when I create a new album inside that from Publisher, it gets created and published, but does not show as if the flow-down links froim the Album Set are not there.
My other Autoindex structures work fine (not true, see edit at the bottom).
I am stuck here. Any help very much appreciated.
Edit: Have just discovered that all my third level galleries have disapeared, not only my locations.
Hi there, I pull this thread up agin, because I deal witht the same problem and I do not really get the point whether there was a solution to the problem or not.
When I have one of my albums shared on Facebook that sits in an album set, then there is no thumbnail shown. I believe this is the problem that was discussed in this thread before?
When I threw the link to the album into Facebook's debugger no photo was shown. When I checked, there was nothing shown in the og:image field. But when I clicked into this field, the browser attempted to open a photo - which was correctly labeled (I mean it showed the name of the thumbnail I had selected in Publisher for this album) but it was epecting it to be in the "photos" directory of the album. I am managing my thumbnails in a seperate thumbnail album (hidden from autoindex), which works fine in publisher and on the website itself.
Now, having said all of that I have - just for curiosity - copied this thumnail into the /photos directory of the album, and now the Facebook debugger shows an image.
Am I right that there is no other way to secure a thumbnail on a Facebbok shared album other than copying the thumbnail into the photos directory?
Thanks, Rod!
Helpful as always - and it worked once I had spelled freewall with two "l" instead of just one....
It is always the same problem, things work for quite some time and then the knowledge of how to do things fades away. For people like me the support here is invaluable. But will study your tips and tricks a bit more thoroughly, before I go out again to pile up heaps of new photos.
Thanks and cheers from Downunder
Alfred
A quick one - I hope.
I am in the process of re-establishing my CRG templates, which I had lost as part of the latest Lightroom update desaster. Now, I have got most of it in place including moving the cell number to the right as described in this threat. But I seem to get this only to work when using the Ce4 Standard Thumbnail grid layout. As soon as I switch to the Freewall (Masonry) layout the cell number sticks to the left.
Is this expected and if so, any suggestions how to modify the Custom CSS to make it work here as well?
Thanks for your help.
Alfred
After I switched to LR 6.2.1 I got problems importing a catalog from my Ultrabook. When I go on a birding tour I usually create a new catalog on my Ultrabook and import and edit my shots while I am on the move. Being back home I export the catalog and import it to my main machine (and copy the source files off course). Doing this worked fine up to 6.1.1. Under 6.2.1 LR goes into a "heaving processing" state using up to 90% processing power and never returns ...
So I rolled back to 6.1.1. Doing this involved deinstalling 6.2.1 and reinstalling 6.1.1 - and all my web-templates were gone. I thought no problem, as I frequently back-up my entire C-Drive using Acronis True Image. When I opened the last backup, the shock was huge when I recognised that there were no web-templates in the directory I had expected them to be. I still do not know what happened, because they were usable up to the last moment before I installed the 6.2.1 update. It is pure luck that I had copied my templates a couple of months ago, when I helped my daughter setting up her web-site. I am telling this to keep everybody alerted who wants to roll back to LR 6.1.1 => BACK UP YOUR TEMPLATES BEFORE DEINSTALLING, actually back them up frequently.
By the way, if it motivates you maintaining your great support work: I have a couple fo spare d's for you Roddddddddd :-)
Cheers from Downunder. Alfred
Hi Ben, when I updated my files last night I recognised the fact that the zipped file was still called BE203, but the readme text referred to changes for version 204. This is a bit confusing, maybe adding a line to the readme explaining the situation, would be helpful?
Hi Gommit,
my site is hosted by "Host Europe" (https://www.hosteurope.de/) and I have had no problems related to the host thus far.
Alfred
Couldn't stop myself from trying befor dinner: Needed to change the permisson setting to 777 (of the exisitng directory) then the update completed successfully. 755 was not sufficient.
Thanks again, Alfred
Thanks, Ben - will do once back from dinner. I am not using cart at all. Just the normal album stuff and CRG.
Alfred
Hi there,
have updated to Publisher 2.3.1 today and get this error message when logging in to TTG-BE:
Updating TTG CE4 Publisher from version 2.3.0 to 2.3.1
Backing up databases...
Unable to backup master.sq3. Make sure this path exists and has correct permissions: ../framework/../data/publisher/database_backups
Error message: copy(../framework/../data/publisher/database_backups/master_2_3_0.sq3) [function.copy]: failed to open stream: Permission deniedCannot modify header information - headers already sent by (output started at /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/helpers/GenericUpgradeHelper.php:60)|#0 [internal function]: ErrorHandler::handleError(2, 'Cannot modify h...', '/is/htdocs/wp11...', 87, Array) #1 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/publisher/application/views/templates/template_admin.php(87): header('Cache-Control: ...') #2 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/helpers/ViewHelper.php(40): require('/is/htdocs/wp11...') #3 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/publisher/application/controllers/AdminController.php(46): ViewHelper::render('admin/index', Array, 'admin') #4 [internal function]: AdminController->index() #5 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/controllers/Controller.php(41): call_user_func_array(Array, Array) #6 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/Framework.php(124): Controller->dispatch(Array) #7 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/publisher/index.php(40): Framework->route() #8 {main}|URL: /ttg-be/publisher/index.php
Since it worked last time, I have been out photographing and not done anything to my website.
Any suggestions what I need to do next?
Thanks, Alfred
Cool! Another entry for my "not to forget" file, although it is much easier not forgetting what you have understood! Have tried setting both at the same time ...
Thanks again for the support in this forum. Alfred
Kyle, what I was trying to do is setting the the size of the exported jpg files in the Gallery template, which I use for the custom-thumbnail album to 300/200, but I can't go below 250 pixels - hence my question. So how do you achieve a short edge of less than 250 pixels?
Thanks Rod, will add a line to my "not to forget" file.
Yeah ... I must admit that not using these features on a daily basis, makes it difficult to maintain oversight. When I use an Iconic Autoindex - I can set the aspect ratio, but not the actual size of the required thumbnails, correct ? The required size of the thumbnails is indirectly determined by the overall core width, the aspect ratio and the number of album columns or? Now, if I am going to use custom thumbnails is it then sufficient to have the aspect ratio set correctly and the size is subsequently scaled automatically?
In any case it is very convienient to manage them through Publisher if one uses custom thumbnails at all. I can see that already.
If I would want smaller thumbnails, then I can see no reason why your suggestion would not work - but I am going to try this tomorrow as I am on the same side of the world as Mat and Ben and need to call it a day.
:-)
Hi Carsten, if I am not getting your point correctly, appologies for that, but I have the feeling I went through the same process when migrating from CE3 to CE4. I had under CE3 created the autoindex structure manually.
Publisher is a huge step forward! My understanding is that "galleries" created by pages is an autoindex folder. You can now simply create autoindexes in there using publisher (creating album sets), which become autoindex folders in which you can publish albums using Publisher. Simple and straightforward. All you need to do is creating autoindex templates, which you ftp upload in ttg-be/templates/autoindex. You then use these templates when you create album sets. You also need to create templates for the albums, which go in ttg-be/templates/gallery, which are used when you create the albums, which go into the album sets. My understanding is further, that you can create nested structures (album sets in album sets) as you like. I trust the experts will correct me, if I am wrong. You could also publish albums directly into "galleries" created by pages.
Rod is always faster ...
Forget my earlier post - when creating thumbnails so far I have created them in the size I was going to use and uploaded them manually. I do think now that this is not really necessary, insofar the raised question is irrelevant. Please correct me if I am wrong.
After some thinking and a bit of trial and error I have got this working. Very nice!
Now here is a question, for which the answer escapes me: How do I create thumbnails, which are having less than 250 pixels on the short side? When I try to set the size of the uploaded photos for the created custom-thumbnails album (which are supposed to serve later as thumbnails) below 250 in the Gallery template I am not allowed to do this. There is a lower limit of 250 pixels. Any clarification much appreciated.
Thanks, Alfred
Same for me - glad that I can stop debugging ... Reverting to 7013 fixes it, but I have left in the broken state for tonight:
http://www.fotowarkstee.de/galleries.php The rest of the website seems to work fine.
I have just completed the updates of all my templates and as part of that process re-activated the "Get shared resources from CE4 Pages" option.
Now, since pages has been updated again today due to a bug-fix as I understand: Do I need to re-issue all my templates (for the reason of using the "shared resources from CE4 Pages" or is it sufficient to only update Pages itself and the Autoindex templates?
All is working now after some trouble sorting permissions - but Ben has been a great help: a CHEERS for him!!
Do still not understand though why the update went off the rails. In any case, thanks for the unvaluable support from this forum!
Ben, have sent a PM with the ftp access info.
When reading the changelog for the Publisher 2.3.0 update, you'll find:
v2.3.0 ( 2015-06-10 )
...
Adds support for file permissions to be managed via the TTG BE Admin page (requires TTG BE 2.0.4 or higher)
...
All I can find in the downloads area is TTG BE 2.0.3 ! So is this a simple typo, a promise for the future or am I missing something here?
Anything I should be worried about?
Thank's Ben going to bed now in Sydney as well. Using CRG for tests at the moment, so no panic on my end. Will take care of the rest tomorrow morning.
Have sent a PM to Ben with the required info.
Hi after I have updated to CRG 6.1.0 I get the following error message when logging in:
Updating TTG Client Response Gallery Admin from version 6.0.5 to 6.1.0
Backing up databases...
Backed up master.sq3
Upgrading to version 6.1.0...
Updating feedback profiles structure
Unable to upgrade to version 6.1.0
Error message: SQLSTATE[HY000]: General error: 14 unable to open database fileCannot modify header information - headers already sent by (output started at /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/helpers/GenericUpgradeHelper.php:60)|#0 [internal function]: ErrorHandler::handleError(2, 'Cannot modify h...', '/is/htdocs/wp11...', 87, Array) #1 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/crg/application/views/templates/template_admin.php(87): header('Cache-Control: ...') #2 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/helpers/ViewHelper.php(40): require('/is/htdocs/wp11...') #3 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/crg/application/controllers/AdminController.php(54): ViewHelper::render('admin/index', Array, 'admin') #4 [internal function]: AdminController->index() #5 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/controllers/Controller.php(41): call_user_func_array(Array, Array) #6 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/framework/Framework.php(124): Controller->dispatch(Array) #7 /is/htdocs/wp1134443_GK99ZZU9WE/www/schulte/foto_warkstee/ttg-be/crg/index.php(24): Framework->route() #8 {main}|URL: /ttg-be/crg/index.php
Any suggestions what went wrong and how to fix this?
Thanks Alfred