Lightroom 4.1: Publishing Service Flickr plugin; Using HTML in Caption field

All,
After hours of troubleshooting I have narrowed down a problem with an error message I’m getting when I try to export from Lightroom 4.1 using the Flickr Publishing service. The error msg is:
Can't update this collection
Could not contact the Flickr web service. Please check your Internet connection
I have narrowed down the problem to my attempt to add basic HTML tags to the Caption (Description) Field of the Meta Data. This has worked perfectly well in all versions of Lightroom 3.6 and below (I didn’t try this type of export using Lightroom 4.0). I have also noticed that a simple page break, such as below, will also throw the same error:
“Lorem ipsum @evansante.com dolor sit amet, consectetuer
adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat veniam, quis nostrud exerci t”
Flickr will recognize URL in simple text and format them properly so:
“Lorem ipsum http://www.myurl.com dolor sit amet, consectetuer “
Will work.
Does anyone know of a work around that will allow including page breaks or HTML??? Thanks in advance - CES

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_rc2_a_cr_or_lf_n_the_m iddle_of_a_caption_causes_failure_to_connect_to_flickr
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.

Similar Messages

Setting up Lightroom 4.3 Publishing Services

I am having a problem setting up Lightroom 4.3 Publishing Services. Each time I click “OK I’ll Authorise button in Flickr it goes to a blank screen with no completion of the process. After many attempts over the last couple of days, this morning I was able to get error message from flickr that says “Oops! Flickr doesn't recognise the "oauth_token" this application is trying to use.” And goes on to say “You don't really need to know what this means, except that you can't use the application until this problem is fixed. (It's a third-party problem, not a Flickr problem).
Will someone in Adobe please advise what I do to correct this problem? I have reached an extreme level of frustration over this, please help.
Thanks in advance.

Hi have solved the problem by uninstalling and reinstalling. I think the problem was because I upgraded from version 3.x to 4.1

Unable to upload photos to flickr using Lightroom 4.4 publish service feature

I post process my images through LR and for several years published images to Flickr via Publish Services feature in LR. The current version is LR4.4. In the past two weeks I have been unable to publish new images on Flickr or update previously published images. Instead, I received the following explanation:
Can’t update this collection [ie., the Flickr collection in Publish Services]:
An internal error has occurred: Error Domain=NSXMLParserErrorDomain Code=4 "Line 1: Document is empty
" UserInfo=0x600010866bc0 {NSLocalizedDescription=Line 1: Document is empty
A blog search shows that this problem has been reported for several years, but I have found no instruction from Adobe or Yahoo that provides a fix. Thanks. David Hawkins. [email protected]

I have a friend who also can't get Lighroom's Publish Service to work with flickr. I don't use flickr but would suggest you try Jeffrey Friedl's Export to Flickr Lightroom plugin. I have used his plugins successfully to publish to other photo sites.

Lightroom 5.2 Publish Services

I have Flickr and 500px set up in Publish Services of Lightroom 5.2. I can send photos to both sites OK. The "problem" is once I move from the "Flickr" highlighted bar to 500px both Bars are illuminated. The Flickr bar does not seem to release focus and I can no longer return to the Flickr Grid view. However, if I then double click the Flickr Bar and enter "Edit photoset" then add, say, a "space" to the Photoset name, press edit then the focus is released and the "Grid View" will return when I next click on the Flickr Bar. Is there a fix for this please

Thanks for the reply. Sadly the Link re preferences shows as invalid.
My system is:
ASUSTeK Computer INC. P7P55D-E PRO
16.0GB Dual-Channel DDR3 @ 782MHz (9-9-9-24)
Intel Core i5 750 @ 2.67GHz Lynnfield 45nm Technology
Microsoft Windows 7 Professional 64-bit SP1
1024MB ATI Radeon HD 5800 Series (ATI)

Can't set up Lightroom Publish Services, internal error occurs

I'm trying to use LR 3's publish service for SmugMug. I'm a little scared since
I have a large number of photos to sync up.
When I click on "setup" on the SmugMug export services, I get a popup
error with this message:
"An internal error has occurred: ?:0: attempt to index field 'exportSettings' (a
nil value)"
Any idea how to fix this?
The same message appears for any of the publish services (Flickr, Facebook).
If I go the Publish manager, I can authorize the SmugMug account. It then says it syncs the hierarchy, but afterwards nothing seems to have happened and the account is not longer authorized.
Thanks.

