Support » Themes and Templates » Comments pushed into top of sidebar

Viewing 15 replies - 16 through 30 (of 41 total)
  • WPyogi

    (@wpyogi)

    Forum Moderator

    I don’t see any on that page either, but you should clear up some other errors. And you absolutely should be using the alt attribute for images on your site — for SEO and for people using readers to access your site.

    http://validator.w3.org/check?uri=http%3A%2F%2Fwww.highondesign.co.uk%2F10-creative-cv-examples-that-strike-the-perfect-balance%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

    zebrathemes

    (@zebrathemes)

    How you don’t see? check this page

    http://www.highondesign.co.uk/category/articles/

    #content is duplicate all along.

    zebrathemes

    (@zebrathemes)

    jeffrey_huynh

    (@jeffrey_huynh)

    That page shows all the different articles I have though? (which is what I intended)

    I’m currently sifting through my code and correcting the errors. I’ll write back to let you know how it goes! 🙂

    jeffrey_huynh

    (@jeffrey_huynh)

    I see that my #content has a duplication error, however, I cannot find in my template files where exactly this is happening! I have only used #content once it seems!

    Confused :S

    WPyogi

    (@wpyogi)

    Forum Moderator

    My bad on the above — but if you just change the content from ID to class, (and change any CSS as well), that may solve it.

    jeffrey_huynh

    (@jeffrey_huynh)

    Ah yes that did solve the duplicate problem… now it’s saying lots of .content is unclosed? But I don’t know where 🙁

    Sorry to be a pain! Is there a way of tracking down the exact line number and column in my code so that I can find the source of the problem quicker?

    jeffrey_huynh

    (@jeffrey_huynh)

    The actual page with the article is fine now.. it’s just the category page: http://www.highondesign.co.uk/category/articles/ that is messed up.

    WPyogi

    (@wpyogi)

    Forum Moderator

    Nope, line numbers in rendered HTML are not relevant to the php code. But you should be able to look carefully in the php and find it. That’s likely what’s making the content sections run off to the right…looks like the missing one is at the end of the content loop.

    jeffrey_huynh

    (@jeffrey_huynh)

    Really appreciate this help!

    I added a closing div at the end of the content loop and it fixed one of the .content unclosed errors. So I added more closing divs to match the number of errors given and now the errors have gone. Why did I have to do this? Does it relate to the amount of individual posts I have? I

    t doesn’t seem right to add so many closing divs after the content loop..

    My wrapper id also seems unclosed as well as the body.

    WPyogi

    (@wpyogi)

    Forum Moderator

    If your php is coded correctly, it should not make any difference how many posts you have. If it does, something is not right in the loop — perhaps that the closing div needs to be inside the loop. The wrapper and body closing tags are generally in the footer.php file – at least that’s how most themes are coded. Since yours is custom, can’t say for sure.

    jeffrey_huynh

    (@jeffrey_huynh)

    Hmm I’ve put one closing div inside the loop instead and its worked.

    The sidebar is still shifted down on only these category pages….
    I’m not too sure what ‘stray end tag div’ means as its come up twice as errors…

    WPyogi

    (@wpyogi)

    Forum Moderator

    In Firebug, it shows two extra closing divs right above the sidebar.

    jeffrey_huynh

    (@jeffrey_huynh)

    Am I right in getting rid of the closing divs above the ‘get_sidebar’ at the bottom of my index/page/single.php files?

    Doing this doesn’t however change this page, but makes my page even more messed up….

    Firebug doesnt tell me that i have 2 extra closing divs right? Is this through your own knowledge?

    WPyogi

    (@wpyogi)

    Forum Moderator

    If you use View Source, those two extra divs show up in red — and those are the same ones that show up in the validator results as extras. I can’t see where they are coming from — it’s in your template somewhere. But in order for the float right on the sidebar to work, you probably need to make the wrapper div to float left… or put the sidebar above the wrapper div.

Viewing 15 replies - 16 through 30 (of 41 total)
  • The topic ‘Comments pushed into top of sidebar’ is closed to new replies.