Very weird. Not sure where to start on that one. Have you altered anything recently?
I can’t think of anything. The only thing that I believe happened may have been an upgrade to MySQL from 1.8 to 2.0 in version.
Not very familiar with MySQL but maybe someone else is. Anyone…?
If you’re running WP 2.0.3, you may want to apply this:
http://txfx.net/code/wordpress/wordpress-203-tuneup/
I’m running 2.0.4 as of this morning. Its still doing it — it appears that it definately does it when you edit the timestamp to post into the future.
My latest post has had this problem again. Does anyone have any other suggestions? We’re running the latest version of MySQL, PHP and WordPress.
Thanks,
Philippe
http://blog.newdirectioninc.com
In general, this is a “mis-conjunction” in the charset your blog uses as opposed to the charset you’re using when you post. This can happen if you use something funky when compositing outside the blog interface, such as using ANYTHING with the program name “Microsoft” (wordpad, word, notepad) to composit offline, then upload to your blog.
If you MUST composit offline, download a truly vanilla editor such as notepad2 from http://www.flos-freeware.ch which will throw NOTHING extraneous into your text. Besides the obvious, notepad2 allows you to edit “natively” vbscript, js, java, php, etc.
I’m composing in the wordpress WYSWYG editor, at least 90% of the time. Any other ideas?
Nope. Don’t use the stupid thing. If you’re not copy n pasting, I don’t have any other ideas.
[Edit: I lied. Yeah, there is another possibility: it could be in one of the formatting plugins, like texturize, textile, etc. Do you have any of those?]
Page has 337 errors:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fblog.newdirectioninc.com%2F
Suggest you address those first, probably a cascading issue. Oh, and don’t use caps for xhtml.
Vkaryl — I don’t. There’s no formatting plugins at all.
Yosemite — I’ll work on them, but from the skim that I just did, most of them are caused by the editor apparently.
Hmm. Well, I still maintain that the wysiwyg causes more problems than it solves, and if it’s the root of your magnitude of errors in the validator, that would tend to prove the statement, ain’t?
Really, you are FAR more well advised to turn it off and post using the plain html with quicktags setup. I never use anything BUT that, and I have no problems such as you experience.
I’ll work on them, but from the skim that I just did, most of them are caused by the editor apparently.
Look closer, most of them are wp-notable related; Take a look at the <span>, it contains id’s that are used over and over again.
