Yes, agree, Ken prohibited such tools by still allowing "unneeded" dividers being omitted.

Well of course I blew everything up while enhancing divider parsing, BY recognition and testing with multiple name variants.

I think things have settled back down now, but I still get consistently the same number of "extra" profiles with some actors. Are they legitimate, or do I have a bug that I just can't find?

If anybody wants to take a shot at helping me figure it out, here is an example: Will Wallace. Current CLT says 379 profiles. I consistently get 382. Have been getting the extra for a long time now. Always with the same actors, but not every actor.

Will Wallace CLT profiles, CLTBoss "skinny" XML.

Will Wallace CLT profiles, Invelos full XML.

Are the 3 extra musketeers for real??? 

And of course I will painfully suffer the news of any other issues you find. 

The profiles, which seem not to exist in the data base:
065935141952-United States
065935222491-United States
086162000355-United States

Wait, I am looking at the XML that includes 065935141952, US.

You know of course that I am getting this information from database calls to the online database.

<DVD>
  <ID>065935141952</ID>
  <ID_Base>065935141952</ID_Base>
  <ID_LocalityID>0</ID_LocalityID>
  <ID_LocalityDesc>United States</ID_LocalityDesc>
  <Title>I Am Sam</Title>
  <OriginalTitle></OriginalTitle>
  <MediaTypes>
    <DVD>True</DVD>
    <BluRay>False</BluRay>
    <HDDVD>False</HDDVD>
    <UltraHD>False</UltraHD>
  </MediaTypes>
  <ProductionYear>2001</ProductionYear>
  <Released>6/18/2002</Released>
  <FrontCoverThumbnailUrl>http://www.invelos.com/thumbs/06/065935141952f.jpg</FrontCoverThumbnailUrl>
  <BackCoverThumbnailUrl>http://www.invelos.com/thumbs/06/065935141952b.jpg</BackCoverThumbnailUrl>
  <Actors>
    <Actor Episode="" GroupName="" FirstName="Will" MiddleName="" LastName="Wallace" BirthYear="0" Role="Bill Carpenter" CreditedAs="" Voice="False" Uncredited="False" Puppeteer="False" />
  </Actors>
  <Credits>
  </Credits>
</DVD>


So, what does it mean that you say they do not exist? Does it mean that you can't download them, using the "Add To Collection"?

And more interesting. The thumbnail link works for one profile, but gives an error on the other. WTF?????

Yet, the covers show when downloaded:

All three Profiles exist in other locations:
065935141952-Canada
065935141952-Canada (Quebec)
065935141952-United States

065935222491-Canada
065935222491-Canada (Quebec)
065935222491-United States

086162000355-Chile
086162000355-Mexico
086162000355-United States

If I had to guess, I'd look for some loose variable binding, which equals the locality 0 with an empty string...

Quoting AiAustria:

Quote:
All three Profiles exist in other locations:
065935141952-Canada
065935141952-Canada (Quebec)
065935141952-United States

065935222491-Canada
065935222491-Canada (Quebec)
065935222491-United States

086162000355-Chile
086162000355-Mexico
086162000355-United States

How did you generate this list?

So, we are on the same page. 

The CLT misses those three profiles that actually ARE in the database! I told you, I downloaded them into my local database, using the plugin online access.

Here is how the API works. I will not reveal the actual API, as Invelos told me not to:

(1) Ask Invelos "give me all profile IDs" based on UPC "086162000355":

tpids
{object[2]}
    [0]: "086162000355.25"
    [1]: "086162000355.49"

(2) Ask Invelos "give me a pointer to the profile with profile ID = "086162000355"

- get non-null pointer (you get a null pointer if the profile does not exist)
- (pointer).GetProfileID() yields "086162000355"
- (pointer).GetXML() yields the XML in the file I gave a link to

This is the part of the Invelos database key scheme that leads to errors. There is no way to tell the difference between a UPC and a locality 0 profile ID.

For example, if you ask: "give me a pointer to profile ID "086162000355.0", you get a null pointer!!!

Of course, the other localities work just as they should.

Bottom line. There is a bug lurking in the Invelos Online, that sometimes misses presenting the locality 0 profile, even though it exists in the database.

I find them. CLT does not.