Hello,
Thanks for the feedback!
The PHP “Allowed memory size exhausted” is often due to memory limit being too small to process all the data, which might happen on some default website setup, where there is a lot of data to process. The Developer module will list all meta of a page in the admin, which might be a lot depending on how many meta you saved.
In order to fix that issue, I would recommend to increase your memory limit by adding the following code in your wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
This configuration is also recommended when using complex plugins such as Woocommerce. Here is an article on Woocommerce on the topic.
Hope it helps!
Have a nice day!
Regards.
this only happens on pages related to other plugins (webstories, amp) which would have no meta data associated with AFCE, I have no problem on posts or pages is that normal?
Hello,
The Developer Mode will list all meta related to posts, pages, no matter if they are linked to ACF, ACFE, or other plugins. Note that WordPress, and other plugins, heavily rely on post meta logic to customize each posts.
Hope it helps!
Have a nice day!
Regards.
I just went through all our code and talked to our other developers. We only have one piece of acf/acfe code on this site, and the fields are only associated with a single page so there is almost no meta data, it seems like there may be conflicts with your plugin and the other ones
Hello,
The memory limit issue simply suggests there is a lot of data to process. If you don’t want to use it, you can keep the module disabled, and simply use PHPMyAdmin to access your database to see what is in it.
If you believe there is a compatibility problem, then the issue should be isolated. Unfortunately the “Allowed memory size exhausted” won’t help much, as it is a generic message error regarding memory limit which might be triggered on some server configuration with a low memory limit. To make sure it’s not simply your memory limit being too low, using the WP_MEMORY_LIMIT to 256M will set a comfortable memory pool.
If the problem is still there with that configuration, I would recommend clone your website on a development / staging environment using Duplicator or your hosting backup solution, if any. Then try to disable all your plugins one-by-one (at the exception of ACF Pro & ACF Extended) until you find which one cause the issue.
If the problem persists, I would suggest switch to the native WP Twenty Twenty Two theme, to make sure you don’t have any custom code in your theme that would break the feature.
In all cases you should be able to confirm the feature works by setting up a clean WP install on a development environment with ACF Pro + ACF Extended only, and test the feature on it.
Regards.
