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

@Zooey123  Please read: https://community.adobe.com/t5/lightroom-classic-bugs/p-unable-to-advance-to-the-next-photo/idc-p/14268477#M49852 

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

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

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

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. 

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

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?

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. 

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

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!