wsdl error: XML error parsing WSDL from https://sna.etapestry.com/v2messaging/service?WSDL on line 1: Not well-formed (invalid token)
Turns out: totally not worth the effort in this case.
I’m working on an NPO site right now whose code concerns me more and more as I get into it. I’m new to the group and don’t have a whole lot of time to devote to the site, but one of my first tasks was to get the owner’s recent Tumblr posts to show on the homepage.
- Windows 7: PHP can’t connect to localhost for mySQL – An issue that I have good reason to suspect has tied up a dev or two for many hours. Windows 7 needs to have a certain entry in the hosts file uncommented to allow PHP to connect to localhost.
- Why I’d Rather See My Book in a Public Library than a Large Bookstore By Stephanie Ann – A really nice perspective on how to distribute books. If you're writing a book on frugal living, are you still trying to make a living off of it?
- Spinning right wrong – Heather spins a great tale. "But then an alien spaceship flew down from the sky, aimed a laser at my head and sucked my brain out through the top of my skull. Leaving me no option other than to join the spin class that had just started. The one being taught by General Patton."
- Big Fat Deal » The Myth Of Fat In The Black Community – A nice article and discussion on the difference between being "thick" and being "fat" when you're black.
- Direct Selling on Amazon – Advantage vs CreateSpace – A pretty nice comparison of two self-publishing options, including fun mathematical formulas for profit.
I just found a creepy case of injection in my index.php file. I noticed this morning that my homepage was throwing a “headers already sent” message pointing to index.php, line 10 when it wasn’t cached by Supercache. A reload of the page cleaned it up. But my RSS feed (which currently goes through Feedburner) was also trashed, and /feed wasn’t redirecting. All with the same error. Disabling Supercache fixed the homepage warning, but not the feed.
Being PHP awesome, I checked index.php for trailing whitespace, and found this snippet of code above the standard WordPress code:
A few things to note:
- My SSH/bash history is complete and untouched. That is, I can see back for weeks, and all the commands are mine. So it doesn’t seem to be that sort of break-in.
- I just upgraded to WP 2.9.2 yesterday through the admin console. Likely culprit? Probably.
Can’t say for sure what it was, since I didn’t do more than a cursory check after I upgraded. The homepage would have been cached, so I wouldn’t have seen the warning there.
I suppose I should report this.