<p>I believe the correct syntax you're looking for is:</p>

<pre><code>{{ node.logo.enclosure['@url'] }}
</code></pre>

<p>As a handy hint, you can use the following to inspect any element parsed by Feed Me to see how you can access it. Using <code>{{ dump(node.logo.enclosure) }}</code> for example, you can see an array with keys and values for you to access.</p>

<p>This is also outlined in the documentation - <a href="https://verbb.io/craft-plugins/feed-me/docs/feature-tour/using-in-your-templates#example-template-code" rel="nofollow noreferrer">https://verbb.io/craft-plugins/feed-me/docs/feature-tour/using-in-your-templates#example-template-code</a></p>

<p>EDIT: Refer to full code below</p>

<pre><code>{% set params = {
    url: 'http://feedme.craft.dev/stack.xml',
    type: 'xml',
    element: 'node',
} %}

{% for node in craft.feedme.feed(params) %}
    &lt;pre&gt;
        {{ dump(node) }}
    &lt;/pre&gt;
{% endfor %}
</code></pre>

<p>Produces:</p>

<pre><code>array(2) {
  ["title"]=&gt;
  string(23) "Test Org - Pleae Ignore"
  ["logo"]=&gt;
  array(1) {
    ["enclosure"]=&gt;
    array(3) {
      ["@url"]=&gt;
      string(60) "https://www.mydomain.org/sites/default/files/louis%20xiv.jpg"
      ["@length"]=&gt;
      string(5) "71280"
      ["@type"]=&gt;
      string(10) "image/jpeg"
    }
  }
}
</code></pre>

<p>EDIT 2: Looking at your exact feed, I can see the issue. Your feed actually has HTML, which is interpreted as a string. For instance:</p>

<pre><code>&lt;logo&gt;
    &amp;lt;enclosure url="https://www.mydomain.com/1959440_10152076927213038_3915913252856478361_n%5B1%5D_2.jpg" length="35608" type="image/jpeg" /&amp;gt;
&lt;/logo&gt;
</code></pre>

<p>Notice how is your original example its assumed its all XML? In fact, the logo node contains HTML, which is just treated like a string.</p>

CC BY-SA 3.0
2017-11-14T00:01:52.643Z
You'll see in the OP I tried that syntax and got no output. I'll try the dump and see what happens.
Philip Jones
CC BY-SA 3.0
2017-11-14T00:05:49.150Z
Added code with full implementation of the array dump on my end.
crawf
CC BY-SA 3.0
2017-11-14T00:09:30.740Z
I added `{{ dump(node.logo.enclosure) }}` and got an `unknown "dump" function` error.
Philip Jones
CC BY-SA 3.0
2017-11-14T00:21:32.087Z
Apparently I needed Dev Mode on. I added the dump output to my OP, which you'll see doesn't look like what you expected.
Philip Jones
CC BY-SA 3.0
2017-11-14T05:48:45.903Z
Without looking at your feed, its hard to tell, but there seems to be HTML directly in your feed, which is considered a string to Feed Me (it will parse the XML, but not the inner HTML). Maybe we'll follow up further via Slack? Username is @crawf
crawf
CC BY-SA 3.0
2017-11-14T15:38:11.680Z
Okay, I see what you're saying. I didn't understand that previously because everything I viewed the XML feed in rendered the HTML, which made it _LOOK_ like a valid XML tag. But when I view the raw feed, I see now that the tag brackets are actually being stored as HTML entities. Thanks for the assist. I'll see if the data provider can modify how that is being output.
Philip Jones
CC BY-SA 3.0
2017-11-13T23:48:54.703Z
2017-11-14T05:54:37.403Z
2017-11-14T05:54:37.403Z
crawf
<p>I have the following XML:</p>

<pre><code>&lt;nodes&gt;
    &lt;node&gt;
        &lt;title&gt;Test Org - Pleae Ignore&lt;/title&gt;
        &lt;logo&gt;
            &lt;enclosure url="https://www.mydomain.org/sites/default/files/louis%20xiv.jpg" length="71280" type="image/jpeg" /&gt;
        &lt;/logo&gt;
    &lt;/node&gt;
    &lt;node&gt;
        &lt;title&gt;Test Org - Pleae Ignore&lt;/title&gt;
        &lt;logo&gt;
            &lt;enclosure url="https://www.mydomain.org/sites/default/files/louis%20xiv.jpg" length="71280" type="image/jpeg" /&gt;
        &lt;/logo&gt;
    &lt;/node&gt;
    &lt;node&gt;
        &lt;title&gt;Test Org - Pleae Ignore&lt;/title&gt;
        &lt;logo&gt;
            &lt;enclosure url="https://www.mydomain.org/sites/default/files/louis%20xiv.jpg" length="71280" type="image/jpeg" /&gt;
        &lt;/logo&gt;
    &lt;/node&gt;
&lt;/nodes&gt;
</code></pre>

<p>And the following template markup:</p>

<pre><code>{% set params = {
    url: 'https://www.domain.org/xml-details?nid=12345',
    type: 'xml',
    element: 'node',
    cache: 60,
} %}

{% set feed = craft.feedme.feed(params) %}
{% for node in feed %}
    {{ node.title }}
    {{ node.logo.enclosure.attributes.url }}
{% endear %}
</code></pre>

<p><code>{{ node.title }}</code> displays fine, but <code>{{ node.logo.enclosure.attributes.url }}</code> displays nothing.</p>

<p>Based on other threads I've read, I've also tried <code>{{ node.logo.enclosure['@url'] }}</code></p>

<p>Neither returns the value of the <code>url</code> attribute.</p>

<p>Any help getting this to work is appreciated.</p>

