relations in xml text

Friday 20 January 2006 2:39:12 am

Hi there,
Thanks for all of the replies on my last question about creating a new node without a draft. Here's another tricky one I think...

Is it possible to be able to tell which related nodes are used in xml text fields for a node and which ones are ust related.

Why?

I am building a site where the owner is able to link up all kinds of related content to a particular page, which then gets automatically linked up in a list in the right hand column. However, sometimes he uses some of these relations in an xml text field (e.g. embedding images) and so they now show up twice on the page. If I could tell which ones were linked to the xml text area then I could choose not to show them in the RH column.

Any ideas? Short of writing an extension to return an array of related nodes to an xml field.

Cheers,

Ben

Tuesday 24 January 2006 11:18:22 am

Thanks Xavier,
Great extension and absolutely perfect for my needs. Hopefully it will be included in eZ before too long. As suggested I made some changes, which were basically to check for dom elements called "embed" and to also check if they have an attribute of "object_id". So the function "modify" is now as follows:

function modify( &$tpl, &$operatorName, &$operatorParameters, &$rootNamespace, &$currentNamespace, &$operatorValue, &$namedParameters )
    {
        if (!isset($namedParameters['xmlattribute']->DataText))
            return "should be an attribute";
         
        $xmldata =& $namedParameters['xmlattribute']->DataText;
        $xml = new eZXML();
        $dom =& $xml->domTree( $xmldata );
        if ( is_object ($dom) )
        {
            $objects =& $dom->elementsByName( "embed" );
            foreach ($objects as $object)
            {
                $attributes=& $object->attributes();
                foreach ($attributes as $attribute)
                {
                    if ($attribute->Name == "object_id")
                        $operatorValue[] = $attribute->content;
                } 
            }
        }
    }

I haven't done a check for the eZ version, but this is working perfectly on my 3.6 installation.

Thanks again,

Ben Pirt