Support

December 1, 2021 at 11:31 am

Hi Greyowl,

This does indeed look like an issue within Beaver builder.

I noticed you’ve marked the thread resolved, may I ask what the issue/solution was?

December 1, 2021 at 2:39 pm

It is indeed caused by the new version of EE.

The difference between the previous version and now is the Upcoming events widget has a private property called category. It’s not unusual for a class to have private properties but we can’t stop other plugins from trying to call those properties (which is what is happening here).

There must be something wrong in connection with “Cannot access private property EEW_Upcoming_Events::$category”

In English, the error is saying “Woah there class-fl-builder-model.php! You can’t access the private property $category within the EEW_Upcoming_Events class”.

Beaver builder is what is calling the category property on the widget and as it’s a private property (which can only be access by the class itself) the above fatal is thrown.

I downloaded the free version of Beaver builder and had a look at the code, this is what is throwing the fatal error:

/**
 * Returns an array of data for each core WordPress widget.
 *
 * @since 1.0
 * @return array
 */
static public function get_wp_widgets() {
	global $wp_widget_factory;

	$widgets = array();

	/**
	 * Array of known widgets that won't work in the builder.
	 * @see fl_get_wp_widgets_exclude
	 */
	$exclude = apply_filters( 'fl_get_wp_widgets_exclude', array(
		'WP_Widget_Media_Audio',
		'WP_Widget_Media_Image',
		'WP_Widget_Media_Video',
		'WP_Widget_Media_Gallery',
		'WP_Widget_Text',
		'WP_Widget_Custom_HTML',
	) );

	foreach ( $wp_widget_factory->widgets as $class => $widget ) {
		if ( in_array( $class, $exclude ) ) {
			continue;
		}
		$widget->class            = $class;
		$widget->isWidget         = true; // @codingStandardsIgnoreLine
		$widget->category         = __( 'WordPress Widgets', 'fl-builder' );
		$widgets[ $widget->name ] = $widget;
	}

	ksort( $widgets );

	return $widgets;
}

Beaver builder is calling all widgets, looping over them all and trying to set the category to ‘WordPress Widgets’here:

$widget->category = __( 'WordPress Widgets', 'fl-builder' );

Thats what is throwing the error, not Event Espresso and that is why you get the error on page with no connection to Event Espresso at all.

Having said that, I think we can change our property to something other than just ‘category’ to work around this, which is more of a workaround really, but should work.