Skip Navigation

[Resolved] Elementor Pro and Views causing white screen

This thread is resolved. Here is a description of the problem and solution.

Problem:

There is a white screen when the Elementor Pro and Toolset are enabled.

Solution:

The minimum requirement for Toolset is 128M but I suggest that you increase it to 512M:

You can add this by adding the code below to "wp-config.php" file of your WordPress installation root folder:

/** Memory Limit */
define('WP_MEMORY_LIMIT', '512M');
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

Please add the code above the line below:

/* That's all, stop editing! Happy blogging. */

Relevant Documentation:

https://toolset.com/toolset-requirements/

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

This topic contains 1 reply, has 2 voices.

Last updated by Christopher Amirian 1 year ago.

Assisted by: Christopher Amirian.

Author
Posts
#2671223

The site was previously working with Toolset View and Elementor Pro but since upgrading Elementor the site now shows a white screen or critical error .

I have switched off all other plugins (except types) and tried alternative themes and this issue still happens.

#2671265

Christopher Amirian
Supporter

Languages: English (English )

Hi there,

According to the debug information provided, the plugin is the Elementor Pack Pro and not Elementor Pro. Elementor Pack Pro is another plugin which we do not have integration with.

First thing is to know what is the error instead of the white screen. Would you please access your website files and edit the "wp-config.php" file on the root folder of your WordPress installation and add the code below into the file:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true );

Please add the code above the line below:

/* That's all, stop editing! Happy blogging. */

Then share the error that you can see on the screen.

Thanks.

#2671275

Thank you - It was a memory issue - I have increased this and now all appears to be working. Fingers crossed it stays this way.