Posts: 95
Joined: Apr 2010
Reputation:
0
2010-05-01, 18:33
(This post was last modified: 2010-05-01, 18:36 by luger.)
My TMDB scraper is also broken. I'm having trouble locating where the tmdb.xml file is on XBMC Live. Anybody know the location? Thanks.
Posts: 1,264
Joined: Sep 2009
Reputation:
34
*********IMPORTANT - - - PLEASE READ***********
I just talked to Travis who runs tmdb, he wasn't aware of the problem we were having. The change in their api was not supposed to break the scrapers. He will update his api so the original (unmodified) tmdb scrapers should work after the update.
Keep in mind that whatever is currently cached in their system will take about 24 hours to update.
If your scraper is currently not working, do not do anything, just wait a day, it will start working as before.
If you already modified your scraper, you are probably going to have to revert back to the original one by tomorrow.
Posts: 252
Joined: Jan 2007
Reputation:
0
AaronD
Senior Member
Posts: 252
Hi aptalca,
Maybe he shouldn't be too rash. I found that the regexp that I thought was matching against the image ID (which is now a GUID) was actually matching against the show ID which is still a number. So I was wrong. IN other words, the GUID with alphas in the image ID is not a problem!
Your original post, with the addition of the width parameter, is the one that fixes the images. The only thing I found was a typo in your tmdb.xml - you had an extra '>' character at least in the one in pastebin.
But you're right - it is the changes to the api that have broken things here. I suspect that if he moved the width parameter to the end of the image element, or at least after the size parameter which is the last one that the scraper matches on, that this would not break the XBMC scraper either.
Maybe you could direct him to this post?
Cheers
Aaron
Posts: 26,215
Joined: Oct 2003
Reputation:
187
As I wrote in the other thread, XBMC shouldn't be assuming the order of elements if it can avoid it. Unfortunately, we have to in some ways. We can, however, get away with just assuming that url comes before size and ignore anything in between. This seems like a reasonable solution in the meantime. A patch for this would be great.
Cheers,
Jonathan
Posts: 6
Joined: Dec 2009
Reputation:
0
Like Travis said, can we use a XML parser instead of RegExp to parse the output?
Posts: 4
Joined: Mar 2010
Reputation:
0
Im also using xbmc live and can't find the tmdb.xml file.
The scraper is still not working for me and I need the pc finished for a project tommorow, can someone point me to where the file is located?
Posts: 95
Joined: Apr 2010
Reputation:
0
Benjie, I believe the it should be working again in the near future. They said they put in an update yesterday that should go into effect in 24 hours and we're around that point so I'd just give it another hour or two and see if the problem resolves itself.
Posts: 45
Joined: May 2007
Reputation:
0
i can confirm it is indeed working once again ...
Posts: 8
Joined: Mar 2010
Reputation:
0
So I'm still having issues. Not sure why. I'll give it some time. AaronD's file worked for a while but stopped pulling cast/crew information. I'll check to see if things are up and running again tomorrow.
Posts: 8
Joined: Mar 2010
Reputation:
0
Sorry for the double post, but I'm learning what these scrapers do.
But the Cast/Crew scraping issue is still a problem but I realize now that these portions get scraped with the "non-common" tmdb.xml. So...I'm still going to have those issues. Other than that I'll hope that things get propagated through soon because I'm having issues still.
I'll try to dig through the other xml to see what's happening with the Cast/Crew query, but I'm not great at Regex.