• Resolved ernstwg

    (@ernstwg)


    Hi David. I use WP/LR Sync for publishing an image incl. data from Lightroom to WordPress. By accident I found an issue and perhaps you can help me here.

    I tagged an LR image with a keyword ‘unbekannt’ within LR and MLA is putting the keywords into Att. Tags on the WP Side. It is shown on my website nicely. At a later stage I deleted the tag/keyword ‘unbekannt’ for the LR image, published it … but the value ‘unbekannt’ in Att. Tags still pops up.

    Many thanks in advance

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author David Lingren

    (@dglingren)

    Good to hear from you again, and thanks for your report. I don’t have a copy of Lightroom so I can’t test your issue on my own. I may be able to give you some help, though.

    You wrote “MLA is putting the keywords into Att. Tags on the WP Side“. Does that mean you are using an MLA mapping rule to put the keywords into Att. Tags? If not, are you using the “Sync Keywords” feature found on the Keywords (Tags) tab on the Meow Apps/Photo Engine | Settings page? Note that Photo Engine is the new name for the old WP/LR Sync plugin.

    Any additional details you can provide will be helpful, thanks.

    Thread Starter ernstwg

    (@ernstwg)

    Photo Engine: creation of keyword taxonomy disabled, synching keywords is setting to None

    I am using an MLA Mapping Rule for Att. Tags which sets 2#025 keywords to parameter IPTC value. Parameter options is set to array, delimiters is empty.

    1. If I set keyword1 as only LR keyword, keyword1 will be shown in Att. Tags after publishing
    2. If I then remove keyword1 as only LR keyword, keyword1 still will be shown in Att. Tags after re-publishing
    3. If I then set keyword2 as only LR keyword, keyword1 will no longer shown be shown in Att. Tags after re-publishing, but keyword2 will.
    Plugin Author David Lingren

    (@dglingren)

    Thank you for confirming the MLA mapping you are using. The current MLA version will only update the term assignment if the new value is not empty. It will not delete existing term assignments if the new value contains no terms.

    I have added a new “Replace All” option for the “Existing Text” setting that should give you the results you want.

    I have uploaded a new MLA Development Version dated 20240726 that includes the enhancement. You can find step-by-step instructions for using the Development Version in this earlier topic:

    How to download & install the current development version of MLA

    Once the Development Version is installed you can change the setting in your rule to the new value and retest the handling of empty values in your mapping rule.

    1. Republish the item from Lightroom, or
    2. Click the “Map IPTC/EXIF/WP Metadata” link in the Media/Edit Media admin page.

    The enhancement will be part of my next MLA version, but in the interim it would be great if you could install the Development Version and let me know how it works for you. Thanks for inspiring this MLA enhancement.

    Thread Starter ernstwg

    (@ernstwg)

    Hi David.

    thanks for helping me, as always ?? . Republishing the item from Lightroom showed an error message already in LR. Excerpt from LR Log indicates an issue with the newly introduced option ‘Replace All

    07/27/2024 14:30:34 ERROR Response:"wplr.lrplugin/JSON.lua:676: wplr.lrplugin/JSON.lua:383: can't parse JSON at char 2 of: \nWarning: Undefined array key \"replace_all\" in /mnt/web206/c0/35/512017535/htdocs/STRATO-apps/wordpress_08/app/wp-content/plugins/media-library-assistant/includes/class-mla-options.php on line 993\n\n

    There seems a reference to that in mla.log (Reporting Level 16

    [27-Jul-2024 12:57:39 UTC] PHP Warning:  Undefined array key "replace_all" in /mnt/web206/c0/35/512017535/htdocs/STRATO-apps/wordpress_08/app/wp-content/plugins/media-library-assistant/includes/class-mla-options.php on line 993

    Of course I can send you the entire log file, if you want.

    Plugin Author David Lingren

    (@dglingren)

    Thanks for trying the Development Version and reporting the results. Thanks as well for sending me the entire log by email. I have found and fixed the cause of the issue you reported.

    I have uploaded a new MLA Development Version dated 20240729 that includes the fix. You can follow the update steps at the link I posted above.

    Once the Development Version is updated you can retest the handling of empty values in your mapping rule.

    Thread Starter ernstwg

    (@ernstwg)

    The issue as described is fixed. Thats great and much appreciated.
    There is a minor question on that, but as I will be off for a few days, I will come back to you later on this.

    Ernst Wilhelm

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.