PDA

View Full Version : Invalid markup?



p|nK^bEe
February 26th, 2006, 19:53
I have a problem with this line of code:


<div id="navigations" style="position:absolute; width:225px; z-index:2; top: 450px; left: 1px;"><?php include ("navigations.php"); ?></div>

Dreamweaver gave "Invalid markup. Marked invalid beause it's an overlapping or unclosed tag."

Is there any problem with this code?

stuffradio
February 26th, 2006, 21:43
It could be something in the navigations.php file. Give us the exact error message please. Copy and paste it.

p|nK^bEe
February 26th, 2006, 23:04
It could be something in the navigations.php file. Give us the exact error message please. Copy and paste it.
I can't copy & paste. But I've typed out the error message above: "Invalid markup. Marked invalid beause it's an overlapping or unclosed tag."

The error is from the bolded parts...

kabatak
February 27th, 2006, 05:07
Don't mind dream weaver. It could be treating your PHP code as part of the markup. Use the real validator to check you pages. http://validator.w3.org

p|nK^bEe
February 27th, 2006, 21:20
It shows this:


Error Line 62 column 66: required attribute "ALT" not specified.
...moro/Images/banner3-1.jpg" width="800" height="675"></div>
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>.



Error Line 62 column 72: end tag for element "DIV" which is not open.
...banner3-1.jpg" width="800" height="675"></div>
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 occured in a script section of your document, you should probably read this FAQ entry.


I still don't understand the errors...