WordPress.org

Ready to get started?Download WordPress

Forums

Upgrade to 2.6.5 affects sidebar in IE7 (8 posts)

  1. icarusgraeme
    Member
    Posted 5 years ago #

    I just upgraded to 2.6.5 from 2.6.3 (using the pluging WordPress Automatic Upgrade ver. 1.2.2). Everything with the upgrade went smoothly, but when I was finished, my sidebar stopped working properly in IE7.

    By not working properly, it looks like WordPress is no longer treating my sidebar as a sidebar: the headers and text are using the wrong CSS styles and so on.

    You can see it here. When I looked in Firefox, it worked fine (I'm on vacation so I can't check in Safari or Chrome or anything else.)

    Any thoughts on this problem? Do I need to downgrade or is there an easy fix?

  2. alexleonard
    Member
    Posted 5 years ago #

    I really don't think this has anything to do with the upgrade.

    I would suggest that there's an issue with the long list of HTML validation errors around the site

    line 117 column 1 - Warning: <noscript> isn't allowed in <head> elements
    line 4 column 1 - Info: <head> previously mentioned
    line 117 column 1 - Warning: inserting implicit <body>
    line 133 column 1 - Warning: </head> isn't allowed in <body> elements
    line 117 column 1 - Info: <body> previously mentioned
    line 134 column 1 - Warning: discarding unexpected <body>
    line 162 column 4 - Warning: missing </i> before </p>
    line 163 column 4 - Warning: inserting implicit <i>
    line 216 column 97 - Warning: missing </div> before <li>
    line 222 column 1 - Warning: inserting implicit <ul>
    line 222 column 1 - Warning: missing </ul> before </div>
    line 234 column 71 - Warning: <br /> element not empty or not closed
    line 234 column 119 - Warning: <br /> element not empty or not closed
    line 234 column 128 - Warning: missing </a> before <div>
    line 234 column 420 - Warning: discarding unexpected </a>
    line 234 column 424 - Warning: <br /> element not empty or not closed
    line 312 column 95 - Warning: adjacent hyphens within comment
    Info: Doctype given is "-//W3C//DTD XHTML 1.0 Transitional//EN"
    Info: Document content looks like XHTML 1.0 Transitional

    I recommend fixing all of these template errors first as that will make the issue much much easier to track down.

  3. icarusgraeme
    Member
    Posted 5 years ago #

    Hmm...That's disturbing. Obviously I'm not a pro here, but I'm confused about how these errors could have just suddenly appeared. I've been running this site for over a year without any of these kinds of problems, which is why I thought it had something to do with the upgrade.

    I know this isn't an HTML forum, but any suggestions on why these error would have suddenly appeared?

  4. alexleonard
    Member
    Posted 5 years ago #

    Well, to be honest I can't see how an upgrade would suddenly have made all those errors appear, I really can't.

    However, the upgrade might have caused an issue with one of your plugins which happens to have knocked things out of kilter in IE7 (you should see it in IE8beta2 - it's even worse!).

    However, when you've got a whole host of issues like that, the best thing is to slowly pick through your template file and fix each of these issues.

    If you're using Firefox I highly recommend Firebug and HTML Validator to speed up the tracking down of these issues.

    I think your biggest issue probably arises from a missing </div> as this sort of thing can cause havoc with style and layout!

    I'm kind of amazed that it's rendering right in FF3.

    The only other thing to check out is to go through your plugins and turn them off one at a time and see if it makes a difference.

    And one other thing that occurred to me is to remove the text widget from your sidebar, as the issue seems to be coming from there on in.

    It is possible that the text widget in 2.6.5 has a typo and is missing a </div>. If that does fix it I will have to eat my words about it being highly unlikely that an update would cause this ;)

  5. icarusgraeme
    Member
    Posted 5 years ago #

    Thanks for your help. That was all very helpful. In theory at least :)...Now let's see if I can put to good use.

  6. Logistics Monster
    Member
    Posted 5 years ago #

    I am having the exact same problem and it started with upgrading to 2.6.5. My site looks normal in all except IE where the sidebars are missing and the bottom of the page has completely disappeared.

    I am a newbie to CSS and code, so if you have any ideas - please explain like I am 6.

    Mahalo,
    LM

    http://logisticsmonster.com/

  7. Samuel B
    moderator
    Posted 5 years ago #

    @ Logistics Monster
    Where to start?

  8. Logistics Monster
    Member
    Posted 5 years ago #

    Thank you Samboll - but once again could you take the time to explain to me since I am a total newbie. I have checked the W3C page. Because of my inexperience with code, I have not changed anything and am assuming these errors are due to the theme I am using, and that being said, I do not want to even start trying to correct these errors until I know exactly what I should be doing and where. Any help would be very much appreciated - even if it is to direct me to tutorials on WP. I do not expect anyone to hold my hand - just point me in the right direction.

Topic Closed

This topic has been closed to new replies.

About this Topic