Timeline for How to format QueryPath Xpath Mappings in Feeds Module
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2020 at 8:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 18, 2020 at 2:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 17, 2020 at 8:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 9, 2015 at 14:43 | comment | added | bgrobertson | I had simplified the XML a little for this post, but I tried an XML validator and didn't get any errors. I updated the XML above to better reflect the actual XML. And I agree that "XML is not well formed" would be a sensible error, but it is specifying 'CSS selector is not well formed.' | |
| Dec 9, 2015 at 14:36 | history | edited | bgrobertson | CC BY-SA 3.0 |
Update the XML example.
|
| Dec 8, 2015 at 23:26 | answer | added | Patrick Ryan | timeline score: 1 | |
| Dec 8, 2015 at 21:57 | comment | added | Clive♦ |
Are you sure that error isn't "XML is not well formed" ? Your XML is invalid at the moment is all. Your query is valid, but if you want to extract the title it'll be something more like //ooh/occupation/title/text()
|
|
| Dec 8, 2015 at 21:44 | history | asked | bgrobertson | CC BY-SA 3.0 |