묻고답하기

1.3.1.2 업데이트 후 글이 읽히지 않습니다.

2010.01.21 01:53

허 민

제목과 같이.. 최종버젼 업그레이드후에..

단 한가지 기능..

1. 글 읽기가 불가능 합니다.

- 글의 목록과 간략한 내용은 보여지나 정작 링크를 통해서 게시물을 열람할 경우 페이지 오류가 납니다.

<유효성 검사를 해보니 다음과 같은 메세지가 나오더군요>

Errors found while checking this document as HTML 4.01 Transitional!

Result:	5 Errors, 3 warning(s)
Address:
Modified:	(undefined)
Server:	Apache/2.2.8 (Unix)
Size:	(undefined)
Content-Type:	text/html
Encoding:	utf-8
Doctype:	HTML 4.01 Transitional
Root Element:	html

Result:

5 Errors, 3 warning(s)

Address:

Modified:

(undefined)

Server:

Apache/2.2.8 (Unix)

Size:

(undefined)

Content-Type:

text/html

Encoding:

utf-8

Doctype:

HTML 4.01 Transitional

Root Element:

html

The W3C validators rely on community support for hosting and development.
Donate and help us build better tools for a better web.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

Unable to Determine Parse Mode!

The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
- the MIME Media Type (text/html) can be used for XML or SGML document types
- No known Document Type could be detected
- No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
- No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.

It is recommended to use a DOCTYPE declaration as the very first thing in your HTML document, to identify the precise language being used. For example, for a typical XHTML 1.0 document:
```
      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
      <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
        <head>
          <title>Title</title>
        </head>

        <body>
          
        </body>
      </html>
    
```
For XML documents, you may also wish to include an "XML Declaration" even before the DOCTYPE Declaration, but this is not well supported in older browsers. More information about this can be found in the XHTML 1.0 Recommendation.

The W3C QA Activity maintains a List of Valid Doctypes that you can choose from, and the WDG maintains a document on "Choosing a DOCTYPE".
No Character encoding declared at document level

No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

See this tutorial on character encoding for techniques and explanations.

↑ Top

Validation Output: 5 Errors

Line 2, Column 1: 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.
Line 22, Column 10: element "FRAMESET" undefined. Did you mean "frameset"?
```
<FRAMESET>
```
✉
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).
Line 23, Column 13: Attribute "SRC" is not a valid attribute. Did you mean "src"?
```
	<FRAME SRC="/xe/home" NAME="home">
```
✉

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.
Line 23, Column 29: Attribute "NAME" is not a valid attribute. Did you mean "name"?
```
	<FRAME SRC="/xe/home" NAME="home">
```
✉

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.
Line 23, Column 35: element "FRAME" undefined. Did you mean "frame"?
```
	<FRAME SRC="/xe/home" NAME="home">
```
✉

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).

----------------------------------------------------------------------------------

이상의 정보를 통해서 무엇이 문제인지 판단 할수 있을 까요??

이 게시물을

글쓴이	제목	최종 글
XE	공지 글 쓰기,삭제 운영방식 변경 공지 [16]	2019.03.05 _by 남기남
amd짱좋아	PHP 5.3.1 나왔습니다 [1]	2009.11.21 _by DuRi
중년	보드0.1로 바꿀려면.. [1]	2009.11.21 _by DuRi
MazeHz	onMouseOver시 Menu 글씨 색변경... [2]	2009.11.21 _by MazeHz
김정문1	하나의 레이아웃에 메뉴를 여러개 동시 사용가능한가요? [1]	2009.11.21 _by DuRi
애셔	게시판에 url 은 새창으로 링크 걸리도록 설정가능한가요? [1]	2009.11.21 _by dkb111
kbisama	로그인폼과 게시판화면 출력 질문드립니다.
sctaix	이곳에 이런 질문을 그렇지만;;; [1]	2009.11.21 _by Gekkou
엘카	zendoptimizer + eaccelerator 제대로 설치 된건지... [1]	2009.11.21 _by guny
김신애826	제로보드 설치 xe.1.3.0 에러 [2]	2009.11.21 _by piasol
kbisama	게시판 이미지 출력 질문드립니다. [1]	2009.11.21 _by DuRi
touhouTUNA	졸졸이 처럼 따라다니는 메뉴 만들고 싶어요 [2]	2009.11.21 _by DuRi
정현준656	분류별 권한은 동작하지 않나요???
김창환855	서버이전후 발생문제 [2]	2009.11.21 _by Gekkou
로꾸루톰	첨부 사진 업로드 에러 [2]	2009.12.31 _by 캥수
로꾸루톰	제로보드 4과 같이 사용하기 [1]	2009.11.21 _by 공듀
Uprin	댓글에 댓글달기창을 이런식으로 변경하고 싶습니다.
가우류	xe]로그인이 갑자기 반응이없습니다. [2]	2009.11.20 _by 곰이넷
김정문1	메뉴를 좀 많이 만들고 싶은데요.
오스카	게시판에서 [분류]를 선택 후 [GO]를 누르지 않고 이동하게 하려면 어떻게 하는지요... [2]	2009.11.20 _by 오스카
실속제로	여러개의 게시판에 올린 이미지 최근이미지출력이 가능한가요? [3]	2009.11.20 _by 실속제로

태그 쓰기

묻고답하기

1.3.1.2 업데이트 후 글이 읽히지 않습니다.

Errors found while checking this document as HTML 4.01 Transitional!

Notes and Potential Issues

Validation Output: 5 Errors

댓글 0

About

Get involved

Blog

Download

Support

Showcase