Fatal error after pro update to 4.0.1 (Soliloquy)

Support
#23

Reporting the same issue here on pro v 4.08. Are you guys running another update?

#24

@rrhode I have this same issue - logged in a separate ticket - Fatal error: Soliloquy - where another user pointed me in the direction of your fix here.

I have added the code - but I’m still seeing the error. Please could you confirm if this is how it’s supposed to be added:

public function __construct() {
    
    if ( ! class_exists( 'Soliloquy_Common' ) && file_exists( ABSPATH . 'wp-content/plugins/soliloquy/includes/global/common.php' ) ) {
		require_once ABSPATH . 'wp-content/plugins/soliloquy/includes/global/common.php';

	// Load the base class object.
	$this->base   = Soliloquy::get_instance();
	$this->common = Soliloquy_Common::get_instance();

	// Register the main slider style.
	$this->stylesheets[] = array(
		'id'   => 'soliloquy-style-css',
		'href' => esc_url( add_query_arg( 'ver', $this->base->version, plugins_url( 'assets/css/soliloquy.css', $this->base->file ) ) ),
	);

	// Register main slider script.
	wp_register_script( $this->base->plugin_slug . '-script', plugins_url( 'assets/js/min/soliloquy-min.js', $this->base->file ), array( 'jquery' ), $this->base->version, true );

	// Load hooks and filters.
	add_shortcode( 'soliloquy', array( $this, 'shortcode' ) );
	add_filter( 'widget_text', 'do_shortcode' );

	add_action('wp_footer', array( $this, 'remove_no_js' ), 100 );

}

Many thanks in advance.

Fatal error: Soliloquy
#25

@markwest you did forget the closing }
with this it works:

	public function __construct() {

    if ( ! class_exists( 'Soliloquy_Common' ) && file_exists( ABSPATH . 'wp-content/plugins/soliloquy/includes/global/common.php' ) ) {
		require_once ABSPATH . 'wp-content/plugins/soliloquy/includes/global/common.php';
	}
	// Load the base class object.
	$this->base   = Soliloquy::get_instance();
	$this->common = Soliloquy_Common::get_instance();
#26

Hi Everyone,

We’ve corrected this for the next version that we will release after looking into a few more potential issues.

#27

Is that version 4.0.9?

#28

Hi Alexander,

the Version 4.0.9 fixed the fatal crash with soliloquy. Thank you!
Btw. really really great update!

cheers

#29

Hi Alexander,
i dont know what happened, but the error is back again. the update 4.0.9 does not fix the error.
can you investigate it?

thanks in advance

#30

Same thing here. Updating didn’t do anything. https://prof-rauch-hs-regensburg.de/
I had to manually disable the plugin for the time being. Can you please take a look at this.
Thank you very much.

#31

Can confirm, soliloqui is working (for me) with 4.0.9! (php7.4 and php8.0 tested)

#32

my config : (here it does not work)

Server-Architektur Linux 2.6.32-openvz-042stab127.2-amd64 x86_64
Webserver nginx/1.19.6
PHP-Version 7.4.13 (Unterstützt 64bit-Werte)
PHP-SAPI fpm-fcgi
Erweiterung mysqli
— —
Server-Version 10.2.17-MariaDB-10.2.17+maria~stretch
Client-Version mysqlnd 7.4.13

i also tried it nowq on a second server with this config, here it works:

Server-Architektur Linux 5.4.41-1-pve x86_64
Webserver Apache
PHP-Version 7.3.13 (Unterstützt 64bit-Werte)
PHP-SAPI cgi-fcgi
Erweiterung mysqli
— —
Server-Version 5.7.25
Client-Version mysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $
#33

Hi @deranaloge, @eckiles thanks for writing back with more info. I’m trying to find out why we’re not seeing a complete fix here. Here are some things that would help me narrow it down:

  • Are you using Pro or Cornerstone?
  • When do you see the fatal PHP error? WordPress admin, front end, in the builder? If there are specific URLs that would help.
  • Can you try testing for a plugin conflict? Deactivate all plugins that are not Cornerstone and Soliloquy, then see if the issue persists. If it starts working, begin activating plugins until the error comes back and it may reveal another plugin introducing a conflict.

Anyone else having the same issue, feel free to add your feedback as well based on those questions. Thank you!

#34

I just updated to 4.09 and the problem still persists. As soon as I activate the Soliloquy plugin there is a fatal error on both the front end and the backend. I tried the plugin testing you suggested and the problem still persisted.

#35

Same thing here… :point_up_2:

#36

hi alexander,

*i am using PRO
*as soon as the plugin is activated the fatal error is everywhere. frontend/backend
*i deactivated all plugins. deleted soliloquy, reinstalled it (all ok), then activated one plugin after the other and now it does work?

i dont get it. can anyone else with the error repeat the steps? deactivate all plugins, delete soliloquy and reinstall it, then activate all other plugins?

cheers

#37

Hi everyone,

We’re going to include another fix for this in the next point release this afternoon that should address the remaining cases.

#38

hi alexander,
thank you, the latest update did adress the error! :slight_smile:
cheers and merry xmas!

#39

Hi @deranaloge,

Great that it resolved now. And Merry Christmas to you too.

Thanks

#40

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.