Extended is causing fatal errors with Pro

Hello,

Thanks for the feedback!

Unfortunately, I cannot provide support for Pro users on this forum. Please open a ticket from your?Account Dashboard?instead.

Thanks!

Have a nice day!

Regards.

No, I have ACF Pro, and your plugin is broken with it, mate. I don’t have your extended pro plugin. Your base plugin does not work right now with the pro ACF plugin

Hello,

Oh okay I see. Note that ACF Pro is a requirement for both ACF Extended Free & Pro, that’s why I thought your ticket suggested you were an ACF Extended Pro user.

Regarding the issue, It’s hard to tell without a specific error message. It could be a compatibility issue with a third-party plugin, or a custom code in the theme. I would recommend to enable the WP Debug mode (see documentation), it will help you to identify the cause of the issue.

To do so, please add the following code in your wp-config.php file, right before the comment: “That’s all, stop editing! Happy publishing”:

define('WP_DEBUG', true);          // enable debug
define('WP_DEBUG_LOG', true);      // enable error logs
define('WP_DEBUG_DISPLAY', false); // disable errors on screen

/* That's all, stop editing! Happy publishing. */

This will log server errors in the file: /wp-content/debug.log.

Once the debug mode code has been added, trigger the error again, and open this file. You should see some error message. Please share it here.

You can read more about how to debug WordPress and ACF on our guide here.

Let me know if you found something!

Thanks!

Regards.

Hello!

Any news about this issue?

Thanks!

Regards.

No, it’s still happening. Might have to just remove the plugin. I dunno. Both you and them claim no responsibility which is the most irritating response to get when using other people’s products or services.

Hello,

Did you manage to enable the debug mode as I described in my previous answer? The best way to understand what cause the issue to get a precise error message.

Thanks!

Regards.

This is the only reports from the debug

[25-Feb-2025 05:04:37 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 12288 bytes) in httpdocs/wp-includes/capabilities.php on line 1306
[25-Feb-2025 05:04:37 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in httpdocs/wp-content/plugins/forminator/library/external/src/Forminator/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Lock.php on line 1

Everything works as soon as I turn off your plugin though so it’s something with this plugin specifically interacting, I would imagine.

Hello,

Thanks for the details!

The “Allowed memory size of XXXXXXXX bytes exhausted” is a common server error. It means PHP ran out of memory while trying to display a page. Typically, every PHP script, plugins, custom code etc… add a load on your server’s RAM memory. Your error message suggest your current memory limit is set to 128MB (134217728 bytes).

The more complex your site (Woocommerce, ACF etc…), the more likely you are to reach this limit. It seems like ACF Extended is the one that show this limit. But in reality, it could be any additional plugin. You could disable ACF Extended, and add some new plugins and see the exact same error. This is why Forminator is displayed in your error message and not ACF Extended. The problem is “the global load”, not one specific plugin/code.

For complex WordPress websites, it is recommended to increase the default memory limit. For example, Woocommerce recommends it (see woocommerce documentation).

In order to increase your memory limit, add the following code in wp-config.php before the /* That's all, stop editing! Happy publishing. */ comment:

define('WP_MEMORY_LIMIT', '256M');

/* That's all, stop editing! Happy publishing. */

This should fix the issue.

If the problem is still here, it might means you also need to increase the limit in your PHP configuration. To do that you need edit your php.ini file, and update the following parameter:

memory_limit = 256M ; Maximum amount of memory a script may consume

If you don’t have access to your php.ini, try to contact your hosting provider.

Let me know if that fixed the issue!

Regards.

Note: you can read more about WP_MEMORY_LIMIT on the WordPress documentation here.

Ah okay that has worked. Thank you very much =)

Hello,

I’m glad to hear it now works as expected!

Regards.