[MAGNOLIA-3794] JCR node name and web page title for new pages Created: 09/Aug/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Per Andersson [X] (Inactive) | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | admincentral | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 10.10, JBoss 4.3.AS |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
When creating new web pages in the administration interface, you have the columns: Page, Title, Status, Template and Mod. Date. Something I have noticed when I work in Magnolia is that I enter a "readable" friendly page name for a web page. I then use the same name (non-normalized) in the title. Page | Title | Status ... ========================= Hello-World Hello World A nice feature, which should lessens the work for us, is for Magnolia to automatically set the "Title" for the newly created web page to the JCR page name the administrator entered in the text field before it was normalized. I would then only have change the web page from "untitled" into "Hello World" and it would set the JCR name into "Hello-World" and the title "Hello World" at the same time. Thoughts? |
| Comments |
| Comment by Magnolia International [ 10/Nov/11 ] |
|
That's probably something you could do in a custom TreeHandler class. Seems like a decent idea to me, but as mentioned in As a side note, we have to consider the fact that "title" is a totally arbitrary property... but it's so prevalent that we might go with it. Not sure how that'll be handled in 5.0. |
| Comment by Andreas Weder [ 03/Dec/13 ] |
|
I like the idea of simplifying and speeding up the creation of all new content items (not just pages). I would suggest we try to solve this in the "add" dialog that is opened when you want to add a new item. I would then actually do the reverse, meaning that we first ask for a (natural language) title, then convert that title into a node name using a pre-defined algorithm - this seems to me the more obvious direction for editors. My approach would also make it easier to match people's expectation: in the reverse case, some users might want to a title to be written in "title case" (most nouns are capitalized), while others would prefer "sentence case" (only the first character is written with an uppercase letter). Since the two options are more or less equally distributed among the group of writers and editors I know, at least one half of the users wouldn't be helped by a feature that would pick a title for them. Some more things to ponder about:
|
| 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. |