Hi @johnmoody,
Thank you for writing in,
We have the search username as per your instructions. However, we have not found any issues in our testing environment. Could you kindly explain how to replicate such errors throughout the search?
Regards!
I have done more research on the problem. It may just be what happens when you search for something and there is no match on the site, e.g. searching for “zzyx” but it also happens for subscribers who haven’t provided any content, e.g. (on our site) “Pam Gully” or “Brenk1”. It seems to happen whenever there is no match to a search, i.e.
“404 Nothing Found
Sorry, but nothing matched your search terms. Please try again with some different keywords.”
with the message across the top
“Warning: Attempt to read property “post_content” on null in /homepages/20/d905201267/htdocs/clickandbuilds/TimesfortheTimes/wp-content/plugins/user-registration/includes/functions-ur-template.php on line 858″
Any help with this would be appreciated!
I’ve managed to suppress the warning by adding the following to my wp_config.php file…
ini_set(‘display_errors’,’Off’);
ini_set(‘error_reporting’, E_ALL );
define(‘WP_DEBUG’, false);
define(‘WP_DEBUG_DISPLAY’, false);
Nevertheless, there is clearly a bit of a bug your developers might like to look at.
John.
Hi @johnmoody,
Glad to know the issue is resolved. We will investigate furthermore if we are able to replicate the issue in our testing environment. We will fix it in our upcoming updates.
Regards!
