WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Sidebar won't move despite changing CSS (25 posts)

  1. benjaminzand
    Member
    Posted 1 year ago #

    Hi there,

    I was editing my site's CSS today (trying to put a little flash map in position) and all of a sudden my sidebar has shifted to the left. Everything else is in the exact same position and can be moved via CSS, but despite what I do to the sidebar's CSS it stays in the exact same position. If I edit the CSS using firebug on Firefox I can successfully move the side bar into the right position, but when I try and save this in the style.css I see no changes at all.

    Here is my site and here is the code I'm using:

    /* Sidebar */
    #sidebar {float: right; display: inline; width: 320px; }
    #sidebar .widget {margin-bottom: 10px; font-size: 12px; line-height: 18px; }
    #sidebar .widget li {font-size: 14px; line-height: 24px; }
    #sidebar div.cover {margin-right: 10px; }
    #sidebar ul.posts h3 {overflow: hidden; font-size: 12px; line-height: 18px;}
    #sidebar ul.posts p.postmetadata {font-size: 11px; }

    Any help would be amazing.

  2. Josh Hardman
    Member
    Posted 1 year ago #

    I can't actually view anything except a holding page?

  3. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    Can't see your site :) - your landing page... It's likely that you have a CSS error someplace in the stylesheet - which can render any subsequent CSS non-functional.

  4. benjaminzand
    Member
    Posted 1 year ago #

    Sorry! That's deactivated now completely forgot about that. You should be able to see it now.

    I've been having issues all day with WordPress going ridiculously slow as well and the server randomly dropping, do you think this could be related?

    Thanks for the help.

  5. Josh Hardman
    Member
    Posted 1 year ago #

    The holding page is still showing.

    Might have something to do with WP Super Cache running.

  6. benjaminzand
    Member
    Posted 1 year ago #

    Hi there,

    Okay I'll delete the plugin making the holding page and see if you can access it then.

    And I've only literally downloaded WP Super Cache a few minutes ago due to my hosts (iPage) telling me this could improve the speed of WordPress. The problem was happening before then.

    I really don't understand why. I'm guessing I've made an error somewhere like WPyogi said, but I just don't know where!

    Thanks again for helping me out.

  7. Josh Hardman
    Member
    Posted 1 year ago #

    You don't want to download WP Super Cache until your website is ready to be cached. Otherwise the plugin starts caching things that are not finished.

  8. benjaminzand
    Member
    Posted 1 year ago #

    Oh okay, I'll get rid of that right now then.

    I really don't understand what the problem is. As I said the site is also going very slow as well and I keep getting a connection error when trying to access the theme editor. I don't know what I've done but I've definitely done something wrong.

  9. Josh Hardman
    Member
    Posted 1 year ago #

    It might be the WordPress install, but more likely it is iPage. I'm assuming it is hosted on a shared server, because in the past I've had the exact same problem with WordPress blogs on iPage which have been fine on other servers.

  10. benjaminzand
    Member
    Posted 1 year ago #

    Okay, I'm flagging it up to iPage again to see if they'll actually do anything this time. So I'll see what happens. Could this be the reason for the CSS also or is that more likely to be something else?

  11. benjaminzand
    Member
    Posted 1 year ago #

    Anyone have an idea why changing the CSS isn't updating?

  12. Andrew
    Forum Moderator
    Posted 1 year ago #

  13. benjaminzand
    Member
    Posted 1 year ago #

    Okay, I've found the problems. First of all, iPage was using a cacheing program and despite speaking to them on about 50 occasions they didn't decide to tell me so until I found out on the internet. They've deactivated this now but I've also realised that my child theme style.css is no longer overriding the parent style.css.

    Does anybody have an idea of why this may be?

    Thanks again for the help.

  14. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    Without seeing the site no way to even guess (landing page is up)... Might well be that you have an error someplace in the stylesheet.

    Try validating your CSS:

    http://jigsaw.w3.org/css-validator/

  15. benjaminzand
    Member
    Posted 1 year ago #

    Sorry that plugin is deactivated now so you should be able to take a look. I'm not quite sure what my child theme's URI is, how would I find that?

    Thanks.

  16. benjaminzand
    Member
    Posted 1 year ago #

    Oh wait, I've just realised you can input code directly! I'll do this, thanks again.

  17. benjaminzand
    Member
    Posted 1 year ago #

    Okay, it's telling me I have 15 errors. So I've definitely done something wrong. Nearly everyone is a 'Parse Error'. Do you know what this is?

  18. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    When you have a child theme set up -- it IS your site -- so it's just your regular URL -- and you do have some errors - look at the second section of the validator report -- for the child theme stylesheet:

    http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Finformedexplorer.com%2F&profile=css3&usermedium=all&warning=1&vextwarning=&lang=en

    Some "errors" are not a problem and are actually just because not all CSS is recognized as valid -- even though it does not cause problems. But parse errors (usually syntax) are problematic.

    For example, look at this error:

    #map 	Parse Error #navigation {line-height: 34px; }

    Then go find that line on the stylesheet and you'll see that you are missing a closing bracket for the #map CSS.

    Missing brackets invalidate any CSS that follows...so those are major. You may also be missing things like semi-colons.

  19. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    The other thing that I would suggest is that you use the standard WP (and preferred convention) format for CSS code - it's MUCH easier to read and track down errors --

    i.e.:

    selector {
    style;
    style;
    style;
    }

  20. benjaminzand
    Member
    Posted 1 year ago #

    Okay, I'll do my best to rectify the errors. Do you think this will resolve the problem of not overriding the parent stylesheet? Also, I think I'm definitely going to need to read up on CSS a bit more because I'm a bit confused.

    In terms of the standard WP, how would I write something like this in the standard way?

    #container {width:100%; text-align:center; min-height: 200px; }
    #container div.wrapper {margin: 0 auto; text-align: left; width: 960px; }
    #container div.cleaner {clear: both; font-size:1px; height: 1px; margin:0; line-height: 1px; }
    #container div.sep {font-size:1px; height: 1px; margin:0; line-height: 1px; margin: 3px 0; background-color: #ccc; }

    Thanks so much for helping me out.

  21. benjaminzand
    Member
    Posted 1 year ago #

    Okay, I've rectified the errors apart from these two which I don't understand.

    #menuSocial img {-moz-opacity:30; filter:alpha(opacity=30); opacity:30;}
    #menuSocial img:hover {-moz-opacity:1; filter:alpha(opacity=100); opacity:1;}

    It says there are issue with alpha(opacity=30) and alpha(opacity=100) which I can't fix no matter what I've changed.

    Despite sorting out these issues though, the child theme is now completely disregarding its CSS and only using the parent theme's CSS. Do you have any idea of why that may be?

  22. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    Yeah, don't worry about those errors -- those are browser specific and not a problem.

    But, you have bigger problems with other (non CSS) errors - looks like something weird is happening in the header.php file -- a bunch of stuff is in the body which should not be...

    http://validator.w3.org/check?uri=http%3A%2F%2Finformedexplorer.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

  23. benjaminzand
    Member
    Posted 1 year ago #

    Wow, I have never even touched that file that's came with the theme.

    I've actually fixed the CSS problem now, basically I just recreated my child theme as when I previously created it I copied over the entire parent style.css into the child theme so I think that may have caused a few problems.

    The theme editor's working completely fine now, do you think these header.php issues are gunna cause future problems?

    Thanks for your help btw I really appreciate you taking the time out!

    [ Please do not bump especially with a blank posyt. That's not permitted here. ]

  24. WPyogi
    Volunteer Moderator
    Posted 1 year ago #

    I really don't know, but I'd suggest you contact the theme vendor (wpzoom?) about those issues. It looks like that's a commercial theme, in which case, they should be supporting it.

  25. benjaminzand
    Member
    Posted 1 year ago #

    Okay I will do, thanks a lot the help.

Topic Closed

This topic has been closed to new replies.

About this Topic