Unexpected persistence of "From where?" value when adding new book
DiscussionsBug Collectors
Rejoignez LibraryThing pour poster.
1ltji_test
Steps to reproduce:
1. Navigate to the "Add books" > "Manual entry" form: https://www.librarything.com/addnew.php
2. Scroll to "From where?" and click the "change" link
3. Click the "Free text" tab, enter some text, and click the "Save" button
4. Scroll to the end of the form and click "Cancel" to dismiss the form.
5. Navigate to the "Manual entry" form again
6. Enter a title
7. Scroll to "From where?" and confirm it is not set
8. Click "Save" to create a new book
9. Navigate to the "Book details" for the new book
Expected:
* New book has blank "From where?" field
Actual:
* New book has the "From where?" value from step 3.
It appears the information from the first book is somehow persisted server-side and then associated with the next book created. This behavior occurs even when logging out, clearing site data and caches, and quitting the browser between steps 4 and 5, so it doesn't seem to be a client caching issue.
1. Navigate to the "Add books" > "Manual entry" form: https://www.librarything.com/addnew.php
2. Scroll to "From where?" and click the "change" link
3. Click the "Free text" tab, enter some text, and click the "Save" button
4. Scroll to the end of the form and click "Cancel" to dismiss the form.
5. Navigate to the "Manual entry" form again
6. Enter a title
7. Scroll to "From where?" and confirm it is not set
8. Click "Save" to create a new book
9. Navigate to the "Book details" for the new book
Expected:
* New book has blank "From where?" field
Actual:
* New book has the "From where?" value from step 3.
It appears the information from the first book is somehow persisted server-side and then associated with the next book created. This behavior occurs even when logging out, clearing site data and caches, and quitting the browser between steps 4 and 5, so it doesn't seem to be a client caching issue.
2lh_test_1
L'adminstrateur de groupe a masqué ce message (afficher)
Ce message a été supprimé par son auteur3knerd.knitter
You are correct; it is being stored in the database. I am not sure why, so I will have to research.
4knerd.knitter
This has been fixed.
5ltji_test
>4 knerd.knitter: I repeated the steps to reproduce and confirmed the bug is fixed. Thanks for the fast turnaround!