DocSheldon

Found it, Slobodan! I was wrong, the data that was being displayed WAS in the DB. In the zzt0p_usermeta table. Now I just need to find how THAT was being called, rather than the user profile info.

Yeah, I saw how it calls it calls it, which is what blew me away when I found her bio empty. I’ll do some more digging and let you know what I find. Thanks, Slobodan!

I suppose I could simply disable FAB for her posts, but I prefer not to have to do that. And I’d really like to know where this bio data is being imported from.

Thanks for the response, Slobodan. Unfortunately, this isn’t my profile, it’s that of my departed partner, who still has several authored posts on the site. And when I visit her profile page, the bio block is totally empty.
What really surprised me was that an exact match search of my database didn’t find the information that is currently appearing in her FAB on her posts.

Sorry, Peter, for failing to get back to you. NO, I did not get any notification email. I have deactivated the plugin, as I didn’t have time to investigate further. At this point, we’re undergoing some redesign, so maybe we’ll find the issue while debugging.

Thanks for responding, Peter! I’ll keep digging and if I learn what the problem is, I’ll post it back here.

Cheers!

Okay, now it got strange, Peter. I did as you said and the Fetch as Google worked, twice in a row. I then went to the Mobile-Friendly testing tool, and it failed. After that, the Fetch as Google tool again finds the domain unreachable.
It doesn’t seem likely, but it would appear that testing with the Mobile-Friendly tool triggered something that then blocks GoogleBot!

I did that, Peter. And I have no cache plugin on the site, and I also checked to ensure that my host wasn’t caching it. The only thing that I’m seeing that might have something to do with an incompatibility issue is that my host is running php v. 5.2.17… could that possibly be it?