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!

[GoldingD]

You might want to compare the Plug-In version, what is installed vs what is available at the publishers website. When looking at the version installed, look at both what is listed in the LrC Plug-In Manager, and what is indicated via Finder in the LrC Modules folder.  The Plug-In Manager may or may not know about what the Publisher has made available, and The copy at Adobe may or may not be the latest. I ran inot this for SmugMug.

[johnrellis]

A few of my plugins use exporting internally in limited ways but none provide export or publish services like the problem plugins do.

[johnrellis]

Also, another person has also reported that Friedl is aware of the problems.

[Dimitri21886113d585]

When I want to publish from lightroom classic, I got a failure...  I have no idea what the problem is.  Thanks for your advice

Tx

Dimitri

[GoldingD]

Question, Is this the same problem as in:

https://community.adobe.com/t5/lightroom-classic-discussions/issue-with-pixieset-uploads-after-updat...

[johnrellis]

The error message indicates a programming error either in the Pixieset plugin or in LR. The file path in the error message, "src/pixieset.Irdevplugin/PixiesetAPI.lua", suggests you may have an older or beta version of  the plugin installed. 

So remove the current plugin and download and reinstall the current version:

https://help.pixieset.com/hc/en-us/articles/115003009832

If that doesn't help, you'll need to contact Pixieset.

[GoldingD]

Did they have you accomplish the following?

• In LrC, in the Plug-in Manager, Select the Pixiset Plug-in, Look at the Status box, look at the location, Select to Show in Finder, then bring up Finder.
• Note (wright down) the folder location.
• In Finder, copy the plug-in to another folder. (alternately, you might want to download a fresh new copy from Pixiset)
• In Finder, delete the plug-in that LrC was using (not the copy)
• Close LrC.
• Open LrC, in the Plug-in Manager, verify that Pixiset does not exist.
• Close LrC
• In Finder, copy or move that copy of the plug-in to where you want it, perhaps the folder the original was in.
• Open LrC.
• In the Plug-in Manager, add the plug-in
• Close, and restart LrC. test

I had an issue with my SmugMug Plugin, mind you with the Adobe provided one. Went thru much of the above, but with using the SmugMug site copy, not the Adobe site one.

I also had an issue with my DcO NIK plug-in's (external editor), had to re-install NIK. I have no idea yet, if other plug-in's have gone belly up.

I have no idea if this will fix anything. Thinking LrC v13 is running afoul on Plug-in's

Note that my rig is Windows OS, could be a OS issue.

[Rikk Flohr: Photography]

Matching to existing bug logged for investigation. 

[Martin-dualpixel]

I also have a problem with the LR/Mogrify plugin since the new Lightroom V13.0.1 Update. Images are watermarked in 2 steps. Likewise, an upload with the watermark option on an FTP no longer works.

[Mario_tr]

Great observation! I noticed the same phenomenon, The images are dump in the folder and modify in a second pass!

[stefanm25580085]

Hi,

I used the Mogrify plugin to create a white canvas. This stopped working with the most recent Lightroom. Is there any way to fix this? Is there any other way to reach the effect of Mogrify Canvas?

Thanks!

[kittynoodlesoup]

Also looking for a solution - I am having the EXACT same issue as OP.  I'm trying to publish to ShootProof.  It will do a handful, and then the message shows up.  I have been doing this with no problems up until yesterday.  Not sure if something updated to a new version or what.  Going to check around on shootproof, but it's extremely annoying.  Here's my error message:

Can't update this collection.  An internal error has occurred: ?:0: attempt to perform arithmetic on field 'fileSize' (a nil value)

Steps are the same as OP - click publish, it works for a few images, and then the message pops up and uploading stops.

[loicg48397723]

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

[lukedyson]

Glad to know it's not just me, the only way I've found to get around this so far is after pressing publish is to export the same photos locally at the same time and it will manage to complete the export with no problems. I'm not sure why that works but to me it suggests it's not a problem with the publish services but something lightroom is struggling with.

