묻고답하기

  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 남기남
한스김 저만의 문제가 아니었군요.. 하지만 해결책을 찾을수가 없네요.. [2] 2010.01.21 by 이쁜이쁜이
so_simple 도와주세요 ㅠ_ㅠ게시글 선택하여 출력하기 [1] 2010.01.21 by 라르게덴
낭만사객 페이지 모듈에 DB 자료 가져오기를 못하고 있습니다 [1] 2010.01.21 by 라르게덴
sungjaeq [고수만] 쪽지 보내기 보내기 사라짐현상 (이미지 첨부함) [1] file 2010.01.21 by 라르게덴
준희^^+ 카테고리별로 최근글 뽑아오기, 도움좀 --;; [1] 2010.01.21 by 라르게덴
궁금이658 제로보드4처럼 아웃로그인폼 어떻게 만들지요 [1] 2010.01.21 by Gekkou
낭망백수 로그인, 로그아웃, 가입 등 액션 처리이후 리다이렉팅 [4] 2010.01.21 by 낭망백수
장우136 추천수를 숫자 대신 이미지로 나열하기  
영구만세 갤러리 목록에서 이미지가 나오지 않네요? [1] file 2010.01.21 by 오델라가루
임수정찜했다 홈페이지 첫화면에 게시판 띄우기 질문 [1] file 2010.01.21 by 오델라가루
cje321 업데이트 후 이전에 쓰던 레이아웃을 쓸려면 [1] 2010.01.21 by 오델라가루
autism26 카페 생성시 site_srl를 입력하라고 뜹니다 file  
빛바랜남자 메일서버 구축해야되나요? [1] 2010.01.21 by 공듀
연공중독 제로보드4를 사용하다 문제점이 발생해서 질문드립니다. [1] 2010.01.21 by shuden
젠이 XE 자료실에서 누가 자료를 다운받았는지 남도록 할 수 있나요? [1] 2010.01.21 by 라르게덴
겨울소년 ssl 선택적으로 적용하기 관련 질문입니다.  
봉이지비 모듈 Template에서 Jquery 사용 오류 [2] 2010.01.21 by 봉이지비
reform 페이지수정  
허 민 1.3.1.2 업데이트 후 글이 읽히지 않습니다.  
Hide_D 단일 모듈에 그룹별 권한을 설정하는 방법 [1] 2010.01.21 by 된장맛껌
박노열 쉬운 설치 후 동작 업데이트 안되는 경우에 대한 질문입니다. [1] file 2010.01.21 by 백성찬
오델라가루 성별 아이콘 확장변수 게시판 리스트와 내용페이지 넣는 방법 가르쳐주세요  
빛바랜남자 DB 삭제복구 자세히좀요! ㅠㅠ  
Xman 샌드위치 샵 홈페이지 구축에 대한 조언 부탁드립니다.  
영재아닌영재 회원가입 부분 관련  
비행소년™ Cafe XE 레이아웃 라이프팟 버그 file  
검은고양이- 외부페이지(php)에서 데이터전송 질문 [2] 2010.01.21 by 오뎅궁물
욜로로우 가끔씩 홈페이지 메뉴가 안나와요 file  
빛바랜남자 DB삭제 복구문제예요..해결책좀요.. [1] 2010.01.21 by Gekkou
소피아7 서버 이전 때문에 질문드립니다. [1] 2010.01.21 by Gekkou
태그 쓰기