Thanks Mark, but that's not it.
I'm not using Jeff's plugin, but the new built-in one for LR 3.2 and LR3.3. I did try to install Jeff's plugin just before LR3.2 came out. I uninstalled Jeff's version (or at least tried to - it doesn't appear anymore) before I ever used it.
I'm not even to the point of exporting to SmugMug, I just click 'setup' and get the error.

Seems like SmugMug publish service clobbers my connection

When I am uploading via a SmugMug publish service it only uses 80KB/s of my 500KB/s upload bandwidth, yet other computers on the network(DSL Router) fail to load webpages, sometimes even fail to find web servers(I assume DNS lookups are failing in this case).
Has anyone else noticed this behavior? Is there anything that can be done? I don't see any QoS type settings on the router, priority settings, etc. I have installed some bandwidth throttling software and the network frees up when I set it below what LR is trying to use, e.g. a setting of 60KB/s is enough to free up the other computers and allow them to surf fine.
I'm all for efficient uploads but if LR isn't allowing other devices to share the network while uploading that would seem to be a defect.

If your net is that sensitive to an app then you have some other problem. TCP/IP implementions are tuned to ensure that network applications are "good neighbours" to each other. You shouldn't need QoS tweaks for this sort of traffic. It is more likely your provider is doing traffic-shaping of some kind.
Without basic network diagnostic details it is impossble to say what is going on, but it is important to note that all that Lightroom is doing is making API calls, letting the lower levels of the TCP/IP connection manage throughput and connection management, which includes managing traffic for multiple applications and consumers. This is pretty much how everything works, and always has.
You should break the problem down into smaller pieces. How is your router sharing this single connection? Is the private side actually a router, or is it a switch? Is the switch working correctly? What sorts of connection affects are we seeing? Is the problem at the TCP or application level, or the IP level. If you suspect name resolution, why are exsiting caches also suffering? Or can you prove it is always new or expired lookups? What is the nature of the connection(s) created by Lightroom (netstat and tcpdump are your friends in this regard.)
In reference to this last question, it may be that Lr is doing multi-threaded concurrent uploads, and the number of open connections is triggering some sort of traffic shaping heuristic. I don't know the details of the SmugMug API, but it is possible. Flickr, et al, pretty much handle uploads and replaces as a series of multipart POSTs. If SmugMug is doing something similar, then there is no way the app is at fault here. It is sending the POST parts as fast as it can through the standard OS TCP libraries, which will stop when the TCP messages it gets tell it to wait for bit and back off. The app spends most of this time waiting.
Networks are subtle and complicated beasts, and the majority of consumer all-in-one routers out there, quite frankly, suck. But the take-away here is that the application is only one small part of the equation. TCP/IP is designed from the ground up to be resilient to hungry apps, which will accept throttling as normal operation. If that connection is not being throttled, then we need to look lower down in the network stack.

Publish Services

Did the export feature in Lightroom 5 replace publishing services?

eadamquinn wrote:
So my question is how to populate those publish services? I used to just
drag photos to it. Now that is not working.
Consider posting a screen shot - circle the drop target...
But to clarify: you should be able to drag photos to publish service collections, unless they're smart collections.
For example, I can drop photos here and then publish them:

Using Lightroom publish service for either Flickr or SmugMug. I have many images with a keyword Madd

Using Lightroom publish service for either Flickr or SmugMug. I have many images with a keyword Maddy. This frequently doesn't show up in SmugMug or Flickr. All my other keywords seem to work fine. Anybody experience anything like this?

You only get one opportunity to set up the hard drive under publish and the folder cannot be changed unless you get a plug-in to provide a work around.
However you could just create a generic publish folder - something like Photo Lab, or Print Job.
But you could then right click on your publish folder and select “make target collection” - you will see the plus sign added.
Simply highlight the photos you want to print and press B (the same as adding to a quick collection) and your Publish Services folder on your hard drive will be populated with the exports.
The real problem is that you would need to edit the publish settings every time you required different dimensions etc (not sure possible). I use a similar system, which works well and I like how I can see what has already been published and what is still to be published but my prints are always the same size and resolution.

Lightroom 4 Publish Services will not connect to Flickr.

I have been trying to set up Flickr in Lightroom 4 Publish Services but get an error message when I press "OK, I'll Authorise it" on the Flickr authorisation page. The message is "The address wasn't understood. Firefox dosen't know how to open this address". Can anyone help?

Unfortunately, there isn't anything we can really do on our side, as the problem here is that the expected behavior is not occuring and the failure is outside of Lightroom itelf.
Here is what is supposed to happen:
1. Lightroom sends a request to your web browser to open an authentication page that is already built in to the host web site.
2. You authenticate, which gives permission for your account information to be sent back to Lightroom. This substitutes the need to enter a user name and password. It's a hall pass for Lightroom to send your files to your online account.
3. With authentication complete, the web page sends a token (similar to a cookie) back to Lightroom, which is then used whenever Lightroom needs to access the web servers to upload a file.
The problem occurs in step three. The token is not being sent to Lightroom. Instead, the web browser is keeping it for some reason and attempting to open it. This shouldn't happen, but Lightroom doesn't have any control over your browser. Some suggestions are to clear your temporary internet files and cookies to see if corruption there is changing the behavior. Also, the Facebook app for Lightroom may have some issues, try deleting this from your Facebook account (within your account settings on the website).

How to migrate publish service from Lightroom 4 to Lightroom 5?

I have been upgrading from LR4 to LR5. Then I imported the LR4 catalog. But no Publish service was following to LR5.
I have used the FLICKR plugin a lot - made more than 80 FLICKR-sets. Therefore I would be terribly sorry if I do not succeed in restoring the contact to the old service files. Does anybody know how to migrate publish services from Lightroom 4 to Lightroom 5? Very fine if it's going to be a kind of a workaround.
Best regards
Jimmy

You'll need to backtrack a little, open your LR4 catalogue in LR5 and allow it to upgrade the catalogue with publish services.
If you've done work on images in the "wrong move" catalogue, identify those images, select them, and do a File > Export as Catalog. in the "right move" catalogue, bring this work in by File > Import from Another Catalog.
Alternatively, it may be worth looking at Jeffrey Friedl's Flickr plugin as he may have looked at this problem. Maybe someone here will know if it would help.
John

Flickr publishing service and privacy settings

Hi,
I recently purchased Lightroom 3, and am loving it. I've played around with the Flickr publishing service, and it seems that at the moment there is a limitation in that it is not possible to specify permissions for individual photos, but rather, an overall choice for the publishing service. I usually upload an album with restrictive permissions then make some of the photos public, so I was wondering whether if I upload an album via Lightroom 3 with permissions set to 'Private', and I change the permissions on the flickr website to 'Public', then if in future I re-upload the image after modifying it, will the permissions be reset to 'Private', or will Lightroom respect any privacy settings set directly on Flickr?
Thanks for any advice,
Thomas

I don't know the answer to your specific scenario - my simple advice is "try it".
But I do have an alternate idea if you try it and find that it doesn't work as you expect.
I have 2 publish services both based on the Flickr plugin. (You can add additional ones by right-clicking on the existing Flickr publish service, and choosing [Add Another Publish Service via "Flickr"]
One's set up to upload as public, the other is set to upload as private. Under these 2 publish services I have my various photosets (public & private).
You can also use this method to support multiple Flickr accounts (family vs. business, etc)
- Robert

Flickr Publish Service Error

I have used the service to upload many pictures to my account, however on my latest upload (5 photos, one of them was a virtual copy, could this be the cause of the problem perhaps?), it ended with the following dialog box:
"Can't update this collection.
An internal error has occurred: assertation failed!"
All the pictures uploaded though. I tried to upload another one to see what would happen. It did upload as well, but it also ended with the same error coming up. It's quite annoying, can someone help me please?

I worked with Gokul from Adobe support, and we eventually stumbled into the solution.
The system clock was wrong!
Based on something Friedl says on the blog for his Flickr plugin, the Flickr authentication APIs will fail if the system clock is wrong. His plugin helpfully points out that the clock is wrong when you install it. It also reports the error that he gets from the Flickr APIs: HTTP 401 (not authorized). Unfortunately, Lightroom's builtin Flickr publishing plugin doesn't report any error, and it just fails silently.
In my case, Windows appeared to be displaying the correct time, but the time zone was incorrect, and my system time was actually 3 hours ahead. I reset the clock and timezone and restarted Lightroom. Now, the builtin Flickr publish plugin is working again.

Unable to set up Flickr Publish Services in LR4.1

I have tried on numerous occasions and end with the same result. After I finish setting up the parameters in the Flickr Publish Services form I receive the "Lightroom needs your permission to upload images to Flickr" I click on the "Authorize" button and then I'm taken to my account within Flickr. Once i click on the "OK, I'll authorize it" button, I'm taken to: http://lightroom://com.adobe.lightroom.export.flickr/#?oauth_token=72157630835444112-9ff8c 3faeafcb667&oauth_verifier=84249d3a8099d4dd, where I get another pop up window that says "This web page cannot be displayed"
No matter what I do I cannot get the publish service to work. I had no issues with Lightroom 3.6 using the same procedure. What has changed, or what am I missing? Please help. Thanks in advance.

Hi
You will need to have different configuration in each service.bat file as the SVCNAME must be unique across multiple instances, for example:
JBoss Server 1 service.bat config:
set SVCNAME=CCP_RC
set SVCDISP=CCP - RequestCenter
set SVCDESC=JBoss instance for RequestCenter
JBoss Server 2 service.bat config:
set SVCNAME=CCP_SL
set SVCDISP=CCP - ServiceLink
set SVCDESC=JBoss instance for ServiceLink

Lightroom 3 publish service: Sending 3 files from one photo

Hi,
I have created a lightroom 3 publish service that will export each photo as a huge TIFF file over a slow broadband connection to an external server. The external server creates 3 compressed JPEG files from the TIFF file.
I think this is too slow and that it would be much better if the lightroom publish service created those three files and then sent them over the internet. Please note I am using Mac OS X 10.8.5 and Lightroom 3.
My question is, what would be the best way to accomplish this task? Can lightroom compress the photo 3 times, or is it best to create another script on the local machine to accept each file, compress them, and then send them via the internet? What is the most secure and easy way to do this?

Well, I don't see any reason to use an external script, since your Lightroom plugin can do this without it. Since you are controlling the code of the publish service, I recommend just doing this 3 times:
local session = LrExportSession {
photosToExport = { ... },
exportSettings = { ... }.
session:doExportOnCurrentTask() -- or new task.
-- upload via FTP...
PS - SDK forum would be better place to ask this question.
Cheers,
Rob

Lightroom 5 publish services - order of published images

I have created several collections in which I have manually sorted the photos in a certain order. I am going to use them in a book (will be sending them to SmartBooks) and I don't want to reorder them once they are published to my hard drive. I have tried to publish them to my hard drive using publish services, but I can not find a way to rename the files so that they come out in the order I have selected in the collection. They appear by capture date or current filename with a jpg extension. Does anyone know of a way to do this?

Worth noting: the order of files outside Lightroom depends on how the device orders things (and no longer depends on Lightroom, once they've been pushed from the nest..).
That said, alphabetic ordering is the most common denominator - most devices are capable of displaying in alphabetic ordering.
Many devices will also display by date (usually capture date, but sometimes file-creation date..).
If you are publishing repeatedly the same photos, it get's very tricky indeed, since Lr will not re-order already exported files or take them into consideration. If you are re-exporting the whole lot, then it's much simpler.
Anyway, Lr5user-pt's method gives total control, but also has some drawbacks - you have to redo the copy names if/when you reorder photos (and then, re-export/publish all photos whose copy-names have changed).
TreeSyncPublisher will map in-Lr ordering to capture dates (in exported file metadata) or file-creation dates (by "touching" exported file dates on disk), so if devices support such ordering (by date), then published photos will remain ordered upon republishing, automatically. Granted, you have to be conscious of some stuff, and read the documentation, and learn to follow the rules..
(PS - a new version is coming out soon, which will have less "gotchas").
Exporder is like TreeSyncPublisher except it renames exported files to match in-Lr order - even trickier to use though, but works dandy if you're willing to learn where are the hoops to jump through..
The above mentioned plugins are free, and I wrote them - they only make sense if you will be re-ordering, or re-publishing changed photos.
If you are just exporting or publishing one-time/all-at-once, then the simplest method is just to prefix an ordering number to the export filenames:
Rob

Lightroom 4.1: Publishing Service Flickr plugin; Using HTML in Caption field

Similar Messages

Maybe you are looking for