Extruct not matching up with Schema.org structured data testing tool (Incorrect image Urls)

[dconnx]

Test Url: https://www.fabucci.ie/ladies-shoes/marian-gold-stiletto-with-black-toe-cap.html Schema.org Structured Data Testing Tool for same: https://validator.schema.org/#url=https%3A%2F%2Fwww.fabucci.ie%2Fladies-shoes%2Fmarian-gold-stiletto-with-black-toe-cap.html

On this page there is 1 product with embedded microdata structured data. The product has 3 images and the structured data testing tool shows 3 JPG image URLs.

Extruct parses this page HTML and returns an "images" Array but, instead of the JPG image URLs, the Array contains the [structured data] Product Url repeated 3 times.

Schema.org structured data testing tool:

Extruct parsed data:

[The-Nightwing]

How can I get this parsed data using the url given? I mean how can i reproduce this error.

because i am able to get a perfect array of jpg image urls, and that too correct.

like this: (part of the extruct parsed data)

'type': 'http://schema.org/BreadcrumbList'},
               {'properties': {'description': 'Read more',
                               'image': ['https://www.fabucci.ie/14873-medium_default/-marian-navy-suede-envelope-clutch-bag.jpg',
                                         'https://www.fabucci.ie/14874-medium_default/-marian-navy-suede-envelope-clutch-bag.jpg',
                                         'https://www.fabucci.ie/14875-medium_default/-marian-navy-suede-envelope-clutch-bag.jpg',
                                         'https://www.fabucci.ie/14876-medium_default/-marian-navy-suede-envelope-clutch-bag.jpg'],

Also the url given by you is not working anymore, so picked a different product from the same website.

[getorca]

I've noticed this issue before as well. It shouldn't be in the breadcrumb list.

because i am able to get a perfect array of jpg image urls, and that too correct.

You're sharing the breadcrumb list, I would check the type for Product.

I've noticed this issue before as well with extruct

[The-Nightwing]

Can we resolve this issue internally? @getorca