Import cant find serie "24" (1 Viewer)

Paranoid Delusion

Moderation Manager
  • Premium Supporter
  • June 13, 2005
    13,062
    2,978
    Cheshire
    Home Country
    United Kingdom United Kingdom
    24 - S01E01 works, make sure you do not have under the online data tab "automatically chose series when exact match is found" enabled, this for me blocks finds.
     

    FloBo

    New Member
    February 21, 2009
    4
    0
    Home Country
    Germany Germany
    Hi thx for your help but even if i disable this option the import wont work. Now ich find something in the logfile:

    00000009 - 21.02.2009 13:06:22 - *************** Identifying Unknown Series Online ***************
    00000009 - 21.02.2009 13:06:22 - Found 1 unknown Series, attempting to identify them now
    00000009 - 21.02.2009 13:06:24 - Xml parsing of http://thetvdb.com/api/GetSeries.php?seriesname=24&language=all failed (line 122 - Das 'br'-Anfangstag in Zeile '120' stimmt nicht mit dem Endtag von 'Overview' überein. Zeile 122, Position 170.)
    00000009 - 21.02.2009 13:06:24 - Found 0 possible matches for "24"
    00000009 - 21.02.2009 13:06:26 - User cancelled Series Selection

    translation: (line 122 - The 'br'-Starting tag in line 120 didnt agree with the endtag of 'Overview'. Line 122, position 170.)

    If I open the URL with ie then i get also an error message, i can manually change the URL tolanguage=en and I get a valid xml file. This line never changes with the GUI language option

    Now I found a similiar thread but with older versions https://forum.team-mediaportal.com/my-tvseries-162/mytv-series-24-a-28596/


    Florian

    MP-TVSeries v2.1.3331
     

    ltfearme

    Community Plugin Dev
  • Premium Supporter
  • June 10, 2007
    6,751
    7,196
    Sydney
    Home Country
    Australia Australia
    If there is a problem with the XML, then it should be reported on teh theTVDB.com forums.

    I did a test this morning and seems ok though. From the looks of it one of the language descriptions were not generated correctly in the XML. TVseries couldn't parse the document hence your tvseries were not imported.
     

    bil1010105

    Portal Member
    April 24, 2008
    8
    0
    Home Country
    United Kingdom United Kingdom
    I had about 100 seasons of '24' during the last import because the parser messed up & didn't recognise my episode names, so I took the plunge and renamed everything on disk so it had the following (consistant) format:

    '24 - 1x01 - Day 1- 8-00 A.M.-9-00 A.M.avi' or similar. This has been picked up since season 7 with my current MP-TVseries database. It's also the format I use for all other series (which work fine).

    I removed all the 24 episodes from the database, and ran import again.

    I then get the error mentioned above ("line 122 - The 'br'-Starting tag in line 120 didnt agree with the endtag of 'Overview'. Line 122, position 170.")

    Now '24' is no longer recognised at all by MP-TVSeries. :confused:
     

    ltfearme

    Community Plugin Dev
  • Premium Supporter
  • June 10, 2007
    6,751
    7,196
    Sydney
    Home Country
    Australia Australia
    I
    I then get the error mentioned above ("line 122 - The 'br'-Starting tag in line 120 didnt agree with the endtag of 'Overview'. Line 122, position 170.")

    It seems ok at the moment, the problem might be intermittent. Either way, nothing can be done from the client side. As I said the problem should be raised over at theTVDB.
     

    bil1010105

    Portal Member
    April 24, 2008
    8
    0
    Home Country
    United Kingdom United Kingdom
    It seems ok at the moment, the problem might be intermittent. Either way, nothing can be done from the client side. As I said the problem should be raised over at theTVDB.

    You're right, it was only a temporary problem at their end.

    However, it completely screwed up my TV episodes database - even once the tvdb.com error was resolved MP-TVSeries refused point blank to re-find the episodes that I'd been forced to skip before.

    I eventually had to go into the SQL database and manually remove the errant rows.

    Now it all works :)

    (I'm sure there's probably a far easier way to accomplish what I did, but brute force is sometimes the best & quickest option! :p)
     

    Users who are viewing this thread

    Top Bottom