"Barcode" Replace/Remove Bugs

DiscussionsBug Collectors

Rejoignez LibraryThing pour poster.

"Barcode" Replace/Remove Bugs

1kristilabrie
Modifié : Avr 11, 2023, 3:38 pm

Responding to https://www.librarything.com/topic/349997, looks like I had found and reported some of these bugs a couple of years back (internally), but drawing up an official report to share and track here.

"Barcode" bugs on book-edit page/s:

1. From https://www.librarything.com/catalog/MEMBERNAME, click to edit any book in "Your books" that has an existing barcode number in the "Barcode" field (I've tested on a number of my own).
2. From the book-edit page, remove the "Barcode" number from the field OR edit to a different (available) barcode number.
3. Click the top OR bottom "Save" button, it doesn't matter which one. The page may jump and do nothing else. If this happens, select "Save" once more. You should be brought back to "Your books".

Bug: the book you removed the "Barcode" field from still has the original barcode number. You cannot replace or remove an existing barcode number from the book-edit page/s.

"Barcode" bugs on "Your books":

1. From https://www.librarything.com/catalog/MEMBERNAME, view a display Style that has the "Barcode" field included. Find a book with an existing barcode number, or add a barcode to one of your books.
2. Double-click to edit the "Barcode" field for that book.
3. Change the barcode number to something else (make sure it's an available barcode number). Hit the return key to save.
4. Refresh the page to show the change/s.

Bug: The original barcode number remains, and the new barcode number was not saved.

5. Repeat steps 1-2.
6. Remove the barcode number entirely. Hit the return key to save.
7. Refresh the page.

Result: The barcode field is now empty. Now, you can edit the "Barcode" field again and add a different barcode number. You just cannot replace an existing barcode number with something else: you must delete the old first, then add a new one.

I've played around with my Barcodes Settings a bit, and don't think they play into these bugs.

2kristilabrie
Avr 18, 2023, 11:41 am

Bump, another member reported this issue.

3kristilabrie
Avr 28, 2023, 12:11 pm

Bump and an update: developers have a solution in place, but we cannot push it until next week. I hope to have an update for this by Monday/Tuesday! Thanks for your patience.

4knerd.knitter
Mai 1, 2023, 11:42 am

Fixed.