newsmedia

Well, no one is more suprised than me to find a working version of 2.2.2 without this problem. I had to do a fresh install of 2.2.2 (not an upgrade) into a blank directory. That is the only way to get rid of the problem as far as I can tell. I think the problem began around the upgrade to 2.1.2

WordPress Support: Look for the answer somewhere around the upgrade process from previous versions to 2.1 or 2.1.2 to not have a repeat of the same issue in the future. The solution is not always offering an upgraded version, if the upgrade process is the problem.

Users: You want to fix this problem? Switching to default theme won’t work. Doing any kind of upgrade won’t work. (for now at least until they figure out what went wrong, which they might never bother to do)

You need a fresh install of 2.2.2 into a blank directory.

I know it’s depressing if you have a big or complex blog to migrate over, but I’m afraid you will just have to do it and move on. On the bright side, you can stop tearing apart your theme looking for the answer and it is NOT browser related as some have suggested in other threads.

Dan

there is no reason that html code should change when switching from rich text editor to html code.

can you imagine if any other html editor on the market did this?

obviously it doesn’t have to be this way because as someone said earlier, if you view source on the web page the correct code is there, so therefore they could have it retain the html code when switching to wysiwyg mode if they wanted to.

why have yet another beta without fixing existing code first? waste of users’ time having to re-edit posts all the time. pushing me toward Typo and Ruby on Rails.

if I was the only one using the blog, then maybe I could put up with it, but try explaining it to 2000 users. Basically you have to say your blog is broken and will remain so for the immediate future unless they want to learn html and that if they don’t like it, nothing you can do about it. And if you leave rich text editor on for them, get prepared for piles of email about how their code gets lost switching from rich editor to html. Yes, yes, Mr. Customer, I know it looks amateurish, but hey I’m using free software and you have to expect this level of inconvenience.

Not really a way to move a platform forward, when the core function, writing posts, doesn’t work properly for users.

Dan