WordPress Footer floating up

[Anonymous]

Hi – we’ve noticed in Firefox3.6 and IE9 that the the wordpress footer floats upwards when editing an event in admin. making it so you can’t click on whatever it’s floating over.

Here’s a screenshot: http://www.studio3arts.com/eme_footer.png

Look at the RSVP box – see the Version 3.2….. that’s from the wordpress footer. And since it’s over the RSVP box, I can’t uncheck it.

In order to work with it, I have to expand or collapse boxes to move what I want to click out from under the footer.

Thanks,

/Wendy

[Franky]

Yes, I believe this is some CSS issue. I can’t reproduce it here though, so it must be a theme issue. If you switched to 3.2.1, you can’t just keep using the old themes just because of things like this I guess. Firebug might help you to find the real culprit.

[Anonymous]

I had this problem too and ended up adding this line to my eme.css

.wp-admin #footer { display: none !important }

[Anonymous]

Wendy – for what it’s worth: after upgrading to WP 3.2.1 I started having the same issue. I’m not experienced enough to investigate and fix something like this, but did find that by zooming in/out (CTRL+ or CTRL-) the footer would move up and down, as you found – so you can click what you need to click! Might be a little faster than the ‘expand/collapse’ approach.

[Anonymous]

Paperboy – I think I will do what you did for now. Who uses the footer anyway?

But Franky, I checked firebug and here’s the problem:

http://www.studio3arts.com/wp-admin/load-styles.php?c=1&dir=ltr&load=global,wp-admin,ms&ver=bdb0ec292ad0b1a07f3b44410fe99090

line 2:

#footer {

border-style: solid;

border-top: 1px solid;

bottom: 0;

left: 0;

margin-right: 20px;

padding: 10px 0;

position: absolute;

right: 0;

}

If I remove the “position: absolute” property in Firebug, the footer goes to the bottom of the page where it belongs.

I am using Suffusion, BTW.

The footer doesn’t float up on an edit page/post page, and it does have the absolute property.

[Franky]

Hmmm … maybe it’s a table or div not being correctly closed. I can’t check it here now, but if you paste the html source of that page into

http://validator.w3.org/#validate_by_input

does it show anything interesting?

[Anonymous]

I ran it through. It can’t find the closing tag for <form>, but I checked the source and there are 2 <forms> and 2 </forms> – maybe something is nested improperly?

Here are the results:`

Validation Output: 16 Errors

1. Error Line 1043, Column 12: end tag for “form” omitted, but OMITTAG NO was specified

</div>

✉

You may have neglected to close an element, or perhaps you meant to “self-close” an element, that is, ending it with “/>” instead of “>”.

2. Info Line 610, Column 4: start tag was here

<form id=”eventForm” method=”post” action=”admin.php?page=events-manager&am…

3. Error Line 1044, Column 10: end tag for element “form” which is not open

</form>

✉

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

4. Error Line 1410, Column 167: document type does not allow element “link” here

…-includes/css/jquery-ui-dialog.css?ver=20101224′ type=’text/css’ media=’all’ />

✉

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).

5. Error Line 1412, Column 56: there is no attribute “tabindex”

<div style=”display:none;”><form id=”wp-link” tabindex=”-1″>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

6. Error Line 1412, Column 60: required attribute “action” not specified

<div style=”display:none;”><form id=”wp-link” tabindex=”-1″>

✉

The attribute given above is required for an element that you’ve used, but you have omitted it. For instance, in most HTML and XHTML document types the “type” attribute is required on the “script” element and the “alt” attribute is required for the “img” element.

Typical values for type are type=”text/css” for <style> and type=”text/javascript” for <script>.

7. Error Line 1433, Column 95: there is no attribute “autocomplete”

…id=”search-field” class=”link-search-field” tabindex=”60″ autocomplete=”off” />

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

8. Error Line 1439, Column 12: end tag for “ul” which is not finished

<ul></ul>

✉

Most likely, you nested tags and closed them in the wrong order. For example <p><em>…</p> is not acceptable, as </em><em> must be closed before <p>. Acceptable nesting is: <p></em><em>…</em></p>

Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is “not finished”, not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (

<ul> and

<ol> require

<li>; <dl> requires <dt> and <dd>), and so on.

9. Error Line 1446, Column 12: end tag for “ul” which is not finished

<ul></ul>

✉

Most likely, you nested tags and closed them in the wrong order. For example <p><em>…</p> is not acceptable, as </em><em> must be closed before <p>. Acceptable nesting is: <p></em><em>…</em></p>

Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is “not finished”, not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (

<ul> and

<ol> require

<li>; <dl> requires <dt> and <dd>), and so on.

10. Error Line 1476, Column 170: document type does not allow element “link” here

…ymce/plugins/wplink/css/wplink.css?ver=20101224′ type=’text/css’ media=’all’ />

✉

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).

11. Error Line 1492, Column 143: there is no attribute “role”

…nEnabled mce_bold” href=”#” id=”wp_fs_bold” role=”button” aria-pressed=”false”>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

12. Error Line 1492, Column 165: there is no attribute “aria-pressed”

…nEnabled mce_bold” href=”#” id=”wp_fs_bold” role=”button” aria-pressed=”false”>

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

13. Error Line 1503, Column 32: there is no attribute “aria-orientation”

<div><span aria-orientation=”vertical” role=”separator” class=”mceSeparator”…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

14. Error Line 1503, Column 48: there is no attribute “role”

…span aria-orientation=”vertical” role=”separator” class=”mceSeparator”></span>…

✉

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

15. Error Line 1574, Column 35: required attribute “rows” not specified

<textarea id=”wp_mce_fullscreen”></textarea>

✉

The attribute given above is required for an element that you’ve used, but you have omitted it. For instance, in most HTML and XHTML document types the “type” attribute is required on the “script” element and the “alt” attribute is required for the “img” element.

Typical values for type are type=”text/css” for <style> and type=”text/javascript” for <script>.

16. Error Line 1574, Column 35: required attribute “cols” not specified

<textarea id=”wp_mce_fullscreen”></textarea>

✉

The attribute given above is required for an element that you’ve used, but you have omitted it. For instance, in most HTML and XHTML document types the “type” attribute is required on the “script” element and the “alt” attribute is required for the “img” element.

Typical values for type are type=”text/css” for <style> and type=”text/javascript” for <script>.

17. Error Line 1607, Column 31: end tag for element “div” which is not open

<div class=”clear”></div></div><!– wpwrap –>

✉

The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.</li>

</ol>

</ul>

</li>

</ol>

</ul>`

[Franky]

I just tried it using the current trunk version and I don’t get the form-validation issue. So @wputler: would you be willing to try out the trunk version?

[Anonymous]

Franky, This problem exists on my live site (3.3.5), but NOT on my testsite – trunk version downloaded 8/17.

[Franky]

So I can safely assume the problem is fixed 🙂

Thanks for testing!

[Anonymous]

You are welcome. Thanks for creating the plugin.

[Anonymous]

I will have to wait until the 26th. I will let you know if it works.

[Anonymous]

OK, this is a weird one… I have not had this problem since I responded a week+ ago.

For the last hour I’ve been editing and adding events – no problem, and then suddenly it started happening again a few minutes ago – out of the blue.

Hmmm… what had changed? The only thing I had done was add 2 attributes that I was playing with… so I deleted them – and voila – the footer issue disappeared.

Thought I’d pass this along in case it means anything to you… 🙂

[Franky]

Does this happen even if you use just one empty attribute?

[Franky]

Never mind, I think I found it …

[Author]

Posts