Forum: Ruby Moving Mechanize to Nokogiri

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Patrick L. (Guest)
on 2009-02-19 02:05
Hey guys,
I'm on the second iteration of an app I'm writing to scrape some data
from iStock and right now, I'm trying to force Mechanize to use
Nokogiri. I've gotten away with not having to for a while, but as I keep
adding to this app, it's inevitable.

This is what I thought worked (; namely, drop
the WWW::Mechanize.html_parser = Nokogiri::HTML inside the constructor.
But if I do that, it thinks all my Nokogiri functions don't exist (ie
it's still using hpricot).

Any clues?
Patrick L. (Guest)
on 2009-02-19 02:45
You know, I just realized that these error messages probably mean that
though the parser is Nokogiri, Mechanize pages cannot yet be treated
like Nokogiri objects.

Here are the bread crumbs I'm following:
 - (down at the bottom but
apparently the transition from hpricot is not yet implemented, even
though it says so)

Aaron P.  Sat, 01 Nov 2008 10:41:39 PDT

"@PhoeniX: Yes, it will be integrated with WWW::Mechanize. I am working
on the Hpricot deprecation roadmap now. I hope Nokogiri will be
integrated with Mechanize by version 1.0 (possibly around January, I’m
not sure)."

Patrick L. (Guest)
on 2009-02-19 02:45
Regardless, I'm still not sure how to deal with the situation I pastied
above. Thanks.
Ryan D. (Guest)
on 2009-02-19 07:11
(Received via mailing list)
On Feb 18, 2009, at 16:05 , Patrick L. wrote:

> Any clues?

This topic is locked and can not be replied to.