ZEN theme (5.x-1.0) is messed up! The Footer blocks come up
immediately under the Header block area! Also, the DIV order of the
blocks on the right column are messed, as all subsequent
block-divs after the fist one come up as embedded under the first block.
see my screenshot from Firebug. I could not find any divs out of order in
page.tpl.php (to my knowledge)

I thought it be an error I made with my custom zen-subtheme (from starter kit)
but I switched my site to just plain zen theme (not classic) and problems still exist,
what am I doing wrong! Was this fixed in 5.x-1.1???

CommentFileSizeAuthor
#2 zen-div-order.jpg23.51 KBGlowingtree
zen-div-order.jpg21.06 KBGlowingtree

Comments

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Status: Active » Fixed

It's not Zen. Its your #block-block-3. It has a missing </div>.

Thanks for the screenshot. That made it easy to diagnose. :-)

Glowingtree’s picture

Glowingtree commented
Status: Fixed » Active
StatusFileSize
new zen-div-order.jpg23.51 KB

Hello, sorry, that screen-shot was not giving you the full picture, that's not my "code"
its just a partial screen-shot of the expandable div/html element view that Firebug
Firefox plugin gives you.. I didn't get all the divs in the screenshot... here is a proper screen-shot

Glowingtree’s picture

Glowingtree commented
Title: ZEN theme (5.x-1.0) has messed up DIV order or block regions » ZEN theme (5.x-1.1) has messed up DIV order or block regions
Version: 5.x-1.0 » 5.x-1.1

BTW this new screenshot is from ZEN 5.x-1.1 - I backed up my layout.css, dis-abled and deleted ZEN 5.x-1.0 and my custom subtheme, replaced with ZEN 5.x-1.1 and actived standard ZEN theme (no subtheme). The div order and footer block placement
problem still exists

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Status: Active » Postponed (maintainer needs more info)

Firebug will auto-close any dangling <div>s in that code view. Look at the actual source code. What's in there?

I'm pretty sure your 3rd custom block (#block-block-3) has one (maybe two?) opening <div> but no closing </div>. That's what is causing the the #block-event-0 and #block-block-4 to appear inside the #block-block-3.

Glowingtree’s picture

Glowingtree commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

ok, I guess the Firebug view is throwing me off.
The one block I added in RAW html format must not have had all tags closed...
i removed the block and things went back to normal.
I guess the answer is most often getting more sleep ( ;