Pink dash line around edit block as opposed to red - ( important?)
Permalink
Crazy question - has anyone seen a pink dashline around their edit block ( a sitewide block in the header). Does it mean something important?
I'm used to seeing a red dashline around all edit blocks, including sitewide.
(checked it out on a few sites)
hoping this might be the reason why I'm not seeing this block in IE.
thx in advance!
Karen
I'm used to seeing a red dashline around all edit blocks, including sitewide.
(checked it out on a few sites)
hoping this might be the reason why I'm not seeing this block in IE.
thx in advance!
Karen
Put the block in edit mode and you should get box at the top explaining what's up with the block. I believe pink means it's a block that has been copied from another block and hasn't been edited yet since being copied. Just saving it as-is should turn the border red again.
duh! You are absolutely right. Thx - looking for the smoking gun.
Sorry this doesn't resolve your IE thing. Is there a public URL that I could have a look at to see if I can see anything that might affect IE?
sure - I fixed the problem of everything below the header shifting to the right and up, but the menu bar is not showing up.
Only on 7,8,9 - ie10 it looks great. OK for Safari, Firefox and Chrome.
the odd thing is the div is not showing up when I check it with the developer tools for those IE versions: the div is: main_nav and of course the menu block that goes in it.
here it is: http://www.clickactivate-accounts.com/alottasdeli...
any idea about this would be greatly appreciated.
thanks so much,
Regards,
K
Only on 7,8,9 - ie10 it looks great. OK for Safari, Firefox and Chrome.
the odd thing is the div is not showing up when I check it with the developer tools for those IE versions: the div is: main_nav and of course the menu block that goes in it.
here it is: http://www.clickactivate-accounts.com/alottasdeli...
any idea about this would be greatly appreciated.
thanks so much,
Regards,
K
First let me say that I'm no expert in IE issues but something quick you can try is to just declare the DOCTYPE as HTML instead of loose.dtd
Try changing the first line of '/elements/header.php' to be:
The original '960-starter' theme has <!DOCTYPE HTML> so I assume you changed it at some point to try to fix things.
Also, you have:
I believe only the last is the one the browser will listen to. This is an all-or-nothing declaration. It doesn't tell the browser to be compatible with all three; just one I'm afraid.
Also(2)... a lot of your images are large .png files. I find that unless the image requires transparency, I just save them as .jpg with 80% compression and the site will load much faster.
Try changing the first line of '/elements/header.php' to be:
<!DOCTYPE HTML>
The original '960-starter' theme has <!DOCTYPE HTML> so I assume you changed it at some point to try to fix things.
Also, you have:
<meta http-equiv="X-UA-Compatible" content="IE=7" /> <meta http-equiv="X-UA-Compatible" content="IE=8" /> <meta http-equiv="X-UA-Compatible" content="IE=9" />
I believe only the last is the one the browser will listen to. This is an all-or-nothing declaration. It doesn't tell the browser to be compatible with all three; just one I'm afraid.
Also(2)... a lot of your images are large .png files. I find that unless the image requires transparency, I just save them as .jpg with 80% compression and the site will load much faster.
I think I might have found the problem.
There is some HTML issues starting at line 63-ish of elements/header.php:
I believe you are missing "<![endif]-->" to close out the IE6 conditional comment
There is some HTML issues starting at line 63-ish of elements/header.php:
I believe you are missing "<![endif]-->" to close out the IE6 conditional comment
Hi MHawke,
I think this is going to be the answer. I'll do the fix ( plus the other recommendations -including the images for performance.) I'll repost here if it works. I also found :
http://validator.w3.org/
and it had also pointed out that same line - (plus some other things that may or may not be an issue)
Karen
I think this is going to be the answer. I'll do the fix ( plus the other recommendations -including the images for performance.) I'll repost here if it works. I also found :
http://validator.w3.org/
and it had also pointed out that same line - (plus some other things that may or may not be an issue)
Karen
Thanks again :
that : was missing and a few divs had to be re-organized, but it all snapped into place once it was figured it out.
works in all browsers now.
You made my week!
K
that :
<![endif]-->
works in all browsers now.
You made my week!
K
