FluentDOM 6.0 is released.
So a major version jump means that here are backwards compatibility breaks and major new features. File loading has changed to improve security. FluentDOM\Query has got a major overhaul to improve the integration of alternative formats. This affected the interfaces and usage. I tried to keep the breaks to a minimum and easily fixable.
To load a file you will now have to explicitly allow it using the options argument. Here are two options. FluentDOM\Loader\Options::ALLOW_FILE basically restores the previous behaviour. The loader still checks if it is a file or string and will load both. FluentDOM\Loader\Options::IS_FILE means that only a file will be loaded. This has to be implemented into to respective loader. So if you notice that some loader behaves differently, please drop me a note.
All loading functions allow you to provide the option.
$fd = FluentDOM($file, 'xml', [ FluentDOM\Loader\Options::ALLOW_FILE => TRUE ]); $document = FluentDOM::load( $file, 'xml', [ FluentDOM\Loader\Options::IS_FILE => TRUE ] );
Fragment Loading / Query Content Types
Several loaders now support fragment loading. It is used by methods like FluentDOM\\Query::append(). It allows the Query API to keep the content type that you loaded. So if you load HTML, the fragment are expected to be html, if you load XML the fragments are expected to be XML, if you load JSON ... well you get the picture. :-)
$fd = FluentDOM('<form></form>', 'text/html')->find('//form'); $fd->append('<input type="text" name="example">'); echo $fd;
You can change the behaviour by setting the content type. It works with additional loaders, so if you install fluentdom/html5 you get transparent support for HTML5.
$fd = FluentDOM('<form></form>', 'text/html5')->find('//html:form'); $fd->append('<input type="text" name="example">'); echo $fd;
The changes mean that all existing loaders need to be updated for FluentDOM 6.0.
Serializers need to register itself on the FluentDOM class. It allows the FluentDOM\Query objects to output the same content type it loaded. Additionally you can use FluentDOM::getSerializerFactories()->createSerializer(); to get a serializer for a node by content type. I am thinking about adding something like a FluentDOM::save() function as a shortcut for that, but I am not sure about the name and implementation yet. If you have a suggestion please add it to the Issue.
Replace Whole Text
Character nodes (Text nodes and CDATA sections) have a property $wholeText. It returns the text content and the sibling character nodes. It even resolves entity references for that. The property is read only, but DOM Level 3 specifies a method replaceWholeText() as a write method for it. FluentDOM 6.0 implements that method in its extended DOM classes now.
$document = new FluentDOM\Document(); $document->loadXML( '<!DOCTYPE p ['."\n". ' <!ENTITY t "world">'."\n". ']>'."\n". '<p>Hello &t;<br/>, Hello &t;</p>' ); /** @var \FluentDOM\Text $text */ $text = $document->documentElement->firstChild; $text->replaceWholeText('Hi universe'); echo $document->saveXML();
The examples directory did grow a little confusing over the years. I restructured and refactored it. Some examples got removed, because the features are shown by newer examples.
I still have to updated some of the plugin repositories (loaders, serializers) and add some more documentation to the wiki. After that I plan to take a look into DOM Level 4. If you have suggestions please add a ticket to the issue tracker