XML 解析错误:文档元素后的垃圾

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/1364101/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-09-06 12:43:06  来源:igfitidea点击:

XML Parsing Error: junk after document element

xmlparsing

提问by Marty

I am getting this error when I try to view my dynamically generated (PHP) XML document:

当我尝试查看动态生成的 (PHP) XML 文档时出现此错误:

XML Parsing Error: junk after document element Location: http://dev.leisurepublishing.com/vtc/master.xml.phpLine Number 17, Column 1: ^

XML 解析错误:文档元素后的垃圾位置:http: //dev.leisurepublishing.com/vtc/master.xml.php第 17 行,第 1 列:^

I have googled and looked through the document and I can't figure out what's wrong, can someone help me spot the problem?

我用谷歌搜索并查看了文档,但我无法弄清楚出了什么问题,有人可以帮我找出问题所在吗?

<?php

header("Content-type: text/xml");
require_once("admin/assets/db_connect.php");

echo "<?xml version=\"1.0\" encoding=\"utf-8\"?>"
?>

<master> 

<categories>
    <category>
        <gsm>GFoo</gsm>
        <category_id>1</category_id>
    </category>
    <category>
        <gsm>SFoo</gsm>
        <category_id>2</category_id>
    </category>
    <category>
        <gsm>MFoo</gsm>
        <category_id>3</category_id>
    </category>
</categories>

<region_codes>
    <code>
        <code_id>11000</code_id>
        <code_name>Central</code_name>
    </code>
    <code>
        <code_id>12000</code_id>
        <code_name>Eastern</code_name>
    </code>
    <code>
        <code_id>13000</code_id>
        <code_name>Western</code_name>
    </code>
    <code>
        <code_id>14000</code_id>
        <code_name>Northern</code_name>
    </code>
</region_codes>

<headers>
    <header>
        <header_id>1</header_id>
        <header_name>Featured A</header_name>
    </header>
    <header>
        <header_id>2</header_id>
        <header_name>Featured B</header_name>
    </header>
    <header>
        <header_id>3</header_id>
        <header_name>Featured C</header_name>
    </header>
</headers>

<advertisers>
    <partner>
        <name>Crestline</name>
        <file>crestline.asp</file>
        <logo>microsites/crestline/logo.jpg</logo>
        <blurb>blah blah blah.</blurb>
        <cat>3</cat>
        <region>15000</region>
        <header_type>1</header_type>
    </partner>
    <partner>
        <name>Example 2</name>
        <file>example2.asp</file>
        <logo>microsites/meeting/example2.jpg</logo>
        <blurb>example 2 example 2 example 2 example 2 example 2 example 2 example 2 example 2 example 2 .</blurb>
        <cat>2</cat>
        <region>14000</region>
        <header_type>1</header_type>
    </partner>
    <partner>
        <name>Example 3</name>
        <file>example3.asp</file>
        <logo>microsites/meeting/example3.jpg</logo>
        <blurb>example 3 example 3 example 3 example 3 example 3 example 3 .</blurb>
        <cat>3</cat>
        <region>11000</region>
        <header_type>1</header_type>
    </partner>
  <partner>
    <name>Example 4</name>
    <file>example4.asp</file>
    <logo>microsites/meeting/example4.jpg</logo>
    <blurb>example 4 example 4 example 4 example 4 example 4 example 4.</blurb>
    <cat>1</cat>
    <region>11000</region>
    <header_type>1</header_type>
  </partner>
  <partner>
    <name>Example 5</name>
    <file>example5.asp</file>
    <logo>microsites/meeting/example5.jpg</logo>
    <blurb>example 5 example 5 example 5 example 5 example 5 example 5.</blurb>
    <cat>1</cat>
    <region>11000</region>
    <header_type>1</header_type>
  </partner>

  <partner>
    <name>Example 6</name>
    <file>example6.asp</file>
    <logo>microsites/meeting/example6.jpg</logo>
    <blurb>example 6 example 6 example 6 example 6 example 6 example 6.</blurb>
    <cat>2</cat>
    <region>11000</region>
    <header_type>2</header_type>
  </partner>
  <partner>
    <name>Example 7</name>
    <file>example7.asp</file>
    <logo>microsites/meeting/example7.jpg</logo>
    <blurb>example 7 example 7 example 7 example 7 example 7 example 7.</blurb>
    <cat>3</cat>
    <region>11000</region>
    <header_type>3</header_type>
  </partner>

  <partner>
    <name>Example 8</name>
    <file>example8.asp</file>
    <logo>microsites/meeting/example8.jpg</logo>
    <blurb>example 8 example 8 example 8 example 8 example 8 example 8.</blurb>
    <cat>1</cat>
    <region>11000</region>
    <header_type>3</header_type>
  </partner>

  <partner>
    <name>Example 9</name>
    <file>example9.asp</file>
    <logo>microsites/meeting/example9.jpg</logo>
    <blurb>example 9 example 9 example 9 example 9 example 9 example 9.</blurb>
    <cat>1</cat>
    <region>11000</region>
    <header_type>3</header_type>
  </partner>

  <partner>
    <name>Example 10</name>
    <file>example10.asp</file>
    <logo>microsites/meeting/example10.jpg</logo>
    <blurb>example 10 example 10 example 10 example 10 example 10 example 10.</blurb>
    <cat>1</cat>
    <region>12000</region>
    <header_type>2</header_type>
  </partner>

</advertisers>

</master>

<?php

require_once("admin/assets/db_disconnect.php");

?>

回答by vishal

Remove all PHP header tags except xmland add:

删除所有 PHP 标头标签,xml并添加:

<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
</head>

回答by Marty

Nevermind. I found that the path to the last require_once() was bad and when I fixed the path the parse error went away too.

没关系。我发现最后一个 require_once() 的路径不好,当我修复路径时,解析错误也消失了。