Re: WWW:Mechanize and Windows

Keep in mind I know nothing about WWW::Mechanize, which sounds like the name of a world war 3 tank game.

What you were doing was trying to invoke a method named requests_redirectable on your $self object, and treat its return value as an array reference.

You probably meant to use:

    # note the extra layer of {}
    push( @{$self->{requests_redirectable}}, 'POST' );
[download]

--
Mike

Comment on Re: WWW:Mechanize and Windows Download Code

Replies are listed 'Best First'.
Re: Re: WWW:Mechanize and Windows by Akira71 (Scribe) on Aug 12, 2003 at 16:41 UTC
Thank you Mike for the answer. I went ahead and made the change only to get an error further down the page. The code I displayed, was actually code from the WWW::Mechanize PM and was not written by me. It has been around a while and even Randall Schwartz (sp?! sorry if wrong) has included a demo in the example.pod file. I cannot help but feel there is something else missing and that this should compile. For completeness the error I get later when making the changes suggested above is: `C:\Perl Dev\Screen Scraper Test>perl despair.pl Can't locate object method "get" via kage "WWW::Mechanize" (perhaps yo +u forgot to load "WWW::Mechanize"?) at C:/Perl/site/lib/WWW/Mechanize +.pm line 183.` [download] Line 183 of the file is: `sub get { my $self = shift; my $uri = shift; $uri = $self->{base} ? URI->new_abs( $uri, $self->{base} ) : URI->new( $uri ); return $self->SUPER::get( $uri, @_ ); }` [download] The return $self line exactly. Thank you for you help though. It is always appreciated.	[reply] [d/l] [select]
Re: Re: Re: WWW:Mechanize and Windows by RMGir (Prior) on Aug 12, 2003 at 17:09 UTC
I'm sorry, I have no idea what the problem is. However, looking at CPAN, I see that WWW::Mechanize is up to version 0.57. Maybe the problem you're running into is fixed in that release? In any case, you're more likely to be able to get help from the maintainer if your problem is happening with the latest release. That latest version was release on July 31 of this year, so it looks like this module is still being actively maintained. -- Mike	[reply]