feed corrupted, again
-
After essentially making any feed to the WordPress blog on my domain
essentially useless because it was hacked quite speedily after installing whatever was the latest version back last spring, I essentially started all over again. I was aided in this, in that my ISP, Web.com, gratuitously moved my site, the MySQL server and database, etc. to new servers, with new names for the schema, etc., new username, new password in mid-October.
Basically, I updated the W-P files to the latest release at the time (2.6.2) and re-initiated the blog. I have been slowly and laboriously adding old posts from the previous version of the blog, still sitting on the old server at Web.com (for however long they’ll let me do that before they discover the accessibility to the old schema, which they seem not to have moved successfully when they made the shift).
However, before I began this latter process, and after posting only one or two new posts to make sure the new setup was working properly, I have discovered an old problem, which I complained about last May. That is, the feed is corrupted, probably with a virtually endless set of ridiculous URLs to some obscure blog elsewhere in the world.
I don’t understand this vulnerability. I don’t understand how to correct it. I don’t understand how to prevent it. As I understood the explanation wiser heads than mine provided, it’s not my ISP. Somehow the feed itself is hackable. I think this puts it at the feet of WordPress.
Can someone please explain how this happens, and also offer some concrete practical suggestions on who can help me (even for money) first to fix the problem, and second to keep it from happening.
Thanks.
Howard
- The topic ‘feed corrupted, again’ is closed to new replies.