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.
Perhaps a little too tedious. As it stands now, you'd also need to republish the images. The one benefit is that you wouldn't need to plan out your structure or reconfigure your album sets and album settings, or which photos belong in the albums.
I'm looking to see whether the image republishing can be avoided. The publisher checks the database to determine which images need to be uploaded, and since the photos are not in the database they all need uploading. Ideally, the photos on the server itself could be checked to determine whether they needed to be republished.
An update probably won't be released for a while. However, I had in mind sending you over a new publisher before then. This won't be the a perfect solution. The idea is that you'd go through every album set one-by-one in Lightroom and edit them. That will save the album sets anew on the server. You'd then do the same thing for the albums. I see that you have a lot of albums, so unfortunately the process may be tedious.
Cpanel is the name of the software that runs the configuration dashboard on your server. I'm not sure about what upgrading the cpanel entails, but that's the terminology that GoDaddy has been using with other customers. I would have assumed that upgrading to a newer server and upgrading the cpanel were one and the same thing.
Other TTG customers have had their cpanels upgraded, and subsequently had the issue of timeouts fixed, without needing to manually migrate or rebuild their sites.
That's no good. I wonder if moving you to a new server upgraded the cpanel (which is what other customers have found to be successful). Is the behaviour the same as before the move? In particular when the server stops responding, is it for 60 seconds?
I can see that the numbering could be confusing. The a's and b's reflect almost-inconsequential changes that can be ignored as updates.
That's fine. The reason you received that message was because the albums weren't in the database. Has the republishing been successful?
I don't think the order matters, so long you remove them both from the server and from Lightroom.
I see it's gone from the database. You can try creating it again.
I've just run a test and it worked without a hitch: http://www.ioscapes.com/galleries/ben-test/
I suggest you remove 4-winter from Lightroom and creating it again. Please post here again before you create the album again, and I'll check that it's been properly removed from the database.
It looks like you changed the admin password to the one you sent me.
Thanks. My suspicions were wrong. Do you mind if I try publishing a test album to your server?
I suspect what has happened is that the album was still in the database. When you created it again in Lightroom, Publisher didn't copy over the necessary files or create the gallery.xml file. Unfortunately, the Update Albums link doesn't recreate gallery.xml files. If you can provide the guest admin is described above then I'll be able to confirm that this is the case.
Would you be able to change the Guest Admin's role to Administrator, set a strong password and email it to me? That will let me look at the publisher database to see if sheds any light on the problem.
Thanks Ken. I can't see anything amiss from your log file. Can you try logging in to http://www.ioscapes.com/ttg-be/publisher/admin and clicking the Update Album Files link on the Dashboard? That should copy over any missing files.
That's strange. Can you email me the ttg.log file? You should be able to find it under My Documents or Documents in your computer's home directory.
What steps have you taken to recreate 4-winter? Have you removed the files and directory from the server before doing so?
The directory ttg-be/data is not a temp folder. It is the most important directory in your entire setup, that you shouldn't overwrite or remove.
Hi Rod, those two folders are the best items to replace when upgrading TTG BE. However TTG BE has not been updated so there's no need to change any files. Note that Matt makes no mention of upgrading TTG BE in his blog post: http://theturninggate.net/2014/08/ce4-u … st-5-2014/
Can you look in the folder ttg-be/data/publisher/database_backups/ using FTP and post the filenames in there, if any?
What steps did you take to upgrade your site? Did you by chance replace the entire ttg-be folder?
Can you provide a link to a gallery where we can see the issue?
Are you still facing this issue? A link to a gallery would be good.
Hi Jack, the underlying cause of this has been fixed with Publisher 2.1.0. The scenario to create duplicates was to remove an album from Lightroom, while leaving it on the service (i.e. the backend), then creating the gallery again in Lightroom with the same slug. This usually wouldn't be a problem, except that the gallery-on-homepage expects one and only one gallery in the database with a slug of pages-gallery.
Is your site fully-working now in regards to this issue?
There are two ways of fixing this:
1. Remove all of the albums and album sets from your CE4 Publisher Instance. If asked to leave them on the service, then select to leave them.
2. Migrate your galleries again from CE3
or alternatively, wait for an update to the Publisher that re-creates albums and album sets if not found on the server when editing them. If you haven't worked much on your albums post-migration, then I suggest migrating them again.
I'd still like to know whether you accidentally removed the data directory, most likely by replacing the entire ttg-be directory.
Hi Michael, all of your galleries have gone from the database. Did you only replace the changed files, or did you replace ttg-be entirely?
That's great. It took a while to nut out the issue.