Stop LightRoom 4 from overwriting Flickr photoset description field.

  • 4
  • Question
  • Updated 3 years ago
  • (Edited)
The Flickr plugin for LR4 is quite good, but there's one annoying oversight. The "edit" or "create new" photoset dialogues need a field for "description" that would map to the Flickr photoset description (LR already maps the set's title). Currently, when you modify a photo & have to republish (or add a new image to the set & publish), it overwrites any existing description on Flickr.

While we're at it, if I change the set's title, it should be smart enough to modify the title on Flickr, but publish to the existing set, rather than creating a new set w/ the new title.
Photo of seezee

seezee

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 6 years ago

  • 4
Photo of perception101

perception101

  • 4 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled LR5 Flickr Sync - replaces album description.

Lightroom 5 overwrites the Album description for Flickr Albums (formerly sets) using the built in Flickr sync and there's no way to enter the description in Lightroom itself. Am I missing something? Can this be changed?
Photo of John R. Ellis

John R. Ellis, Champion

  • 3587 Posts
  • 927 Reply Likes
You might consider using this third-party Flickr plugin:

http://regex.info/blog/lightroom-good...

The author's plugins have an excellent reputation, and he is very responsive to his users.
Photo of perception101

perception101

  • 4 Posts
  • 0 Reply Likes
John, the thing is, it's not missing functionality (in which case, I'd be happy to use a 3rd party plugin), it's purely broken behaviour. Lightroom shouldn't overwrite anything at the Flickr end, that you can't update yourself at the Lightroom end. Can't believe it's been an issue for 3 years, it's probably a small fix (stop sending an empty description field with the API call or whatever it's doing).
Photo of John R. Ellis

John R. Ellis, Champion

  • 3587 Posts
  • 927 Reply Likes
I fully agree that it would be better if the plugin didn't do that. However, based on a number of years of experience closely observing these forums, I think it's unlikely that the issue will be addressed. (I would be very glad to be proven wrong.) So if you need to get work done, you might consider the plugin, which historically has been very well maintained.