PHP Notices, Warnings

Hi

1.I get php warnings whenever i get in to customize mode on my website and I get these notices on the top of my page

Notice: Trying to get property of non-object in /home/ulook/public_html/wp-includes/nav-menu.php on line 821

Notice: Trying to get property of non-object in /home/ulook/public_html/wp-includes/nav-menu.php on line 821

Notice: Trying to get property of non-object in /home/ulook/public_html/wp-includes/nav-menu.php on line 825

See attachment1

2. I keep getting these php warnings in my error log

[10-Mar-2019 17:40:11 UTC] PHP Warning: strstr() expects parameter 1 to be string, object given in /home/ulook/public_html/wp-includes/functions.php on line 930
[10-Mar-2019 17:40:11 UTC] PHP Warning: stripos() expects parameter 1 to be string, object given in /home/ulook/public_html/wp-includes/functions.php on line 936
[10-Mar-2019 17:40:11 UTC] PHP Warning: stripos() expects parameter 1 to be string, object given in /home/ulook/public_html/wp-includes/functions.php on line 939
[10-Mar-2019 17:40:11 UTC] PHP Warning: strpos() expects parameter 1 to be string, object given in /home/ulook/public_html/wp-includes/functions.php on line 946
[10-Mar-2019 17:40:11 UTC] PHP Warning: explode() expects parameter 2 to be string, object given in /home/ulook/public_html/wp-includes/functions.php on line 947

I deactivated plugins and they still happened
I changed theme and stopped

Please help me solve these problems.
Thank you

Attachments:

You must be logged in to view attached files.

Hi,

Please, send us an exact algorithm of how to reproduce them on your website. Then, deactivate all the installed plugins as well as the child theme and send us your admin and FTP access.

Thank you

For the first three notices (1) it happens whenever I get in to customization mode for home page or any page.

The others (2) I get them on my server error log no matter what I do….

Ive deactivated all plugins and disabled child theme..

Please let me know as soon as you check the problem, as I can only keep the website like that for a few hours…

Thank you

I will restore my website now and maybe set it up on a demo domain so you can check it there

OK, send us the actual data where should we troubleshoot it. Also, provide us an access your to the error logs.

Hello can you please check now on the actual website?
The error log is accessible via FTP in the public html
Thank you

*I can leave the live website like that for approximately the next 12 hours, I it is enough

*I hope it is enough

Hello,

We can’t enter your dashboard and connect your FTP with the data you sent.

Regards

Sorry, please try again

Also FTP works fine, just checked it

Sorry, but we still can’t access.

I have reset your password and checked again

We see that those errors are not related to the theme and exist with default theme as well.

This Applies to no1 and no2 php errors?

Only the first one. We don’t see that 2nd errors appear in the error logs now.

there are in error log, please check it via ftp….
I ve been trying so long to find out whats wrong

But we don’t see errors from the last few days. They are outdated.

Did you see the screenshot attached?

[08-Apr-2019 13:05:05 UTC] PHP Warning: explode() expects parameter 2 to be string, object given in /home/ulook/public_html/wp-includes/functions.php on line 947

I deleted the old error log, these are all from today until a couple of moments ago

We didn’t see the screenshot because you didn’t upload it. OK, please, disable all external plugins and remove the current error log so we can check.

Ok I have left all external plugins disabled.

Sorry for not uploading the file, but have no idea why it was not posted…

I post it here

We have fixed it on your website. Please, test it some time and see if the error doesn’t appear again.

OK I will check it, but may I know the source of the problem and the modifications you made?

I’ve been trying to debug this thing since several months……

Thank you

We don’t know why it happened on your website and it was very hard to reproduce. Anyway, we fixed it on your side.

[Author]

Posts