Re^3: Problem getting fields out of an XPath node list

Why do you keep using ->findvalues ? Simply retrieve the nodes or find the text within the nodes explicitly:

/tr/td/text()
[download]

Personally, I simply find the nodes and then use their ->as_text() method to get at their textual content.

Comment on Re^3: Problem getting fields out of an XPath node list Select or Download Code

Replies are listed 'Best First'.
Re^4: Problem getting fields out of an XPath node list by ejc1 (Novice) on Mar 29, 2016 at 14:58 UTC
I've tried to look at the raw nodes with dumper, and I cant make any sense of it. The document is very complex (see http://www.threatexpert.com/report.aspx?md5=2aafcad88572d98c154ab7d80cbafc02) and as I mentioned, I have zero understanding of xpath. I looked at as_text, but the problem is, I just don't understand xpath format at all, to even attempt to scope my node elements to just that one section I mentioned. If I understood how the nodes were built, I think I could be ok, but to be honest, I just totally don't get this at all. When I do '//tr/td', I get _all_ of the td elements in one giant array, instead of just narrowing the damn thing to the one section I tried to match against in my post. :(	[reply]
Re^5: Problem getting fields out of an XPath node list by Corion (Patriarch) on Mar 29, 2016 at 15:44 UTC
I recommend that you learn XPath. There are also browser plugins that show you the XPath to a node if you click on its HTML element. If XPath feels too complex for you to tackle but HTML / CSS selectors feel more accessible to you, you can easily convert most CSS selectors to XPath by using HTML::Selector::XPath.	[reply]