Twenty Ten menu question

That’s not TwentyTen. It’s 2010 Weaver. You also have quite a few validation errors that you need to sort out.

Not sure what you mean by “first” and “second” submenus…

I am seeing six menu items with five and six side by side (IE8 and FireFox), so it looks like you have this structure, if so then it is correctly shown.

Demo Page 1
Demo Page 2
-Demo Page 5
–Demo Page 6
Demo Page 3
Demo Page 4

Not seeing the rounded corners to the navigation bar in IE8, only FireFox

HTH

David

Weaver is a twenty ten child theme basically, so the code used would usually be the same, which it was. The validation errors have nothing to do with my issue. I really don’t know what’s so hard to understand “first and second submenus” but thanks for your reply I guess.

I was looking for a second nav bar. The 2nd and 3rd page sub-level flyouts looked fine to me in Firefox.

Hi zeaks,

The validation errors have nothing to do with my issue

I have only been developing themes for a short while, and I would say that when parts of the theme layout play up, 99.99% of the time it is html tag validation errors that cause it, not the theme changes but the content, where the user has added bad html or tags.

One this morning where the sidebar had migrated to the bottom of the page was reporting a closing </div> without an opening element, it looks like a missing ” is the cause.

If I had seen a layout problem when I visited your website that would have been the first thing I would have done, validated the theme url and looked at the errors, and then told you about them.

One thing about answering these posts is you do not know how skilled the topic owner is, so you look at the basics first.

HTH

David

And since I wandered back in here…

Weaver is a twenty ten child theme basically, so the code used would usually be the same, which it was.

The keyword there is “usually”. A child theme can completely over-write any and all of the parents templates, CSS and functions. So the distinction between parent & child themes is important – especially when troubleshooting.

@esmi The menu css is the same in twenty ten as it is in weaver, as is everythign else as far as I know besides, the extra things weaver comes with such as top and bottom widgets.

I said twenty ten because more people are familiar with it than weaver and an answer regarding twenty ten would work as well. The code validates now, it was the filler content plugin that caused it.

Your reply seemed to just brush me off and not even attempt to answer my question and only pointed out I had validation errors, which I doubt you looked past the “your site has 5 errors” part.

If you didn’t intend on taking the time to help, then a simple “Validate your site, it could be causing your problem” or not reply at all would of been better than bashing parts of my post.

Anyways, I marked the topic as resolved long ago.

Actually I looked though the list of 19(?) validation errors to see if they were all minor or could cause some issues on your site. As it turned out, some were definitely significant and, as Adeptris said, markup & CSS validation are the very first things that you should turn to when a theme layout starts misbehaving. The validation reports can help you fix the errors or can point you in the direction of plugins that may be creating a problem.

Trying to fix layout issues on top of uncorrected & significant validation errors is usually just a pointless exercise in frustration. Hence my suggestion that you needed to fix some of the errors first.

I also examined your site without CSS in an attempt to locate your “first & second sub-menus” given that I couldn’t find any obvious display problems with your flyouts when using Firefox. So hardly a brush-off…

I had something here, but I think I’ll just let this topic die, it’s as pointless as the reply was.