Comments on: Known Issues with my Plugins http://regex.info/blog Not a photo blog. A personal blog with photos. Tue, 07 Feb 2012 15:03:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Mike http://regex.info/blog/lightroom-goodies/issues#comment-45028 Mike Tue, 10 Jan 2012 05:47:53 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-45028 Hi Jeffrey, Lately I can't seem to use the Twitter feature on any of your plugins (export to facebook, flickr and zenfolio. I get the following error: Couldn't authenticate at Twitter Unexpected HTTP error reply #401 from Twitter I've tried revoking authorization on twitter to try re-authorizing, but I get the error before I'm asked to authorize. Any thoughts? (I am using the latest versions of all your plugins.) Thanks, Mike <span class='jfriedl'>Some people get this error, but I have not been able to figure out why. Everything seems right on my end, and it works for most people, but it could somehow be a bug in my stuff or at Twitter. I'll keep digging. —Jeffrey</span> Hi Jeffrey,

Lately I can’t seem to use the Twitter feature on any of your plugins (export to facebook, flickr and zenfolio. I get the following error:

Couldn’t authenticate at Twitter
Unexpected HTTP error reply #401 from Twitter

I’ve tried revoking authorization on twitter to try re-authorizing, but I get the error before I’m asked to authorize. Any thoughts? (I am using the latest versions of all your plugins.)

Thanks,

Mike

Some people get this error, but I have not been able to figure out why. Everything seems right on my end, and it works for most people, but it could somehow be a bug in my stuff or at Twitter. I’ll keep digging. —Jeffrey

]]> By: Jim http://regex.info/blog/lightroom-goodies/issues#comment-44949 Jim Sun, 01 Jan 2012 15:58:28 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-44949 Win7 x64, LR3.6 Metadada Wrangler 20111210.75 Tampa, Florida USA Exporting JPG from Nikon NEF raw file. No matter what I do I can not get MDR to replace the JPG Capture time with the Original file's capture Date/Time . The only date that I can get carried through the export is the "extra" section's "set the image file's modification date to to the image date." For legal requirements I need the original image's capture Date/Time carried over the the exported JPG file. (I still can't believe that Adobe didn't provide an option to do this.) Hoping someone here can tell me what I'm doing wrong. Or if this is even possible. Would be great if we had a forum to help each other. Happy New Year everyone! (especially Jeffrey for all of his unselfish hard work.) <span class='jfriedl'>You might try using <a href='http://www.sno.phy.queensu.ca/~phil/exiftool/' rel="nofollow">ExifTool</a> and my <a href='http://regex.info/blog/lightroom-goodies/run-any-command' rel="nofollow">run any command</a> export filter to copy metadata fields around as you like. —Jeffrey</span> Win7 x64,
LR3.6
Metadada Wrangler 20111210.75
Tampa, Florida USA

Exporting JPG from Nikon NEF raw file. No matter what I do I can not get MDR to replace the JPG Capture time with the Original file’s capture Date/Time . The only date that I can get carried through the export is the “extra” section’s “set the image file’s modification date to to the image date.” For legal requirements I need the original image’s capture Date/Time carried over the the exported JPG file. (I still can’t believe that Adobe didn’t provide an option to do this.)

Hoping someone here can tell me what I’m doing wrong. Or if this is even possible. Would be great if we had a forum to help each other.

Happy New Year everyone! (especially Jeffrey for all of his unselfish hard work.)

You might try using ExifTool and my run any command export filter to copy metadata fields around as you like. —Jeffrey

]]> By: sharad mathur http://regex.info/blog/lightroom-goodies/issues#comment-44485 sharad mathur Fri, 04 Nov 2011 14:55:23 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-44485 I just installed the current version of the FB plugin and authenticated, but albums in my "groups" don't show up (neither existing ones nor new ones). I tried both "secret" and "closed" groups with me as the admin, but no dice. Am I missing something? <span class='jfriedl'>The plugin can give you access only to what FB allows. For whatever reason, they don't include everything for everyone. No one knows why. —Jeffrey</span> I just installed the current version of the FB plugin and authenticated, but albums in my “groups” don’t show up (neither existing ones nor new ones). I tried both “secret” and “closed” groups with me as the admin, but no dice. Am I missing something?

