Vibe Custom Types Plugin v3.9.9.3 is causing fatal critical error and crash the site with the latest Elementor plugin v3.11.0.

We need the Vibe Custom Types Plugin as we are using WPLMS 4.800 Legacy.

Please help urgently.

We have upgraded Vibe Custom Types Plugin to version 3.9.9.8 and also upgraded Elementor and elementor pro to the lastest version 3.11.1. The issue still persist causing fatal error with Vibe Custom Types Plugin.

PHP: 2023-02-14 12:59:51 [error X 211][/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php:339
Stack trace:
#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/includes/elementor/fix.php(10): Elementor\Frontend->__construct()
#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/vibe-customtypes.php(44): include_once('/opt/bitnami/ap...')
#3 /opt/bitnami/apps/wordpress/htdocs/wp-settings.php(447): include_once('/opt/bitnami/ap...')
#4 /opt/bitnami/apps/wordpress/htdocs/wp-config.php(119): require_once('/opt/bitnami/ap...')
#5 /opt/bitnami/apps/wordpress/htdocs/wp-load.php(50): require_once('/opt/bitnami/ap...')
#6 /opt/bitnami/apps/wordpress/htdocs/wp-admin/admin-ajax.php(22): require_once('/opt/bitnami/ap...')
#7 {main}
  thrown [array (
  'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-14 13:00:49 [error X 13][/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php:339
Stack trace:
#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/includes/elementor/fix.php(10): Elementor\Frontend->__construct()
#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/vibe-customtypes.php(44): include_once('/opt/bitnami/ap...')
#3 /opt/bitnami/apps/wordpress/htdocs/wp-settings.php(447): include_once('/opt/bitnami/ap...')
#4 /opt/bitnami/apps/wordpress/htdocs/wp-config.php(119): require_once('/opt/bitnami/ap...')
#5 /opt/bitnami/apps/wordpress/htdocs/wp-load.php(50): require_once('/opt/bitnami/ap...')
#6 /opt/bitnami/apps/wordpress/htdocs/wp-cron.php(46): require_once('/opt/bitnami/ap...')
#7 {main}
  thrown [array (
  'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-15 11:45:27 [error X 25][/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php:339
Stack trace:
#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/includes/elementor/fix.php(10): Elementor\Frontend->__construct()
#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/vibe-customtypes.php(45): include_once('/opt/bitnami/ap...')
#3 /opt/bitnami/apps/wordpress/htdocs/wp-settings.php(447): include_once('/opt/bitnami/ap...')
#4 /opt/bitnami/apps/wordpress/htdocs/wp-config.php(119): require_once('/opt/bitnami/ap...')
#5 /opt/bitnami/apps/wordpress/htdocs/wp-load.php(50): require_once('/opt/bitnami/ap...')
#6 /opt/bitnami/apps/wordpress/htdocs/wp-admin/admin-ajax.php(22): require_once('/opt/bitnami/ap...')
#7 {main}
  thrown [array (
  'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-15 11:46:05 [error X 4][/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php:339
Stack trace:
#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/includes/elementor/fix.php(10): Elementor\Frontend->__construct()
#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/vibe-customtypes.php(45): include_once('/opt/bitnami/ap...')
#3 /opt/bitnami/apps/wordpress/htdocs/wp-settings.php(447): include_once('/opt/bitnami/ap...')
#4 /opt/bitnami/apps/wordpress/htdocs/wp-config.php(119): require_once('/opt/bitnami/ap...')
#5 /opt/bitnami/apps/wordpress/htdocs/wp-load.php(50): require_once('/opt/bitnami/ap...')
#6 /opt/bitnami/apps/wordpress/htdocs/wp-cron.php(46): require_once('/opt/bitnami/ap...')
#7 {main}
  thrown [array (
  'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-15 13:44:12 [error X 1][/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php:339
Stack trace:
#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/elementor/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/includes/elementor/fix.php(10): Elementor\Frontend->__construct()
#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/vibe-customtypes/vibe-customtypes.php(45): include_once('/opt/bitnami/ap...')
#3 /opt/bitnami/apps/wordpress/htdocs/wp-settings.php(447): include_once('/opt/bitnami/ap...')
#4 /opt/bitnami/apps/wordpress/htdocs/wp-config.php(119): require_once('/opt/bitnami/ap...')
#5 /opt/bitnami/apps/wordpress/htdocs/wp-load.php(50): require_once('/opt/bitnami/ap...')
#6 /opt/bitnami/apps/wordpress/htdocs/wp-blog-header.php(13): require_once('/opt/bitnami/ap...')
#7 /opt/bitnami/apps/wordpress/htdocs/index.php(17): require [array (
  'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]

Please look into this ugently.

Will it be released for WPLMS 3.9.9 as well?

Thanks

I'm not getting any update notification, even for the older version

Hi Alex,

any update on the availability?

Thanks!

Hi Alex, 

sorry to bother but few days ago a new vulnerability that afflicts sites using Woocommerce and Elementor pro <= 3.11.6 has been discovered, and there is evidence of many attacks using it.

All sites still using WPLMS 3.9.9 and Elementor Pro need to upgrade to Elementor Pro 3.11.7 at least, but at the moment is impossible for the mentioned reasons.

Is there an ETA for the upgraded Custom Types Plugin?

Thanks

Facing the same error. Need update asap.

Yes, i got hacked due to this! An update is really urgent. 

For everyone involved, the only way at the moment to avoid risks is to manually patch Elementor Pro. I know it's not the best way but it could save many headaches.

You need to edit the file elementor-pro/modules/woocommerce/module.php

look at this part

public function update_page_option( $data ) {   update_option( $data['option_name'], $data['editor_post_id'] );
}

and change with:

public function update_page_option( $data ) {
		$is_admin = current_user_can( 'manage_options' );
		$is_shop_manager = current_user_can( 'manage_woocommerce' );
		$is_allowed = $is_admin || $is_shop_manager;
		if ( ! $is_allowed ) {
			return new \WP_Error( 401 );
		}
		$allowed_options = [
			'woocommerce_checkout_page_id',
			'woocommerce_cart_page_id',
			'woocommerce_myaccount_page_id',
			'elementor_woocommerce_purchase_summary_page_id',
		];
		$option_name = $data['option_name'];
		$post_id = absint( $data['editor_post_id'] );
		if ( ! in_array( $option_name, $allowed_options, true ) ) {
			return new \WP_Error( 400 );
		}
		update_option( $option_name, $post_id );
	}

now you are good to go, at least until things get fixed.

Any update?

Yes, I have this issue as well - now I am in a bad position - my site won't work with new Elementor, and the old one has a security issue. Any updates?

It's been 5 months after the first issue report and still no action.

At least let us know if there is any intention to solve it, otherwise we can plan different strategies.

Please do not forget that we all have businesses running on top of WPLMS.

Thanks.

Hi Ripul,
Any update on this?

Seems like they don't care about this.

Does anyone else have a solution to this?

I'm not sure they are still reading tickets issued by this platform. They stated somewhere tu use the WPLMS forum again.

Anyway we are considering to move away from WPLMS, it will be a long journey since we have quite a lot of customizations, but I'm quite fed up with these people

"We're still working on this."

The issues was reported back in February and it's almost September..

I kindly request an estimated timeframe for when we might expect a fix or an update. Our website relies heavily on both these plugins, and having a tentative ETA would greatly assist us in planning our operations and managing user expectations.

Thank you for your attention to this matter. We appreciate the hard work and effort the team puts into this. Looking forward to your prompt response.

Regards

Dear Ripul,

after more than one month still no progresses or update (the issue was reported 8 months ago)

Please be transparent: will you solve the problem ever, or do we have to find out workarounds by ourselves?

I think, as clients, we at least we deserve an honest statement.

Thank you

It is a disgrace that this hasn't been repaired - yet.

Still no update on this issue?