Updates: TTG CE2 Publisher 1.1.2 + TTG CE2 Highslide Gallery 4.2.4
Xitang, China
I am returned from China. Good trip, apart from the snow and cold. While I was away, Ben kept busy in the community forum working with users to improve the publisher, making fixes and adding support for new features. Updates are available for both TTG CE2 Publisher and TTG CE2 Highslide Gallery, the details of which are outlined below.
TTG CE2 Publisher 1.1.2
* Fix for error in reparenting album sets or changing album set slugs (caused by issue in updating 'Go To Published Album' URLs)
* Fix for handling Titles starting with '1', that were being interpreted as 'true'
* Updated pagination nav to be consistent with Highslide pagination (maximum of 5 listed pages to each side of current page)
* Changed {CellNumber} values to be continuous between pages
* Changes to metadata now automatically move photos to the re-publish queue
* Added support for HTML markup in the Content Block
* Added support for embedded metadata configuration in Publisher settings
* Changed publishing of thumbnails to only include Copyright info in embedded metadata
* Reduced amount of data sent back from server when obtaining URLs for Go To Published Album
* Added support for maps zoom level (requires Highslide 4.2.4 or higher)
TTG CE2 Highslide Gallery 4.2.4
* Fixed a bug when both OGP integration and password protection are enabled.
* Publisher: Map Zoom value is now passed to publisher template.
* Publisher: Updated handling of $cellnumber.
January 7, 2013 at 9:17 am
The Publisher documentation tells how to install, but not upgrade, Publisher. What is the proper way to upgrade — just move contents of the templates and templates_autoarchive folders out, overwrite the publisher folder with the new publisher folder, and then move the templates contents back into place?
January 7, 2013 at 9:59 am
Actually, there’s a page that covers just that:
http://wiki.theturninggate.net/doku.php?id=ttg_ce2_publisher_upgrading
To simplify, it usually comes down to three steps:
1. Update the plugin in LR.
2. Update the /publisher/api/ folder on your server.
3. Update individual templates as necessary.
Then, depending on the changes, you may or may not need to republish images or metadata.
January 7, 2013 at 3:12 pm
and if you overwrite the api/config.php file, be sure to edit it so that it matches the API key you entered in the Publisher set up in Lightroom. (or just don’t replace the config.php file)
January 7, 2013 at 9:25 pm
Thanks and sorry … I was expecting the upgrade info to be in the Setup section with the install info and didn’t see it further below.
Unfortunately, the phrase “replace the files publisher/api with the files under publisher/api on your server” can be read two opposite ways. To be clear, should I replace all of the old files in the api folder on my server with all of the new files in the api folder in the upgrade, with the exception that the config.php file which has my password? That is, should I be using the new lib subfolder in your upgrade? I assume so, but the phrasing does not make this perfectly clear.
January 7, 2013 at 10:14 pm
Everything in the /api/ folder. And be sure to change your password in the config file.
January 7, 2013 at 10:09 pm
replace the old files on the server with the new files from the update.
January 7, 2013 at 11:56 pm
Many thanks Matt and Rod.