Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
25

P: with LR/Mogrify vs LR/Export to Flickr

Participant ,
Oct 12, 2023 Oct 12, 2023

Copy link to clipboard

Copied

 

I am a Jeffrey Friedl's “Export to Flickr” Plugin user since many years.
Yesterday morning Lightroom Classic passed to V13
I used LR/Mogrify 2 and LR/Export to Flickr for many years now.
With previous version of Lightroom Classic I used Mogifiy without problem with Export to flickr
This is an example uploaded Oct 7th 2023 https://flic.kr/p/2p7NDVm
This morning, after updating to LR V13 and Register Export to flickr the export of new pictures gave only the picture without its frame producef by Mogrify
This is an example of the frame free picture uploaded this morning : https://flic.kr/p/2p8vNW9
I also tested exporting with LR/Mogrify 2 alone in a picture file, it worked just normally
LR/Export to Flickr alone also worked normally but not the mix of two!
Bug Fixed
TOPICS
macOS , Windows

Views

8.4K
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 2 Pinned Replies

Adobe Employee , Oct 27, 2023 Oct 27, 2023

Matching to existing bug logged for investigation. 

Status Investigating

Votes

Translate
Adobe Employee , Dec 13, 2023 Dec 13, 2023

Greetings all,

 

Updates for the Adobe Photography Products have been released.  The December 2023 updates contain an update for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

 

Thank you for your patience.

Status Fixed

Votes

Translate
90 Comments
Community Beginner ,
Nov 14, 2023 Nov 14, 2023

Copy link to clipboard

Copied

Thank you for this. It's creating a lot of extra work at the moment, but I'm happy knowing it will be fixed eventually.

Votes

Translate

Report

Report
Explorer ,
Nov 20, 2023 Nov 20, 2023

Copy link to clipboard

Copied

I also have the same problem with the LR/Mogrify plugin using Lightroom V13.0.1

LR 13.1 Release, PS 25.2 Beta Release
iMac (Retina 5K, 27-inch, Late 2015), 4 GHz Intel Core i7, 64 GB 1867 MHz DDR3, AMD Radeon R9 M395X 4 GB

Votes

Translate

Report

Report
Community Beginner ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

Is it OK to say I upgraded to the latest version of LR Classic today and the problems remain. Exporting with Jeffrey Friedl's Metadata Wrangler still leaves colour labels, comments and keywords/tags, in spite of them being turned off

Votes

Translate

Report

Report
Adobe Employee ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

Votes

Translate

Report

Report
Explorer ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

I can report that upgrade 13.0.2 of LrC on a MacMini running OS Sonoma 14.1 does work with LR/Mogrify plug-in ver 5.1 to add a text annotation to an image export. (I added the filename as a watermark using the Ariel Unicode.ttf). It seems we're back in business with LR/Mogrify.

Votes

Translate

Report

Report
Explorer ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

Check the Publish issue again today with LRC13.0.2 on my mac. The issue remains.

Votes

Translate

Report

Report
Participant ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

I confirm that the original problem is still present with version 13.0.2

Regards

Mario

Votes

Translate

Report

Report
Engaged ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

Acccording to the release notes for 13.0.2 at https://helpx.adobe.com/lightroom-classic/kb/fixed-issues.html only one issue was fixed — and the problem with export/plugins isn't it...

 

(typically, dot-dot releases such as 13.0.1 and 13.0.2 only fix very specific, urgent issues with a broad impact)

Votes

Translate

Report

Report
Community Beginner ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

Unfortunately no.

LrC 13.0.2, M1Pro Ventura 13.6.2
Lr/Mogrify 5.10, add borders, same problems as with LrC 13.0.1.

There is also no bugfix that addresses the problem.
https://helpx.adobe.com/lightroom-classic/kb/fixed-issues.html

 

 

Votes

Translate

Report

Report
Community Beginner ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

LrC 13.0.2, M1Pro Ventura 13.6.2
Lr/Mogrify 5.10, add borders, same problems as with LrC 13.0.1.

There is also no bugfix that addresses the problem.
https://helpx.adobe.com/lightroom-classic/kb/fixed-issues.html

Votes

Translate

Report

Report
LEGEND ,
Nov 30, 2023 Nov 30, 2023

Copy link to clipboard

Copied

Votes

Translate

Report

Report
Community Beginner ,
Dec 01, 2023 Dec 01, 2023

Copy link to clipboard

Copied

I could cry I'm so happy - I think I just figured it out. 

JPEG MINI. 

 

So - I spent an hour on chat with Adobe. Shared my screen with the agent. We uninstalled, deleted, and re-installed everything. Updated Mac OS. Nothing worked. And then I was thinking about it - the file size tidbit in the error message. So on a whim, I turned off jpeg mini as an option on my shootproof uploader. And I just, for the first time in about a month, was able to successfully upload a full album. 

so go to the + sign next to "Publish Services" and click on "go to publishing manager". Select shootproof (or whatever your service is) and then if you're using jpeg mini, scroll down and just click the "x" in the top right corner.  (or just click remove)

 

I don't know why it's suddenly causing a problem, but this fixed it for me. Hope it's your issue, too!!

Votes

Translate

Report

Report
Engaged ,
Dec 01, 2023 Dec 01, 2023

Copy link to clipboard

Copied

