We have a client who wanted a 100% new website look in 2017. So we spent all of December and the first week in January building a beautiful new site using a Shaped Pixel Theme in one of our WordPress Website Models. Every page had an Elementor component or was 100% Elementor. Then we took the site live on January 6th. Everything worked perfectly.
Then yesterday the client asked us to update some pages since we do 100% of the site maintenance. Ouch! When we clicked on “Edit with Elementor” we got the WordPress White Screen of Death!
I put in a support ticket with the Elementor team and got back the usual drivel:
Please make sure you are using the latest versions of both Elementor (1.1.2) and Elementor Pro (1.0.8).
If the problem still occurs, try the following:
1. Could you try to deactivate all your plugins (besides Elementor) and see if it helps?
2. If it didn’t help, try to switch your theme to a default WP theme such as Twenty Sixteen.
If this issue continues, please send us your system info.
You can find it under Elementor > System Info.
Of course that is no help. Everything worked (and still works) perfectly on our dev server so it can’t be any of those. We had already told them that. ?
As is often the case, we figured that we better figure this out ourselves. So we setup a local instance of the site to investigate. Nothing, no problem on our local instance. So then we jumped onto their GoDaddy cPanel and checked out the error log. Aha, out of memory! Our dev servers and local instances all have a local PHP.ini file that allows for huge chunks of memory use in PHP.
The solution was clear: We added a directive to enable the Apache SuPHP (Single user PHP) handler. It executes PHP scripts so you can make settings from a local chosen php.ini file global for the entire account.
Then we added a local php.ini file with the increased memory settings.
; Resource Limits ;
max_execution_time = 120 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
;max_input_nesting_level = 64 ; Maximum input variable nesting level
memory_limit = 128M ; Maximum amount of memory a script may consume (16MB)
; Maximum size of POST data that PHP will accept.
post_max_size = 1000M
; Maximum allowed size for uploaded files.
upload_max_filesize = 1000M
; Default timeout for socket based streams (seconds)
default_socket_timeout = 300
; Maximum time (in seconds) for connect timeout. -1 means no limit
mysql.connect_timeout = -1
Boom! Works like a charm. This is a good example of the value we bring into the Minneapolis – St. Paul WordPress support market with our new company, Fast Fix Web Design, if you are asking about that! ?