[MGNLDMS-209] Invalid characters should not break the link Created: 07/Mar/11 Updated: 20/Apr/12 Resolved: 18/May/11 |
|
| Status: | Closed |
| Project: | Document Management System (closed) |
| Component/s: | None |
| Affects Version/s: | 1.5.1 |
| Fix Version/s: | 1.5.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Matt Dertinger | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | dms | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Magnolia International [ 22/Mar/11 ] |
|
iirc, the part between the last / and the extension is ignored. It does generate an ugly url, but it seems to be properly encoded - what kind of issues are you encountering ? Also note that there's always two kinds of links for dms assets - the /dms-static/ ones, using the uuid, and /dms/ ones, using the path to the document. |
| Comment by Magnolia International [ 06/Apr/11 ] |
|
Guys, a lot of details are to be found on the support issue, reported by Matt. Once we figure it out, let's report the relevant bits here ! |
| Comment by Ondrej Chytil [ 22/Apr/11 ] |
|
Actual issue here was fact that with changing of title also fileName was updated to match this value and therefore links were generated with that name (during generating the link the fileName is called). |
| Comment by Jan Haderka [ 16/May/11 ] |
|
just removing the possibility to set the file name via title is not fixing the issue. The proper fix should use already existing methods for encoding the file name and control should be updated to use encoded file name as well. |