When getting the values for elements like <sponsorHtml/>, the xpath call returns the text of the elment "<sponsorHtml/>" instead of an empty string.

Comments

johnbarclay’s picture

Status: Active » Needs review
StatusFileSize
new766 bytes

Here's a patch for this. I didn't break any simpletests that weren't already broken. I didn't add the case to the simpletests either, but can if its accepted.

twistor’s picture

I think your description got eaten. Not sure what's it's doing wrong.

paulgemini’s picture

Yup - johnbarclay, please take another look at the issue description.

twistor’s picture

Status: Needs review » Postponed (maintainer needs more info)

Try wrapping the elements in a <code> tag when you post, otherwise they will be stripped out.

Robin Millette’s picture

Assigned: johnbarclay » Unassigned
Status: Postponed (maintainer needs more info) » Active

Anyone can update the summary, so I did.

moehac’s picture

Issue tags: +feeds_xpathparser

I have a related issue, so don't know if I need to start a new thread for this.

The parser will not recognize additional child elements because of a space before the closing tag. Example:

<links>
<visualLink pid="6" gid="1" />
<visualLink pid="6" gid="2" />
<visualLink pid="6" gid="3" />
</links>

It will only read the first child with attribute "1" and skip the rest. If I eliminate the space between gid="1" and />, it will read all the child elements.

Any fixes?

moehac’s picture

Issue summary: View changes

Updated issue summary.

twistor’s picture

Issue summary: View changes
Status: Active » Closed (works as designed)
Issue tags: -feeds_xpathparser

Closing out old issues. If someone is still having this problem, feel free to re-open.