The plugin can give you access only to what FB allows. For whatever reason, they don’t include everything for everyone. No one knows why. —Jeffrey

]]> By: Michael J. O'Connell http://regex.info/blog/lightroom-goodies/issues#comment-44105 Michael J. O'Connell Wed, 21 Sep 2011 15:45:13 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-44105 I would like to have Lightroom 3 show the entire file name in the Loup view (using one of the Info configurations). Currently it cuts it off and replaces the missing text with ellipses. I have used your font configuration tool (and others which I very much enjoy) but it doesn't change this font or the filename field size. Is there a way to do what I am attempting? Can you add this capability to the Lightroom configuration tool? Best regards, Michael http://www.michaeljoconnell.com <span class='jfriedl'>It's not possible as far as I know, sorry. —Jeffrey</span> I would like to have Lightroom 3 show the entire file name in the Loup view (using one of the Info configurations). Currently it cuts it off and replaces the missing text with ellipses. I have used your font configuration tool (and others which I very much enjoy) but it doesn’t change this font or the filename field size. Is there a way to do what I am attempting? Can you add this capability to the Lightroom configuration tool?

Best regards,

Michael
http://www.michaeljoconnell.com

It’s not possible as far as I know, sorry. —Jeffrey

]]> By: Meghan http://regex.info/blog/lightroom-goodies/issues#comment-44053 Meghan Tue, 13 Sep 2011 22:01:10 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-44053 Hey Jeff, I am a photographer in Charlotte, NC, US. I am trying to re-publish photos that have been edited in lightroom onto my Zenfolio site, and continue to recieve this error message: Unexpected HTTP reply from http://up.zenfolio.com/replace=333585342: 503 which will not allow me to publish the photos. Is there anything I can do to fix this? I have the latest version of the plug-in and have tried refreshing my galleries and nothing helps. Any advice would be GREATLY appreciated! Thank you so much!! ~ Meghan <span class='jfriedl'>Zenfolio seems to be having sporadic issues these days... I've just pushed a new version of the plugin that reports the error more clearly, but it'll be up to Zenfolio to solve the underlying issue with their servers, whatever it is. —Jeffrey</span> Hey Jeff,
I am a photographer in Charlotte, NC, US. I am trying to re-publish photos that have been edited in lightroom onto my Zenfolio site, and continue to recieve this error message: Unexpected HTTP reply from http://up.zenfolio.com/replace=333585342: 503 which will not allow me to publish the photos. Is there anything I can do to fix this?

I have the latest version of the plug-in and have tried refreshing my galleries and nothing helps. Any advice would be GREATLY appreciated! Thank you so much!! ~ Meghan

Zenfolio seems to be having sporadic issues these days… I’ve just pushed a new version of the plugin that reports the error more clearly, but it’ll be up to Zenfolio to solve the underlying issue with their servers, whatever it is. —Jeffrey

]]> By: Peter Beheydt http://regex.info/blog/lightroom-goodies/issues#comment-44052 Peter Beheydt Tue, 13 Sep 2011 20:37:43 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-44052 Hi Jeffrey, I have exactly the same problems like Sammuel had about 2 years ago: "Awesome plugin for Lightroom to Flickr exporting. I use it alot or at least I did until I started getting this error. It says “Invalid API Key” and I can’t export to Flickr anymore. Everything seems to be in order on Flickr as well as in Lightroom. I have not made any changes to my hardware or software nor any patching or anything like that. I’m using Lightroom 2 by the way. Any help would be greatly appreciated as I don’t know where to begin troubleshooting this issue." And this was your answer: "My plugin’s key is still valid, so perhaps Flickr was having temporary issues. Just tested it and it’s fine at the moment. If you get again, please send a log via the “Send to Jeffrey” button in the Plugin Manager. —Jeffrey" I have no idea where to begin to solve this: I'm using the latest plugin within lightroom 2, I have a pro-account on flickr and I'm using windows 7. I've renewed the app conection, I have removed the plugin, and reinstalled it. But I still receive the same errors. "Invalid signature", or "Invalid API key". Any new ideas since then, to solve this? Oh, I must not forget to tell you you make wonderful stuff. Many thanks! Peter <span class='jfriedl'>Next time you get the error, please send the plugin log (as described <a href='http://regex.info/blog/lightroom-goodies/faq#log' rel="nofollow">here</a>) and I'll take a look. —Jeffrey</span> Hi Jeffrey,
I have exactly the same problems like Sammuel had about 2 years ago:

