Shopping at LEGO or Amazon?
Please use our links:
LEGO.com •
Amazon
As an Amazon Associate we earn from qualifying purchases.
Sets aren't showing as having figs/figs have disappeared?
Whilst a set will list a figure number, on the actual figs tab Brickset is reporting "No minifigs found. Please try another search term or select something from the drop-down lists." Is this happening to anyone else?
So far it appears to be unrestricted to theme (Nexo Knights, World City, City and Marvel Super Heroes have been tested so far) and
http://brickset.com/minifigs/category-Castle is appearing empty, for example.
0
Shopping at LEGO.com or Amazon?
Please use our links: LEGO.com • Amazon
Recent discussions •
Categories •
Privacy Policy •
Brickset.com
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Brickset.com is a participant in the Amazon Services LLC Associates Program, the Amazon.com.ca, Inc. Associates Program and the Amazon EU Associates Programme, which are affiliate advertising programs designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.
As an Amazon Associate we earn from qualifying purchases.
Comments
Think there is a site glitch somewhere as @TheOneVeyronian has had the same issue in a trading thread.
I tagged Huw in my other post in my marketlace thread as soon as I was aware of the problem but I think he's away at the moment, so it could be a while before the problem gets sorted... if it doesn't rectify itself. It may not even be a Brickset glitch that can be sorted out by Brickset staff...
This sounds probable... however the redesign of Bricklink went live a week ago. The minifigs list was absolutely fine until about 12 hours ago. Maybe a BL "fix" caused all minifigs to disappear from Brickset.
So Brickset gets the data from BL, and then Rebrickable gets the data from Brickset which means indirectly from BL. And Brickset also gets data from lego.com? Sounds complicated!
Yesterday I re-ran it, fount it still worked, but because I ran it in the day and not as part of the overnight batch job it had the unintended consequence of upsetting the database.
Following last night's import it's all back to normal.
We don't import theirs.
An example I came across recently: the nine Bright Red horn/spike pieces from #8916 Takadox are listed twice: once as Design ID 53451/Element ID 4276053, and once as Design ID 88513/Element ID 4568388. So even though the piece count of the set is 62, the inventory includes 71.
In big sets that are in circulation a long time, these new versions of old parts can really add up. For example, #10188 Death Star, notorious for how long it took to be discontinued, has a piece count of 3803, but its inventory includes 3996 parts — nearly 200 more! This is because over 40 types of elements in that set's inventory were replaced with new versions during its lifespan, some of them more than once!
There are just 6 pieces listed against the farmer #71011-1 but the parts inventory shows all 116 pieces from the series. I checked the Disney series and Stitch has the same thing.
It's because LEGO's inventory for 71011 includes all parts for all figs and they get attached to the '-1' variant of the set automatically when imported.
When I've worked out the best solution I'll implement it :)
No big deal, just had me questioning my sanity and if I'd being buying minifigs and updating my Brickset list in my sleep!
Is there an easy way to just not include parts for sets with this problem as missing the 6 pieces is better than including a large number of parts you don't have.
Just a thought.