(PHP 5)

DOMDocument::load Загрузка XML из файла


public mixed DOMDocument::load ( string $filename [, int $options = 0 ] )

Загружает XML документ из файла.


Пути к файлам в стиле Unix с прямыми слешами могут отрицательно сказаться на работоспособности скриптов в среде Windows; используйте функцию realpath() для исключения подобных ситуаций.

Список параметров


Путь к XML документу.


Побитовое ИЛИ констант настройки libxml.

Возвращаемые значения

Возвращает TRUE в случае успешного завершения или FALSE в случае возникновения ошибки. При статическом вызове возвращает объект класса DOMDocument или FALSE в случае возникновения ошибки.


Если через аргумент filename передана пустая строка или файл ничего не содержит, будет сгенерировано предупреждение. Это предупреждение генерируется не libxml, поэтому оно не может быть обработано обработчиками ошибок библиотеки libxml.

Этот метод может быть вызван статически, но при этом будет сгенерирована ошибка уровня E_STRICT.


Пример #1 Создание документа

= new DOMDocument();

Смотрите также

  • DOMDocument::loadXML() - Загрузка XML из строки
  • DOMDocument::save() - Сохраняет XML дерево из внутреннего представления в файл
  • DOMDocument::saveXML() - Сохраняет XML дерево из внутреннего представления в виде строки


Suppose you wanted to dynamically load an array from an .XSD file. This method is your guy. just remember to use the actual xs: portion in xpaths and such.

All the other "load" methods will error out.

= array();
$xsdstring "/htdocs/api/xsd/common.xsd";
$XSDDOC = new DOMDocument();
$XSDDOC->preserveWhiteSpace false;
if (
$xsdpath = new DOMXPath($XSDDOC);
    foreach (
$attributeNodes->childNodes as $attr
$attributes$attr->getAttribute('value') ] = $attr->getAttribute('name');
2005-10-18 20:08:09
Note that this method uses the local file system before doing anything remote. The 'disadvantage' would be that if you would do the following:
= new DOMDocument;

This would not make the method read the actual output of the news.php file --presumably valid xml data--, but the file contents --obviously this would be php code. So this will return an error saying news.php is missing the xml declaration and maybe the xml start-tag

What would work is the following:

= new DOMDocument;

This will force a http request to be used to get this file instead of just locally reading it and the file just returning code
2007-01-18 10:50:07
In reply to BadGuy [at] BadGuy [dot] nl

When the news.php file is located on the same server, like you said in the first example then wouldn't work, but you should use http://localhost/xmlsource/news.php or
2007-06-02 07:39:48
BadGuy´s note may be confusing since what he depicts is no special property of the relevant method. PHP works always in and on a local file system which means that if you want to use resources from other systems or - what is, indeed, BadGuy´s problem - need resources that have been dealt with by other programs or processes, you have to state and manage that explicitly in your code. PHP is just a quite normal program in that.

BadGuy´s solution is using the "http wrapper" to get output from another process (see "wrappers" in the PHP manual). Doing this, the appropriate syntax for http calls has to be respected.
2007-08-30 06:48:31
NOTE, will not load successfully if there is a comment at the beginning of the file before the <?xml version="1.0" ?> declaration!
2008-07-15 19:53:28
If you are loading xml with the intention of validating it against an internal dtd and you have experienced issues with the validation it could be related to missing LIBXML constants.

I found this post by "aidan at php dot net" in root level dom docs and thought it might be more useful here:
As of PHP 5.1, libxml options may be set using constants rather than the use of proprietary DomDocument properties.

DomDocument->resolveExternals is equivilant to setting

DomDocument->validateOnParse is equivilant to setting

PHP 5.1 users are encouraged to use the new constants.

= new DOMDocument;
// Resolve externals
// OR 
// Validate against DTD
2008-08-05 10:17:35
Function will not work if using XML DOM PECL module
2009-04-05 01:16:23
I had a problem with loading documents over HTTP. I would get errors looking like this:

Warning: DOMDocument::load(http://external/document.xml): failed to open stream: HTTP request failed! HTTP/1.1 500 Internal Server Error

The document would load fine in browsers and using wget. The problem is that DOMDocument::load() on my systems (both OS X and Linux) didn't send any User-Agent header which for some weird reason made Microsoft-IIS/6.0 respond with the 500 error.

The solution is found on function.libxml-set-streams-context : 

= array(
'http' => array(
'user_agent' => 'PHP libxml agent',

$context stream_context_create($opts);

// request a file through HTTP
$doc DOMDocument::load('');
2009-06-09 11:18:58
You can easily avoid the warning about &nbsp; references by using the LIBXML_DTDLOAD option. 


= <<<EOF
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">
<html xmlns="">

// This one works perfectly.
$dom = new DOMDocument();

// This one produces a warning.
$dom = new DOMDocument();


See also: libxml.constants

Note that libxml will detect that your DTD is locally available via /etc/xml/catalog. So there is no worry about this causing your DOM loads to make external network requests.
2009-07-01 02:28:34
XHTML and entities: The solution proposed below by zachatwork at gmail dot com didn't work for me. I checked on a number of servers (both LAMPP and WAMPP) - on each of them, calling loadXML() with the LIBXML_DTDLOAD option triggered an external request for the DTD. And that's bad news.

If allow_url_fopen is turned off, the request for the DTD fails with a warning. If it is turned on, the request fails because these w3c URLs return a 503 Service Unavailable.

HTML entities still generate a warning in either case. 

The best solution, as far as I can tell, is simply to ignore the warnings and suppress them using '@'. I can't recommend parsing XHTML with loadHTML() instead of loadXML() - yes, you get rid of the entity problem, but loadHTML() changes the source while parsing it (tries to 'fix' it even though there is nothing to fix).
2010-04-19 10:50:36
load() will handle non-ASCII characters depending on the details of the XML declaration, but in a somewhat surprising way. One would assume that the declarations '<?xml version="1.0" encoding="UTF-8"?>' and '<?xml version="1.0"?>' are treated in the same way because UTF-8 is the default encoding anyway. But not so.

* If there is an XML declaration defining the encoding *explicitly*, the non-ASCII characters remain unchanged.
* If the XML declaration does not define the encoding explicitly, or if the XML declaration is missing, non-ASCII characters are converted into numeric entities.

So the document

    <?xml version="1.0"?>

will be converted to

    <?xml version="1.0"?>

The same happens if there is no XML declaration at all. On the other hand, the document

    <?xml version="1.0" encoding="UTF-8"?>

will remain as it is.

This behaviour applies to loadXML() as well.
2010-06-01 11:34:32
adding an id for a child, when i use abstract mode i get the following warning:

[quote]Warning: DOMDocument::load() [domdocument.load]: xml:id : attribute value xx is not an NCName in /fake/path/to/xmlfile[/quote]
2011-02-16 11:31:32
i've found the partial solution for xml:id warning,is explained at this address:

there explains that:
The ID does have to be a valid NCName, which for example means, that the first letter can't be a number.

and in my xml:id i had a number. :D
2011-02-25 07:38:21
in the default example:

= new DOMDocument();

you must enter the absolute path for book.xml due for get a false result in load function.
2012-02-09 17:37:43

    Поддержать сайт на родительском проекте КГБ