This bug, in a related way, has been noted by several users some time ago …

http://forums.adobe.com/thread/999503?tstart=30

and was reported as a bug a month ago during the release candidate period …

http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_1_rc 2_a_cr_or_lf_n_the_middle_of_a_caption_causes_failure_to_connect_to_fl ickr  

Although the above mentioned bug is raised specifically in relation to “Breaks” in the caption text I believe it may be symptomatic of either generically poor XML information encoding by LR when talking to Flickr or poor / incorrect use of Flickr Api’s which cannot cope with trivial complexity in the caption field.

– in either case it needs fixing with some priority in my opinion, but possibly the philosophy of the on-going Flickr plugin support needs fixing too.  

The LR Flickr publishing service has not been maintained very well in my opinion even when fixes may sometimes be trivial.     Perhaps Adobe would do well to employ or contract with JF for such plugins in future.    I use the excellent SmugMug plugin as the yardstick by which I measure the Flickr plugin.

A fix should also be treated as priority because the LR error message takes aim at the reliability of your internet connection which may cause some to erroneously try to chase down non-existent problems with a perfectly good infra-structure or OS / Firewall configuration – that is seriously bad advice for a caption related LR bug and has scope to seriously compound the problem for the user!  

Adobe, you have a responsibility to fix this before people mess with their reliable setups.

Sorry, I am not aware of any work rounds to your problem with this and suspect it may be a windows only problem (please confirm if not).   

Although not entirely exactly as per your problem (I believe it is generically the same) you may wish to add your vote to the above mentioned problem report or raise a new one.

Hi Rob,

Been some time since we exchanged words, and very glad to still see you are as independent and just “user to user” as ever!    Keep it up!

However, I don’t entirely agree with you!   

The difference in this case is that we are talking about a serious failure of LR out of the box functionality which is high on the LR marketing feature list.   I should not have to replace this with a third party product.  

As much as I respect JF’s plugins – although seriously, seriously, good work, many do not need this level of publish complexity or, however slight, the long the term risk - Adobe will not be run over by a bus.

If Adobe cannot support this kind of functionality then perhaps they should have a commercial arrangement with him – with a source code escrow of course!

But alas, we are straying off topic,  you will surely agree as it stands this is an LR bug which for some (social publishers) will seriously break their workflow and worse could cause, based on the error message,  a person less IT experienced to mess up their infra-structure chasing non-existent connection problems.

Hi Rob and all,

A simple carriage return kill flickr update process, "old" bug in LR4.x.

Maybe, evan.sante can try to put html in one line, just to test ...

Stéphane

I'd consider requesting markdown option too, if Adobe won't do it, JF might.

That way, structured/formatted captions look good when *not* presented as html (e.g. in Lightroom), and are readily converted to equivalent html for Flickr.

There is a markdown lua module that makes it a snap to incorporate.

http://daringfireball.net/projects/markdown/