| Summary: | /{pub-id}/{module}/... URLs interfere with areas | ||
|---|---|---|---|
| Product: | Lenya | Reporter: | Andreas Hartmann <andreas> |
| Component: | Miscellaneous | Assignee: | Lenya Developers <dev> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | P2 | ||
| Version: | Trunk | ||
| Target Milestone: | 1.4 | ||
| Hardware: | Other | ||
| OS: | other | ||
| Attachments: | Introduces prefix for lenya-specific URLs (e.g., modules) inside areas. | ||
Created attachment 19976 [details]
Introduces prefix for lenya-specific URLs (e.g., modules) inside areas.
i don't really like this approach. i don't have a better solution off-hand, but i see a number of issues: * it touches 3 different files * it touches both a module and a global sitemap * it introduces a configuration variety that will be a pain to support later * it adds significant complication and new semantics to fix a bug related to areas, which we agreed we want to get rid of eventually. then again, it has one major benefit: * it solves a problem now. but: the most part of my work on lenya has been ripping out such patches again, which is a huge pain, introduces instability and gets harder the longer such patches are in use. I added a workaround to the UuidToUrlTransformer. |
ATM it is allowed to use URLs like /{pub-id}/{module}/foo.xml This interferes with areas. Specifically, the UuidToUrlTransformer rewrites /default/resource/icons/... to /default/authoring/icons/... because "resource" is not the current area. That's why the icon on resource pages doesn't appear. Another problem is that it doesn't work with proxies out of the box, since the area's URL space is not self-contained. ---- We could use a configurable prefix (preset to "lenya"): /{pub}/{area}/{lenya-prefix}/modules For instance /default/authoring/lenya/modules /yourpub/authoring/cms/modules