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

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. 

@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/14283558

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 ]

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

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.

@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/14284296

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 

"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.

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.