Unless you provide a link to a page demonstrating the problem, no one will be able to offer much in the way of assistance.
http://talesstudio.com/capcon/industries/
Sorry. I didn’t think it was necessary in this case. But that’s the page I was working with when I found the issue. I can move the image out of the <p></p> tags, but wordpress just adds more. Nothing I mentioned in my original post works. =\
The image in that page isn’t being enclosed by p tags itself. It’s the text that’s in the p tags.
Was there a big change in 3.5.1 that made these wpautop() removals different?
Nope. It’s still the same as far as I am aware. May I suggest that you switch to using the Text editor for this page and then enclose just the image in its own div – preferably with a new class. Then you’ll be able to use CSS to float your image left and keep all of the text to the right.
No, no. I’ve moved it outside of the <p></p> tags several times, and wordpress continues to re-wrap the image. I’m only using the text editor, so that’s not the problem either.
I would enclose the image in its own div EXCEPT that this is a client website, and the client needs to be able to insert/remove images on their own as they please. I don’t think telling them that they need to use div tags around every image is very acceptable.
http://talesstudio.com/capcon/industries/
The image is already floated left as it is. There’s nothing wrong with the CSS. The fundamental problem is the unwanted addition of <p></p> tags around every element in the editor.
Ok, I’ve found a kinda weird work-around…
While trying to debug an entirely unrelated issue on another WordPress site, I found that WordPress 3.5.1 has an extremely buggy editor, and to fix it, I told WordPress to use Google libraries instead. THEN I told it to remove the wpautop(); and that worked… kinda. I mean, it doesn’t work 100% of the time, but for now it’s passable.
I really hope someone can fix the WordPress editor. This is really frustrating.
There’s nothing wrong with the Visual editor in WordPress 3.5.1. In fact, it hasn’t really changed since 3.3(?) when a browser problem with flushing jQuery resulted in some people needing to use Google libraries to enforce the jQuery change.
Hmm. I find that hard to believe. I’ve been finding this issue only after updating to 3.5.1 for all of my sites. Seems weird that it would just appear now.
Don’t take my word for it. See http://wordpress.org/support/topic/troubleshooting-wordpress-31-master-list?replies=14
(I got the WP version wrong. It was actually 3.1 – not 3.3)
