- Issue created by @cYu
- 🇺🇸United States japerry KVUO
Pushing this to the top to verify before we make the 1.1 release.
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
While working other things I just stumbled upon the same on the latest
1.1.x-devversion as well:Memo: whoever will work on this, please make sure that all other non-URL-friendly characters are also tested for, not only the forward slash. Thanks!
- Assigned to deepakkm
- Status changed to Needs work
about 2 months ago 5:11am 3 July 2025 - First commit to issue fork.
- Merge request !171Resolve #3491071 "Fix: DAM category with slash throws errors" → (Merged) created by rajeshreeputra
-
japerry →
committed 0b9a209f on 1.1.x authored by
rajeshreeputra →
Issue #3491071 by rajeshreeputra: DAM category with slash throws errors
-
japerry →
committed 0b9a209f on 1.1.x authored by
rajeshreeputra →
- 🇺🇸United States japerry KVUO
That data shouldn't be getting passed raw, so I think encoding the return is the right thing here. Fixed!
Automatically closed - issue fixed for 2 weeks with no activity.