|
 |
| | | Author: | DonnaxNL  | | Posted: | Feb 16, 2024 14:37 | | Subject: | Variant merger causing XML files to fail | | Viewed: | 138 times | | Topic: | Technical Issues | |
|
| Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
|
|
| | | | | |
| | | | | Author: | DonnaxNL | | Posted: | Feb 16, 2024 14:49 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 36 times | | Topic: | Technical Issues | |
|
| In Technical Issues, DonnaxNL writes:
| | Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
Meanwhile there is no consistency...
Has the -b and 'with Groove' moniker removed, but [P=3068bpb0431,1]
has not. While the regular has...
|
|
|
| | | | | | | | | |
| | | | | | | Author: | Admin_Russell | | Posted: | Feb 16, 2024 14:57 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 75 times | | Topic: | Technical Issues | |
|
|
BrickLink
ID CardAdmin_Russell
|
Location:  USA, California |
| Member Since |
Contact |
Type |
Status |
| May 9, 2017 |
 |
Admin |
|
|
| BrickLink Administrator |
|
| In Technical Issues, DonnaxNL writes:
| | In Technical Issues, DonnaxNL writes:
| | Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
Meanwhile there is no consistency...
Has the -b and 'with Groove' moniker removed, but [P=3068bpb0431,1]
has not. While the regular has...
|
We are still updating the 2 x 2 decorated tiles. There are over 2000 of them,
so it will take a while.
|
|
|
| | | | | |
| | | | | Author: | jennnifer | | Posted: | Feb 16, 2024 14:49 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 53 times | | Topic: | Technical Issues | |
|
| You are late to the story:
https://www.bricklink.com/message.asp?ID=1450622
https://www.bricklink.com/message.asp?ID=1451828
https://www.bricklink.com/message.asp?ID=1454437
Those part numbers have been permanently updated and you will need to change
all of your instruction files. And probably some more coming soon...
~Jen
In Technical Issues, DonnaxNL writes:
| | Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
|
|
|
| | | | | | | | | |
| | | | | | | Author: | SylvainLS | | Posted: | Feb 16, 2024 14:58 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 37 times | | Topic: | Technical Issues | |
|
| In Technical Issues, jennnifer writes:
It would be simpler if the upload feature(s) would simply look at the alternate
IDs….
|
|
| | | | | | | | | | | | | |
| | | | | | | | | Author: | 1001bricks | | Posted: | Feb 16, 2024 15:09 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 43 times | | Topic: | Technical Issues | |
|
| | | It would be simpler if the upload feature(s) would simply look at the alternate
IDs…
|
But then... For how long?
3 months, 1 year, 10 years?
Some MOCs are 20 yrs old - should BrickLink keep all the change refs eternally?
And all the further changes of the same item?
Like x176c01 to 30155c01 changed May 20, 2006?
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | Author: | SylvainLS | | Posted: | Feb 16, 2024 15:22 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 33 times | | Topic: | Technical Issues | |
|
| In Technical Issues, 1001bricks writes:
| | | | It would be simpler if the upload feature(s) would simply look at the alternate
IDs…
|
But then... For how long? […]
|
For as long as alternate IDs are in the database.
The site can be smart and recognize them when it reads them in older files.
Yes, the field (as we see it on the part pages) is simple text and would need
to be normalized (and reversed: alt ID » correct ID/part, for now it’s part »
alt ID).
But the site already knows how to convert from LDraw and LXF files. So there’s
already a conversion table (or two) somewhere to convert LDraw’s IDs and LDD’s
IDs to BL’s IDs.
And while they are at it, add XML as a full-citizen file format, like LDR, LXF,
BSX: one that can be uploaded as a file, not copy-pasted.
|
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | Author: | hpoort | | Posted: | Feb 17, 2024 02:20 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 29 times | | Topic: | Technical Issues | |
|
| In Technical Issues, SylvainLS writes:
| | In Technical Issues, 1001bricks writes:
| | | | It would be simpler if the upload feature(s) would simply look at the alternate
IDs…
|
But then... For how long? […]
|
For as long as alternate IDs are in the database.
The site can be smart and recognize them when it reads them in older files.
Yes, the field (as we see it on the part pages) is simple text and would need
to be normalized (and reversed: alt ID » correct ID/part, for now it’s part »
alt ID).
But the site already knows how to convert from LDraw and LXF files. So there’s
already a conversion table (or two) somewhere to convert LDraw’s IDs and LDD’s
IDs to BL’s IDs.
And while they are at it, add XML as a full-citizen file format, like LDR, LXF,
BSX: one that can be uploaded as a file, not copy-pasted.
|
Have you found that yet? If they don't listen to you, whom would
they listen to anyway?
|
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | Author: | Stellar | | Posted: | Feb 17, 2024 13:06 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 27 times | | Topic: | Technical Issues | |
|
| In Technical Issues, SylvainLS writes:
| | In Technical Issues, 1001bricks writes:
| | | | It would be simpler if the upload feature(s) would simply look at the alternate
IDs…
|
But then... For how long? […]
|
For as long as alternate IDs are in the database.
The site can be smart and recognize them when it reads them in older files.
Yes, the field (as we see it on the part pages) is simple text and would need
to be normalized (and reversed: alt ID » correct ID/part, for now it’s part »
alt ID).
But the site already knows how to convert from LDraw and LXF files. So there’s
already a conversion table (or two) somewhere to convert LDraw’s IDs and LDD’s
IDs to BL’s IDs.
And while they are at it, add XML as a full-citizen file format, like LDR, LXF,
BSX: one that can be uploaded as a file, not copy-pasted.
|
Exactly...
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | Author: | DonnaxNL | | Posted: | Feb 16, 2024 15:24 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 35 times | | Topic: | Technical Issues | |
|
| Maybe not for those obscure changes, but they already keep track of some alternate
IDs, for example for at the top they list: "Alternate Item No:
3069b, 30070, 35386, 37293, 54285, 88630"
I'm also explicitly mentioning this tile, as it is, or tiles in general are,
super common.
In Technical Issues, 1001bricks writes:
| | | | It would be simpler if the upload feature(s) would simply look at the alternate
IDs…
|
But then... For how long?
3 months, 1 year, 10 years?
Some MOCs are 20 yrs old - should BrickLink keep all the change refs eternally?
And all the further changes of the same item?
Like x176c01 to 30155c01 changed May 20, 2006?
|
|
|
| | | | | | | | | |
| | | | | | | Author: | DonnaxNL | | Posted: | Feb 16, 2024 15:00 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 42 times | | Topic: | Technical Issues | |
|
| I know about the whole merger debacle, it's just stupid they expect everyone
to update their files (if they don't bother to do anything about it). There
should be a fallback check on their backend for it. They already have the information
for it under 'Alternate Item No'...
In Technical Issues, jennnifer writes:
| | You are late to the story:
https://www.bricklink.com/message.asp?ID=1450622
https://www.bricklink.com/message.asp?ID=1451828
https://www.bricklink.com/message.asp?ID=1454437
Those part numbers have been permanently updated and you will need to change
all of your instruction files. And probably some more coming soon...
~Jen
In Technical Issues, DonnaxNL writes:
| | Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
|
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | | Author: | jennnifer | | Posted: | Feb 16, 2024 15:06 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 42 times | | Topic: | Technical Issues | |
|
| My apologies! I didn't mean to just point out the obvious.
I didn't get the impression from reading through what's been said that
much care was being given to the API and other people who link to BrickLink.
It was always going to be a messy transition.
Take care,
~Jen
In Technical Issues, DonnaxNL writes:
| | I know about the whole merger debacle, it's just stupid they expect everyone
to update their files (if they don't bother to do anything about it). There
should be a fallback check on their backend for it. They already have the information
for it under 'Alternate Item No'...
In Technical Issues, jennnifer writes:
| | You are late to the story:
https://www.bricklink.com/message.asp?ID=1450622
https://www.bricklink.com/message.asp?ID=1451828
https://www.bricklink.com/message.asp?ID=1454437
Those part numbers have been permanently updated and you will need to change
all of your instruction files. And probably some more coming soon...
~Jen
In Technical Issues, DonnaxNL writes:
| | Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
|
|
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | Author: | DonnaxNL | | Posted: | Feb 16, 2024 15:18 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 33 times | | Topic: | Technical Issues | |
|
| Sorry from me too, I didn't meant to take it out on you.
Apparently they are still merging parts ( https://www.bricklink.com/message.asp?ID=1455223
), so I can't even make updated list right now... So will see what happens
and if it really causing other MOC builders problems too for them to have a look
at it or we have to suck it up.
In Technical Issues, jennnifer writes:
| | My apologies! I didn't mean to just point out the obvious.
I didn't get the impression from reading through what's been said that
much care was being given to the API and other people who link to BrickLink.
It was always going to be a messy transition.
Take care,
~Jen
In Technical Issues, DonnaxNL writes:
| | I know about the whole merger debacle, it's just stupid they expect everyone
to update their files (if they don't bother to do anything about it). There
should be a fallback check on their backend for it. They already have the information
for it under 'Alternate Item No'...
In Technical Issues, jennnifer writes:
| | You are late to the story:
https://www.bricklink.com/message.asp?ID=1450622
https://www.bricklink.com/message.asp?ID=1451828
https://www.bricklink.com/message.asp?ID=1454437
Those part numbers have been permanently updated and you will need to change
all of your instruction files. And probably some more coming soon...
~Jen
In Technical Issues, DonnaxNL writes:
| | Hi there,
I got notified by a Rebrickable customer who purchased moc instructions from
me that uploading of the XML file didn't work. After taking a look at it,
I noticed they were all parts that have a 'b' suffix in them. They all
are from tile pieces, just removing the b's from all the items works, but
tile pieces are really common and I assume this has not only broke mine, but
will break everyone's XML files people have shared.
Please let someone take a look at it.
|
|
|
|
|
|
|
| | | | | |
| | | | | Author: | StarBrick | | Posted: | Feb 16, 2024 15:27 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 52 times | | Topic: | Technical Issues | |
|
| Does this mean ALL XML's for example at Rebrickable are affected by the merger
too?
I got hundreds of these file in my collection.
And only a manual update will do the trick.... I feared the merge operation when
it was announced, but this is plain stupid!
Many will be affected, collectors, sellers, buyers, all. At places we never been
notified of beforehand.
|
|
| | | | | | | | | |
| | | | | | | Author: | DonnaxNL | | Posted: | Feb 16, 2024 15:34 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 40 times | | Topic: | Technical Issues | |
|
| If you could check one of the files for me, that would be helpful as a confirmation,
but I fear the worse... Not even necessarily for myself, but like you say people
like you with hundreds of files.
In Technical Issues, StarBrick writes:
| | Does this mean ALL XML's for example at Rebrickable are affected by the merger
too?
I got hundreds of these file in my collection.
And only a manual update will do the trick.... I feared the merge operation when
it was announced, but this is plain stupid!
Many will be affected, collectors, sellers, buyers, all. At places we never been
notified of beforehand.
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | | Author: | StarBrick | | Posted: | Feb 16, 2024 15:47 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 39 times | | Topic: | Technical Issues | |
|
| Uploading the original XML's will default into the same errors you reported.
Downloading the XML's NOW from Rebrickable, fixes this  .
Apparently there's a realtime check when the XML's are generated. That's
nice.
So you need to re-download your XMLS  .
Opening old XML's in BrickStore will start a migration from the old to the
new ID's (see pic).
Crap, a big list to update this weekend.....
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | | Author: | DonnaxNL | | Posted: | Feb 16, 2024 17:12 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 43 times | | Topic: | Technical Issues | |
|
| I suggest waiting with updating for a bit, apparently they aren't done with
all the merging yet... https://www.bricklink.com/message.asp?ID=1455223
In Technical Issues, StarBrick writes:
| | ...
Crap, a big list to update this weekend.....
|
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | Author: | StarBrick | | Posted: | Feb 17, 2024 09:08 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 41 times | | Topic: | Technical Issues | |
|
| It will take months to complete the proposed merges I just read as it needs to
be done manually by Admin...
|
|
| | | | | | | | | |
| | | | | | | Author: | 1001bricks | | Posted: | Feb 16, 2024 15:43 | | Subject: | (Cancelled) | | Viewed: | 23 times | | Topic: | Technical Issues | |
|
| | (Cancelled) |
|
| | | | | | | | | |
| | | | | | | Author: | 1001bricks | | Posted: | Feb 16, 2024 15:45 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 39 times | | Topic: | Technical Issues | |
|
| In Technical Issues, StarBrick writes:
| | Does this mean ALL XML's for example at Rebrickable are affected by the merger
too?
I got hundreds of these file in my collection.
And only a manual update will do the trick.... I feared the merge operation when
it was announced, but this is plain stupid!
Many will be affected, collectors, sellers, buyers, all. At places we never been
notified of beforehand.
|
Open the file with BrickStore it'll update ALL the changes (including those
years ago).
References on BrickLink have never been immutable.
Sure now there are more changes, as changes in basic parts (3062, 3068...) but
it's the same principle.
Your any time files COULD have been (and probably are) obsolete.
One way is to open them in BrickStore - for 2 or 3 years (I'm not sure) it
auto updates.
In short: apart maybe the more important number of recent changes, it's
always have been the same exact problem.
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | | Author: | StarBrick | | Posted: | Feb 16, 2024 15:53 | | Subject: | Re: Variant merger causing XML files to fail | | Viewed: | 41 times | | Topic: | Technical Issues | |
|
| In Technical Issues, 1001bricks writes:
| |
In short: apart maybe the more important number of recent changes, it's
always have been the same exact problem.
|
Thanks for that reflection. However an old problem felt as new is still a felt
problem.
If it never has been felt as a problem, and now it does, it doesn't make
it a lesser problem.
Even if the 'age' of the problem is several decades, it doesn't make
the effect felt less.
|
|
|
|
|
Netherlands, Noord-Holland
France, Nouvelle-Aquitaine
Spain, Comunidad Valenciana
