묻고답하기

  2. Support
  3. 묻고답하기

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)
:
Modified: (undefined)
Server: Apache/2.2.8 (Unix)
Size: (undefined)
Content-Type: text/html
: utf-8
: HTML 4.01 Transitional
Root Element: html
Validators Donation Program LogoThe W3C validators rely on community support for hosting and development.
Donate and help us build better tools for a better web.
<script type="text/javascript" src="http://www.w3.org/QA/Tools/don_prog.js"></script>
Options

Help on the options is available.

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.

  1. Warning 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.

  2. Warning 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 of document ... -->
        </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".

  3. Info 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

  1. Error 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.

  2. Error 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).
  3. Error 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.

  4. Error 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.

  5. Error 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 남기남
lmjy2k 가입시 프로필 사진 필수인데, 안 넣고도 가입이 되네요ㅠㅠ 해결 좀..  
greenleaf 언어선택이 안됩니다 [1] 2012.03.22 by greenleaf
하르로데 네임팟 블로그가 자꾸 이상하게 연결이 됩니다.!  
lmjy2k 동우님~질문..  
zwj0813 회원, 게시판, 문서, 첨부파일다 없어졌어요~댓글만 남았는데요 [1] 2012.03.22 by 날마다좋은날
코코볼이 게시판에서 댓글-도움말 어떻게없애요? [1] 2012.03.22 by 날마다좋은날
배워서남준다 외부페이지 변수 전달에 대해 다시한번 도움요청합니다. [1] 2012.03.22 by lyn
candyelf 사이트맵 메뉴 추가 삭제 이동이 안됩니다.  
nexonx 게시판에서 글의 주소가 안 나오게 했으면 합니다...; [3] 2012.03.22 by 숙희
onionhk 확장변수 값을 게시판 리스트에 보여지게 하는 방법 [1] 2012.03.22 by 익멍
onionhk 한페이지에 두개의 게시판이 보여지게 하고싶어요  
이상철421 1.5.2 어드민에서 게시판, 모듈, 페이지 생성은 어디서 하나요?  
포풍젖산 msg_ftp_invalid_auth_info FTP 설정 목록 가져오기 오류 [1] 2012.03.22 by 난나야S2
Seunghyun xe에 내장된 jw플레이어 확장자 구분없이 모든 동영상 재생  
큰돌♡ 1.5.2에서 쉬운 설치에 [설치] 버튼이 안 뜨네요. [1] 2012.03.22 by 송동우
따라궁디 네이버에서 검색된 페이지 경로가 틀리게 나옵니다. [1] 2012.03.22 by 궁금한것이많앙
튜닝마니아 신고 버튼 재확인  
byneet index.php 와 index.html 질문죰요 [1] 2012.03.21 by 샹하이
참치찌개 블라인드 처리  
필살인생 리퍼러 통계 어떻게 하면 볼 수 있나요?  
태그 쓰기