1Cosettey
I have been excited to use the new "Condition" input field for my books. However, I am running into an issue. When I enter a book condition as "Acceptable", or as "Acceptable" with other details, after I save it changes the condition to "Worn, not with cassette". I have no idea where that is coming from. It does not seem to occur when I type other things in the "Condition" field. Any advice/help would be appreciated!
2Glacierman
it defaults to "Worn, not with cassette" regardless of what I actually type into that field.
NEEDS FIXING!
NEEDS FIXING!
3waltzmn
>2 Glacierman: Confirming; I saw this this morning. Book is here:
State of New York Annual Report of the Adjutant General 1868
https://www.librarything.com/work/11645375/edit/77086859
I also get the text "Worn, not with cassette," even though I have not entered that condition for any book.
ARM M1 Mac
MacOS 18.6.1
Firefox 142.0.1
A curious note: I entered the condition of four books yesterday, and they have not changed. All of those had short condition descriptions. I entered a very long condition for this particular book (since it's old and has suffered a lot of wear). Could it be that there is some upper bound on the length of the condition field, and if the user enters more text, it gets changed?
Experiment: Tried another long condition description; got the bug.
Note to devs: It really looks as if length is what triggers it. All of my long ones got changed, and none of my short ones. Don't just try "good condition" or the like for the condition. Try something like this: "No slipcover. Covers worn and bumped. Writing on back cover. Minor staining of edges. Binding intact." It needs to be a long condition description.
State of New York Annual Report of the Adjutant General 1868
https://www.librarything.com/work/11645375/edit/77086859
I also get the text "Worn, not with cassette," even though I have not entered that condition for any book.
ARM M1 Mac
MacOS 18.6.1
Firefox 142.0.1
A curious note: I entered the condition of four books yesterday, and they have not changed. All of those had short condition descriptions. I entered a very long condition for this particular book (since it's old and has suffered a lot of wear). Could it be that there is some upper bound on the length of the condition field, and if the user enters more text, it gets changed?
Experiment: Tried another long condition description; got the bug.
Note to devs: It really looks as if length is what triggers it. All of my long ones got changed, and none of my short ones. Don't just try "good condition" or the like for the condition. Try something like this: "No slipcover. Covers worn and bumped. Writing on back cover. Minor staining of edges. Binding intact." It needs to be a long condition description.
4Glacierman
>3 waltzmn: Well, for me, it makes no difference how short or long the description is. I can enter a single word, 'Fine', or a long description and it still defaults to "Worn, not with cassette."
This is a glitch for sure, but a very odd one!
This seems to only appear if I enter something in the field. If I skip over it, it remains blank.
This is a glitch for sure, but a very odd one!
This seems to only appear if I enter something in the field. If I skip over it, it remains blank.
5waltzmn
>4 Glacierman: Well, for me, it makes no difference how short or long the description is. I can enter a single word, 'Fine', or a long description and it still defaults to "Worn, not with cassette."
Yeah. that seems to be happening to me now, too, since I tried "Acceptable" and got the "Worn, not with cassette" message instead. It did not happen with my first few. So something changed between my first few books and anything I enter now.
Yeah. that seems to be happening to me now, too, since I tried "Acceptable" and got the "Worn, not with cassette" message instead. It did not happen with my first few. So something changed between my first few books and anything I enter now.
6muumi
I found that it accepts "new" and "used". Any other description ("as new", "vg", "very good", "ex-lib" are the ones I've tried) defaults to "worn, not with cassette".
New and used are, at least, somewhat useful terms.
New and used are, at least, somewhat useful terms.
7anglemark
I will start by putting in values for all my worn books without a cassette for now, I think, and fill in these fields for other books later.
8bnielsen
>5 waltzmn: I think the bug is one of the funnier ones. Maybe "Worn, not with cassette" is a description of the user rather than the book :-)
9waltzmn
>8 bnielsen: You could well be right. I'm certainly pretty worn, and I'm quite sure I didn't come with a cassette. :-)
I wondered at first about too-long entries overflowing the field and grabbing some default somewhere. But now that it's eating short entries, too, I hope that means it's an easier bug. :-)
I wondered at first about too-long entries overflowing the field and grabbing some default somewhere. But now that it's eating short entries, too, I hope that means it's an easier bug. :-)
10bnielsen
>9 waltzmn: I have a couple of bug reports in where I suspect a test for my username is part of the code :-)
11waltzmn
>10 bnielsen: I have a couple of bug reports in where I suspect a test for my username is part of the code :-)
Nah, there's a secret SQL table of "users to watch out for." You're just the first record in the table. :-)
Nah, there's a secret SQL table of "users to watch out for." You're just the first record in the table. :-)
12timspalding
Thanks for the report.
The underlying issue is fixed. (The problem is that we are normalizing the values, but one of the tables didn't have a large enough number.)
The ones that are wrong are still wrong. That's 160 entries. I believe that we can fix them as well, but it will have to wait until Tuesday, as it involves some Lucy code I am not very familiar with.
The underlying issue is fixed. (The problem is that we are normalizing the values, but one of the tables didn't have a large enough number.)
The ones that are wrong are still wrong. That's 160 entries. I believe that we can fix them as well, but it will have to wait until Tuesday, as it involves some Lucy code I am not very familiar with.
13waltzmn
>12 timspalding: Thanks for the update. In my case at least, the books involved are so few that I can just fix them manually. I'll never finish my whole library, so I was just entering them casually.
