• Resolved FLoes

    (@floes)


    Thank you for this most excellent plugin, it has been invaluable to me in my current project.

    I have run into an “Uncaught ReferenceError” being thrown by MLA, that is interfering with my theme’s Custom CSS module editors. The theme is Divi 3.25.4 (unfortunately), and the error makes it so when I try to edit the Custom CSS for a page, the code module becomes unresponsive and won’t allow a cursor or selection.

    I didn’t think it could be from MLA, as it didn’t start until I recently updated the theme, nor do I see how MLA would interfere with the theme’s code. But I am far from an expert in these matters.

    So, after troubleshooting with Divi’s tech support they determined the issue was being created from this file: http://us267.siteground.us/~andrewjm/wp-content/plugins/media-library-assistant/js/mla-define-ajaxurl-scripts.min.js?ver=2.79

    The line in question:
    if((typeof ajaxurl==="undefined")&&(typeof wp.media.view.l10n.mla_strings.ajaxurl==="string")){var ajaxurl=wp.media.view.l10n.mla_strings.ajaxurl};

    Any ideas or help with this would be most sincerely appreciated, as I have relied heavily on MLA for this photography website. Thank You~

    The page I need help with: [log in to see the link]

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

    (@dglingren)

    Thanks for your positive feedback and for your report. I regret the trouble you are having with MLA’s Media Manager Modal (popup) window.

    Without access to a copy of the Divi theme you are using I am unable to do testing on my own system. If the Divi tech support people can give me a copy of the theme I can give it a try. Perhaps you can get them to contact me at my web site if they’re willing to do that.

    In the interim I will see what I can do on my own. Your symptoms are a variation on these earlier topics:

    Ajax url is not defined when plugin is active with Elementor

    Adding new category in Insert Media not working

    The workaround described in the second topic may work for your site. If you try it and it does, let me know.

    You can also disable the MLA enhancements to avoid the problem, although I know that’s inconvenient. To do that:

    1. Navigate to the Settings/Media Library Assistant General tab.
    2. Scroll down to the “Media Manager/Media Grid Enhancements” section.
    3. Uncheck the box to the left of “Enable Media Manager Enhancements”.
    4. Scroll to the bottom of the screen and click “Save Changes” to record your new setting.

    I hope that gives you some relief while I investigate further. Thanks for your help and your patience.

    Thread Starter FLoes

    (@floes)

    Hello David!

    Thank you for your response, you’re the man. I’m sorry to have troubled you with this, right now I think that MLA is most likely NOT the culprit here.

    I may have been sent on a wild goose chase with this; I did more testing last night and this morning and that small JS error does not seem to the issue to blame from what I can see. Disabling MLA entirely does not appear to fix the issue, so in my book I don’t see how MLA can be to blame for this.

    After further chats with Divi support they now have me checking with my host about permissions, so no concern of yours or this most helpful plugin.

    Thanks for all of your work on this plugin and it’s maintenance, it’s a great asset and it’s appreciated! I am going to look into the possible solutions you posted above, however I do not believe MLA is to blame here, so feel free to resolve this topic.

    Thanks and Peace~
    Mason {Floes}

    Plugin Author David Lingren

    (@dglingren)

    Thanks for your update and for your kind words regarding MLA.

    Even if the “small JS error does not seem to the issue“, it does indicate a potential problem since it only occurs if a WordPress global variable MLA depends on isn’t defined.

    I have uploaded a new MLA Development version that contains an improved version of the JavaScript file identified in your first post. If you resolve the other problems and the error persists, it would be great if you could install the Development Version and see if it helps. You can find step-by-step instructions for using the Development Version in this earlier topic:

    PHP Warning on media upload with Polylang

    I will resolve this topic for now, but please post an update if you have new information to report. If you get a chance to install the Development Version, let me know if there are any remaining issues with the code. Thanks again for your help and good luck with your application.

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

The topic ‘JS Error thrown from MLA 2.79’ is closed to new replies.