No customizer option possible, fatal error
-
Hi,
I bought recently the Lay Theme,
but I failed to install it properly.
Once I try to access the "Customizer" I only get:
Fatal error: Class 'WP_Customize_Code_Editor_Control' not found in /homepages/33/d36894704/htdocs/wordpress/wp-content/themes/lay/customizer/assets/php/css.php on line 22
Installed on Wordpress 4.8
Because of that, I don't have any proper running website.
Need an advice to get it done.
Now it's installed on a test webspace:
josefschulz.de/wordpress -
Dear @JoeJoe
sounds like a server issue.
I just had a look here:
http://www.josefschulz.de/And this website is running…
Did you manage to solve the issue?
Best!
Marius
-
@mariusjopen
Hi Marius,
no, I'm not able to solve it.
The wordpress test site is in a subdirectory:
www.josefschulz.de/wordpress
You see now just this white blank page.
All other themes are working quite ok,
I'm testing there at first wordpress solutions.
Every time I want to access the customizer Menue,
I'm getting this fatal error notice:
Fatal error: Class 'WP_Customize_Code_Editor_Control' not found in /homepages/33/d36894704/htdocs/wordpress/wp-content/themes/lay/customizer/assets/php/css.php on line 22
Which doesn't allow me to set start pages.I'm able to create a project or page, but I'm not able to see a preview, this is just a blank page.
It's a 1&1 server, and I till now I had no problems with the wordpress testsite,
The fatal error leads to the css.php in Lay Theme, I'm not sure if I'm right with it.
Best
Josef -
@mariusjopen
Hi Marius,
I did a fresh wordpress install, and now its working.
http://josefschulz.de/wordpress
Server was ok, but there were some issues with wordpress,
couldn't find out which ones, but a fresh install helped and now its ok.
Thanks -
Before you post:
- When using a WordPress Cache plugin, disable it or clear your cache.
- Update Lay Theme and all Lay Theme Addons
- Disable all Plugins
- Go to Lay Options → Custom CSS & HTML, click "Turn Off All Custom Code", click "Save Changes"
This often solves issues you might run into
When you post:
- Post a link to where the problem is
- Does the problem happen on Chrome, Firefox, Safari or iPhone or Android?
- If the problem is difficult to explain, post screenshots / link to a video to explain it