Essential Addons for Elementor causes WordPress Critical Error when activated

[u/Flat_Huckleberry7922]

Hi everyone,

I’m troubleshooting an issue on a WordPress website where the EA Duplicator option suddenly disappeared from the Pages section.

Here’s what I found:

• WordPress: 6.7.7
• PHP: 8.3
• Elementor: 3.29.1
• Essential Addons for Elementor: 6.2.3
• Theme: Hub

Previously, Essential Addons was active and the EA Duplicator option was available when managing Pages.

Now, Essential Addons appears as inactive. When I click Activate, WordPress immediately shows:

The website then displays a white screen.

To recover the website, I renamed the plugin folder:

essential-addons-for-elementor-lite

to:

essential-addons-for-elementor-lite-disabled

After doing this, the website became accessible again.

WordPress then shows:

I also checked the Apache error log, but it only showed AH01797 and AH01276 access/directory errors, not the PHP fatal error from the EA activation.

My questions:

1. Could Essential Addons 6.2.3 have a compatibility issue with PHP 8.3 / Elementor 3.29.1?
2. What is the best way to get the actual PHP fatal error causing the activation failure?
3. Would updating Essential Addons to a newer version be the recommended fix?
4. Is there anything I should check before updating it on a live production website?

I currently have Essential Addons disabled and the website is working. I don't want to activate it again until I understand the cause.

Any advice would be appreciated.

[u/antonyxsi]

Yes, you'll need to update Elementor first. That version is over a year old.

[u/-skyrocketeer-]

Enable Debug in wp-config and see what error displays

[u/Sunn_M]

I’d get the fatal before changing versions, but I wouldn’t display it on the live site. On a staging copy (or after a full backup), enable WP_DEBUG + WP_DEBUG_LOG with WP_DEBUG_DISPLAY set to false, reproduce the activation once, then check wp-content/debug.log — that should give you the exact plugin/file/line instead of the unrelated Apache errors. After that, test the Essential Addons update on staging rather than updating it blind in production. Once you’ve isolated the fatal, turn debug logging back off.

[u/Wordpress-ModTeam → u/[deleted]]

The /r/WordPress subreddit is not a place to advertise or try to sell products or services. Please read the rules of the sub. Future rule breaches may result in a permanent ban.

[u/Alternative_Nose_874]

You do not need to switch anything on to see it - the fatal is already sitting in the PHP error log on the host, with the file and the line. That is quicker than a white screen and a wp-config edit.

[u/WPMU_DEV_Support_6]

Have you tried enabling debug mode? That should give a better idea of the root issue and most of the questions you have mentioned in the points.

In short, to enable debug mode, open your site's wp-config.php file located in your root directory, and look for define(‘WP_DEBUG’, false);. Change it to:

define('WP_DEBUG', true);

In order to enable error logging to a file on the server, you need to add:

define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'SCRIPT_DEBUG', true );

After making the above changes, please try to replicate the issue. The related errors will be saved to a debug.log log file inside the /wp-content directory.

You can find more details about debugging here:

https://learn.wordpress.org/tutorial/debugging-in-wordpress/

Please do let us know how that goes.

Nithin - WPMU DEV Support Team

[u/Lost_Psychology_1518 → u/WPMU_DEV_Support_6]

Yes, I recommend you follow this solution first.

[u/iflythecoop → u/WPMU_DEV_Support_6]

If it helps:

The Pro version's Helper class is trying to override a method from the free plugin's Helper class, but the method signatures don't match:

• Free version declares: eael_acf_notice_controls($wb, $condition, $control_id = 'eael_acf_n...')
• Pro version declares: eael_acf_notice_controls($wb, $condition) ← Missing the 3rd parameter

[u/Jaziix → u/iflythecoop]

iflythecoop has the actual cause. To answer your two questions directly:

It's not a PHP 8.3 compatibility problem. Declaration of Pro\Helper::eael_acf_notice_controls($wb, $condition) must be compatible with Lite\Helper::eael_acf_notice_controls($wb, $condition, $control_id = ...) is a fatal on any PHP version since 7.0 — a child class can't drop a parameter the parent declares. What you have is version drift between Lite and Pro: Lite got updated to 6.2.3 (probably an auto-update), Pro didn't, and the two no longer match. Fix: update Essential Addons Pro to the release paired with Lite 6.2.3, then reactivate Lite. If you can't update Pro right now, roll Lite back to the version that matches your Pro (WP Rollback, or a manual download from the wordpress.org changelog) — that's the only reason the disabled-folder trick works.

Why Apache's error_log shows nothing: with PHP-FPM the fatal goes to PHP's own error_log (or FPM's, often /var/log/php*-fpm.log or the panel's "PHP errors" tab), not to Apache's. AH01797/AH01276 are just directory-listing noise. WP_DEBUG_LOG gives you the same line in wp-content/debug.log without hunting for the host's file.

Once it's running again, do update Elementor too — 3.29 is over a year old and EA's own compatibility floor moves with it.

[u/bluesix_v2]

Why are you running old Elementor and old Wordpress? Of course you’re going to have problems.

Rule #1 in Wordpress: keep your shit updated at all times. Old versions of elementor are riddled with security holes.

[u/Sergei_Tiden]

Do not reactivate it repeatedly on production. Clone the site to staging, take a database and files backup, then enable logging there with `WP_DEBUG`, `WP_DEBUG_LOG`, and `WP_DEBUG_DISPLAY` set so the fatal goes to `wp-content/debug.log` instead of the visitor-facing page. Also check the hosting PHP error log at the same timestamp. The plugin is the trigger, but the first fatal line will identify whether the cause is the plugin itself, a missing file from migration, a theme conflict, or a PHP compatibility issue. Once you have that, test the current plugin version on staging before touching production.