@kittynoodlesoupI'm using JPEGmini and in LrC v13.0 it simply doesn't work — but it does not prevent Publish services from working. The files simply aren't optimized. In your screenshot, it looks like you're using a very old version of JPEGmini too. So it might be worth updating... once the issue in LrC v13.0 is fixed. 🙂

Votes

Translate

Report

Report
Community Beginner ,
Dec 01, 2023 Dec 01, 2023

Copy link to clipboard

Copied

I had to disable jpegmini for the publish plugin to work again.

Votes

Translate

Report

Report
Community Beginner ,
Dec 01, 2023 Dec 01, 2023

Copy link to clipboard

Copied

I have been having this exact same issue with Shootproof and turned off JPEGmini and it seems to have resolved! Yay! Now to tell JPEGmini because I need that to work, hahaha.

Votes

Translate

Report

Report
LEGEND ,
Dec 01, 2023 Dec 01, 2023

Copy link to clipboard

Copied

"Now to tell JPEGmini because I need that to work"

 

It's a bug in LR 13, not JPEGmini, which affects several plugins. See here for the response a few days agao of a previous report to JPEGmini:

https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-exports-twice-and-the-dock-pr...

Votes

Translate

Report

Report
Explorer ,
Dec 02, 2023 Dec 02, 2023

Copy link to clipboard

Copied

The problem still exists with the new version 13.0.2. Come on, Adobe, fix this problem a little bit faster - we need it for our everyday work!

Votes

Translate

Report

Report
Explorer ,
Dec 02, 2023 Dec 02, 2023

Copy link to clipboard

Copied

Hi, I'm the guy who makes the JPEGmini plugin. There is an issue under Lightroom 13 which prevents the images from being optimized in publish mode but it doesn't prevent the publish workflow from working. This looks like an issue with lightroom and not with JPEGmini.

However, there was a bug in prvious versions that caused errors in publish, you should probably update to the latest (simply re-download it from our site) and also tell Adobe that they should fix the issue that causing images not to be optimized in publish mode.

Votes

Translate

Report

Report
Community Beginner ,
Dec 03, 2023 Dec 03, 2023

Copy link to clipboard

Copied

Interesting! Well IDK, the only thing that worked was removing the plug-in from the publish settings. Once I did that, a whole gallery uploaded fine after only sending a few files at a time for over a month. So I’m not sure - maybe it’s not Jpeg mini specifically, but something else that happens during the process? (Not a programmer haha). I tried to download but my old activation code isn’t working. Sent in an email though - I’m sure we’ll get it figured out this week hopefully.

Sent from my iPhone

Votes

Translate

Report

Report
LEGEND ,
Dec 03, 2023 Dec 03, 2023

Copy link to clipboard

Copied

"maybe it’s not Jpeg mini specifically, but something else that happens during the process?"

 

As described elsewhere in this thread, it's a bug in LR itself, affecting several plugins that provide post-processing actions for Export.

Votes

Translate

Report

Report
New Here ,
Dec 03, 2023 Dec 03, 2023

Copy link to clipboard

Copied

I have a Lightroom plugin that enables exporting HEIC files through Lightroom. I'm using the postProcessRenderedPhotos API to hook into the export process and export the HEIC file. Unfortunately starting at Lightroom 13, the renditions provided are always the file format selected by the user instead of the override specified in the exportSettings.LR_format setting.

 

The problem can be reproduced using sample code from the "Lightroom Classic SDK Guide" from the 

"Defining post-processing of rendered photos" section on page 47. Simply create a Lightroom plugin using the code there, start an image export and set the file settings to JPEG. The plugin can copy the input file to a temporary location for further reference. After inspecting the copied file you will see that it is in the JPEG format instead of the requested TIFF.

 

See also my investigation on GitHub https://github.com/milch/LRExportHEIC/issues/6

Votes

Translate

Report

Report
LEGEND ,
Dec 04, 2023 Dec 04, 2023

Copy link to clipboard

Copied

Adobe has acknowledged this bug, which as you've observed, affects plugins defining post-processing actions:

https://community.adobe.com/t5/lightroom-classic-bugs/p-with-lr-mogrify-vs-lr-export-to-flickr/idi-p...

Votes

Translate

Report

Report
LEGEND ,
Dec 04, 2023 Dec 04, 2023

Copy link to clipboard

Copied

Votes

Translate

Report

Report
New Here ,
Dec 09, 2023 Dec 09, 2023

Copy link to clipboard

Copied

I'm trying to update my Flickr page with photographs from the quick collection. It worked last week, but now I get the error

 

Can’t update this collection

An internal error has occurred: A semi colon character was expected.

 

Lightroom classic Build 202311290958-8ff975ea release 13.0.2, Windows 10

 

Error message.jpgexpand image

Votes

Translate

Report

Report
LEGEND ,
Dec 09, 2023 Dec 09, 2023

Copy link to clipboard

Copied

@Graham34151883t4eo, your issue is different than the rest of this thread. Flickr staff have acknowledged that Flickr is currently sick and uploads from LR are broken:

https://www.flickr.com/help/forum/en-us/72157722302354338/

 

I recommend that you follow that thread for updates from Flickr staff.

 

Others here and in the Lightroom Queen forum have reported the issue as well:

https://community.adobe.com/t5/lightroom-classic-discussions/uploads-to-flickr-frequently-fail/m-p/1...

Votes

Translate

Report

Report