/ Forside/ Teknologi / Internet / Hjemme sider / Spørgsmål
Login
Glemt dit kodeord?
Brugernavn

Kodeord


Reklame
Top 10 brugere
Hjemme sider
#NavnPoint
molokyle 23766
Klaudi 7947
bentjuul 7763
BjarneD 4584
severino 4460
Manse9933 4366
natmaden 3985
disken 3947
miritdk 3593
10  refi 3578
Kommentarboks
Fra : Coollemon
Vist : 4759 gange
140 point
Dato : 10-01-07 19:31

Jeg har en hjemmeside, hvor jeg laver indlæg. Jeg laver den i dreamweaver.

Jeg vil gerne have en kommentarboks under hvert indlæg, så folk kan kommentere på det jeg skriver. kommentarene skal så alle ligge under mit indlæg, så der nærmest kan komme en debat under mit indlæg.`Mange blogs har lavet det sådan, hvis det giver en bedre ide om hvad jeg ønsker.

Hvordan opretter jeg sådan en kommentarboks?

- kan jeg gøre det i frontpage eller dreamweaver, eller kan man hente et slags program på nettet der laver en kommentarboks?

 
 
Kommentar
Fra : natmaden


Dato : 11-01-07 00:13

ja du kan, men måden handler mere om hvilket sprog dine sider er lavet i.
Og måske hvor henne du har dine sider.

http://one.com har eks et blogsystem med på deres webhotel,
hvor den er på dansk.
Hjemmesiden for programmet er på fransk http://www.iloblog.com/


Kommentar
Fra : Coollemon


Dato : 11-01-07 08:24

Det er en dansk side og den ligger på surftown.dk

Den er skrevet på dansk. Man kan få gratis quickpolls, som man kan oprette og lægge ind på isin side. Det kunne godt være der var et lignende system for kommentarbokse.

Hvis man kan lave det selv og der var et site med noget allerede færdigt html, ville det være endnu bedre, så man kunne sætte sit personlige præg

Kommentar
Fra : natmaden


Dato : 11-01-07 15:04

Tror ikke lige at jeg kan hjælpe dig !

Men da du skriver at du bruger html og dreamweaver.
Hvori gemmer du så det indskrevne.
Jeg forestiller mig at du bruger noget ASP eller PHP

Du burde kunne flette noget kode ind i din eksisterende.

Surftown har vist ikke nogen færdig service til en blog,
er det noget du selv laver eller er det et færdigt modul ?

Det ville hjælpe hvis jeg kunne se din side.
Hvis du ikke vil ligge et link her, kan du ligge det i et personlig besked til mig,
det gør du ved at trykke dig ind på min profil.

Mvh. Jørgen

Kommentar
Fra : Coollemon


Dato : 11-01-07 15:07

www.blivoplyst.dk er sitet. Under hvert indlæg vil jeg gerne sætte en kommentarboks ind, så man kan bruge den i stedet for et forum

Kommentar
Fra : molokyle


Dato : 20-01-07 21:28

Det vil nok være nemmere, hvis du helt skrottede siden (..samt Dreamweaver), begyndte forfra og lavede din side i et CMS system som:

1.) PHP-Fusion : http://php-fusion.co.uk/news.php
2.) phpbb : http://www.phpbb.com/

..eller lign. for mage til fejlbehæftet spagettikode skal man lede længe efter:
Citat
No DOCTYPE found! Attempting validation with HTML 4.01 Transitional. The DOCTYPE Declaration was not recognized or is missing. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax. Validation has been performed using a default "fallback" Document Type Definition that closely resembles "HTML 4.01 Transitional", but the document will not be Valid until you have corrected this problem with the DOCTYPE Declaration.

Learn how to add a doctype to your document from our FAQ.

This page is not Valid (no Doctype found)!
Below are the results of attempting to parse this document with an SGML parser.

Error Line 1 column 0: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>".
<html>The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback 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.

?

Error Line 3 column 9: document type does not allow element "NOSCRIPT" here.
<noscript><img src="http://minstat.dk/log/image.php?site_id=119" alt="" width="1The 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).

?

Error Line 6 column 5: document type does not allow element "HEAD" here.
<head>?

Error Line 8 column 14: "DESIGN" is not a member of a group specified for any attribute.
<Dette design er udarbejded af duno>?

Error Line 8 column 17: "ER" is not a member of a group specified for any attribute.
<Dette design er udarbejded af duno>?

Error Line 8 column 28: "UDARBEJDED" is not a member of a group specified for any attribute.
<Dette design er udarbejded af duno>?

Error Line 8 column 31: "AF" is not a member of a group specified for any attribute.
<Dette design er udarbejded af duno>?

Error Line 8 column 35: "DUNO" is not a member of a group specified for any attribute.
<Dette design er udarbejded af duno>?

Error Line 8 column 35: element "DETTE" undefined.
<Dette design er udarbejded af duno>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),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case.

?

Error Line 32 column 22: "FPROLLOVERSTYLE" is not a member of a group specified for any attribute.
<style fprolloverstyle>?

Error Line 32 column 22: required attribute "TYPE" not specified.
<style fprolloverstyle>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 39 column 36: document type does not allow element "BODY" here.
<body link="#000000" vlink="#000000">?

Error Line 43 column 89: there is no attribute "HEIGHT".
...llspacing="1" cellpadding="0" height="807">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.

?

Error Line 50 column 23: there is no attribute "SRC".
<embed src="Flash/top logo.swf" width="575" height="115" loop="false?

Error Line 50 column 50: there is no attribute "WIDTH".
...embed src="Flash/top logo.swf" width="575" height="115" loop="false" align="t?

Error Line 50 column 63: there is no attribute "HEIGHT".
...ash/top logo.swf" width="575" height="115" loop="false" align="top" quality="?

Error Line 50 column 74: there is no attribute "LOOP".
...o.swf" width="575" height="115" loop="false" align="top" quality="high" plugi?

Error Line 50 column 88: there is no attribute "ALIGN".
...575" height="115" loop="false" align="top" quality="high" pluginspage="http:/?

Error Line 50 column 102: there is no attribute "QUALITY".
...15" loop="false" align="top" quality="high" pluginspage="http://www.macromedi?

Error Line 50 column 121: there is no attribute "PLUGINSPAGE".
...ign="top" quality="high" pluginspage="http://www.macromedia.com/go/getflashpl?

Error Line 50 column 172: there is no attribute "TYPE".
...cromedia.com/go/getflashplayer" type="application/x-shockwave-flash"></embed>?

Error Line 50 column 203: element "EMBED" undefined.
... type="application/x-shockwave-flash"></embed>?

Error Line 69 column 40: invalid comment declaration: found name character outside comment but inside comment declaration.
<!--- Her slutter din nyhed --->?

Info Line 69 column 10: comment declaration started here.
<!--- Her slutter din nyhed --->Error Line 69 column 41: character data is not allowed here.
<!--- Her slutter din nyhed --->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).

?

Error Line 70 column 40: invalid comment declaration: found name character outside comment but inside comment declaration.
<!--- Her starter din nyhed --->?

Info Line 70 column 10: comment declaration started here.
<!--- Her starter din nyhed --->Error Line 75 column 51: there is no attribute "BORDERCOLOR".
<table width="100%" border="0" bordercolor="#E9E9E9" bgcolor="#E9E9E9">?

Error Line 77 column 55: there is no attribute "BORDERCOLOR".
...dth="99%" align="center" bordercolor="#E9E9E9" bgcolor="#E9E9E9"><p align="le?

Warning Line 82 column 369: cannot generate system identifier for general entity "mforum".
...oplyst.forumup.dk/viewtopic.php?t=13&mforum=blivoplyst" target="_blank">HER</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 "&amp;" (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 &aelig; are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

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.

?

Error Line 82 column 369: general entity "mforum" not defined and no default entity.
...oplyst.forumup.dk/viewtopic.php?t=13&mforum=blivoplyst" target="_blank">HER</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.

?

Error Line 82 column 375: reference to entity "mforum" for which no system identifier could be generated.
....forumup.dk/viewtopic.php?t=13&mforum=blivoplyst" target="_blank">HER</a> <..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.

?

Info Line 82 column 368: entity was defined here.
...voplyst.forumup.dk/viewtopic.php?t=13&mforum=blivoplyst" target="_blank">HER<Error Line 85 column 116: required attribute "ALT" not specified.
...an_stor.jpg" width="250" height="333"></p>?

Error Line 115 column 103: end tag for element "SCRIPT" which is not open.
...qp/qp/QPServlet?pollid=AF5A6></script>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.

?

Error Line 130 column 167: required attribute "ALT" not specified.
...emotion.gif" width="153" height="122"></a></p>?

Error Line 137 column 90: required attribute "ALT" not specified.
.../estland.jpg" width="153" height="92"></p>?

Error Line 149 column 12: end tag for "TABLE" omitted, but its declaration does not permit this.
</body>You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

?

Info Line 43 column 2: start tag was here.
<table border="0" width="533" bgcolor="#000000" cellspacing="1" cellpadding="0Error Line 149 column 12: end tag for "CENTER" omitted, but its declaration does not permit this.
</body>?

Info Line 42 column 2: start tag was here.
<center>Error Line 149 column 12: end tag for "DIV" omitted, but its declaration does not permit this.
</body>?

Info Line 41 column 0: start tag was here.
<div align="center">Error Line 150 column 6: "HEAD" not finished but containing element ended.
</html></td>?

Error Line 150 column 6: end tag for "HTML" which is not finished.
</html></td>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 which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, <head> generally requires a <title>, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.

?

Error Line 150 column 11: end tag for element "TD" which is not open.
</html></td>?

Error Line 151 column 8: end tag for element "TR" which is not open.
</tr>?

Error Line 152 column 7: document type does not allow element "TR" here.
<tr>?

Error Line 157 column 9: end tag for element "TABLE" which is not open.
</table>?

Error Line 160 column 5: end tag for element "DIV" which is not open.
</div>?

Error Line 161 column 6: end tag for element "BODY" which is not open.
</body></html>?

Error Line 161 column 13: end tag for element "HTML" which is not open.
</body></html>?


*IMHO* </MOLOKYLE>





Kommentar
Fra : Coollemon


Dato : 20-01-07 21:43

Jeg dropper ikke Deamweaver.. Sitet er bygger på en skabelon jeg har fået. Jeg er ikke en ekspert og du har sikkert ret i det ikke er optimalt. Sitet virker dog :)

Jeg vil gerne have en kommentar boks som f.eks. denne: http://samfund-politik.danskelinks.dk/debat/detailpage.asp?site=100

Skriv en kommentar omkring websiden: CensurNyt.dk
Dit Navn:
Validering: 7 + 9 =

Kommentar:


Det ser enkelt ud, men jeg ved ikke hvor jeg skal starte. Hvordan laver man sådan en som denne??






Kommentar
Fra : molokyle


Dato : 20-01-07 22:32
Kommentar
Fra : molokyle


Dato : 20-01-07 22:34
Kommentar
Fra : Coollemon


Dato : 20-01-07 23:25

Jeg sidder og roder lidt med .php udgaven nu.. jeg har fundet ud af at sætte en boks ind (se på http://www.blivoplyst.dk/Afskaf_selskabsskat.php )

Meg hvordan sætter jeg den til at poste indlægget nede under kommentarboksen, så man kan se hvem der poster det, personens mail og hp og kommentaren... i bund og grund på samme måde som kommentarfelterne er sat op, bare som en post i stedet

Accepteret svar
Fra : natmaden

Modtaget 140 point
Dato : 24-01-07 18:34

Andre bruger en box(mulighed) ud fra hvert indlæg,
er det du søger en 'allround' boks ?
det der er svært er at flette den ind i dine allerede eksisterende sider,
man kunne forestille sig at den nye tilføgelse startede i dag,
det ville sikkert give kludder i dine sider fra i går,
så må man

Godkendelse af svar
Fra : Coollemon


Dato : 24-01-07 22:07

Tak for svaret natmaden. Du er kommet så tæt på som det er muligt, så går over til et blogsystem.. Tak for forsøget!

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.
Søg
Reklame
Statistik
Spørgsmål : 177415
Tips : 31962
Nyheder : 719565
Indlæg : 6407849
Brugere : 218876

Månedens bedste
Årets bedste
Sidste års bedste