- This topic has 12 replies, 2 voices, and was last updated 3 years, 5 months ago by
.
-
Posts
-
Hi, first time testing this theme – I installed the free version but could not get into customising the theme. When I go to customize.php it gives me this error:
There has been a critical error on this website. Please check your site admin email inbox for instructions.
Learn more about troubleshooting WordPress.
I tried upgrading to pro but still get the same error.
all plugins off – just using your theme.
Is there a minimum requirement for php? I am using 7.3 which I realise is a couple behind but have attempted a server-wide change to php 8 this morning which broke most of my sites.
Customer Support
Hi there,
GP is compatible with PHP 7.x so that should not be an issue.
If you first go to Dashboard > Tools > Site Health – are there any issues being reported ?
Can you also ask your host to enable debugging on the server and get a report from the error_log so we can see what the critical error was.
Hi, site health all good.
Error log below in private info:
The first errors are pointing to the
class-wp-customize-nav-menu-item-setting.phpfunction. Which is related to the navigation menus, do you have any menus setup in Appearance > Menus ?Hi, yes, I had a menu set, also just tried creating a new basic menu with 1 menu item. The error still persists.
What happens if you DELETE any menus you have created ?
normal behaviour, menu deleted and gave me success message.
I’m trying this on an existing website on a development url. I am going to run some tests on a blank install and see what I get. I will report back. probably tomorrow now.
Thanks for help so far!
Let us know how you get on.
Hi, it seems to have worked on a blank install – I am going to investigate further – must be some sort of content on the site itself which is causing an issue – I’ll remove all menus and see how that goes.
I did a bit of googling on that error:
PHP message: PHP Fatal error: Uncaught Exception: Supplied nav_menu_item value missing property: description inNothing real concrete, but other users who experienced that issue were generally working with dynamically generated menu items or had functions that were pulling in CSS classes or other attributes such as the description.
Might give some pointers….
Hope you figure it out!
hi, I removed all menus and I can now get into customiser – not sure which entry it didn’t like but I can now test the theme at least.
: )
Glad to hear that!
- You must be logged in to reply to this topic.
