|
|
 | Submenu
Fra :  golife  | Vist : 529 gange
50 point
Dato : 12-06-05 13:12 |
|
Jeg har lavet en Menu i frontpage i tabelform... Nu vil jeg meget gerne lave en undermenu (submenu) til den... Kig på www.anett.dk
Er der nogen der ved hvordan man gør det???
| |
 | Accepteret svar
Fra : BjarneD  | 
Modtaget 60 point
Dato : 12-06-05 14:55 |
| | |
 | Kommentar
Fra : molokyle |
Dato : 12-06-05 19:54 |
|
Tjaeh... man kunne jo skifter fra Frontpage til Notesblok (notepad.exe), så man bli'r klar over hvad man egentlig laver 
Citat
This page is not Valid HTML 4.01 Transitional!
Below are the results of attempting to parse this document with an SGML parser.
Line 1, column 0: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<html><script language="JavaScript">
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with the HTML 4.01 Transitional DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
✉
Line 1, column 35: required attribute "TYPE" not specified
<html><script language="JavaScript">
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>.
✉
Line 22, column 5: document type does not allow element "HEAD" here
<head><meta name="title" content="Anett's" />
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).
✉
Line 22, column 44: character data is not allowed here
<head><meta name="title" content="Anett's" />
You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>) or forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes).
✉
Line 37, column 5: document type does not allow element "HEAD" here
<head><STYLE TYPE="text/css"><!--
✉
Line 48, column 6: required attribute "TYPE" not specified
<style>
✉
Line 61, column 22: "FPROLLOVERSTYLE" is not a member of a group specified for any attribute
<style fprolloverstyle>A:hover {color: #FFFFFF; text-decoration: blink; font-wei
✉
Line 61, column 22: required attribute "TYPE" not specified
<style fprolloverstyle>A:hover {color: #FFFFFF; text-decoration: blink; font-wei
✉
Line 65, column 60: document type does not allow element "BODY" here
<body style="background-attachment: fixed" bgcolor="#EAE5E1">
✉
Line 69, column 89: required attribute "ALT" not specified
...brygge5.jpg" width="852" height="153"></div>
✉
Line 75, column 130: there is no attribute "HEIGHT"
...B3B3" width="856" id="table1" height="29" background="images/spacer.gif">
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.
✉
Line 75, column 146: there is no attribute "BACKGROUND"
..." id="table1" height="29" background="images/spacer.gif">
✉
Line 130, column 22: there is no attribute "SRC"
<p> <bgsound src="jungle.wav" loop="1"> </p>
✉
Line 130, column 40: there is no attribute "LOOP"
<p> <bgsound src="jungle.wav" loop="1"> </p>
✉
Line 130, column 43: element "BGSOUND" undefined
<p> <bgsound src="jungle.wav" loop="1"> </p>
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 145, column 58: required attribute "ALT" not specified
<img src="http://www.linkworld.dk/toplisten/toplisten.gif"></a>
✉
Line 150, column 57: there is no attribute "BORDER"
...c="midten.htm" align="middle" border="0" frameborder="0" style="border: 4px r
✉
Line 178, column 65: cannot generate system identifier for general entity "view"
....dk/php/showpeakcounter.php?id=35279&view=80" TYPE="text/javascript" Language
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
✉
Line 178, column 65: general entity "view" not defined and no default entity
....dk/php/showpeakcounter.php?id=35279&view=80" TYPE="text/javascript" Language
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
✉
Line 178, column 69: reference to entity "view" for which no system identifier could be generated
...php/showpeakcounter.php?id=35279&view=80" TYPE="text/javascript" Language="Ja
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
✉
Line 178, column 64: entity was defined here
...k.dk/php/showpeakcounter.php?id=35279&view=80" TYPE="text/javascript" Languag
Line 179, column 206: required attribute "ALT" not specified
...5279" title='PeakCounter.dk' border=0><img src="http://www.peak.dk/php/peakco
✉
Line 179, column 291: required attribute "ALT" not specified
...p?id=35279" height=1 width=1 border=0></a></NOSCRIPT>
✉
Line 181, column 29: required attribute "TYPE" not specified
<script language="JavaScript">
✉
Line 182, column 234: end tag for element "A" which is not open
...(location.pathname)+'" border="0"></a>');
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.
✉
Line 191, column 27: required attribute "TYPE" not specified
<script language=JavaScript>
✉
Line 197, column 3: end tag for element "P" which is not open
</p>
✉
Line 203, column 6: "HEAD" not finished but containing element ended
</html>
✉
Line 203, column 6: "HEAD" not finished but containing element ended
</html>
✉
Line 203, column 6: end tag for "HTML" which is not finished
</html>
Most likely, You nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element (e.g. 'ul') which requires a child element (e.g. 'li') that you did not include. Hence the parent element is "not finished", not complete. |
Citat
Message Summary
CSE HTML Validator Lite generated 6 error messages and 1 warning message when checking this web page. These problems could damage this web page's search engine rankings as well as cause viewing problems for visitors. It is highly recommended that any problems be corrected.
URL: <http://www.anett.dk/>, Local Time: 12:51:30 PM, Date: Sunday, June 12, 2005
Messages
Type Line Message
Error 1 The "script" element cannot be used here. It is not contained in an element that allows its use. This element may be contained in "body" and "head".
<html><script language="JavaScript">
Error 22 The "head" tag must have an end tag but the end tag was not found.
<head><meta name="title" content="Anett's" />
Error 37 The "head" element cannot be used here. It is nested in another "head" tag and cannot be nested. Did you forget to close the previous "head" tag? This element may be contained in "html". This element may not be contained in "body" and "head".
<head><STYLE TYPE="text/css"><!--
Error 61 The "fprolloverstyle" attribute is not valid for the "style" element. Some valid attributes for this element are: "dir", "disabled", "lang", "media", "title", and "type".
<style fprolloverstyle>A:hover {color: #FFFFFF; text-decoration: blink; font-weight: bold}
Error 65 The "body" element cannot be used here. It is contained in a "head" tag that cannot contain it. This element may be contained in "html" and "noframes". This element may not be contained in "frameset" and "head".
<body style="background-attachment: fixed" bgcolor="#EAE5E1">
Warning 178 [64] An invalid entity was found in the value for the "SRC" attribute. Often this is because the ampersand character was not properly encoded as the entity "&". Example 1: href="script.cgi?var1=value&var2=value" should be href="script.cgi?var1=value&var2=value", example 2: alt="For him & her" should be alt="For him & her". Note that the ampersand in the values was encoded as "&".
<SCRIPT SRC="http://www.peak.dk/php/showpeakcounter.php?id=35279&view=80" TYPE="text/javascript" Language="JavaScript"></SCRIPT>
Error 203 The end tag for "head" (opened in line 22) should appear before the end tag for "html" (nesting error).
</html>
Comment The lite edition missed more than 20 additional errors and more than 20 additional warnings that the standard or professional edition would have found. |
 </MOLOKYLE>
| |
| Kommentar
Fra : BjarneD |
Dato : 12-06-05 20:20 |
|
Det Molokyle lavede var at køre en test på din side for at se om den overholder en international standard og det gør den ikke fordi Microsoft har indbygget flere funktioner til at blive lavet færdig under udgivelse (eks. fælles kanter) og så er der lavet flere kombinationsfunktioner.
InternetExplorer kan læse alle de funktioner og Mozilla kan læse de fleste.
Jeg bruger selv FP og er vældig glad for den fordi jeg sparer meget tid på ikke at skulle gennemgå for script fejl hele tiden.
Jeg kan jo så bare spørge html eksperten om hvor den international standard står når det drejer sig om CMS der anvender php /asp??
| |
| Kommentar
Fra : golife |
Dato : 12-06-05 20:25 |
|
ok Bjarne???
Jeg fatter ikke en meter... Har bare lært mig selv det jeg kan (eller ikke kan)... Det er bare hygge for mig!!! Kan du måske så fortælle mig hvordan man retter de fejl der er???
| |
| Kommentar
Fra : BjarneD |
Dato : 12-06-05 20:42 |
|
Du har godt nok en del scriptfejl, der får mig til at tro, at du har kopieret nogle ting ind de forkerte steder og for at være helt ærlig så er det fordi jeg ikke syntes at det er sjovt at læse script, at jeg bruger FrontPage.
Jeg lagde specielt mærke til at du har en <HEAD> midt i det hele og, at du har et script over <HEAD> sektionen som så heller ikke virker.
Når man anvender FrontPage og så indkopierer funktioner som scripts skal man være omhyggelig med at anbringe det korrekt. Dit højrekliks script skulle have været et sted imellem <HTML><HEAD> og </HEAD>
Det er ikke alle fejlene der er funktionsbetingede, men nogen er.
FrontPage har gjort mig meget rusten i kildelæsning og jeg har aldrig været så skrap, at jeg kan lave det i Notepad og bliver det aldrig.
Hvis du for eksempel bruger nogle af de script jeg linkede til i starten vil du se at der vises hvor de skal anbringes.
Men jeg orker ikke at stave mig igennem din ellers flotte side.
| |
| Kommentar
Fra : molokyle |
Dato : 12-06-05 20:57 |
|
Tjaeh... jeg sér nu Frontpage og de extensions der hører til, samt Microsofts browser afhængige parametre, som endnu et forsøg på at fasttømre et 'monopol' på; hvorledes en webside skal kodes (..uden skelen til hvorledes webstandarden, som anbefalet af http://w3.org og http://www.webstandards.org/ ellers er skruet sammen ) i et forsøg på at udbygge og fastholde dette 'monopol' !!!
[hør] ..er det godt ???
Tjaeh... Vi sælger mange af dem !!!
 </MOLOKYLE>
| |
| Kommentar
Fra : molokyle |
Dato : 12-06-05 21:11 |
| | |
| Kommentar
Fra : molokyle |
Dato : 12-06-05 21:14 |
| | |
| Kommentar
Fra : golife |
Dato : 13-06-05 00:53 |
| | |
 | Du har følgende muligheder | |
|
Eftersom du ikke er logget ind i systemet, kan du ikke skrive et indlæg til dette spørgsmål.
Hvis du ikke allerede er registreret, kan du gratis blive medlem, ved at trykke på "Bliv medlem" ude i menuen.
| |
|
|