“Awesome plugin for Lightroom to Flickr exporting. I use it alot or at least I did until I started getting this error. It says “Invalid API Key” and I can’t export to Flickr anymore. Everything seems to be in order on Flickr as well as in Lightroom. I have not made any changes to my hardware or software nor any patching or anything like that. I’m using Lightroom 2 by the way. Any help would be greatly appreciated as I don’t know where to begin troubleshooting this issue.”

And this was your answer: “My plugin’s key is still valid, so perhaps Flickr was having temporary issues. Just tested it and it’s fine at the moment. If you get again, please send a log via the “Send to Jeffrey” button in the Plugin Manager. —Jeffrey”

I have no idea where to begin to solve this: I’m using the latest plugin within lightroom 2, I have a pro-account on flickr and I’m using windows 7. I’ve renewed the app conection, I have removed the plugin, and reinstalled it. But I still receive the same errors. “Invalid signature”, or “Invalid API key”.

Any new ideas since then, to solve this?
Oh, I must not forget to tell you you make wonderful stuff. Many thanks!

Peter

Next time you get the error, please send the plugin log (as described here) and I’ll take a look. —Jeffrey

]]> By: JC Dill http://regex.info/blog/lightroom-goodies/issues#comment-44006 JC Dill Tue, 06 Sep 2011 20:56:45 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-44006 I'm trying to replace proof photos uploaded (to Smugmug, flickr, Picasa, ExposureManager, etc). with final edited versions. If the final edited version is edited solely in LR, no problem, LR tags the image as ready to replublish. But if the photo requires edits outside of LR (e.g. in Photoshop), the moment the .psd is created LR treats this as an entirely new "photo" and it shows up in the Publish Module as a "new photo to publish" instead of a previously published photo that has been edited and is ready to replublish. To my way of thinking, the root of the problem is that one can't stack images in Collections, and Publish uses Collections. If I could stack my images, I could put the PSD on top of the previously published RAW, and LR would mark it as an edited photo to republish, and all would be fine! I asked on the lightroomforums site if there was some way to stack the versions in the Publish Module, and they claim this is a problem with the publishing API, rather than a problem inside Lightroom. That doesn't make any sense to me. Can you help me understand where the problem lies, and what the best method is for fixing it? <div class='jfriedl'><p>Being able to stack images wouldn't magically solve this problem; the root of the problem is that you're creating a second, separate image. In this case, you know you want it to be considered the final version of the first image, but in someone else's workflow the exact same actions might result in a completely different image that indeed should be kept as a separate image.</p> <p>So, what's required is a way for you to tell Lightroom (or, at least, the plugin) that you want the second image to swap with the first. It's not impossible, but it's not something that Lightroom makes easy, nor that I've had a lot of requests for, so it's not bubbled to the top of the todo list. There's an ultra-kludgy way you can handle it, but it's really a pain: select the first image and remove it from the published collection (only in Lightroom; leave it on the remote site!), then visit the <b>File > Plugin Extras</b> dialog for the plugin and use the "clear" button to remove all remote data as far as Lightroom is concerned. Then select the second image and in the same plugin-extras link the online version to Lightroom via the "Manual Associate" button. Now, the second image is considered the master source for the remote version, and you can then visit the Publish Service to "populate" it back into the appropriate collection. Ugly and klugy, but that's the best I can suggest at the moment. —Jeffrey</p></div> I’m trying to replace proof photos uploaded (to Smugmug, flickr, Picasa, ExposureManager, etc). with final edited versions. If the final edited version is edited solely in LR, no problem, LR tags the image as ready to replublish. But if the photo requires edits outside of LR (e.g. in Photoshop), the moment the .psd is created LR treats this as an entirely new “photo” and it shows up in the Publish Module as a “new photo to publish” instead of a previously published photo that has been edited and is ready to replublish. To my way of thinking, the root of the problem is that one can’t stack images in Collections, and Publish uses Collections. If I could stack my images, I could put the PSD on top of the previously published RAW, and LR would mark it as an edited photo to republish, and all would be fine!

