• Resolved Roger Correia

    (@correiar)


    Our site was recently upgraded to WP 3.8.1 and I also updated MLA to version 1.70.

    One of our members experienced the following error after the upgrade:

    Fatal error: Call to undefined function wp_read_image_metadata() in …/media-library-assistant/includes/class-mla-options.php on line 1417

    Is this related to the upgrade? Any insights>

    http://wordpress.org/plugins/media-library-assistant/

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

    (@dglingren)

    Thanks for this report – I am sorry to hear you’re having this issue with the new MLA release.

    The location of the error, “class-mla-options.php on line 1417” is in a new function that was added for version 1.70. If the error is persistent, you can avoid it by going back to an earlier MLA version until I can correct it.

    That said, I haven’t been able to reproduce or determine why the error occurs. It’s located in the new v1.70 mla_upload_prefilter hook, which is applied during upload of a new Media Library item. Is that what the member was doing when the error occurred? If so, was the upload from the Media/Add New screen or from some other upload feature? It’s possible that this would occur if the upload was performed from the “front end”, i.e., not in the admin area.

    If you can tell me more about the steps leading up to the error and whether any other plugin is part of the process I can be more helpful. Thanks for any further information you can supply, for your understanding and your patience while I investigate.

    Thread Starter Roger Correia

    (@correiar)

    Our site is used by our camera club to upload images for competitions. For that we use the Entry Wizard plugin developed by Josie Stauffer.

    Our member that experienced this issue was in the process of uploading an image using the EW plugin. I myself have uploaded several images since I upgraded MLA but have not run into the same issue.

    Josie has advised me that she does not reference MLA in her plugin, so it must be indirectly being called by WP, not by her plugin.

    I have not kept a previous version of the plugin, so not sure how to revert back to the previous version.

    Plugin Author David Lingren

    (@dglingren)

    Thank you for posting this update with the additional information, particularly the name and author of your uploader plugin.

    I downloaded and activated EntryWizard and was able to upload an image from a “front end” page without encountering the error, using the “Image Pair” form and layout that comes with the plugin. I’m afraid I will need more specific information about your site’s EntryWizard WebForm, Layout and Permissions settings and the steps your member followed to cause the error.

    I also tested the process of reverting to MLA v1.61. Here are the steps I followed:

    1. Click this link to download the MLA v1.61 ZIP file to your computer. Note the folder/directory it ends up in.
    2. Log in to your site’s admin area.
    3. Go to the Plugins/Installed Plugins admin screen.
    4. Deactivate Media Library Assistant, then Delete it.
    5. Go to the Plugins/Add New screen and select the “Upload” tab.
    6. Click “Browse…”, navigate to the ZIP file’s folder/directory, select the ZIP file and click “Open”.
    7. Click “Install Now” to upload and install the ZIP file.
    8. Click “Activate Plugin” to activate the older version.
    9. Go to the Settings/Media Library Assistant screen and verify the version number in the screen header.

    I regret the inconvenience of reverting to the older version. Let me know if you have any problems with the process or further questions about it.

    I will try to resolve the conflict with EntryWizard. Any additional details you can give me would help.

    Thread Starter Roger Correia

    (@correiar)

    Thanks for the prompt feedback. I was not the one that set up MLA, so before I deactivate it and delete it, should I be exporting all settings and then re-importing them?

    If I delete the latest version, will it also delete the exported settings? I want to make sure I don’t mess up the current configuration. Also, are the settings that are exported, backward compatible?

    Our member was using a custom webform to upload images for an upcoming competition. But I have not been able to recreate the problem myself. I asked the member to send me a copy of the image they want to upload so that I can try it myself. So far I have not had any response.

    Plugin Author David Lingren

    (@dglingren)

    Thanks for the update and for your efforts to reproduce the problem. I haven’t had any luck getting it to happen, either.

    Regarding the reversion, you can export your settings just to be safe, but the settings will not be harmed by deleting the plugin and they are backward-compatible to version 1.61. I haven’t (yet) written the code to remove options when the plugin’s deleted.

    I am leaving for Guatemala on Tuesday morning, so anything you can do in the next day would be great.

    Thread Starter Roger Correia

    (@correiar)

    I noticed that there are some custom Style and Markup Templates that were created by the developer of our site under the MLA Gallery tab in Settings. Not sure how those need to be managed as we try to revert to a previous version.

    Again, I want to make sure we do not impact the existing configuration and end up having to do a lot of rework.

    I placed a call to her to get some feedback.

    Plugin Author David Lingren

    (@dglingren)

    The custom style and markup templates should not be affected by a reversion.

    If you do contact the member, I’d be interested to know if the problem is specific to one image or to all of her uploads, and if the problem persists when she tries a second time to upload the image.

    This “fatal error” is caused by a standard WordPress function that for some reason does not exist when MLA calls it. As far as I can tell, the function should always be there when the call comes in. Very strange.

    Thread Starter Roger Correia

    (@correiar)

    I followed up with the member who experienced the problem and she continues to get the same error, regardless if she uploads one image or multiple images. The webform allows up to 4 images to be uploaded.

    What’s really puzzling is that she sent me one of her images and I was able to upload it without issue. Also, 14 other members have been successful in uploading their images, so the problem seems to be isolated to her setup. I have asked her for her PC configuration, but at this point my inclination is to leave version 1.70 of MLA in place.

    Thread Starter Roger Correia

    (@correiar)

    It looks like this user is running an old Windows XP machine with IE8. I have advised her she should seriously consider an upgrade. At this point I will assume it’s a compatibility issue due to the age of the machine/OS/Browser combination that she is running. Thanks for your efforts.

    Plugin Author David Lingren

    (@dglingren)

    Thanks for these updates; I am glad the issue is restricted to one member. I agree that reverting to an earlier MLA version may be overkill at this time.

    I ran another test with my browser set to IE8 emulation mode. The EntryWizard uploads still work for me. I can’t think of a browser-related cause for these symptoms.

    Sometimes, clearing the browser’s local cache can help, although it’s a long shot.

    I will mark this issue resolved for now because only one of several members is affected and there’s no MLA-related cause I can think of. Please update the topic if you learn anything more or if other members have problems.

    Thanks for all of your work related to this issue!

    Plugin Author David Lingren

    (@dglingren)

    I just had a chance to download and test EntryWizard v1.0.1. You might be interested in my experience with it:

    WordPress database error after fresh install

    You may not encounter the same version upgrade issues I did, but back up your data before you upgrade just in case.

    Thread Starter Roger Correia

    (@correiar)

    Thanks for the heads up… our site is backed up nightly, so we should have a recovery point that hopefully I won’t need. I did get one other user reporting the same fatal error. It turns out that she was also running Windows XP with IE8. That seems to be the common thread…

Viewing 12 replies - 1 through 12 (of 12 total)

The topic ‘Fatal Error’ is closed to new replies.