WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Embarrassing CSS Question | Admin Bar (8 posts)

  1. floydrose5150
    Member
    Posted 1 year ago #

    I have a weird issue, where my horizontal nav menu appears in proper position while logged in, however when logged out, it shifts up approx 10px or more. Drives me nuts.

    I've included links to screen shots from logged in/out below, as well as my site:

    Logged In: http://ebsolo.com/site/wp-content/uploads/2012/09/logged-in.jpg

    Logged Out: http://ebsolo.com/site/wp-content/uploads/2012/09/logged-out.jpg

    Site URL: http://ebsolo.com/site/

    Can anyone offer a suggested fix?

  2. Andrew Nevins
    Volunteer Moderator
    Posted 1 year ago #

    Is it only the hope page that experiences this problem?

  3. floydrose5150
    Member
    Posted 1 year ago #

    All pages actually, thanks

  4. Andrew Nevins
    Volunteer Moderator
    Posted 1 year ago #

    In the screenshots, I can't see a shift upwards the region of 10 pixels of the menu bar.

  5. floydrose5150
    Member
    Posted 1 year ago #

    Try viewing the site, and click on one of the sections that has dropdowns

    (Blog or Media) and you'll see it's shifted up.

    http://ebsolo.com/site/

    Thanks much for trying for me.

  6. Andrew Nevins
    Volunteer Moderator
    Posted 1 year ago #

    May I ask which browser and browser version you're using?

  7. floydrose5150
    Member
    Posted 1 year ago #

    Trying in latest Chrome, FF and IE 9

  8. floydrose5150
    Member
    Posted 1 year ago #

    Ok, I seem to have fixed it myself, and here's what I did if it helps anyone else.

    I ended up getting it to look correct when not logged in, and was bumped down if I was logged in.

    So, I added <body <?php body_class();?>> to my header, and then for my menu class I added this:

    .logged-in ul.menu li:hover > ul {
    display:block;
    position:absolute;
    margin-top:-20px; /* This was the only element changed for logged in display */

    }

    Still frustrated I had to go this route, and not sure what I did wrong to cause this error, but at least it's fixed.

    Cheers

Topic Closed

This topic has been closed to new replies.

About this Topic