• I have two problems I can’t seem to fix. I was using Google’s “properties” to change things to see how it affected the pages, but I can’t figure out what’s causing the problem.

    Our site had a group of pages that were already created. I updated to WP 3.3.1 and now every time I create a new page for the site it won’t hold the same formatting. For example, I made a couple of changes to margins. I added a new page into the NAV menu via WordPress (as opposed to CSS). It fits ok on the old pages, but any new page I create it word wraps the NAV bar (for what reason I don’t know). The new pages have no parent and are the same “default” template as all the other ones on the site.

    My other problem is trying to fix the NAV bar. I managed to move over the search box, but the NAV margins are horrible! How do I get the NAV margins to match the BODY margins for the left column? I also want to be able to use vertically stacked NAV links that align to the bottom and centered over one another like this (although I don’t know if it will work as you can’t preview a post here):

    ——————————————-Three——–Four
    One Link———Two Links——-Links——–Links

    Any help with these two problems would be greatly appreciated. CSS makes me want to throw myself off a cliff. (Figuratively.)

Viewing 10 replies - 1 through 10 (of 10 total)
  • A link to your site would help us to see what’s going on.

    Cheers

    PAE

    Thread Starter vze2363v

    (@vze2363v)

    occupynpr.org

    Thanks for the reply. The page that is presenting the problem is the “Garden” page. The NAV bar margins are too wide on all pages. I don’t know where the command is to make it bigger…whether it’s a margin call or a width call.

    Not sure why you’re saying that there’s more of a problem on the “Learning Garden” page than elsewhere, but here goes…

    If you simply want to stick with the current main nav menu items but get rid of the move to the next line, this works for me:

    #branding .only-search + #access div {
      padding-right: 0;
    }

    If you want to shift the entire menu to the left, you need to alter this rule:

    #access div {
      margin: 0 7.6%;
    }

    Alter the left and/or right margin to suit whatever you want.

    Personally, if you’re planning on adding more items on the main nav menu, I’d move the search box into the sidebar or possibly the footer.

    HTH

    PAE

    Also just noticed you appear to be modifying twentyeleven without using a child theme. This is not a good idea. Basically you run the risk of having your changes overwritten and may be making certain types of support unavailable to you. Search for the various posts by esmi on this subject. For example:

    https://www.ads-software.com/support/topic/kill-margin-fix-floating-content-over-menus?replies=2

    Apologies if you are using a child theme.

    Cheers

    PAE

    Thread Starter vze2363v

    (@vze2363v)

    Quite frankly I have no idea what a child theme is. We had an IT guy that took care of the hard things. I’m an old HTML coder. Never made the switch to CSS so I have no idea what all these #codes mean or where they occur on the page. It seems like these themes use a lot of codes that aren’t under the generic CSS learning pages and I tend to do things more by code than visual editors.

    Any recommendations on a web site or book that will take you very carefully through learning CSS intricately step-by-step? I have no idea where a child theme would be or how to make one, but it would appear I actually need to LEARN CSS now.

    I understand the concept of putting things in one place so you can make one change and have it affect all the pages on a web site, but I’m a WordPerfect person. I like personalizing everything so it’s exactly where I want it when I want it. Old habits are hard to break.

    Thanks for the NAV bar margin info. Worked WONDERFULLY!

    Oh, BTW, I found out the reason the NAV bar word-wrapped was that when you are on that page, that NAV link becomes bold. It was exceeding the margin once bolded due to the number of letters in the word.

    Quite frankly I have no idea what a child theme is.

    https://codex.www.ads-software.com/Child_Themes

    I’m an old HTML coder. Never made the switch to CSS so I have no idea what all these #codes mean or where they occur on the page

    https://dev.opera.com/articles/view/27-css-basics/

    Basically, # denotes an id selector and . a class selector.

    Any recommendations on a web site or book that will take you very carefully through learning CSS intricately step-by-step?

    https://www.w3.org/Style/CSS/learning

    Thread Starter vze2363v

    (@vze2363v)

    Thank you for the information. Now I realize why I hate CSS so much. HTML is nice and compact and organized. CSS is like someone threw up code all over the screen. I don’t understand why anyone would think it’s better to have so many carrier returns around the code you can’t even tell what’s being modified. It just wastes space on your monitor. I feel like I’m taking nine steps backwards in intelligence.

    I do appreciate all the links. I just hate CSS so much, I’m probably going to require medication to get through the instructions. I’ve used the W3 site a lot in the past for specific answers, but I found their lack of explanation as to what things alter what in the more intense code confusing. Perhaps if I start from the *beginning* of the education material it will make more sense. At least I hope so, because I have a bit of a learning disability with things that don’t seem logical to me. LOL!

    Again, thank you very much for the responses.

    HTML that contains formatting information is ugly, bloated and inefficient. HTML that contains only structural information is the reverse, but it leaves your pages formatted using the browser’s default style sheet.

    CSS, when you get to understand it, is very elegant. And you don’t have to put a single carriage return in it if you don’t want to. Good luck reading it if you decide to do that, but you don’t have to.

    HTH

    PAE

    The only reason why you hate CSS is simply because you don’t know it yet.

    As peredur is saying, it isn’t semantically correct to have formatting inside your HTML, it doesn’t make sense to have it there. What if you are redesigning your site and need to change formatting. Do you really want to go through all your HTML over and over again? Imaging now you have 1000+ static pages where you need to make some changes to one of the paragraphs… you get bored to death ?? With CSS, you change a line or two and all your 1000+ pages “automagically” have the formatting you want.

    Check out the CSS Zen Garden. It’s kind of an eye opener of how much power and flexibility you have when you write your markup (HTML, CSS) the right way.

    html+css is vastly superior to html alone as it separates the styling from the CONTENT. mixing the two just makes things hard to change and hard to understand.

    defining ‘styles’ in a separate file (a .css style ‘sheet’) and putting content in the html file which references (links to) the css file allows styles to be later changed without having to edit the content at all.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Twenty Eleven Problem’ is closed to new replies.