I asked on the lightroomforums site if there was some way to stack the versions in the Publish Module, and they claim this is a problem with the publishing API, rather than a problem inside Lightroom. That doesn’t make any sense to me. Can you help me understand where the problem lies, and what the best method is for fixing it?

Being able to stack images wouldn’t magically solve this problem; the root of the problem is that you’re creating a second, separate image. In this case, you know you want it to be considered the final version of the first image, but in someone else’s workflow the exact same actions might result in a completely different image that indeed should be kept as a separate image.

So, what’s required is a way for you to tell Lightroom (or, at least, the plugin) that you want the second image to swap with the first. It’s not impossible, but it’s not something that Lightroom makes easy, nor that I’ve had a lot of requests for, so it’s not bubbled to the top of the todo list. There’s an ultra-kludgy way you can handle it, but it’s really a pain: select the first image and remove it from the published collection (only in Lightroom; leave it on the remote site!), then visit the File > Plugin Extras dialog for the plugin and use the “clear” button to remove all remote data as far as Lightroom is concerned. Then select the second image and in the same plugin-extras link the online version to Lightroom via the “Manual Associate” button. Now, the second image is considered the master source for the remote version, and you can then visit the Publish Service to “populate” it back into the appropriate collection. Ugly and klugy, but that’s the best I can suggest at the moment. —Jeffrey

]]> By: Georgios http://regex.info/blog/lightroom-goodies/issues#comment-43967 Georgios Fri, 02 Sep 2011 21:03:18 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-43967 Hi Jeff, I'm a new user of your flickr plugin. Just came back from vacation and saw the message that the trial period has ended. I've liked the plugin and decide to register via paypal (the receipt is available if you need it). Well it's not working anymore. The only message I'm getting is the "can't access internet......". I can't register and I can't export any more photos either. I've deleted the plugin, update to the new version and reinstall nothing changed. You can check my flickr account if you want to see the photos I've uploaded with the plugin before vacations (1 month ago) Let me know if something like that is a know issue and if there is a solution. Thanks in advance for any help Regards Georgios Hi Jeff,
I’m a new user of your flickr plugin. Just came back from vacation and saw the message that the trial period has ended. I’ve liked the plugin and decide to register via paypal (the receipt is available if you need it). Well it’s not working anymore. The only message I’m getting is the “can’t access internet……”. I can’t register and I can’t export any more photos either. I’ve deleted the plugin, update to the new version and reinstall nothing changed. You can check my flickr account if you want to see the photos I’ve uploaded with the plugin before vacations (1 month ago)
Let me know if something like that is a know issue and if there is a solution. Thanks in advance for any help
Regards Georgios

]]> By: Clyde Lovett http://regex.info/blog/lightroom-goodies/issues#comment-43951 Clyde Lovett Thu, 01 Sep 2011 06:48:08 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-43951 Howdy - love your facebook plugin. Small issue, but important to me: this week facebook made changes to photo viewer and now larger view size is available. It would seem that images being uploaded via your plugin are not displaying in the larger size in spite of the fact that I have changed the setting to 1500 pixels. What is curious is that the photos download and open at 1500 (or whatever I have it set at) meaning of course that they are on the facebook server at that size, but they don't display at that size. I have tried different browsers and compared to uploading directly from the desktop. When I upload from the desktop - even to the same album - the photos DO display at the larger size so it seems something is going on via the plugin. As a comparison, If you go to my page, https://www.facebook.com/CrestoneCreations - the last 2 photos in the gallery demonstrate the issue. The first was uploaded via the plugin with 1500 px long edge setting. It displays "small." Then I downloaded that exact image (it shows it is 1500x1000 - so the plugin put it up on the server at the requested size) and then uploaded the recently download image BACK to the album independent of the plugin - where it sits side by side. As you can see it displays larger. I would love for the images I upload via the plugin to display large and take advantage of the new facebook size. Thanks very much for anything you can offer on this! Regards, Clyde Lovett <span class='jfriedl'>The plugin allows you to upload at Facebook's maximum storage size (2048 pixels on a side); what Facebook decides to show on the web site is up to Facebook, and from what you've written it sounds as if they're artificially limiting photos that were not uploaded with their tool (or, perhaps, they're specifically targeting me). With Facebook, you never know, and having to deal with Facebook is the price you pay for dealing with Facebook. —Jeffrey</span> Howdy – love your facebook plugin. Small issue, but important to me: this week facebook made changes to photo viewer and now larger view size is available. It would seem that images being uploaded via your plugin are not displaying in the larger size in spite of the fact that I have changed the setting to 1500 pixels. What is curious is that the photos download and open at 1500 (or whatever I have it set at) meaning of course that they are on the facebook server at that size, but they don’t display at that size. I have tried different browsers and compared to uploading directly from the desktop. When I upload from the desktop – even to the same album – the photos DO display at the larger size so it seems something is going on via the plugin. As a comparison, If you go to my page, https://www.facebook.com/CrestoneCreations – the last 2 photos in the gallery demonstrate the issue. The first was uploaded via the plugin with 1500 px long edge setting. It displays “small.” Then I downloaded that exact image (it shows it is 1500×1000 – so the plugin put it up on the server at the requested size) and then uploaded the recently download image BACK to the album independent of the plugin – where it sits side by side. As you can see it displays larger. I would love for the images I upload via the plugin to display large and take advantage of the new facebook size. Thanks very much for anything you can offer on this! Regards, Clyde Lovett

