Skip Navigation

Fatal error on customizer page after updating to Elementor 3.5



With the Elementor 3.5 update, when you go to Appearance > Customize the page does not load and a fatal error occurs:

PHP Fatal error:  Uncaught Error: Call to undefined method Elementor\Utils::is_ajax() in .../wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/interop/handler/elementor/widgets/view/view.php:376


Fixed in Toolset Blocks 1.6.2

10 thought on Fatal error on customizer page after updating to Elementor 3.5

  • I have the same kind of error but I don’t have a php error message. Instead it’s a wp view message (critical error). So I can’t identify where to replace the view file. I tried in the folder indicated above without success.

    • Details of the PHP error will be in your debug log.

      If you haven’t already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

      define(‘WP_DEBUG’, true);
      define(‘WP_DEBUG_LOG’, true);
      define(‘WP_DEBUG_DISPLAY’, false);

      That will create a debug.log file in your /wp-content/ directory which you can examine in any text editor.

      Try the same steps which cause the error then inspect the log.

  • When do you expect to patch this officially? It’s really cumbersome to patch this manually on multiple sites. Also, something might have been updated on Elementor because the patch does not correct the problem every time. – This fix works on a few of my sites but other sites I am managing aren’t fixed by the patch.

  • I’m wondering when an update for this will be released as well. I am turning on and off the plugin whenever I need to use the Customizer which is not ideal.

  • The fix for this is included in Toolset Blocks 1.6.2 which has just been released.

    If you don’t see an update notice on the plugins page, go to the custom Toolset installer page (via the registered link) and click the Check for Updates button.

    Or download the zip file from

  • We have the same issue. Verified by disabling toolset and Customizer loads. We have updated to the latest versions: Toolset Types 3.4.7 / Toolset Views 3.4.2

    The issue still persists. Any ideas?

Comments are closed