묻고답하기

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 남기남
라인	저좀도와주세요,, [2]	2008.10.24 _by 느까끼
Leaves@uz9	하나의 게시판에 몇명 정도의 인원이 접속하면 렉이 발생 할까요?
마성의천사	갑자기 제로보드 접근이 않되요... [1]	2008.10.24 _by 수지보더
포트거스.D.에이스	상태표시줄에 나오는 주소 없애는 방법
포트거스.D.에이스	로그인 하면 나오게 하는거.(보세요.)
석이-	방법이 없을까요? 설문조사시 아이디로 중복투표안되게끔...
백종연	자유게시판에 파일첨부 버튼이 클릭이 안됩니다 [3]	2020.03.14 _by BNU
Jeff Yi	제목이 짤려요~ 도와주세요. [2]	2008.10.25 _by acefull
꿀물청년	로그인,로그아웃시 질문.. [2]	2008.10.25 _by 꿀물청년
세노리타	플래쉬 안에 제로보드 게시판넣기 어떻게 하나요
☜ TeRy ☞	서브도메인이 바뀜에 따라 로그인 풀림현상 [2]	2008.10.25 _by 김영대
ddddffdfd	최근 이미지 출력에 붙여넣기 한 이미지가 안떠요 [3]	2008.10.25 _by 신지
가을길e	admin계정 숨김 할수 있나요??
\제로보드/	좌측메뉴 사용하는방법..?ㅠ [2]	2008.10.25 _by 백성찬
천　풍	님들 제로보드XE 하는데 호스트욛ㄷㄷㄷ; [5]	2008.10.25 _by k수호
꿀물청년	메인페이지 꾸미기 위젯추가 강의 화면이 실제와 다른점? [4]	2008.10.25 _by SMaker
TheZen#	제로보드 페이지에 회원 정보를 출력하고 싶습니다...
superion	프로필 사진 gif 애니매이션 [1]	2008.10.25 _by SMaker
할꼬없긔	알ftp 에서 제로보드xe 폴더가 지워지지 않습니다ㅠㅠ [3]	2008.10.25 _by 백성찬
\제로보드/	프레임셋으로 분리해서 bgm을 넣고싶은데..

태그 쓰기

묻고답하기

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