Uncaught RangeError: Maximum call stack

Actually I think this maybe an issue with the latest version of the Advanced Custom Fields Pro plugin

Thanks for your report and for the additional information about Advanced Custom Fields. I have not been able to reproduce the problem on my system, using the free ACF Version 4.4.7.

Other MLA users are having a similar problem and I have uploaded a new Development Version that may help. See this topic for more information:

Uncaught RangeError: Maximum call stack with Download Monitor

Thanks for your patience and for any additional details you can provide.

I’m having the same issue.

MLA v.2.25. ACF (pro) v.5.3.8.1 installed.

The error disappears if I deactivate ACF, but if also disappears if I deactivate MLA and activate ACF.

Acronyms OMG.

I tried installing ACF (pro) 5.3.7 and the JS error disappears (when both plugins are activated).

The changelog for 5.3.8.1 reads

Image field: Fixed JS bug causing errors when Uploaded to post library setting is checked

I’m wondering if this might cause the issue.

I’ll also add a support ticket on the ACF site, but I’m guessing you might want to check this out as ACF is so widely used nowadays it seems *sigh*.

The site is a single site intall: WordPress 4.5.2, core in a subdirectory.

Thanks for your report. It’s going to be a few days before the next MLA version. In the interim I encourage you to download and try the Development Version to confirm that your problem is solved by the fix I added there. Here’s a link to more information:

Uncaught RangeError: Maximum call stack with Download Monitor

If that’s not possible, you can avoid the problem and still use most of MLA by disabling the features that conflict with ACF. Go to the Settings/Media Library Assistant General tab and scroll down to the checkboxes shown in Austin’s first post in this topic. Uncheck the two options, scroll to the bottom and click Save Changes to record the new settings.

One of the two alternatives should give you some relief while I complete the next version. I regret any inconvenience caused by the delay. Thanks for your understanding, patience and interest in the plugin.

I have released MLA version 2.30, which contains a JavaScript fix for this problem.

I am marking this topic resolved, but please update it if the problem persists in the new version. Thanks for your patience in awaiting the new version.

Thanks David, really appreciate all the work you’ve put into the plugin!