Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TK2142]

Hi,

it'll be fantastic if some experienced plug-in developers could support me in fixing the Flickr Publish Service.

My problem:
1. LR sometimes flags published images as "Modified" for no good reason.
2. I don't have a Flickr pro account, so I cannot simply re-pbulish the images without losing all comments others made.
3. I have no way to explicitly mark the allegedly modified images as "unmodified".

I looked at the flickr.lrdevplugin in the SDK and was able to tweak it. I simply added a "rendition:recordPublishedPhotoId( flickrPhotoId )" call into a new else branch of the test "if not rendition.wasSkipped" in function "exportServiceProvider.processRenderedPhotos". So now "skipped" images are reset to a "Published" status again. That's just fine for me; I might add another choice in the dialogue later to leave the original "Skip" untoched and provide an "Mark as Published", but for me personally a pure "Skip" has no purpose.

My remaining problem is that the new behaviour doesn't help me with the images that are already managed by the original Flickr Publish Service.If I move them to my FlickPlus Publish Service they receive new photoIDs so I cannot influence their "Modified" status.

Is there any way I could access the images within the "Modfified" collection of the standard Flickr Publish Service so that I can reset their status to "Published"?

Is there any way I could extent the context menu of an image that is in a Publish Service collection? I noticed I can change the text of the "Go to Published Photo" context-menu item, but so far I haven't seen a way to add another item to that context menu. The latter would be ideal, as it would give me a way to reset the status of an image to "Published" again.

I'd be thrilled if someone experienced could tell me what my options are. I don't need a spelled out solution, just hints as to what is possible. Pointers to API functionality would be great, but the documentation seems really good so I'm confident I can work my way around.

N.B. I thought about replacing the standard Flickr Publish Service in the LR installation directory with my version but have no hope that this will work since the two versions use different API keys to talk to Flickr. I guess if I could use the standard Flickr Publish Service's API key in my one, I'd be good since then I'd be getting the correct photoIds.

P.S.: I think even LR were free of the problem that images sometimes receive a "Modified" status in error, it would be useful for the user to tell the Publish Service that it should consider an image to be "up to date".

[clee01l]

I think the problem is a bug in LR not just in the Flickr Publishing service, It also shows up in Jeffrey Freidl's Flckr Pluging AND the Adobe supplied Publishing service for Hard Drive. I also have "Modified Photos to Republish"  queues in those Publish services and nothing I can do will make them go away.
 
Jeffrey Freidl is aware of the issue.  Perhaps he can find a work around with his plugin.

[TK2142]

I think the problem is a bug in LR...

Yes, it is  but we cannot do anything about this. The only thing we can do is to extend the Flickr plug-in or write another plug-in that extends the general publish service functionality (-> context menu).

Jeffrey Freidl is aware of the issue.  Perhaps he can find a work around with his plugin.

Note that I found a work around with my plug-in version but that this doesn't help me with the incorrectly flagged images in the standard Flickr publish service. I doubt that Jeffrey Freidl is looking into solving this issue, but of course I'd love to be proven wrong.