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

[Mario_tr]

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!

[22ART11]

I too can confirm that the problem with the plugins, particularly LR/Mogrify and Metadata Wrangler, persist in Lightroom Classic v. 13.0.2, on a Windows 10 machine.

[Sarah Takes Pics]

YESSSSS!!! Shut off Jpeg Mini and now uploading to pixieset properly! THANK YOUUUUUU

[jean-louis 99425839]

When publishing to Flickr, I get the error message "Unable to update this collection An internal error occurred: A semicolon character was expected." This issue is recent and largely reported in the Flickr forum, but the problem might come from LR.

When I remove and then allow the Flickr connection again, the next photo publication is correct. But the problem appears again for the next publication.

On the other hand, I'm using the Flickr API and for the past few days there have been numerous connection errors and a new request refusal response that I've never seen before when the signature is valid: "oauth_problem=signature_invalid ..." . If I execute the same request immediately afterwards, it works normally. According to my (about 50) tests, the request seems always accepted after a failure.

If this new error is not handled in the Flickr plugin, it may lead to unexpected behavior. There could be a link between the two errors above and it would be interesting to check whether this case is handled in the Flickr plugin, perhaps this is the source of the problem?

______________________________________________

Version Lightroom Classic: 13.0.2 [ 202311290958-8ff975ea ]
Licence: Creative Cloud
Paramètre de langue: fr
Système d'exploitation : Windows 11 - Business Edition
Version : 11.0.22621
Architecture de l'application : x64 Architecture du système : x64
Version SQLite: 3.36.0
Mémoire intégrée : 32430,2 Mo
Mémoire GPU dédiée utilisée par Lightroom: 2342,8Mo / 8003,0Mo (29%)
Version interne de Camera Raw: 16.0 [ 1677 ]

[John R Ellis]

@jean-louis 99425839, uploads from LR to Flickr haven been broken for the past week, and Flickr staff have acknowledged the problem.  See here for more details:

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

[EMSI68219]

LRc 13.0.2 with WIN11 latest Updates installed, with JPEGMIN (latest version).

I think there is more than this bug when exporting, because when exporting to a folder, and there are external Plugins configured like JPEGMINI or MOGRIFY - the exported files are stored in the temp folder but nothing happend with the external programs. That means, that the files are not reduced by filesize by JPEGMINI and the doubleborders with watermark created by mogrify left in the temp-dir instead of coping the files back to the root-dir. 

[EMSI68219]

I´ve reported the same issue. If you have only one plugin like Mogrify activated, instead of two (for exaple mogrify + JPEGMINI), then you will find the files maybe in the temp-folder. In case when you have two plugins or files installed, then nothing heppans at all.

[EMSI68219]

What is the solution for the problem? I missed it.

[John R Ellis]

The only reported workaround for the bug with post-processing actions provided by plugins (e.g. LR/Mogrify, Metadata Wrangler) is to roll back to Lr 12.  LR 13.2 is most likely coming out this week or next, and hopefully it will fix the bug.

[Rikk Flohr: Photography]

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.

[mwallner93]

I can confirm that the issue has been fixed. My plugin is getting the intermediate representation in the format it requests as expected. 

[Martin-dualpixel]

Thanks! Now its working again 🙂 … yipee

[Rikk Flohr: Photography]

@mwallner93  Thank you for confirming

[darr529]

It is working again after the update! Thank you Adobe!!

[BigRedler]

Tested the issue we had with publish and it seems that the issue is indeed fixed, at least on the mac.

[Mario_tr]

J upgraded to version 13.1 today, the export to flickr using mogrify is working now! Also Export to disk using mogrify works now normally!

Thank you for this fix!