HTML Codes in Posts

Your refferring to ascii codes right?

Well, you could have done what I just did to find the solution.

Open up your dashboard, edit your post, and go into your html mode.

type your ” ” into your post

then preview the post, look for the area of where you put your ” “‘s at, that is where you answer will be revealed.

I’ve done the step by step to this, but a job is more rewarding when you find the answer ??

Ok, thanks for your commentary “kreativjustin”.

I am referring to html codes (which is what they are most commonly referred too). Some people do refer to them as ascii codes — so you are correct…we’re talking about the same thing.

As for my post, the spirit behind my question was this — “I am curious how WordPress handles embedded html codes inside the posts during database upgrades and conversions.“

I have been using them often so I know what they look like when the page renders in the browser.

I am just wondering how WordPress handles them when an upgrade/update occurs and the tables get altered. I found strange things happening as I stepped through 8 upgrades over the past couple weeks (from 2.1.1 to 3.1) and was thinking that the backend upgrade wasn’t translating the html codes correctly for me.

I just spent a ton of hours cleaning them up so I am very hesitant to now go to version 3.1.1 (yes, I know to backup my db).

Again thanks for helping out.

I did some digging on google, it seems to be a common problem. I can only recommend Google ??

So are you suggesting that having the html codes embedded in posts will, in fact, result in problems when doing a DB upgrade/update?

When digging through an incredible amount of posts about this related issue, it does appear that the way wordpress deals with the mysql is producing a poor result. Remember though, this option is still in beta state. I’m not suggesting that the actual html code itself is what is causing this issue. Just the way that wordpress is handling it.

My suggestion, and I always suggest this when dealing with databases, upgrade the database manually. Plus, always back up your mysql databases before any upgrade.

All you can really take from this experience is that issues can go eery, doing stuff manually can be the difference.

You kind of had gotten lucky that’s all that went wrong, many people were experiencing very catastrophic results.

Interesting.

Now when you say upgrade the databases manually — what exactly do you mean by that. That is, how do you “upgrade the db’s manually”?