|
smdawg
|
November 23, 2021 at 5:16 pm
We are currently seeing some errors with Beaver Builder that we have not seen previously.
During our investigation, we see the following information in the log files:
[23-Nov-2021 20:44:22] WARNING: child 25205 said into stderr: “NOTICE: PHP message: PHP Warning: Use of undefined constant EE_FRONT_AJAX – assumed ‘EE_FRONT_AJAX’ (this will throw an Error in a future version of PHP) in /www/wp-content/plugins/eea-wp-user-integration/EED_WP_Users_SPCO.module.php on line 121”
24.126.169.210 – 23/Nov/2021:20:44:20 +0000 “POST http://www.ceucreationsinc.com/wp-admin/admin-ajax.php” 200 /www/.wordpress/wp-admin/admin-ajax.php 107466360 3145272 3628.273 2048 15.71%
[23-Nov-2021 20:15:44] WARNING: child 24939 said into stderr: “NOTICE: PHP message: PHP Fatal error: Uncaught Error: Cannot access private property EEW_Upcoming_Events::$category in /www/wp-content/plugins/bb-plugin/classes/class-fl-builder-model.php:3685”
Can you please provide some additional information into these variables: EE_FRONT_AJAX and EEW_Upcoming_Events?
Any direction/guidance is greatly appreciated.
|
|
Tony
|
December 2, 2021 at 7:37 am
Hi there,
Apologies for the delayed reply, we’ve been investigating these issues and have a fix.
The first issue (warning about EE_FRONT_AJAX) should be fixed in the current version of Event Espresso available and the EEW_Upcoming_Events issue will be fixed in the next update we push live (4.10.21.p).
The EE_FRONT_AJAX warning was due to a change in how EE handles the requests in 4.10.14.p, we fixed that in version 4.10.17.p
The EEW_Upcoming_Events error is due to an issue within Beaver Builder, the latest versions of Event Espresso have a private property set within the upcoming events widget call category. Beaver Builder is looping over all widgets on the site and trying to set the category property on all of them, which then throws a fatal error on EEs widget (private properties can only be accessed by the class itself). In the next version of Event Espresso we’ve changed the name of the property the widget uses to work around that.
|
|
smdawg
|
December 2, 2021 at 1:22 pm
Thank you for the information, Tony.
So, will both issues be resolved in build 4.10.21.p? FYI, I have 4.10.18.p installed and am seeing the EE_FRONT_AJAX warning. But since it is a warning, that’s probably not causing the issue that I am seeing.
So, will that widget issue (private property) be fixed in 4.10.21.p? Or when will that fix be available? Is there a way for me to go back to a version of EE that works with Beaver Builder until the fix is available? Right now, EE is working for us but we are extremely limited in what we can do with creating new pages without BB. So, the front-end is working for our customers, but we cannot make page updates on the back-end.
Please advise.
Thank you, Steve
|
|
Tony
|
December 2, 2021 at 1:53 pm
FYI, I have 4.10.18.p installed and am seeing the EE_FRONT_AJAX warning. But since it is a warning, that’s probably not causing the issue that I am seeing.
Hmm, strange. I’m not getting that on my test sites…. I’ll check into this again.
So, will that widget issue (private property) be fixed in 4.10.21.p?
Yes and I’ve just pushed that update live.
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.
|
|
smdawg
|
December 2, 2021 at 2:38 pm
Thank you, Tony and team!
I was able to successfully upgrade EE to 4.10.21.p and everything is working perfectly now! Whew!
Thanks so much for the quick turn-around and getting this fix out there.
|
|
Tony
|
December 2, 2021 at 2:55 pm
Great, I’m glad it worked.
Is that version still throwing the EE_FRONT_AJAX warning on your site?
|
|
smdawg
|
December 3, 2021 at 8:22 am
Sorry for the delay, Tony. I wanted to wait to get a fresh set of logs to be sure I wasn’t picking up an old message.
I AM still seeing that error. Here is an example:
WARNING: child 3110 said into stderr: “NOTICE: PHP message: PHP Warning: Use of undefined constant EE_FRONT_AJAX – assumed ‘EE_FRONT_AJAX’ (this will throw an Error in a future version of PHP) in /www/wp-content/plugins/eea-wp-user-integration/EED_WP_Users_SPCO.module.php on line 121”
I have not looked at every message, but I did take a look at about 20 of them and all are referencing that same php file.
Thanks for looking into this.
|
|
Tony
|
December 3, 2021 at 8:33 am
Ok, thank you for checking.
I’ll do some digging into this and see if I can reproduce, not sure why I’m not already really as if the definitions aren’t loading are should be getting that notice.
Anyway, now I know its still a ‘live’ issue I’ll see what we can do.
(Side note for any future readers, the warning will not cause any issues on the site currently, in English its basically saying ‘Hey this isn’t right but I know what to do with it anyway!’)
|
