WordPress 2.1 image problem (6 posts)

  1. goku1234
    Posted 9 years ago #

    I have just updated to wordpress 2.1 and there is a bug. Almost all my img id= line changing to newline with p tag

    <div style='float:right;margin-top:0px;margin-left:5px;'><img id="image1164" src="http://www.domain.com/blog/wp-content/uploads/2007/01/logo.png" alt="WordPress Logo" /></div>

    <div style='float:right;margin-top:0px;margin-left:5px;'><p><img id="image1164" src="http://www.domain.com/blog/wp-content/uploads/2007/01/logo.png" alt="WordPress Logo" /></div>

    As a result my blog image display is not working in FF but works under all other browser.

    How do i stop this crazy replacement. If i switch back to 2.0.7 it works perfectly.

    Please help. I have 1200 post with images all of them gone from FF :(

  2. Chris_K
    Posted 9 years ago #

    I'm either blind or dumb, but I don't see the difference between your two examples.

  3. goku1234
    Posted 9 years ago #


    Sorry. I've updated post with buggy output. It is inserting

    <img id >

    So it looks as
    <p><img id >

    Which is not working in FF but in all other browsers it works find. I never inserted p tag.

  4. xenogere
    Posted 9 years ago #

    I'm having the same problem. WP 2.1 is inserting an opening P tag in image DIVs, but it's not closing them. I've never used P tags in those image blocks and they're not required to be valid XHTML, so I'm wondering how to stop WP from inserting them in the first place (besides going back to 2.0.7).

  5. goku1234
    Posted 9 years ago #

    Going back to 2.0.7 backup means I will loss at least 50+ comments and 8 new posts. This is a small bug and may be someone will point out solution. I don't know which file is use to display final output to end user. If I edit the post it displays no sign of extra p tag.

  6. xenogere
    Posted 9 years ago #

    Actually, you should be able to install the 2.0.7 files and do the normal upgrade process without losing any data. Your link groups will probably get messed up, but those are easy to fix. I just went through the downgrade process to resolve the various issues I was having--including the whole P tag mess in image DIVs. Amazing that once I went back to 2.0.7, my site is now back to valid XHTML and is working properly. I think I'll wait to upgrade when a major bug clean-up takes place with 2.1.

Topic Closed

This topic has been closed to new replies.

About this Topic