• Resolved elenim

    (@elenim)


    Since updating to WordPress 4.2, most users on my WordPress site have been experiencing an issue with the image crop feature of WordPress. When trying to crop a photo, the dimensions show as NaN. When deactivating Media Library Assistant, this issue does not occur. So, it seems there is a conflict with the plugin and WordPress 4.2. Can you offer a fix for this? Thanks!

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

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

    (@dglingren)

    Thanks for reporting this issue. From my preliminary testing it looks like a new conflict between MLA and the Media/Library “grid” view has come up. The issue is not specific to the “Edit Image” feature of the grid’s “Attachment Details” popup window. There is a JavaScript problem with the grid toolbar that stops JavaScript from handling the crop.

    I will investigate and correct the problem. In the interim, please let your users know that they can crop/edit images by clicking the “Edit more details” link at the bottom-right of the Attachment Details popup window and using the traditional Media/Edit Media screen. I know that is inconvenient, but it may help while I am working on the MLA defect.

    You can also avoid the problem by disabling MLA’s media grid enhancements. Go to the Settings/Media Library Assistant General tab and scroll down to the “Media Manager/Media Grid Enhancements” section. Uncheck the box “Enable Media Grid Enhancements”, then scroll to the bottom of the page and click “Save Changes” to record the setting change.

    I will post an update here when I have progress to report.

    Plugin Author David Lingren

    (@dglingren)

    I have just uploaded a new Development Version that contains a fix for the issue you reported.

    You can find step-by-step instructions for using the Development Version in this earlier topic:

    MLA errors when using plugin

    I will leave this topic unresolved until the fix is released in the next MLA version. If you get a chance to try the Development Version, let me know if it solves your problems. Thanks for bringing this issue to my attention and for your interest in the plugin.

    Thread Starter elenim

    (@elenim)

    Hi David,

    Thank you so much for your quick response! I would love to try out the developer version. Just so I know, are there any precautions to take when using the developer version?

    Plugin Author David Lingren

    (@dglingren)

    Thanks for agreeing to give the Development Version a try. There are no special precautions you need to take, just follow the steps laid out in the earlier topic.

    If the Development Version doesn’t work for any reason, deactivate it, delete it and re-install the production version. If the Development Version works for you, keep using it until it is replaced by the next official MLA release, just like any other update.

    Let me know how it goes.

    I did download development version from development section on plugin page. But still got NaN values when cropping image with 4.2.2 wordpress.

    🙁

    Plugin Author David Lingren

    (@dglingren)

    Thanks for your report – I regret the trouble you are having.

    You may be able to resolve the problem by refreshing your browser cache, as described in this related topic:

    Debug Error

    In particular:

    2. Make sure you have “refreshed” the Media/Library grid screen. Unless you click the browser’s “refresh page” button you will not get the corrected copy of the MLA scripts.

    If that does not help, let me know and I will continue to work with you. Thanks for your patience and your interest in the plugin.

    Plugin Author David Lingren

    (@dglingren)

    I have released MLA version 2.11. It contains the Media Grid fix that resolves the issue you raised in this topic.

    I am marking this topic resolved, but please update it if you have any problems with JavaScript errors in the new version. Thanks for your interest in the plugin.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Conflict with WP 4.2’ is closed to new replies.