I wish there were little changes in the code. Substitute "qp" function with "htmlqp" (function details here).

What's the reason?
Many pages are poorly formatted or erroneous thus using this module is almost impossible (errors and errors during parsing). Why not to use function that's especially designed for this purpose (dealing with markup errors)?

CommentFileSizeAuthor
#1 FeedsQueryPathParser.inc_.htmlqp.patch1.08 KBpawel_r

Comments

pawel_r’s picture

pawel_r commented
StatusFileSize
new FeedsQueryPathParser.inc_.htmlqp.patch1.08 KB

Patch according my previous post.

twistor’s picture

twistor commented

Does this still work with XML?

pawel_r’s picture

pawel_r commented

Yes it does work with XML.

imclean’s picture

imclean commented

It appears the function just sets a few HTML options for qp(). A more flexible approach would be to enable configuration of those options directly.

See this previous issue: #1283520: Add QueryPath Options use_parser and ignore_parser_warnings

imclean’s picture

imclean commented

Refs:

- htmlqp() documentation
- htmlqp() source code

This could be presented as a set of options, although being able to select htmlqp() or qp() could make things easier.

pawel_r’s picture

pawel_r commented
Issue summary: View changes
Status: Active » Closed (outdated)