rpali

I did as you said, switched to text mode, and I see nothing. No breaks, no space, no nothing. Even after publishing the post, viewing the source in any browser reveals nothing where I inserted the non-breaking space.

It seems the next step is to search the bugs.

That’s doubly weird because I often want to change regular spaces to non-breaking spaces. To do so, I select the space, and then chose the non-breaking space button, as I described earlier. The result is that the space collapses to nothing. It appears that there’ son space of any kind. So weird.

It is useless in its current state because it doesn’t work properly! It used to work, but not in this version.

I’m not sure what you mean by “All it does is add a nbsp but it doesn’t shift the cursor position” because by definition, a space does indeed shift the cursor position.

Still, I’m grateful to know that it’s not just me. Thanks for writing.

No…I select the Special character button (The omega) and choose the ‘blank’ character in the upper left corner, the non-breaking space. The tool-tip confirms that’s what it is. But it’s not in this version.

Thanks esmi, but that’s always the way I use the ‘more’ tag. It still doesn’t work, even in entries that *did* work before.

I’m having the same problem. The <!–more–> tag seemed to do nothing at all. I have older posts that used to work in older versions of WordPress, but not now. The only effect the tag seems to have is adding a span into the HTML:

<p><span id=”more-1917″></span></p>

and that’s it. The entire entry still appears. I tried using the default theme that comes with 2.7 with no change in behaviour.

Has anyone had any luck in fixing this?

It gets weirder and weirder. In trying a few things, I set notification to be sent when comments are posted. I normally don’t bother with this since all comments require modification.

I was quite surprised to find no post sent to let me know a comment required moderation, but a notification was sent as soon as I approved it!

I wonder if one’s host does play a role. If I have the notifications sent to my gmail account, everything works perfectly. <sigh>

My comment notification messages stopped arriving a while after I updated to 2.7, so I know the update didn’t cause this. It did work for a while after the update. The strange thing is trackback notification e-mail messages still arrive! Bizarre.

Seriously? No one else is having this problem?!

I had the same thing happen about a month ago. It just stopped working. I haven’t been able to figure out how to get it back. <sigh>

To my surprise, the error does not appear on one of the five images I’ve uploaded. It’s smaller and doesn’t have any copyright metadata, but it was produced with the same workflow as the others.

I’m stumped.

shetakaey,

What I did when I saw 2.3.3 was also having the same problem was open a support ticket with my host. Everything suddenly started working again and a few moments later I received a message that said, in part: “Your Apache processes weren’t dying off correctly/normally but I don’t know why. I’ve restarted your account and things are loading fine now.” She specifically stated there was no issue with the database. It was strictly with Apache. Very strange…

davidinjp,

Sorry about the mix-up. What you described sounded familiar so I ran with it. Possibly part of the reason is I first noticed the problem when trying to edit/post a new item. Then the media viewer was affected, and it spread from there until nothing worked.

I too experienced this problem. Within 24 hours of upgrading to 2.5, my site was so bogged down, I could barely log in, much less actually doanything. I was also informed by others that viewing the site was a hit or miss affair (mostly miss).

I reverted to 2.3.3 and was stunned to see no difference in behaviour. A quick action on the part of my host had me back in business. They told me processes were not ending properly. I can’t say for certain it was 2.5, though the problem started soon after I upgraded. Now that I’ve reverted, the problem hasn’t returned.

Along with the image upload problem, I’m content to stay with a working 2.3.3 install for a while longer, until fixes for these problems are rolled out.