<p>EDIT: Using just <code>{{ node.logo }}</code> in the template outputs <code>&lt;enclosure url="https://www.mydomain.org/sites/default/files/louis%20xiv.jpg" length="71280" type="image/jpeg" /&gt;</code>.</p>

<p>EDIT: Here's my <code>{{ dump(node) }}</code> output.</p>

<pre><code>array(30) {
  ["recordId"]=&gt;
  string(5) "19795"
  ["title"]=&gt;
  string(22) "Robertson Blood Center"
  ["summary"]=&gt;
  string(101) "&lt;p&gt;Volunteer- Donate blood. Your donation of life is used by wounded military at home and abroad.&lt;/p&gt;"
  ["logo"]=&gt;
  string(156) "&lt;enclosure url="https://www.mydomain.org/sites/default/files/1959440_10152076927213038_3915913252856478361_n%5B1%5D_2.jpg" length="35608" type="image/jpeg" /&gt;"
}
</code></pre>

CC BY-SA 3.0
2017-11-10T05:43:27.003Z
You could dump the `{{ node.logo}}` to see if it contains the property enclosure and continue with that until you reach `attributes`
Robin Schambach
CC BY-SA 3.0
2017-11-10T12:22:55.457Z
@RobinSchambach - I should have mentioned in the OP that `{{ node.logo }}` does, indeed, display the full `<enclosure />` element. So the content is there. I just can't get FeedMe to parse it.
Philip Jones
<plugin-feedme>
FeedMe Node Attributes
# FeedMe Node Attributes

(Asked by: username_0 on 2017-11-09)

I have the following XML:

    
        Test Org - Pleae Ignore
        
            
        
    
    
        Test Org - Pleae Ignore
        
            
        
    
    
        Test Org - Pleae Ignore
        
            
        
    


And the following template markup:
{% set params = {
    url: 'https://www.domain.org/xml-details?nid=12345',
    type: 'xml',
    element: 'node',
    cache: 60,
} %}

{% set feed = craft.feedme.feed(params) %}
{% for node in feed %}
    {{ node.title }}
    {{ node.logo.enclosure.attributes.url }}
{% endear %}

{{ node.title }} displays fine, but {{ node.logo.enclosure.attributes.url }} displays nothing.
Based on other threads I've read, I've also tried {{ node.logo.enclosure['@url'] }}
Neither returns the value of the url attribute.
Any help getting this to work is appreciated.
EDIT: Using just {{ node.logo }} in the template outputs .
EDIT: Here's my {{ dump(node) }} output.
array(30) {
  ["recordId"]=>
  string(5) "19795"
  ["title"]=>
  string(22) "Robertson Blood Center"
  ["summary"]=>
  string(101) "Volunteer- Donate blood. Your donation of life is used by wounded military at home and abroad."
  ["logo"]=>
  string(156) ""
}

**Tags:** plugin-feedme

> **Comments:**
> **username_1**: You could dump the `{{ node.logo}}` to see if it contains the property enclosure and continue with that until you reach `attributes`  
> **username_0**: @RobinSchambach - I should have mentioned in the OP that `{{ node.logo }}` does, indeed, display the full `<enclosure />` element. So the content is there. I just can't get FeedMe to parse it.  

---

## 1 answers

### Answer by username_2 on 2017-11-13. Score: 2 | Accepted answer

I believe the correct syntax you're looking for is:
{{ node.logo.enclosure['@url'] }}

As a handy hint, you can use the following to inspect any element parsed by Feed Me to see how you can access it. Using {{ dump(node.logo.enclosure) }} for example, you can see an array with keys and values for you to access.
This is also outlined in the documentation - https://verbb.io/craft-plugins/feed-me/docs/feature-tour/using-in-your-templates#example-template-code
EDIT: Refer to full code below
{% set params = {
    url: 'http://feedme.craft.dev/stack.xml',
    type: 'xml',
    element: 'node',
} %}

{% for node in craft.feedme.feed(params) %}
    
        {{ dump(node) }}
    
{% endfor %}

Produces:
array(2) {
  ["title"]=>
  string(23) "Test Org - Pleae Ignore"
  ["logo"]=>
  array(1) {
    ["enclosure"]=>
    array(3) {
      ["@url"]=>
      string(60) "https://www.mydomain.org/sites/default/files/louis%20xiv.jpg"
      ["@length"]=>
      string(5) "71280"
      ["@type"]=>
      string(10) "image/jpeg"
    }
  }
}

EDIT 2: Looking at your exact feed, I can see the issue. Your feed actually has HTML, which is interpreted as a string. For instance:

    <enclosure url="https://www.mydomain.com/1959440_10152076927213038_3915913252856478361_n%5B1%5D_2.jpg" length="35608" type="image/jpeg" />


Notice how is your original example its assumed its all XML? In fact, the logo node contains HTML, which is just treated like a string.

> **Comments:**
> **username_0**: You'll see in the OP I tried that syntax and got no output. I'll try the dump and see what happens.  
> **username_2**: Added code with full implementation of the array dump on my end.  
> **username_0**: I added `{{ dump(node.logo.enclosure) }}` and got an `unknown "dump" function` error.  
> **username_0**: Apparently I needed Dev Mode on. I added the dump output to my OP, which you'll see doesn't look like what you expected.  
> **username_2**: Without looking at your feed, its hard to tell, but there seems to be HTML directly in your feed, which is considered a string to Feed Me (it will parse the XML, but not the inner HTML). Maybe we'll follow up further via Slack? Username is @username_2  
> **username_0**: Okay, I see what you're saying. I didn't understand that previously because everything I viewed the XML feed in rendered the HTML, which made it _LOOK_ like a valid XML tag. But when I view the raw feed, I see now that the tag brackets are actually being stored as HTML entities. Thanks for the assist. I'll see if the data provider can modify how that is being output.  

---

