1Bookwomble
I guess this isn't the most pressing thing in the immediate aftermath of a spam attack, but when you have time to look, when I write the characters ' and " in a post, they display as /, which I can see in the posts of others so it may be a general issue.
2waltzmn
>1 Bookwomble:
Do your quote marks display as / (that is, just a slash) or do they display as /' or /" -- that is, a slash followed by the quote mark you used? If it's the latter, then you are "escaping" the symbol, so that it isn't interpreted as part of HTML or some other code. You might see that also apply to slashes themselves.
I ask because the two different problems would require very different fixes. :-)
Do your quote marks display as / (that is, just a slash) or do they display as /' or /" -- that is, a slash followed by the quote mark you used? If it's the latter, then you are "escaping" the symbol, so that it isn't interpreted as part of HTML or some other code. You might see that also apply to slashes themselves.
I ask because the two different problems would require very different fixes. :-)
3timspalding
Thanks. Will take a look.
Is this on the app or on the web?
Is this on the app or on the web?
4Nevov
I've seen this today on some parts of LT main site, eg. awards pages, for example this award organization description: https://www.librarything.com/award/organization/4192/descriptions
Cat Writers' Association changes into Cat Writer\'s Association, and editing doesn't permit removal of the backslash.
Edit: this is on the web.
Edit2: clarifying.
Cat Writers' Association changes into Cat Writer\'s Association, and editing doesn't permit removal of the backslash.
Edit: this is on the web.
Edit2: clarifying.
5Bookwomble
>2 waltzmn: Thanks for highlighting the distinction: it displays the original character and the /. I've tried editing a couple of instances, and some edits stick but others don't.
>3 timspalding: Thanks for your attention, Tim. It's happening on both platforms. I've had a couple of other Litsy users confirm they're seeing it, too.
>3 timspalding: Thanks for your attention, Tim. It's happening on both platforms. I've had a couple of other Litsy users confirm they're seeing it, too.
8katemcangus
>7 Ann_R: >5 Bookwomble: Thanks for the additional information! We're looking into it.
10timspalding
Thanks for the report. We're working on it.
11Bookwomble
>10 timspalding: When you have time, could you provide an update on progress, please? 🙂
12knerd.knitter
>11 Bookwomble: I believe this should have been fixed. Can you tell me where you're still seeing it?
13Bookwomble
>12 knerd.knitter: I've just reported on Litsy an instance from 02/10/24 of another user posting about the problem still happening, and in the comments, they and another users pay display the issue. I had been getting it myself, but it seems to have stopped for me.
15Bookwomble
>14 timspalding: No, I'm still seeing it come up in new posts, though not presently my own, so it seems to be specific rather than general.
You can see the issue appearing in the comments under this post, made between 5 and 2 hours ago at the time of my writing: https://litsy.com/p/b1JjQ3dXY2pN
You can see the issue appearing in the comments under this post, made between 5 and 2 hours ago at the time of my writing: https://litsy.com/p/b1JjQ3dXY2pN
16Bookwomble
>14 timspalding: Here's another instance I can share from a Litsy post of my own, made on 5th October 24, again the bug showing in the comment rather the original post: https://litsy.com/p/QnVzUHVCbE9B
18knerd.knitter
Fixed.

