[MAGNOLIA-3380] Virtual URI mapping delivers wrong URI for files with a dot in file name Created: 10/Nov/10 Updated: 12/Apr/11 Resolved: 12/Apr/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Diana Racho | Assignee: | Magnolia International |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
We use theme files like jquery.jscrollpane.js. |
| Comments |
| Comment by Magnolia International [ 17/Dec/10 ] |
|
Hi Diana, Could you provide a (failing) test case for info.magnolia.cms.beans.config.RegexpVirtualURIMappingTest - or, perhaps simpler, your failing configuration. I'm not convinced the provided patch is satisfactory. I'm guessing either your regular expression can be improved (did you escape dots ?), or perhaps you simply need a custom/different VirtualURIMapping implementation (that's what the if (result != null) block makes me think anyway - it's sometimes simpler to have a custom implementation that try to shoehorn the desired behavior in a regex!) What do you think ? |
| Comment by Diana Racho [ 20/Dec/10 ] |
|
Yes, we have a special use case and have created an own class for it. You're right, it probably is not relevant to the general Magnolia users. |
| Comment by Magnolia International [ 12/Apr/11 ] |
|
So I'll close this issue, assuming your regular expression was badly formed (\.). Should that not be the case, please reopen with more configuration details on how to reproduce the issue. |