Brian Layman wrote:
There were three things I wanted to look into for the 2.0.4 beyond just getting a chance to try to exploit it. With 2.0.3, I was getting an error on manage post screens. I had a post title with the ASCII for a quote in it. That, for some reason, caused the onclick JavaScript to blow up expecting a ). I guess it was interpreting the ASCII code for a real quote and the tune-up plugin didn't handle it much better. With the plug in installed, I could put a real quote in the title again, but the manage page still had the script error. 2.0.4 seems to handle this correctly. I haven't been able to duplicate this since the upgrade.
Yes, we fixed several JS escape bugs in 2.0.4.
The next thing was an error, in version 2.0.4, that I could not isolate it last night. I had a post with links to just under 30 other blog articles. Until the pings were actually processed, which seems to have been done correctly, every save action generated an error at some irrationally high character position, like line 89 character 18,410. I can reproduce this even now by copying the contents of that post into a new post and hitting save or by navigating off that page. In ie's postdata, the content parameter is 108,000 characters long. The postdata itself is a full 11430 characters. So compared to that 18410 isn't that far into the data if you look at it that way. The error is in post.php Object expected, code 0 character 18410. The published version of that post doesn't get the error and neither do other posts without the links to other blogs.
Curious. I'll try to reproduce, but a fix probably won't make it into 2.0.4.
_______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