I'd suggest cancelling the local export once the publish has complete as I've noticed lightroom is also exporting photos twice over (double ding bug that's currently reported).

[dj_paige]

Simply searching for this error turns up a number of posts, some of which are marked correct.

https://community.adobe.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&...

[lukedyson]

I did research these, they're mostly very old results and I've confirmed I don't have this error when rolling back a version of LrC, it was the new version that's brought around this problem.

My best guess is there's a breaking change to the SDK.

[JRRGibbs]

Also noticed that i does a double pass added the border and watermark. Just exported 500+ photos and thought it hadn't added the border and watermark, but after it finished and I saw all the jpg's it started running a second pass and all images have the added things. 

[joart125]

Hallo
ich arbeite mit einem Macbook M2 Pro / 14.1 Sonoma / LRMogrify 5.1 / Lightroom Classic 13.1 /
Nach der Installation von LRMogrify wird nur die erste  Datei mit den LRMogrify-Vorgaben exportiert. Alle nachfolgenden Dateien  werden ohne die LRMogrify-Vorgaben exportiert.
Nach einem Neustart von Lightroom wird wieder nur diie erste Datei korrekt exportiert.

Wo liegt der Fehler?

[BigRedler]

Our plugin does a post processing step on exported/published photos. The plugin was working just fine before LRC13 but stopped working for publish.

Essentially, what the plugin does is to implement postProcessRenderedPhotos and then iterate through the renditions and call a command line tool to the actual processing (see code later). In export mode this works, in publish its not. With versions before LRC13 it worked in both modes.

Digging in it seems that with export, the file paths that are passed to the plug in are the paths of the files in the final location while in publish mode, the paths are for a temp files, right next to the final location, and the final location has the file before our plugin processing.

The plugin is both mac and windows and the failure is on both platforms.

Here's the code used:

function MyFilterProvider.postProcessRenderedPhotos( functionContext, filterContext )
PluginManager.executeCommand({action="reset-session"},false)

local command
local quotedCommand

for sourceRendition, renditionToSatisfy in filterContext:renditions( ) do
local success, pathOrMessage = sourceRendition:waitForRender()
if success then
local path = pathOrMessage
local ext = string.lower(string.match(path,".*%.(.*)"))

if ext == "jpeg" or ext == "jpg" then
local commandResult = PluginManager.executeCommand({action="process", path=path},false)
if not (commandResult == 0 or commandResult == 1005 or commandResult == 1006) then
renditionToSatisfy:renditionIsDone(false, "Failed to process image: " .. stringFromToolResult(commandResult))
end
end
end

end

end

[MrApricots]

I can report that LrC 13.0.1 on a MacMini running OS Sonoma 14.1 does not work to add a text annotation to an image export with LR/Mogrify plug-in ver 5.1. (I am trying to add the filename as a watermark using the Ariel Unicode.ttf) The error message that eventually pops up from LrC is "A file is not located at the specified path."
I selected the LR/Mogrify Debugging option in the Plug-in Manager to "Log debug information to a file (LRMogrify2_dbg.txt) on your desktop", yet no such file is created anywhere. I also tried the "Send debug to system log" option and I don't see anything related to LR or Mogrify in the system log.
I then watched the folder to where I instructed LrC to send the image exports and I noticed that the files are initially created then a second copy appears briefly that has a '~' at the end of the name before all files disappear and then LrC shows the error message. I'm guessing the files without the '~' are the exports from LR before LR/Mogrify begins its work which creates the temporary '~' version. Then probably some error with the LR/Mogrify script causes the system to clear out all the files because LR/Mogrify was trying to modify the original files and the process failed.
I looked at the ImageMagick.org documentation and noticed an option to create a new file rather than modify and overwrite the original, yet I'm unsure how to use that option with the LrC export plug-in. It probably involves editing one of the LR/Mogrify .lua files in the plug-in, but that's above my pay grade at this point. 

[johnrellis]

Many have been experiencing this issue in LR 13 with the popular LR/Mogrify plugin. Adobe has filed an internal bug report and is investigating.

[johnrellis]

Moderators, @Rikk Flohr: Photography, please merge with the existing Bug:

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

[johnrellis]

Adobe is investigating many reports of LR/Mogrify not working with LR 13.

Moderators, @Rikk Flohr: Photography, please merge with this bug:

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

[Zooey123]

I'm not very technical, so please bear with me. I've used several of Jeffrey's plugins for some time and not had a problem until upgrading to LR13 last month. I use the wrangler to remove coloured labels, strip tags/keywords and captions. Now, it doesn't strip any of those.

I also found that while the file name appeared correct within LR, when I uploaded some files to my WordPress website using NextGen galleries, my silly personal comments made in the captions field had become the file names. I had to type them back in manually.

I've seen one bug report in here mentioning one of Jeffrey's plugins, but it wasn't the Metadata Wrangler. I don't seem to be able to leave a comment on his plugin page because he doesn't read them any more.

I'm using Windows 11

[john beardsworth]

I believe there is a recent bug in LR's export post-processing - the code that tells plugins to do something to exported files. Not all plugins would be affected, but post-processing plugins would be -  and that would include MW.

I'd be surprised if this isn't fixed in the next LR update.