Community @ The Turning Gate

Hi, I'm assuming you're referring to the migration tool that comes with Publisher?  If so, the migration tool does move CE3 CRG galleries to a CE4 instance.

I have just tried this out.  The steps I took:

1. Setup the CE4 CRG on the server.  This entails setting up ttg-be, ttg-be/crg and ttg-be/publisher, as documented

2. Uploaded a CE4 CRG template into ttg-be/templates/gallery/

3. Created a new Publisher instance that points to the equivalent location to the CE3 instance.  The CE3 instance API URL pointed to http://localhost/ttg/crg-migration-test/publisher/api/.  The new CE4 instance pointed to http://localhost/ttg/crg-migration-test/ttg-be/publisher/

4. Ran the migration tool (within LR: File -> Plug-in Extras -> Migrate galleries from CE3 Publisher to CE4 Publisher)

The albums from the CE3 instance were then managed by the CE4 Publisher, and had the look and feel of the CE4 template

Two further steps are needed to complete the process:

1. Migrated CRG galleries have feedback disabled by default, which is a limitation of the migration tool.  You'll need to double-click each CRG album and enable feedback in the Integration tab.

2. The fields that are available for feedback will be set according to the 'default' profile.  You'll want to update this profile to your own needs in the CRG admin console at ttg-be/crg/admin/

Thanks for the suggestion.  There isn't currently a way of showing something more unique.  I've added this to my CRG to-do list, to work on for the next feature update.

Hi Kris, it sounds like your host is suggesting you use the SMTP service that they provide to you as a customer.  This may be the same SMTP details that your host gives you for setting up external email clients (e.g. Outlook or Thunderbird), perhaps with a different SMTP hostname intended to be used internally within or between their servers.

Thanks for the URL.  According to this page: http://michaelvest.com/ttg-be/admin/lib … verify.php
your server is running PHP 4.  This version is long-deprecated and not supported by us or the PHP community.
PHP 4.4 has been unsupported since 2008, even prior the existence of any TTG plugins that use PHP (including all versions of CRG).

Who are you hosting with?  I suggest you contact their tech support and request an upgrade to PHP 5.  Depending on the host, it may just be a matter of changing a setting.

Are you using  'mail' or 'smtp' for your mail settings?  Can you forward on one of the emails you *have* received to my email address, available with the Email link under my name.

Hi, thanks for pointing this out. All Publisher images are exported as JPEGs, so clashing on the file name. If you were to export both files to disk as JPEGs, how does Lightroom manage the names so that they're distinct?
Virtual copies are handled correctly as we coded Publisher to handle that scenario.

Unfortunately, Lightroom's Publisher module doesn't support presets.  We're looking to add a checkbox so that the previously-entered album details will be used as defaults.

You would need to use transaction less and approve the sale.

Further from what Rod said, galleries under /galleries/ (or whatever directory you are using) are stubs that the Publisher back-end turns into a gallery on-the-fly.

For example, if you had an album at /galleries/my-album/, upon viewing the album, Publisher will check the unique ID of the gallery, and fetch all of the relevant information about the gallery from the database, such as the list of photos and the template to use.  Let's say that particular gallery was assigned to use a template named 'my-template'.  Publisher would then pass the album data to the files at /ttg-be/templates/gallery/my-template and generate the gallery for the user to view in the browser.

This happens on-the-fly and isn't something you need to think about.  The main points to note:

1. A published gallery will appear somewhere under /galleries/ (or whatever directory you have seen).

2. Galleries draw from templates under /ttg-be/templates/gallery/ (or /ttg-be/templates/autoindex/ for Album Sets)

3. From the perspective of the URL and what you see in the browser, a gallery under /galleries/ is functionally identical to launching a set of HTML files that fully reside under /galleries/.  The process of fetching data from the database and constructing a gallery with template files is transparent to the end user.

I'm assuming that you're trying to publish from the album named Default Album?  Publisher can't use that.  As suggested, please delete the album and create one of your own.

Publisher doesn't use .lrtemplates.  A Publisher 'template' is an exported CRG Gallery.  To set this up:

1. Setup the appearance and functions within the CRG web module of Lightroom
2. Click 'Export...' and save the files somewhere on disk.  For example as 'my-template'.
3. Using your favourite FTP program, upload the entire exported directory, e.g. 'my-template', to ttg-be/templates/gallery/

You should then have files at somewhere like ttg-be/templates/gallery/my-template/.  When creating a Published album, the available templates should include 'my-template'.

The above steps only need to be done once, for each type of appearance you're looking for.  You can then create as many Published galleries as you like that will use that same template.

It may be easiest to look into this via FTP. Can you provide me with access via the Email link under my name?

Hi Martin, thanks for the further info.  That is a pretty huge file.  Can you zip your local copy of the file and email it to me?  (using the Email link under my picture).  I'll then look into what is making the file so large and see if there's a good way to make it smaller.
If the file is still huge after zipping, could you upload the zip to your server and provide the link via email?

I'm wondering if the database files increase in size over time as they keep old versions of the data.  Thinking aloud, it may be possible to run queries on the database and exporting all of the data into a clean database file.  This would be akin to copying and pasting from an old Word doc to a new Word doc, which can greatly reduce the file size of the doc.

There may be ways of running command line tools.  Who are you hosting with?  I'm with Bluehost and have full command line access.