Support » Plugin: Media Library Assistant » IPTC/EXIF Mapping not working after update?

  • Resolved damon70


    Thanks for your plugin, great work!
    I’ve been using it for two years now and never experienced any problems.

    But after the last update Media Library Assistant to v2.81 and WordPress to version 5.3, “IPTC/EXIF Mapping when adding new media” stopped working.

    Is this a problem in WordPress Update or in the plugin?


Viewing 5 replies - 1 through 5 (of 5 total)
  • After the experiments: the problem is not in update Media Library Assistant to v2.81. It is working just fine, as before. So the problem occurs after update WordPress to version 5.3. Can this be somehow fixed?


    Plugin Author David Lingren


    Thanks for the positive feedback and for your report.

    WordPress 5.3 changed the way metadata generation worked on new image uploads:

    Use of the “wp_update_attachment_metadata” filter as “upload is complete” hook

    I made some changes in the MLA 2.81 update to accommodate the core WordPress changes. It is working fine on my test system, but perhaps I’ve missed something that is causing the issue on your system.

    Any information you can provide on the rules you are using on your site will be helpful.

    If you can access your site’s error log you can try activating MLA’s debug logging:

    1. Navigate to the Settings/Media Library Assistant Debug tab.
    2. Scroll down to the “MLA Reporting” text box and enter “31”. This will turn on MLA debug logging for mapping rule Processing.
    3. Click the Save Changes button to record your new setting.
    4. Optionally, scroll to the bottom of the screen and click “Reset” to clear the error log. You may not want to do this depending on how you manage your error log.

    Once that’s done you can run one or more Upload tests. Then, go back to the Debug screen and:

    1. Enter “0” in the MLA Reporting text box to turn debug logic off.
    2. Click the Save Changes button to record your new setting.
    3. Scroll to the bottom and click “Download” to get the log content in a text file.

    There might be a lot of messages written to the log, so limit the amount of activity during the logging period. You should see messages in the log like these:

    [22-Jan-2018 19:47:05 UTC] 591 MLACore::mla_plugins_loaded_action() MLA 2.81 (20180115) mla_debug_level 0x1F

    You can post the interesting messages in this topic. You can also email me the information if that’s better for you. You can contact me at my web site to continue the dialog.
    Thanks for your patience.

    Hi, thanks for your answer.

    There is my rules for IPTC/EXIF Mapping when adding new media:

    Plugin Author David Lingren


    Thanks for posting a link to your rules. I regret that I cannot access the image. I receive:

    Error 1011 Access denied
    What happened?
    The owner of this website ( does not allow hotlinking to that resource (/wp-content/uploads/2019/11/Media-Library-Assistant-v2.81-Settings.jpg).

    You can contact me at my web site to send a copy of the image and any other information you have by email. Thanks!

    Plugin Author David Lingren


    Thank you for working with me offline to investigate this further. It looks like some changes made in WordPress 5.3 to process “big images” might be involved. Here’s some background:

    Introducing handling of big images in WordPress 5.3

    In particular:

    If an image height or width is above this threshold, it will be scaled down, with the threshold being used as max-height and max-width value. The scaled-down image will be used as the largest available size.

    The “scaled down” version of the image becomes the “attached file” for the item, and this image is also used for MLA’s mapping rules. On your site the scaled down image does not have any of the metadata found in the original image, so your mapping rules have no data to work with. I do not completely understand this because, on my system, the metadata is preserved when the image is scaled down.

    On one of my test systems the scaling process causes fatal errors within Imagemagick when WordPress tries to generate the intermediate sizes for big images. My other system works fine on all images. There may be some problem with different versions of PHP and Imagemagick that I have not uncovered.

    On a brighter note, you eliminated the problem on your system by installing the Disable “BIG Image” Threshold plugin, which disables scaling. I found that in the Repository, as well as another plugin, Scale Large Image Threshold.

    I have also made a small change in MLA itself to use the original image to source the data for mapping rules and [mla_gallery] substitution parameters. I believe this change would solve the problem on your system without disabling the scaling.

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

    PHP Warning on media upload with Polylang

    I am marking this topic resolved, but please update it or let me know if you have any problems or further questions about the new 5.3 big image updates. If you or anyone else who finds this post installs the Development Version I would love to know if it works for you. Thanks for your help and persistence.

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