Menu

#158 latest yahoo site and latest parser not totally compatible

Parser_Error
open-fixed
nobody
None
5
2004-07-21
2004-06-28
No

In the past few weeks - about 2 weeks - I have begun
getting these errors:
Processing URL 1 of 7
Yahoo Parser Version 2.04
Use of uninitialized value in substitution (s///) at
yahoo.pm line 409.
Use of uninitialized value in substitution (s///) at
yahoo.pm line 410.
and then, later

Processing URL 2 of 7
Yahoo Parser Version 2.04
Unable to parse time: freeadmission

and later
Processing URL 3 of 7
Yahoo Parser Version 2.04
Unable to parse time: freeadmission
Unable to parse time: freeadmission
Unable to parse time: advancedticketsonsalenow
Unable to parse time: advancedticketsonsalenowAM

Note there are multiple occurances of these 'Unable to
parse' values.
I'm on a sun sparc solaris 8 machine, using perl 5.6.1
and showtimes 0.7 but with the various updates that
have appeared here on the site.

Here's an example of my getdata.cfg URL line:
URL
http://movies.yahoo.com/showtimes/showtimes.html?z=43068&date=todayplus0&nt=20

Is there any other info that would be useful?

Discussion

  • Kevin Jones

    Kevin Jones - 2004-07-13

    Logged In: YES
    user_id=970574

    Larry,

    I believe I have fixed the problem - at least the part about
    the "Unable to parse time" message.

    https://sourceforge.net/tracker/?
    func=detail&atid=302989&aid=990436&group_id=2989

    Let me know if the error "Use of uninitialized value in
    substitution (s///)".

    Kevin

     
  • Nobody/Anonymous

    Logged In: NO

    I also am receiving the "Use of uninitialized value in substitution (s///) at
    yahoo.pm line 419"

    and also for line 420.

     
  • Larry W. Virden

    Larry W. Virden - 2004-07-20

    Logged In: YES
    user_id=15949

    I have downloaded the patch to yahoo.pm to make it 2.05 and
    here is what I see:

    Processing URL 1 of 7
    Yahoo Parser Version 2.05
    Use of uninitialized value in substitution (s///) at
    yahoo.pm line 419.
    Use of uninitialized value in substitution (s///) at
    yahoo.pm line 420.
    Processing URL 2 of 7
    Yahoo Parser Version 2.05

    My first URL is
    http://movies.yahoo.com/showtimes/showtimes.html?z=43068&date=todayplus0&nt=
    20

     
  • Kevin Jones

    Kevin Jones - 2004-07-20

    Logged In: YES
    user_id=970574

    I have found the problem and fixed it:
    http://sourceforge.net/tracker/index.php?
    func=detail&aid=994766&group_id=2989&atid=302989.

    Kevin

     
  • Nobody/Anonymous

    Logged In: NO

    Tried the new patch (2.06) and got this error:

    "my" variable $movie_title masks earlier declaration in same scope at
    yahoo.pm line 424.

     
  • Kevin Jones

    Kevin Jones - 2004-07-20

    Logged In: YES
    user_id=970574

    Fixed: http://sourceforge.net/tracker/index.php?
    func=detail&aid=994836&group_id=2989&atid=302989. My
    Perl environment didn't report it as a problem.

    Kevin

     
  • Nobody/Anonymous

    Logged In: NO

    Patch 2.07 works great (Mac OS X 10.3.4, perl 5.8.1)
    If you want to you could update the version number in the yahoo.pm
    output...it says:

    Processing URL 1 of 3
    Yahoo Parser Version 2.05

    instead of 2.07

    Thanks for all the work, zorvek. Nice Job.

     
  • Kevin Jones

    Kevin Jones - 2004-07-20

    Logged In: YES
    user_id=970574

    I fixed the version number reported in the log. Didn't change
    anything else so I'll just keep the version 2.07 for now. I
    posted it to www.zorvek.com/showtimes.

    Kevin

     
  • Larry W. Virden

    Larry W. Virden - 2004-07-21

    Logged In: YES
    user_id=15949

    This new yahoo.pm, version 2.07, solves my problem - so this
    bug can be closed.

     
  • Larry W. Virden

    Larry W. Virden - 2004-07-21
    • status: open --> open-fixed
     
  • Larry W. Virden

    Larry W. Virden - 2004-07-21

    Logged In: YES
    user_id=15949

    Actually, one more thing here is needed - to incorporate
    these changes into the CVS (like the previous bug comment I
    updated suggests)

     

Log in to post a comment.

MongoDB Logo MongoDB