|
lt3030
|
November 30, 2021 at 1:36 pm
Since the recent upgrade to version 4.10.19.p the Beaver Builder editor isn’t working. By deactivating plugins we were able to identify EE4 as the culprit. When EE4 has been deactivated the Beaver Builder editor works fine. We are running WordPress 5.8.2 on PHP 7.4.26. Any thoughts on how to fix this?
|
|
Tony
|
November 30, 2021 at 5:05 pm
Hi there,
What happens with Beaver Build when EE4 is active?
If you check the server’s PHP error logs does it show any errors from Event Espresso?
Which version of Beaver Builder are you using and what steps are you taking to trigger the error? I’ll check locally to see if I can reproduce it.
|
|
lt3030
|
December 1, 2021 at 5:15 pm
The Beaver Builder editor (/?fl_builder) does not activate/launch and takes us to a view of the live page. When we deactivate EE4 then we are able to edit pages with Beaver Builder as normal.
Running
WP v5.8.2
PHP v7.4.26
Astra Theme v3.7.5 with child theme
Beaver Builder Agency v2.5.0.2
Event Espresso v4.10.19.p
EE – Calendar (EE 4.3+) v3.2.15.p
|
|
Tony
|
December 2, 2021 at 4:32 am
This sounds like it’s the same issue reported by another user here:
https://eventespresso.com/topic/fatal-error-after-update-to-4-10-20-p/
In short, Beaver Builder is calling properties on all widgets and trying to set a ‘category’ property. In our upcoming events widget we now have a private property called category so when Beaver Builder tries to access it a fatal error is thrown.
We have changed the property name we use in the widget to work around this in the next version of Event Espresso.
|
|
Tony
|
December 2, 2021 at 1:53 pm
I’ve just pushed the update to fix this live (4.10.21.p)
If you don’t see it yet then go to Event Espresso -> General Settings, make no changes and just hit save to force an update check.
That should show the update in Dashboard -> Plugins.
Update the 4.10.21.p and that should resolve the fatal from Beaver Builder.
|
