Vortex Radar

Wordfence is alerting to this issue now too.

https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/jquery-collapse-o-matic/collapse-o-matic-184-authenticated-contributor-stored-cross-site-scripting

Hopefully we can get an update soon to address this issue.

Thanks for checking in on that. I also see no issues in that AMP validator too. For some reason with Google, the AMP issues come and go even if I don’t change anything.

I’m testing now with the “AMP validator” extension for Chrome and it’s still reporting the issue, though now on line 128 instead. (I’ve been messing with stuff.)

Ooh it looks like you’re right @ipstenu! I tried disabling it just now and am browsing around. The admin pages are all now just working with no mess and no fuss! Thank you! ??

Hey Josh.

So the domains themselves are the same. I don’t see anything referencing the specific server or its IP address.

I migrated using VaultPress.

Cache was definitely cleared.

I just went in to check. wp-admin/ was 755 and wp-admin/*.php were all 644. wp-config.php is 400. I redid the chmod again anyway just in case.

Just putzed around a little more and I’m still getting the occasional 404.

Good idea. I just took a look at the Apache logs and here’s one that I just got:

End of script output before headers: update-core.php, referer: https://www.vortexradar.com/?s=update+core.php&search_404=1

Googling a bit, it looks like it may be a permissions error which could have happened when I transferred files from one server to the other. It’s odd that the error happens only sometimes while other times it works fine though.

@jamesosborne That’s so weird. I’m testing it again now and now it’s validating. I wonder why the results are inconsistent. I mean I’m glad it’s validating now, but that makes it hard to troubleshoot, heh.

@jamesosborne Yeah it looks like the number of pages with issues has gone down quite a bit, but I’m still seeing issues on a few such as this one. Same error saying “The parent tag of tag ‘noscript enclosure for boilerplate’ is ‘noscript’, but it can only be ‘head’.” when I test with the Google AMP tester.

@westonruter That’s great news. Thanks for the heads up!

It was Smush and its lazy load has since been disabled. That looks to have fixed about half of the validation errors, but Google is still complaining about the other half of the pages like this one.

That may have done the trick. I found a lazy load option in one of the plugins and disabled it and it looks like things are validating now. Thank you. ??

Oh, it looks like it affects individual posts, but not the home page. Sorry about that.

For example, here’s an AMP post and here it is failing the AMP validator.

huh well that is good news, haha. Thank you for checking.

If that’s the case though, why would I keep getting an error with Google Search Console?

Oh, and here’s the AMP link: https://www.vortexradar.com/?amp

Hello, as of about a week ago, I started getting the same error on vortexradar.com. I have lazy loading disabled on WP Fastest Cache and I don’t see any options to disable lazy loading in the AMP settings.

Is there a way to move this question to that section? If not, I can just mark it as resolved and create a new thread there.