• Nick Keenan

• in reply to: Fatal error: Maximum function nesting level reached
• July 16, 2019 at 7:45 am

An Update to this issue – As of ACF Pro 5.8.2, this issue appears to be resolved.

• Nick Keenan

• in reply to: Fatal error: Maximum function nesting level reached
• June 7, 2019 at 2:16 am

To answer your question, Marco, at last check we were still having the issue but only on one of our sites – we have frozen the ACF version and haven’t had a chance to test again with the latest release, I will try devoting some more troubleshooting time this week or early next week.

This site also has our largest number of JSON files (Another site has nearly as many but not quite as many), and we do some filtering of field configuration after loading these via JSON using ACF hooks. We use these JSON files pretty deeply in our workflow in a custom plugin, so we’ll give this a test but we’re talking about 30 – 40 required by the theme so this will take us a while to test to narrow things down. We use two add-ons typically as well, and we haven’t been able to localize if it’s an issue with those fields in particular:

Advanced Taxonomy Selector: https://wordpress.org/plugins/acf-advanced-taxonomy-selector/
Image Crop Add-On: https://wordpress.org/plugins/acf-image-crop-add-on/

We’re on Vagrant servers in developemnt where we have control over a range of PHP configuration options – we’ve tried increasing server and PHP memory limits, max number of variables limits, all with no luck.

• Nick Keenan

• in reply to: Fatal error: Maximum function nesting level reached
• February 21, 2019 at 8:39 am

I had a similar “Maximum function nesting level of ‘200’ reached” issue this AM when updating a site using WP 5.0.3 to version 5.7.12.

This site imports a number of ACF Pro fields via JSON, and I’m working to localize the issue further.

I reverted to previous versions of ACF Pro and the problem seems to introduced in the 5.7.11 release. The problem resolves if I rollback the version to 5.7.10.

The traceback of the error log hit the following before the page failed to render. Both Pages and AJAX Requests that use ACF fields via the WP API were failing to render.

We use ACF Pro pretty heavily – is there a particular case where the acf/validate_setting filter might be hitting recursively when the page loads?

`
#0 {acf-pro-path}/includes/api/api-helpers.php(145): apply_filters(‘acf/validate_se…’, ‘export_textdoma…’)
#1 {acf-pro-path}/includes/api/api-helpers.php(165): acf_validate_setting(‘export_textdoma…’)
#2 {acf-pro-path}/includes/deprecated.php(78): acf_get_setting(‘export_textdoma…’, ”)
#3 {wp-path}/wp-includes/class-wp-hook.php(286): acf_deprecated->acf_settings_l10n_textdomain(”)
#4 {wp-path}/wp-includes/plugin.php(203): WP_Hook->apply_filters(”, Array)
#5 Error while reading response header from upstream.
2019/02/20 19:19:38 [error] 1352#1352: *4123 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Error: Maximum function nesting level of ‘200’ reached, aborting! in {wp-path}/wp-includes/plugin.php:176
`