[MAGNOLIA-2861] content resolving, virtual urls: introduce concept of extension similar to sling Created: 03/Sep/09 Updated: 03/Dec/13 Resolved: 03/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
The regular expression based virtual uri mapping is very often not sufficient as one has to predefine under which location a certain template (product catalog for instance) is used. /products/the-product.html --> /products.html?product=my-product Todays workaround is using the selector which leads to ugly page names= /products.my-product.html In Sling they use extensions to solve that use case: /products.html/my-product In my opinion this is a rather a nice solution to that problem. |
| Comments |
| Comment by Magnolia International [ 09/Sep/09 ] |
|
some more related ideas/thoughts can be found at http://wiki.magnolia-cms.com/display/DEV/Proposal+-+merging+of+URI2RepositoryMapping+and+VirtualURIMappings |
| Comment by Philipp Bärfuss [ 03/Dec/13 ] |
|
We currently don't plan to implement such a feature |