gbps
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseMarius you have cracked it!!!
I tried re-saving the menus which didn’t fix the problem so I deleted the primary menu and the 2 that weren’t in use and created a new menu from scratch. Now the theme customiser works. Thanks so much for your help.
Also James Huff, thanks for your suggestions too.
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseWhen I rename .htaccess to htaccess it doesn’t make any difference to the theme customizer, I still get the error, but renders most of the site un-accessable except for the front page.
I tried a new wp-config.php file from the sample too. The theme customizer still shows the fatal error.
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseI have had a response from the webhosting company: –
I have double checked your issue and I’m afraid that this is a coding related issue. As this is not a platform related error, it will not appear on our logs.
I have also tried to change the version of PHP used by your hosting package to 5.4 and 5.5, however this has also not solved the issue.
I have then also checked the file class-wp-customize-nav-menu-item-setting.php on line 191 as advised by the error message.
If you check it yourself, you will see that the script checks to ensure that an initially-supplied value is valid. As the value is not valid, this message is displayed.
Therefore, there is an issue with a setting made by you in WordPress or the core files of the theme you are using.It can’t be a problem with the core file of the theme as it happens on all themes. But it has got me wondering if something I have amended on one of the other files is causing the problem. For instance I had added Future Expires Headers to the .htaccess file. I have replaced .htaccess with a backed up copy I had. And same for wp-config.php which hasn’t fixed it.
When I did a manual update of wordpress it instructs you not to delete wp-content folder as obviously this is the content of the website so could it be something in there causing problems?
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseYes, same error message.
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseI’ve tried chasing this up with the hosting company (123 reg) but they just give standard answers and ask me to reinstall wordpress manually over and over.
Their latest response is: –
The error logs are not displaying any errors. This indicates that the issue is not related to your hosting package.
Please try to perform another manual WordPress updated in order to see if this will fix the error that you are receiving. This can be done by following this article: https://codex.wordpress.org/Updating_WordPressIf we can be of any further help with regard to this or any other matter, please do not hesitate to contact us.
I just did a manual wordpress update. I still get a fatal error message when trying to customise any theme, but it has changed slightly: –
Fatal error: Uncaught exception 'Exception' with message 'Supplied nav_menu_item value missing property: description' in /websites/123reg/LinuxPackage23/go/od/bo/goodboypetservices.co.uk/public_html/wp-includes/customize/class-wp-customize-nav-menu-item-setting.php:191 Stack trace: #0 /websites/123reg/LinuxPackage23/go/od/bo/goodboypetservices.co.uk/public_html/wp-includes/class-wp-customize-nav-menus.php(551): WP_Customize_Nav_Menu_Item_Setting->__construct(Object(WP_Customize_Manager), 'nav_menu_item[6...', Array) #1 [internal function]: WP_Customize_Nav_Menus->customize_register(Object(WP_Customize_Manager)) #2 /websites/123reg/LinuxPackage23/go/od/bo/goodboypetservices.co.uk/public_html/wp-includes/plugin.php(525): call_user_func_array(Array, Array) #3 /websites/123reg/LinuxPackage23/go/od/bo/goodboypetservices.co.uk/public_html/wp-includes/class-wp-customize-manager.php(583): do_action('customize_regis...', Object(WP_Customize_Manager)) #4 [internal function]: WP_Customize_Manager->wp_loaded('') #5 /websites/123reg/L in /websites/123reg/LinuxPackage23/go/od/bo/goodboypetservices.co.uk/public_html/wp-includes/customize/class-wp-customize-nav-menu-item-setting.php on line 191Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseYes that’s the fatal error that is causing me the problems and not allowing me to customise the site. I still get it. But the error logs are empty 🙁
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseAfter a long drawn out process with the web hosting company they say: –
Our system administrators have found that the logs for your account were disabled, however, these have now been enabled and should take about 24 hours to generate.
After a few days they were blank so I chased them up and their response was: –
I can see that the access logs are displaying successfully and so is the website, therefore, there are no more errors to display.
If the website will show any errors in the near future and these won’t appear in the error logs, please let us know so that we may further look into the issue.If we can be of any further help with regard to this or any other matter, please do not hesitate to contact us.
—————————–
Any ideas?
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseThe strange thing is I have a second site on the server, and don’t get the same error on the customisation menu. I have even tried deleting the second sites files which didn’t help.
I had been in touch with my hosting company 123-reg about this. Their last response was this:-
“Most of the form pages related to the errors you are encountering advise on deactivating all your plugins: https://wordpress.org/support/topic/fatal-error-1830, however since you already tried this, at this point I would strongly recommend you contact a web developer which should help you resolve the issues you are currently encountering.
I am afraid that coding related matters such as this one are a little outside our area of expertise.
If we can be of any further help with regard to this or any other matter, please do not hesitate to contact us.”I have copied your response to them about it looking like a PHP or server configuration issue but based on their last response I don’t hold out much help
Thanks for your patience and advice. If you or anybody else has any other suggestions it would be appreciated.
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseI have followed the instructions from the webhost on how to view error logs but they are blank unfortunately.
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomisePHP/5.3.29
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseI renamed .htaccess to htaccess, updated the wp-config-sample.php with the database connection details and put it on the server as wp-config.php but still have the same fatal error message.
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseI renamed .htaccess to htaccess but it makes the website unaccessable. Via either the website at http://www.goodboypetservices.co.uk or http://www.goodboypetservices.co.uk/wp-admin
I tried making a new wp-config.php file using the wp-config-sample.php file but then when I go to the website I get the following message: –
Error establishing a database connection
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseI tried that twice. I still get the same error. Which makes me wonder if it’s something in the wp-config.php or .htaccess files (Or one of the files that I keep when I do a reinstall) that is causing the problem?
What if I deleted every file on the server (I’ve backed it up via FTP) and do a new install of wordpress and import the backed up database. And start from fresh, that could be worth a try? I believe I won’t lose anything that way?
Forum: Fixing WordPress
In reply to: Fatal error on Appearance > CustomiseHi James, I have already tried deactivating all plugins which didn’t resolve the issue unfortunately.
It’s not theme specific either as I have tried other themes including Twenty Fifteen and still get the same error message.
Any other ideas?