Archived topic
Cannot get into Appearance > Customize because too many pages
10 replies · Started by Steve on October 1, 2021
Hi,
The site has 196,077 pages. I *think* what is happening is Appearance > Customize is trying to load data from all the pages in the off chance that I want to manage Menus. But I have a custom menu, that accounts for just a few pages.
It seems Appearance > Customize should take that custom menu.
Interestingly, I can open Appearance > Menus without a problem.
Hi there,
to test the theory you could remove the Menu Component from the Customizer.
This stackexchange provides the PHP Snippet for that:
Well - that didn't work. Any ideas? I honestly believe it has to do with the number of pages. I've disabled plugins just to make sure - and that didn't make a difference.
Not getting any errors in the browser console, although the browser is complaining of High CPU requirements, which kinda says something just dumped a tonne of code that its having to compile and execute... not sure what that could be as the Theme wouldn't do that.
Before getting into that muddy water, try increasing your server PHP Settings.
See here for a link to my basic settings which is for normal size sizes but has more Memory and Time outs then your current site does:
I did this in functions.php:
set_time_limit(0);
ini_set("memory_limit", "2G");
Still getting "Aw, Snap! Something went wrong".
This is a dedicated server with lot's of resources. I'd be happy to turn something on to capture helpful information.
How do you use the customize_loaded_components filter to also not load widgets? I figure I can remove what is not needed, one at a time, and see if it helps.
That didn't work, either. What could be happening here?
Hard to say. The browser is maxing out the CPU so it could be a Javascript looping infinitely thats blocking the render or even the PHP requests. Could you move to a staging site and disable ALL plugins and any custom functions/scripts to see if the customizer then loads ?
I (sort of) found it. The Rover IDX plugin (of which I am the author) was initializing widgets during the Appearance > Customize load. Disabling the init of those widgets solves the issue. Scratching head...
Glad you found it!
Maybe the Query Monitor Plugin will give some insight as to whats going on behind the scenes.
