lmfoster

Thanks Mark. What I can’t figure out is WHY this URL is included in my sqlbackup file. Other than having the plugin Yoast (which is where I believe the URL came from), there is nothing on my site that is referencing that domain. So in theory, the only way I could have protected my site was to remove the Yoast plugin since that’s where it looks like the domain was being referenced, correct? I’m fairly new to WordPress, so just want to make sure I understand how to protect my site. When this occurred, I didn’t have a clue how I’d fix it since it was only showing up as in issue in my backup. I was in a panic worrying I’d also get blacklisted by Google. BTW, I LOVE Wordfence! ??

Wordfence is no longer reporting this as an issue in my backups?

I’m having the exact same problem reported in my sql backups starting with my files on July 20th. I run a backup once per week(and I’ve never used a Weaver theme). Only thing I haven’t done is dig into the sql file to locate where the error is generating from. But I’m assuming it’s the same issue as I also use Yoast.

I’m having the exact same problem reported in my sql backups starting with my files on July 20th. I run a backup once per week(and I’ve never used a Weaver theme). Only thing I haven’t done is dig into the sql file to locate where the error is generating from. But I’m assuming it’s the same issue as I also use Yoast.