The plugin allows you to upload at Facebook’s maximum storage size (2048 pixels on a side); what Facebook decides to show on the web site is up to Facebook, and from what you’ve written it sounds as if they’re artificially limiting photos that were not uploaded with their tool (or, perhaps, they’re specifically targeting me). With Facebook, you never know, and having to deal with Facebook is the price you pay for dealing with Facebook. —Jeffrey

]]> By: Daved http://regex.info/blog/lightroom-goodies/issues#comment-43945 Daved Wed, 31 Aug 2011 15:41:30 +0000 http://regex.info/blog/lightroom-goodies/issues/#comment-43945 Hi Jeff, Thanks for the wonderful plugins you are making. Really makes life easier! I am trying jf Flickr plugin and for privacy reasons I would like to prevent the City (which is managed by LR) to show up as a keyword (and of course I would still like to use that field in LR). Any idea how I could achieve that? Even a limited number of tags I would want to remove would do it, I would only want to remove the city I live in. So the opposite of the "Extra tags to register with exported images..." would be ideal for me. Thanks, David <span class='jfriedl'>Flickr extracts the city from the Exif data and adds it as a tag, and they offer no options to control this, so the only thing I can suggest is to strip the city from the Exif on export. My <a href='http://regex.info/blog/lightroom-goodies/metadata-wrangler' rel="nofollow">Metadata Wrangler plugin</a> can do that. —Jeffrey</span> Hi Jeff,

Thanks for the wonderful plugins you are making. Really makes life easier!

I am trying jf Flickr plugin and for privacy reasons I would like to prevent the City (which is managed by LR) to show up as a keyword (and of course I would still like to use that field in LR).

Any idea how I could achieve that? Even a limited number of tags I would want to remove would do it, I would only want to remove the city I live in. So the opposite of the “Extra tags to register with exported images…” would be ideal for me.

Thanks,

David

Flickr extracts the city from the Exif data and adds it as a tag, and they offer no options to control this, so the only thing I can suggest is to strip the city from the Exif on export. My Metadata Wrangler plugin can do that. —Jeffrey

]]>