You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got logbooks with names that have spaces in them. If I load them via URL (e.g. https://forester.radio/K-1209%2520Barr%2520Lake%2520SP/qsos), the spaces show up in the title portion of the UI with big ugly %20 sequences instead of spaces. Loading the logbook via navigation in the UI seems to show the properly unescaped value, though I may have gotten an escaped title that way once or twice.
The text was updated successfully, but these errors were encountered:
A bit of background: I had intended for a "logbook" to be basically one per callsign and comprise the entire corpus of one's logs, similar to the way Google Photos works. Then there would be some concept of "albums" or "saved searches." Of course, I've never gotten around to that sub-grouping, so it's kind of moot.
That is to say, I didn't plan for titles with spaces. So I'm not too surprised I have escape sequences being displayed. I'll try and do a pass to clean those up.
I've got logbooks with names that have spaces in them. If I load them via URL (e.g.
https://forester.radio/K-1209%2520Barr%2520Lake%2520SP/qsos
), the spaces show up in the title portion of the UI with big ugly%20
sequences instead of spaces. Loading the logbook via navigation in the UI seems to show the properly unescaped value, though I may have gotten an escaped title that way once or twice.The text was updated successfully, but these errors were encountered: