Allow displaying products with barcodes > 24 OR disallow barcode length greater than 24(?)

[CharlesNepote]

Describe the bug

Current situation:

• 12,000+ products have a barcode > 13
• 160 products have a barcode > 24
• Open Food Facts can display products with a barcode up to 24: eg. https://world.openfoodfacts.org/product/232847100000100120001200/berlina-glace-mercadona
• Open Food Facts can't display products with a barcode greater than 24: eg. https://world.openfoodfacts.org/product/0105400141340210310300051/gouda-belegen-everyday%22 (the product exists, it is findable)

To Reproduce

https://world.openfoodfacts.org/product/0105400141340210310300051/gouda-belegen-everyday%22 (the product exists, it is findable)

Expected behavior

I think products should be displayed, even if the barcode is wrong, at least to allow moderators to delete them, if necessary.

Screenshots

No response

Additional context

See also:

• https://wiki.openfoodfacts.org/Barcodes
• Quality facets - barcodes that have a strange number of digits, or a bad last digit key #1806

Type of device

Browser

Browser version

No response

Number of products impacted

No response

Time per product

No response

[manognyaa]

hello, I am manognya, an outreachy applicant. I would like to work on this issue @stephanegigandet sir. So, the issue is like the products up to 24 only the scanner is taking the input. and remaining i.e. above 24 digits barcode, it is not accepting and displaying as an error. I would love to complete this issue. I have gone through the links provided in the issue template. @stephanegigandet sir, if you don't mind, could pls guide me further how to do it. I need help.

Thank you!

[alexgarel]

@manognyaa it surely starts in display.pl, but this file is a little confusing, so you have to trace where it happens. The difficulty is that we did not work on setting up the debbugger yet…

But you can follow logs (make tail)

And you can edit the source code to add temporary debug logs (look at existing logs) - but remember to restart the server if you edit the code : docker-compose restart backend

[manognyaa]

@manognyaa it surely starts in display.pl, but this file is a little confusing, so you have to trace where it happens. The difficulty is that we did not work on setting up the debbugger yet…

But you can follow logs (make tail)

And you can edit the source code to add temporary debug logs (look at existing logs) - but remember to restart the server if you edit the code : docker-compose restart backend

thank you for the info. I will start working on it. If I face any issue, pls guide me, @alexgarel sir.

[github-actions]

This issue is stale because it has been open 90 days with no activity.