[MAGNOLIA-1381] Parameter substitution in controls Created: 16/Feb/07 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | templating |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major |
| Reporter: | Boris Kraft | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
any |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
It would be useful in certain situations to have the ability to enter parameters like the page name or page title as content into controls. As an example, take the keywords of Magnolia's partner section. Each country where we have partners has its own page with a list of these partners. The keywords for the page Benelux (the countries of Belgium, Netherlands and Luxemburg) will be something like: Magnolia Benelux, Magnolia Partner Benelux, CMS Benelux, ECM Benelux, CMS support Benelux, ECM support Benelux, ... I have to enter this information for each page, potentially lots of them times lots of pages = a whole lot of work. Ideally it should be possible to say instead: Magnolia $PAGE_NAME, Magnolia Partner $PAGE_NAME, CMS $PAGE_NAME, ECM $PAGE_NAME, CMS support $PAGE_NAME, ECM support $PAGE_NAME, ... We could go so far as to allow any nodeName of our dialogs (how do we know their names?) as a parameter. (need to avoid circular references, though). By the way, this seems to be another example of one earlier issue I filed of introducing per-control filters/plugins that manipulate the content before saving and displaying. Finally, it would be useful to determine per control if we want to inherit its content, in which case I might be able to enter this information only once, possible in an "invisible" paranet page ("hide from navigation"). I am not sure that anyone else would find these features useful, so I put it out here for your feedback. |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |