{"id":1538,"date":"2010-06-07T20:35:50","date_gmt":"2010-06-07T11:35:50","guid":{"rendered":"https:\/\/regex.info\/blog\/lightroom-goodies\/flickr\/publish"},"modified":"2010-06-16T23:27:20","modified_gmt":"2010-06-16T14:27:20","slug":"publish","status":"publish","type":"page","link":"https:\/\/regex.info\/blog\/lightroom-goodies\/flickr\/publish","title":{"rendered":"&#8220;Publish&#8221; in Jeffrey&#8217;s Export-to-Flickr Lightroom Plugin"},"content":{"rendered":"<p style='margin:0; padding:0; color:#666; font-size:90%'>This page documents plugin version     \n   \n  \n    20130612.310 as of June 12, 2013\n  \n<\/p>\n\n<img loading=\"lazy\" decoding=\"async\" width=\"720\" height=\"438\" class=\"ic\" src=\"\/i\/p\/lr_with_empty_list_of_publish_services.png\"\/>\n\n<p>This page describes the Publish aspect of <a href='\/blog\/lightroom-goodies\/flickr'>my export-to-Flickr plugin<\/a> for\nAdobe Lightroom.  The &#8220;normal export&#8221; portions of the plugin work in all\nversions of Lightroom from Lr 2 on, but its Publish features, described on this page, work only in Lr3.3 and later.\n\n\n<p style='color:#F66; font-size:110%'><span style='font-weight:bold; color:red'>Warning:<\/span> The idea behind\nPublish is simple enough, but if you hope to avoid unpleasant surprises,\nyou must understand important details before getting started with it.<\/p>\n\n<style type='text\/css'>\n .post_container { background-color: #2C2C2C; font-size: 105% }\n body   { color: #AAA }  \/* #C4B98F *\/\n body b { color: #CCC }  \/* #C4B98F *\/\n\n div.section { border-left: 10px solid black; padding: 10px 0 10px 10px; margin-bottom:20px }\n\n\n div.section:nth-child(3n)   { border-color: rgba(255,128,18,0.05) }\n div.section:nth-child(3n+1) { border-color: rgba(128,255,18,0.05) }\n div.section:nth-child(3n+2) { border-color: rgba(255,0,0,0.07) }\n div.section:nth-child(3n+3) { border-color: rgba(128,128,255,0.05) }\n\n .h  { font-size: 130%; font-weight: bold; color: white; margin-top: 0 }\n .h2 { font-size: 105%; font-weight: bold; margin-top:20px; color: white }\n .defn { color: #F88; font-weight: bold }\n .todo { color: red }\n .cmd  { margin-left: 3em }\n .float_sidebar_right {\n   float:right;\n   padding: 0;\n   margin: 0 0 30px 3em;\n   text-align:center;\n }\n .float_sidebar_right img { border:0; margin:0; padding:0 }\n .badimg { border: 5px solid red!important }\n\n  div.warning {\n        background-image: url(http:\/\/regex.info\/i\/p\/warning.png);\n        background-repeat: no-repeat;\n        background-position: 20px 20px;\n        background-color: black;\n        border: solid 1px white;\n        margin:60px 50px;\n        padding-left: 120px;\n        padding-top: 15px;\n        padding-right: 2em;\n        min-height: 95px;\n  }\n  div.warning p:first-child { margin-top:0px }\n\n<\/style>\n\n\n<div class='section' id='premise'><p class='h'><a class='permalink' href='#premise'>Basic Premise of Publish: <i>Ongoing Relationship<\/i><\/a>\n<\/p>\n\n<p>The premise is simple: drag a photo to a special collection in\nLightroom, and <i>voila<\/i>, it's sent to Flickr. From then on, changes that\nyou make to the photo in Lightroom are automatically kept up to date in the\ncopy at Flickr.<\/p>\n\n<p>Ah, but the devil is in the details...<\/p>\n\n\n\n\n\n   <p>First of all, Publish is an extra feature <b>in addition to<\/b> the\n   &#8220;normal&#8221; export offered by Lightroom via this plugin (and earlier\n   versions of this plugin all the way back to Lightroom 1). Publish allows\n   you to set up an ongoing relationship between specific images in your\n   Lightroom catalog and their appearance at Flickr. This kind of ongoing\n   relationship makes a lot of sense for some situations, while the normal\n   export we've had since Lr1 makes more sense in others.<\/p>\n\n   <p>Here's a hint: if it's a situation where you'd consider setting up an\n   export preset that you'd use via &#8220;<b>File &gt; Export with\n   Preset<\/b>&#8221;, Publish is worth a look.<\/p>\n\n\n\n<p>Because Publish involves setting up an ongoing relationship, it's more\ncomplicated than simply firing off an export. The length of this document,\nwhich covers only Publish and assumes you're already familiar with\nnormal export, attests to the extra complexity. But once the initial\nup-front fee has been paid with your time and attention, you'll reap the\nbenefits from then on.<\/p>\n\n<\/div>\n\n<div class='section' id='defn'><p class='h'><a class='permalink' href='#defn'>Introduction and Important Definitions<\/a><\/p>\n\n<p>Generally speaking, Publish functionality is provided by a <span class='defn nobr'>Publish\nService Provider<\/span>. Lightroom comes with a few publish service providers:\nthe built-in &#8220;Hard Drive&#8221; provider, a bare-bones Flickr plugin and a Behance plugin. You\ncan add additional publish service providers by <a\nhref='\/blog\/lightroom-goodies\/plugin-installation\/'>installing<\/a>\nappropriate plugins, such as\n\nthis fuller-featured Flickr plugin.\n\n\n(I have plenty of other publish plugins available on my <a\nhref='\/blog\/lightroom-goodies'>Lightroom Goodies<\/a> page,\nand there may well be other Publish plugins available on Adobe's <a\nhref='http:\/\/www.adobe.com\/go\/lightroom_exchange'>Lightroom Exchange<\/a>\nsite.)<\/p>\n\n<div class='float_sidebar_right'>\n<img loading=\"lazy\" decoding=\"async\" width=\"236\" height=\"204\" class=\"raw\" src=\"\/i\/p\/lr_publish_set_up-flickr.png\"\/>\n<br\/>\nAfter installing the Flickr plugin, you\n<br\/>can configure your publish service\n<\/div>\n\n<p>Before you can use Publish to send images to Flickr, you must first\nconfigure the particulars about how the exports are to be done, such as\ndeciding on the size and quality of the exported images, and the details\nabout which account at Flickr they should be sent to. This configuration,\nwhich you generally do only once, creates a <span class='defn nobr'>Publish Service<\/span> in your\nLightroom catalog.<\/p>\n\n<p>You can have multiple Flickr publish services (all provided by the one\nplugin), but it makes sense for most people to have only one. However, if\nyou have multiple accounts at Flickr that you'd like to send images to with\nPublish, you'll need to configure multiple Flickr publish services.<\/p>\n\n<p>Important details about creating a publish service are covered below,\nbut for the moment, let's wave our hand and say that the publish service\nhas now been set up as you like.<\/p>\n\n<p>After you've configured a publish service in your Lightroom catalog, it\nis represented in your Lightroom library as one or more <span class='defn nobr'>publish\ncollections<\/span>, each holding\n\n\n\n   a group of photos that are to be sent to Flickr. The standard publish\n   collection, &#8220;<i>Flickr photostream<\/i>&#8221;, holds photos to actually\n   be rendered and uploaded, while any other publish collection you might\n   configure represents Flickr albums and\/or group pools to add those\n   photostream images to.<\/p>\n\n\n\n   <div class=\"float_sidebar_right\">\n   <img loading=\"lazy\" decoding=\"async\" width=\"274\" height=\"240\" class=\"raw\" src=\"\/i\/p\/lr_publish_collections-flickr.png\"\/>\n   <br\/>\n   Several publish collections in a\n   <br\/>Flickr publish service\n   <\/div>\n\n\n   <p>For example, you might create a publish collection named &#8220;Vacation 2010&#8221;\n   that you configure to send photos to your &#8220;Vacation 2010&#8221; album,\n   but another collection named &#8220;B&amp;W&#8221; configured to send photos\n   both to your &#8220;My Best B&amp;W&#8221; album, and to Flickr's \n   <a href=\"http:\/\/www.flickr.com\/groups\/blackandwhite\/\">&#8220;Black and\n   White&#8221; group pool<\/a>: if you drag a new photo to the &#8220;B&amp;W&#8221;\n   publish collection then press the &#8220;Publish&#8221; button, it is uploaded\n   to your Flickr photostream, added to your &#8220;My Best B&amp;W&#8221;\n   album, and added to the group pool. (Just like on Flickr, all photos\n   added to any collection in the publish service automatically get added\n   to the <i>Flickr photostream<\/i> collection, and any photo deleted from\n   the <i>Flickr photostream<\/i> collection is removed from all other\n   collections in the same publish service.)<\/p>\n\n   <p>I sometimes refer to the publish-service's <i>Flickr photostream<\/i> collection\n   as the <span class='defn nobr'>local photostream<\/span>.<\/p>\n\n\n\n\n\n\n<p>Just like regular Lightroom\ncollections, a publish collection can be either a <span class='defn nobr'><i>regular<\/i> publish\ncollection<\/span> that holds whatever photos you manually add to it, or a\n<span class='defn nobr'><i>smart<\/i> publish collection<\/span> whose list of photos is computed by some\ncriteria that you set up (e.g. &#8220;all five-star photos taken this\nyear&#8221;).<\/p>\n\n\n<p id='states'>A <span class='defn nobr'>published photo<\/span> is a photo that's part of a publish collection.\nAt any particular time, a published photo is in one of four publish\nstates:<\/p>\n\n<ol>\n\n<li><p><b>New Photos to Publish<\/b> &mdash; photos that have been added to\nthe publish collection, but have not yet actually been sent to Flickr.\nThey'll be sent to Flickr the next time you launch Publish (via the\n&#8220;Publish&#8221; button).<\/p><\/li>\n\n<li><p><b>Published Photos<\/b> &mdash; photos that have been sent to Flickr and\nhave not been modified in your Lightroom catalog since.<\/p><\/li>\n\n<li><p><b>Modified Photos to Re-Publish<\/b> &mdash; photos that have been sent\nto Flickr, but which have been modified in Lightroom since. They will be\nre-sent to Flickr the next time you launch a Publish action.\n\n\n\n<\/p><\/li>\n\n<li><p><b>Deleted Photos to Remove<\/b> &mdash;\n\n\nNON_FACEBOOK {\n\n   photos that have ostensibly been removed from the publish collection,\n   but have not yet been removed from Flickr. (Whether to actually remove a\n   photo from Flickr when it is removed from your publish collection is\n   controlled by publish-service options, discussed below.)\n\n}\n\n\n<\/p><\/li>\n\n<\/ol>\n\n<div class='float_sidebar_right' style='margin-top:15px'>\n<img loading=\"lazy\" decoding=\"async\" width=\"463\" height=\"400\" class=\"raw\" src=\"\/i\/p\/lr_publish_segmented_grid-flickr.png\"\/>\n<br\/>\nSegmented grid showing photos in a publish\n<br\/>collection in various states of Publish\n<\/div>\n\n<p>When viewing a publish collection in Grid mode, you can see the photos\npartitioned into their various states in the <span class='defn nobr'>segmented grid<\/span> with\nheaders as listed above (and illustrated in the screenshot at right).<\/p>\n\n<p>You can add and remove photos from a normal publish collection as you\nlike (and they are automatically added and removed from smart publish\ncollections as per the criteria that you've set up), but nothing is\nactually done with them until you launch Publish, via the &#8220;Publish&#8221;\nbutton. The Publish button appears in the lower left of Lightroom, in place\nof the &#8220;Export&#8221; button, when viewing a publish collection, as in the\nscreenshot at right.<\/p>\n\n<p>There's also a &#8220;Publish&#8221; button in the upper right of the segmented grid.<\/p>\n\n<p>When you actually launch a Publish action, Lightroom fires up an export\nunder the hood, and photos are rendered as per the various settings\nconfigured when the publish service was created (the details of which\nfollow in the next section of this document). As each photo is uploaded to\nFlickr, it's moved to the &#8220;Published Photos&#8221; section. You can click on\neach segmented-grid section's header to expand and collapse it; if they're\nall collapsed you can watch their photo counts, shown at the right side of\neach segmented-grid header, update in real time.<\/p>\n\n<\/div>\n\n\n\n<div class='section' style='margin-top:50px' id='create'><p class='h'><a class='permalink' href='#create'>Creating a Flickr Publish Service<\/a><\/p>\n\n\n\n\n\n<p>Let's look in detail at configuring a publish service to export to your\nFlickr account. Make sure that the Flickr plugin is installed and enabled, then\nclick on the &#8220;Set Up...&#8221; of the Flickr header in Library's list of publish\nservices.\n(Take care to differentiate between Adobe's built in plugin and mine.)\n\n<\/p>\n\n<div style='margin:0' class='ic'><img loading=\"lazy\" decoding=\"async\" width=\"236\" height=\"204\" class=\"raw\" src=\"\/i\/p\/lr_publish_set_up-flickr.png\"\/><\/div>\n\n<p>This brings up the <span class='defn nobr'>Lightroom Publishing Manager<\/span>, a dialog that\nlooks like a cross between the normal export dialog and the Plugin\nManager...<\/p>\n\n<div class='wide ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"910\" height=\"454\" class=\"raw\" src=\"\/i\/p\/lr_publish_manager_overview-flickr.png\"\/><\/div>\n\n<p>Items show up in the list of Publish Services (highlighted in\nthe upper left) when their plugin is installed and enabled in the Plugin\nManager. Old Lr1 or Lr2 plugins won't provide this new feature, of course,\nbut most of my &#8220;export to...&#8221; plugins, including Flickr, do.<\/p>\n\n<p>If any of the plugins you have installed provide <span class='defn nobr'>export filters<\/span>,\nthey are listed in the middle-lower-left section of the Publishing Manager,\njust as they are in the normal export dialog. Lightroom does not come with\nany export filters built in, but they can add powerful features to your\nexports &mdash; both normal and publish &mdash; so it behooves you to know\nwhat's out there. Popular ones include my <a\nhref='\/blog\/lightroom-goodies\/metadata-wrangler\/'>Metadata\nWrangler<\/a> for controlling exactly what metadata is included in exported\ncopies, my <a\nhref='\/blog\/lightroom-goodies\/gps\/'>geoencoding\nsupport<\/a> shadow injecter for ensuring that the geoencoded location is\nproperly included, and Tim Armes' <a\nhref='http:\/\/www.photographers-toolbox.com\/products\/lrmogrify2.php'>LR\/Mogrify<\/a>\nplugin for advanced watermarking and image borders.<\/p>\n\n<p>The main panel of the Publishing Manager shows the export\/service\nsettings for the Publish Service that's about to be created (an\nexport-to-Flickr service in the example above). Like the normal export\ndialog, it has numerous sections; let's look at them in detail....<\/p>\n\n\n\n\n\n<p class='h2' id='service-naming'><a href='#service-naming' class='permalink'>Naming your Publish Service<\/a><\/p>\n\n<p>The first section allows you to give your export service a name, so you\ncan keep them straight if you have more than one.<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"79\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-1-name-flickr.png\"\/><\/div>\n\n<p>If you have only one Flickr account, you probably want to leave it at its\ndefault of &#8220;jf Flickr&#8221;. It looks ugly in this dialog, but when left at\nits default it won't even be shown in the list of publish service in\nLibrary, as seen in the screenshots above. If you set your own name, such\nas &#8220;My Flickr Stuff&#8221;, it shows up in the Library list as &#8220;jf Flickr:\nMy Flickr Stuff&#8221;. So if you need just one Flickr publish service, it's cleanest\nall around to just leave the name at its default. You can always change it later.<\/p>\n\n<p>However, if you have multiple accounts, you'll want to name them,\ne.g. &#8220;Flickr Work&#8221; for one and &#8220;Flickr Play&#8221; for another.<\/p>\n\n\n\n\n\n<p id='login' class='h2'><a class='permalink' href='#login'>Which Flickr Account?<\/a><\/p>\n\n\n<p>The next section is where you\n\n\n\n\n   authenticate to your Flickr account. (Before starting the authentication,\n   be sure that you are logged in to Flickr in your system-default web\n   browser, to the Flickr account that you want to use with this Publish\n   service.)\n\n\n\n\n\n<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"151\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-2-login-flickr.png\"\/><\/div>\n\n\n\n\n\n<p>Once the publish service has been created, <b>you can not change the\nassociated account<\/b> for the publish service, and this section becomes\ndeactivated during a publish-service edit. (You can make another publish\nservice for use with a different Flickr account, or even for use with the\nsame Flickr account but with different export options.)<\/p>\n\n\n\n<p id='loc' class='h2'><a class='permalink' href='#loc'>Export Location<\/a><\/p>\n\n\n<p>The next section is also available only at publish-service create time:\nsetting the export location:<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"589\" height=\"153\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-3-loc.png\"\/><\/div>\n\n<p>Most people leave the export-location setting at the default of\n&#8220;Temporary folder&#8221;, but you might set it to some specific named folder\nif you want to keep a local copy of all the images that have been published\nto Flickr. Again, Lightroom does not allow this setting to be changed once\nthe publish service has been created.<\/p>\n\n\n\n\n<p class='h2' id='standard-export-settings'><a href='#standard-export-settings' class='permalink'>Various Standard Lightroom Export Settings...<\/a><\/p>\n\n<p>The next sections are all the same as in the standard Lightroom export\ndialog...<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"589\" height=\"191\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-4-etc.png\"\/><\/div>\n\n\n\n   <p>These settings, such as the image size and quality, <i>can<\/i> be changed\n   later, but doing so means that you have to re-publish (re-render and\n   re-upload) everything you'd already sent to Flickr, at least if you want the\n   setting changes to be reflected in the images already at Flickr. More on this\n   later, but it's best to pick the settings you want up front, so you don't\n   have to change them later.<\/p>\n\n\n\n\n\n\n<p class='h2' id='filters'><a href='#filters' class='permalink'>Export Filters<\/a><\/p>\n\n<p>The next sections are for export filters you have installed and enabled,\nif any. Here's an example illustrating what some sections from <a\nhref='\/blog\/lightroom-goodies\/metadata-wrangler\/'>Metadata\nWrangler<\/a>, <a\nhref='\/blog\/lightroom-goodies\/run-any-command\/'>Run Any\nCommand<\/a>, and <a\nhref='http:\/\/www.photographers-toolbox.com\/products\/lrmogrify2.php'>LR\/Mogrify<\/a>\nmight look like...<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"589\" height=\"159\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-5-filters.png\"\/><\/div>\n\n<p>The blue rectangle marks Lightroom's controls for adjusting the order\nthat the filters are applied, and for removing them altogether.<\/p>\n\n<p>Each section can be opened to reveal the filter's particular settings,\nof course, but the filter details are not relevant to this overview about\nPublish, except to note that like the standard Lightroom settings (image\nsize, etc.), changing these filter settings after a publish service has\nbeen established\n\nmeans that you have to republish everything if you want the changes to be reflected in images previously published to Flickr.\n\n\n<\/p>\n\n\n      <p class='h2' id='delete-options'><a class='permalink' href='#delete-options'>Options for Deleting from Flickr<\/a><\/p>\n\n<p>Moving along to the next section, we have three photo-deletion options\nthat allow you to decide which kinds of local Lightroom deletions should\nresult in something actually getting deleted at Flickr.<\/p>\n\n<p>The option first concerns straight-up removal from the main &#8220;<i>Flickr\nphotostream<\/i>&#8221; publish collection. If you remove a photo from this\ncollection, it is automatically removed from all the collections in the\nservice, but should it actually be deleted from your account at Flickr? You\ndecide:<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"257\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-6-delete1-flickr.png\"\/><\/div>\n\n\n<p>If you delete a photo from Flickr, you can always upload it again, but\nall its &#8220;value add&#8221; at Flickr will have been lost forever &mdash;\n\n  notes, comments, inclusion in albums and group pools, etc.\n  \n\n&mdash; will be disassociated from the photo and lost. On the other hand,\nif you don't delete it at Flickr, it's still there, which is perhaps not what\nyou want if you're deleting it from your local photostream collection.<\/p>\n\n<div class='warning'>\n\n   <p>I <b>strongly<\/b> recommend that you leave this option at &#8220;Ask&#8221; until\n   you're <i>so<\/i> comfortable with the idea that photos at Flickr will be deleted\n   when you delete from your local photostream collection that you become annoyed at the\n   &#8220;Ask&#8221; dialog.<\/p>\n\n   <p>This automatic deletion is not something yet familiar in the Lightroom\n   world, and just a bit of forgetfulness about these new things can lead to a\n   very unpleasant sinking feeling.<\/p>\n\n<\/div>\n\n<p>Actually, to be clear, when a photo is removed from your local photostream collection, it goes\ninto the collection's &#8220;Deleted Photos to Remove&#8221; section, as <a\nhref='#states'>mentioned above<\/a>. It's only when you then initiate the\nPublish action on the collection that this option comes into effect, and\nthat photo copies at Flickr are deleted (if you've so instructed).<\/p>\n\n\n\n<p id='remove-from-sets'>Moving on to the second option, we have the\nless-drastic case of simply removing a photo from one of the other publish\ncollections in the service, which represent albums and group pools at\nFlickr. Should a removal here result in a removal from the associated\nalbums and\/or group pools at Flickr?<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"210\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-6-delete2-flickr.png\"\/><\/div>\n\n<p id='delete-from-Lightroom'>Finally, we have an option that covers the\nmost drastic case, of a photo that happens to be published via this service\nbeing deleted from Lightroom altogether.<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"173\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-6-delete3-flickr.png\"\/><\/div>\n\n<p>If you want to protect photos that have been published at Flickr, choose &#8220;Disallow&#8221;.<\/p>\n\n\n\n<div class='img_right' style='position:relative; top:-10px; margin:0 0 10px 1em; padding:0'><a\nhref='\/blog\/lightroom-goodies\/photosafe'><img class='raw'\nsrc='\/i\/lrp\/photosafe-big.png' height='100' width='86'\/><\/a><\/div>\n\n<p>For a more general way to protect images from deletion from the catalog,\nyou might also want to consider my <a\nhref='\/blog\/lightroom-goodies\/photosafe'>PhotoSafe\nplugin<\/a>, which allows you to specify specific photos that can't be\ndeleted from Lightroom, and\/or rules describing the kinds of photos that\ncan't be deleted (e.g. &#8220;all five-star photos&#8221;). You have to explicitly\nremove the restriction to remove a protected photo from the catalog, making\nit highly unlikely to do accidentally.<\/p>\n\n\n\n\n\n\n\n<p class='h2' id='metadata'><a class='permalink' href='#metadata'>Flickr Metadata Options<\/a><\/p>\n\n\n<p>Then we have some huge sections allowing you to configure various\nFlickr-related metadata options, just as in a &#8220;normal&#8221; Flickr export.<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"1618\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-7-options-flickr.png\"\/><\/div>\n\n\n\n\n\n\n\n\n<\/div><div class='section' style='margin-top:60px' id='populate'><p class='h'><a class='permalink' href='#populate'>Populating Your Local Album With Prior Uploads<\/a><\/p>\n\n\n\n\n\n<p>Finally, we have a section that deals with populating the &#8220;Flickr\nphotostream&#8221; publish-service collection that the plugin will make with\nphotos in you Lightroom catalog that are already at Flickr.<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"514\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-8-import-flickr.png\"\/><\/div>\n\n<p>This is a fairly complex section, so let start out with these points:<\/p>\n\n<ul>\n\n<li><p>If you want to use this publish service for only new uploads, and not\nre-uploading photos already at Flickr, you can ignore this section.<\/p><\/li>\n\n<li><p>If you don't want to deal with this section now and don't mind using\nthe publish service for only new uploads for a while, you can ignore this\nsection and come back to it later.<\/p><\/li>\n\n<\/ul>\n\n<p>This section deals with two very different &mdash; but directly related &mdash; issues:<\/p>\n\n<ol>\n\n<li><p>Getting Lightroom to understand which photos in your catalog are\nwhich photos at Flickr.<\/p><\/li>\n\n<li><p>Claiming those photos for the specific &#8220;Flickr\nphotostream&#8221; publish-service collection being created now.<\/p><\/li>\n\n<\/ol>\n\n<p>Let's look at them each in turn...<\/p>\n\n<p class='h2'>Step 1: Connecting Lightroom Photos to Copies at Flickr<\/p>\n\n<p>Step one is not specific to creating a publish service. Generally\nspeaking, if you do any uploads with this plugin &mdash; publish or\n&#8220;normal&#8221; export &mdash; you want the plugin to know whether the photo\nis new to Flickr, or should replace some copy already there. This first\nstep is about teaching Lightroom about the photos you've already uploaded\nto Flickr.<\/p>\n\n<p>This all assumes that there's at most one copy of a Lightroom photo at\nyour Flickr account; if multiple copies of the same Lightroom image exist\nat Flickr, tread <i>very<\/i> carefully. I have not tested this\nsituation.<\/p>\n\n<p>There are two ways to teach Lightroom photos about their counterparts at\nFlickr, but you might not even need to....<\/p>\n\n<p><b>Were they uploaded from this catalog with any version of this Flickr\nplugin<\/b>, any time going all the way back even to Lr1?<\/p>\n\n<p>If so, <i>voila<\/i>, Lightroom knows. You can confirm this by looking at\nthe &#8220;All Plugin Metadata&#8221; metadata-viewer preset, as illustrated by the\nyellow arrow at right, to see that the Uploaded-to-Flickr information is present,\nas highlighted with the blue box.<\/p>\n\n<p>Actually, there's one potential <i>gotcha<\/i> here, for those who use\nmore than one Flickr account: the data shown in the Uploaded-to-Flickr\nplugin-metadata area is that for the most recent upload to Flickr for\n<i>any<\/i> account, but all the image-reconnecting stuff talked about in\nthis section is handled on a per-account basis. So it's possible that data\nis shown there even if the photo was never uploaded to the current Flickr\naccount in question.<\/p>\n\n<p>If Lightroom doesn't already know about it, we have two options...<\/p>\n\n<ol><li><p><b>Were they uploaded from this catalog with Adobe's Flickr plugin?<\/b><\/p>\n\n<p>If you'd uploaded them with Adobe's simple built in Flickr plugin, we\ncan copy that data over. In the dialog screenshot above, the &#8220;<b>1)<\/b>&#8221;\nsection shows the situation when the Adobe Flickr plugin is not enabled, or\nis enabled but has no collections.... unfortunately, the plugin can't tell\nthe difference. If indeed this catalog has no Adobe Flickr collections,\nthere's nothing to do here, but if you'd simply disabled the plugin, you'll\nwant to dismiss enable it before continuing. (To avoid having to re-fill in\nthis entire dialog, go ahead and save it without doing anything in this\nsection, then after enabling Adobe's plugin, return back here via the\n&#8220;Edit Settings...&#8221; context-menu item.)<\/p>\n\n<p>If there are collections in the Adobe Flickr publish service that relate\nto this Flickr account, the dialog becomes:<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"181\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-8-import-flickr2.png\"\/><\/div>\n\n<p>Click on the &#8220;Import data from Adobe's Flickr plugin&#8221; to launch the\ndata copy; it should be fairly fast.<\/p>\n\n<p>Once you've imported data from Adobe's Flickr plugin, you probably want\nto disable it in the Plugin Manager so that two publish services aren't\ntrying to upload the same photos to the same Flickr account. Later, after\nyou're satisfied that you want to use this plugin for your Flickr\npublishing needs, you can go ahead and actually delete the Adobe Flickr\npublish service from your Lightroom library.<\/p>\n\n<\/li>\n\n<li><p><b>Try to match up photos via image time<\/b><\/p>\n\n<p>You can have the plugin scan all your photos at Lightroom and Flickr, looking\nat photo capture times and linking photos when it finds a one-to-one match.<\/p>\n\n<p>This method is not sure-fire, but can be quite successful for many\npeople. However, it fails for photos that were uploaded to Flickr without\nmetadata, and for groups of photos taken during the same second (such as a\ngroup of photos taken in burst mode, or one photo for which you've made\nvirtual copies in Lightroom or have multiple copies at Flickr).<\/p>\n\n<p>Pairing up the wrong photos could make for disaster, so the plugin is\nvery conservative about it. Click on &#8220;Launch Deep Scan&#8221; to give it a\ntry. It could take a while.<\/p><\/li>\n\n<\/ol>\n\n<p class='h2' id='claiming'><a class='permalink' href='#claiming'>Step 2: Claiming Lightroom Photos For This Publish Service's Photostream<\/a><\/p>\n\n\n<p>It's been a long haul, but we're getting close to the end.<\/p>\n\n<p>Now that Lightroom knows which photos in your catalog also live at\nFlickr, the next time you do an export of the image, it'll be an image\n<i>replacement<\/i> rather than a straight-up upload.<\/p>\n\n<p>If you'd like to pre-populate all those images into your publish-service\nphotostream (get them added in there with an already-published state, so\nthat they don't need an initial render\/upload to make Lightroom happy), you\ncan &#8220;claim&#8221; them to this publish service. This is not automatic\nbecause some users may want different export settings (image size,\nwatermarking, etc.) for different albums or groups or images, and that\nmeans creating multiple publish services with this plugin.<\/p>\n\n<p>But if you want to do all your Flickr publish uploading with the\nsettings defined for <i>this<\/i> publish service, enable the &#8220;claim&#8221;\noption...<\/p>\n\n   <div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"181\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-8-import-flickr3.png\"\/><\/div>\n\n<p>If you don't do this, you'll start out with an empty photostream publish\ncollection; photos will become part of it when you add them manually,\nthough like all manually-added images, they'll be marked as needing to be\nre-uploaded.<\/p>\n\n<p>I should point out that &#8220;claim&#8221; is not quite the right word,\nbecause a photo can certainly be part of multiple Flickr publish services.\nThis makes perfect sense if each publish service is for a different Flickr\naccount, but if you have more than one publish service trying to update the\nsame photo in the same Flickr account, confusion and conflict will ensue.<\/p>\n\n<p>Publish is all about <b>maintaining a relationship<\/b> between Lightroom\nand Flickr, and there should be only one relationship per image per Flickr\naccount.<\/p>\n\n\n\n<\/div><div class='section'><p class='h2'>Phew !<\/p>\n\n\n\n\n<p>Finally, you can press the &#8220;Save&#8221; button to create the publish\nservice and the default &#8220;<i>Flickr photostream<\/i>&#8221; collection.<\/p>\n\n   <div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"585\" height=\"159\" class=\"raw\" src=\"\/i\/p\/lr_publish_settings-9-save-flickr.png\"\/><\/div>\n\n<p>At this point you can drag photos to it and, upon invoking a Publish\naction (via the &#8220;Publish&#8221; button), photos are uploaded to your\nphotostream at Flickr as per all the various settings configured above.\nAlso, photo comments and ratings and pulled for each photo, appear in the\n&#8220;Comments&#8221; panel at the bottom of the right-hand-side set of\npanels.<\/p>\n\n<p>If, after publishing a photo to Flickr, you make develop changes to it\nin Lightroom, republishing it uploads an updated version.<\/p>\n\n<p>But the Flickr experience isn't complete without albums and group\npools...<\/p>\n\n\n<\/div><div class='section' id='sets-and-pools'><p class='h'><a class='permalink' href='#sets-and-pools'>Albums and Group Pools<\/a><\/p>\n\n\n\n\n\n<p>The default &#8220;<i>Flickr photostream<\/i>&#8221; publish collection is created\nautomatically and represents your photos at Flickr, but you can set up any\nnumber of extra publish collections to represet your albums and group\npools at Flickr. Any one publish collection can represent a single album\nor group pool, or any combination of any number of either.<\/p>\n\n<p>Casual Flickr users may want a one-to-one correspondence between their\nFlickr albums and the publish collections they set up, so, for example,\n10 albums at Flickr would mean creating 10 similarly-named publish\ncollections in this publish service. You don't necessarily need to have\nevery Flickr album represented in Lightroom... just the ones that you\nwant to create an ongoing relationship with your Lightroom catalog, so that updates &mdash; additions\nand subtractions of photos, and developmental changes to photos &mdash; are\nautomatically maintained. You'd still use a normal export for one-time\nuploads.<\/p>\n\n<p>You create a new Flickr publish collection via the service name's context menu...<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"751\" height=\"382\" class=\"raw\" src=\"\/i\/p\/lr_publish_flickr-collections-1.png\"\/><\/div>\n\n<p>... which brings up a dialog like this:<\/p>\n\n<div class='ic tight'><img loading=\"lazy\" decoding=\"async\" width=\"700\" height=\"523\" class=\"raw\" src=\"\/i\/p\/lr_publish-flickr-create-collection.png\"\/><\/div>\n\n<p>Of course, your own albums and permissioned group pools will be\nlisted. (If you've recently added albums or pools and they're not\nlisted, click on the &#8220;refresh data from Flickr&#8221; button, but until I\ncan push out a new version that works around some issues I've run in to,\nyou'll have to then dismiss the dialog and bring it up again to see the\nchanges.)<\/p>\n\n<p>Pick any combination of albums and group pools that you want this one\npublish collection to represent. Again, as I mentioned earlier, many users\nwill want a one-to-one mapping between albums and publish collections,\nso in that case:<\/p>\n<ol>\n<li><p>Check the box next to one album.<\/p><\/li>\n<li><p>Update the name at the top of the dialog to correspond to the album.<\/p><\/li>\n<li><p>Make sure the &#8220;include selected photos&#8221; option is turned off, unless you\nreally want to add the selected photos to the album.<\/p>\n\n   <div class=\"float_sidebar_right\">   <img loading=\"lazy\" decoding=\"async\" width=\"274\" height=\"240\" class=\"raw\" src=\"\/i\/p\/lr_publish_collections-flickr.png\"\/>\n   <br\/>\n   After I Created Four\n   <br\/>Extra Publish Collections\n   <\/div>\n\n<\/li>\n\n\n<li><p>Click the &#8220;Create&#8221; button.<\/p><\/li>\n<\/ol>\n\n\n<p>The new publish collection will now appear under the publish service's\n&#8220;Flicker photostream&#8221; collection, as with the four collections\nillustrated at right.<\/p>\n\n<p>Astute readers will realize a few shortcomings of this situation:<\/p>\n\n<ul><li>There's no way to automatically have one-to-one publish collections\nmade for all your albums and group pools... you have to do each. one.\nmanually.<\/li>\n\n<li>There's no way to create a new album from this dialog.<\/li>\n\n<li>The new publish collections aren't pre-populated with appropriate images from the local photostream.<\/li>\n\n<\/ul>\n\n<p>I just didn't have time to get these working before Lr3 was launched. I\nhope to remedy them soon.<\/p>\n\n\n\n\n\n\n<\/div><div class='section' id='smart'><p class='h'><a class='permalink' href='#smart'>Smart Flickr Publish Collections<\/a><\/p>\n\n\n<p>The previous sections describes creating <b>normal<\/b> Flickr publish\ncollections, but you can also create <b>smart<\/b> Flickr publish\ncollections, which incorporate Lightroom's <i>smart collections<\/i>\nfeatures that allow you to set up rules that describe what kinds of photos\nshould and shouldn't appear, such as &#8220;photos with a 5-star rating\nphotographed this year&#8221;.<\/p>\n\n<p>The thing about smart collections is that you can't manually add or\ndelete photos from them, so this makes for some interesting gymnastics in\nthis Flickr publish-collection world: you can't delete a photo from your\nlocal photostream if it's in a smart Flickr publish collection; you must\nhave it removed from the smart collection before you can delete it from the\nlocal photostream.<\/p>\n\n<div class='warning'>\n    <p id='cant-import-smart-collections'>\n\n       Do <span style='color:white'>not<\/span> attempt to create smart collections via the &#8220;Import Smart Collection Settings...&#8221;\n       item in the Publish Service context menu. A bug in Lightroom causes this to create a corrupt publish collection, and the plugin\n       infrastructure doesn't offer me a way to disable that menu item.\n\n   <\/p>\n\n<\/div>\n\n\n<\/div><div class='section' id='collection-sets'><p class='h'><a class='permalink' href='#collection-sets'>Publish Collection Sets<\/a><\/p>\n\n\n<p>You can create &#8220;publish collection sets&#8221; as you like, which are\njust like normal Lightroom collection sets: empty shelving on which to put your\nvarious publish collections. You can use collection sets to organize your publish\ncollections as you like.<\/p>\n\n\n<\/div><div class='section' id='photo_comments'><p class='h'><a href='#photo_comments' class='permalink'>Photo Comments<\/a><\/p>\n\n<p>Publish supports the ability to fetch comments and ratings from Flickr\n(where in this case a photo's rating is the count of people who have\nfavorited it).<\/p>\n\n<p>However, due to a bug in either Lightroom or my understanding of things,\ncomments are shown only when you're viewing a photo in the <i>Flickr\nphotostream<\/i> publish collection, and are not shown while viewing the\nphoto from whatever album\/group collections it might also be in.<\/p>\n\n<p>This can lead to the odd situation where you add a comment to a photo\nyourself (via the &#8220;click here to add a new comment&#8221; box in the\ncomments section of Library), but it doesn't show up if you're not in the\n<i>Flickr photostream<\/i> publish collection. If you were, it would show up\nright away. But if you're not and you don't realize what's going on, you\nmight try adding it again, and again, until you get frustrated enough to\nmove on. Who will be the first to admit that they added half a dozen copies\nof the same comment to a photo because they didn't know about this, or\nforgot? \ud83d\ude42<\/p>\n\n<p>Hopefully I or Adobe can figure this out before it comes to that.<\/p>\n\n\n  \n\n\n<\/div>\n\n\n\n\n\n\n<div id='edit' class='section'><p class='h'><a class='permalink' href='#edit'>Making Changes to an Existing Flickr Publish Service<\/a><\/p>\n\n\n\n<p>You can edit the publish-service settings via the &#8220;Edit\nSettings...&#8221; item in the publish-service name's context menu. You can\nchange all settings except the <a href='#login'>account at Flickr<\/a> and the\n<a href='#loc'>export location<\/a>, but there's a catch: if the change\nrelates to something about how each image is exported and uploaded (such as\nthe size or image quality, metadata settings, etc.) and you want those\nchanges to be reflected in photos already at Flickr, it won't happen\nmagically: you'll have to republish them all.<\/p>\n\n<p>Republishing can take a long time if you've got a lot of photos, and not\nall changes necessarily need to be reflected in every photo, so it is not\ndone automatically.<\/p>\n\n\n\n   <p>With most publish services in Lightroom, you can invoke the\n   &#8220;Mark To Republish&#8221; thumbnail context menu item, but that doesn't\n   actually work in the Flickr one due to (extremely complex) issues under\n   the hood. It'll indeed put them into the &#8220;Modified Photos to\n   Republish&#8221; section, but when you actually Publish them, they'll\n   immediately jump back to &#8220;Published Photos&#8221; without actually being\n   rendered and uploaded. There's a kludge that works to get around this\n   issue: <i>after<\/i> invoking &#8220;Mark To Republish&#8221; on them, make some\n   small change to them (such as clicking one of the exposure buttons in\n   Quick Develop, then clicking on the opposite button to effectively undo\n   the change without actually invoking Lightroom's undo). Then publish,\n   and they'll actually be rendered.<\/p>\n\n\n\n\n\n\n\n<\/div><div class='section' id='another'><p class='h'><a class='permalink' href='#another'>Adding Another Flickr Publish Service<\/a><\/p>\n\n\n\n\n\n<p>If you have another Flickr account you'd like to publish to, or you'd like\nto publish with different settings (e.g. your first Flickr publish service\nhad full size exports, but you'd like to be able to upload to some\ncollections with smaller sizes), choose<\/p>\n\n<div class='cmd'><b>Create Another Publish Service via &#8220;jf Flickr&#8221;...<\/b><\/div>\n\n<p>from the existing publish service's title context menu (where &#8220;Set\nUp...&#8221; had been before the first one was created.)<\/p>\n\n\n\n\n\n\n\n\n\n<\/div><div class='section' id='warnings'><p class='h'><a class='permalink' href='#warnings'>Issues to Watch Out For<\/a><\/p>\n\n\n<p>The following issues are inherent shortcomings in Lightroom's initial\nversion of Publish, and apply to all publish services:<\/p>\n\n<ul>\n\n<li><p>There's no way to tell which publish collections have photos\nawaiting action except by visiting each publish collection in turn and\nviewing the grid to see whether the &#8220;Publish&#8221; button is enabled or\ndisabled.<\/p><\/li>\n\n<li><p>There's no way to invoke publish on all your publish services in one\ngo; the best you can do is address each publish service in turn, selecting\nall its published collections and then invoking Publish on them.<\/p><\/li>\n\n<li><p>The photo-thumbnail &#8220;Go to Collection&#8221; context menu item does\nnot list any kind of smart collection that the photo may be part of,\nincluding smart publish collections.<\/p><\/li>\n\n<li><p>The use of <i>undo<\/i> with publish-related operations is likely to\nnot work and perhaps even corrupt the publish parts of your catalog. Take\ncare.<\/p><\/li>\n\n<li><p>You <a href='#cant-import-smart-collections'>can't import\nsmart-collection settings<\/a> to a publish smart collection; doing so\ncreates a corrupt smart collection.<\/p><\/li>\n\n<li><p>I have not tested export-to-catalog yet, but I would expect that Publish\ninformation does not go along with the images.<\/p><\/li>\n\n<\/ul>\n\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>This page describes the Publish aspect of my export-to-Flickr plugin for Adobe Lightroom. The \"normal export\" portions of the plugin work in all versions of Lightroom from Lr 2 on, but its Publish features, described on this page, work only in Lr3.3 and later. <p style='color:#F66; font-size:110%'>Warning: The idea behind Publish is simple enough, but if you hope to avoid unpleasant surprises, you must understand important details before getting started with it.<\/p> <p>Before you can use Publish to send images to Flickr, you must first configure the particulars about how the exports are to be done, such as deciding on [...]","protected":false},"author":1,"featured_media":0,"parent":886,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/1538"}],"collection":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/comments?post=1538"}],"version-history":[{"count":0,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/1538\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/pages\/886"}],"wp:attachment":[{"href":"https:\/\/regex.info\/blog\/wp-json\/wp\/v2\/media?parent=1538"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}