Looking again at a discussion about navon vs. folder names, right now I’m thinking it would be better if the navon propagation process automatically named navons “about_nav” or “contactus_nav” (adding “_nav” to the folder name during propagation) instead of just “about” or “contactus”. Users might be more likely to want to give those choice names to pages instead of navons. Some of us use those names as publishable filenames, but who needs to know what a navon is named? But by default you can’t have two files with the same name in the same folder.
As far as that goes, it should be possible to programmatically copy the displaytitle from the landing page to use as the default displaytitle field of the navon. Obviously it couldn’t be done until the landing pages are named, so we could do it with a new menu item, “Nav Reset”. No wait, that name is already taken…
We add " (navon)" to the sys_title (the one displayed in the Content Explorer) of navons. There are different ways of doing this, all with limitations or subtle gotchas. The method we eventually chose was an input field transform on the sys_title field using the sys_CloneTitle extension, passing {0} (navon) for the Pattern parameter and PSXSingleHtmlParameter/displaytitle for the InsertionItem0 parameter.
Andrew.
Just wondering if anyone else has tried doing what Andrew has implemeted?
We add " (navon)" to the sys_title (the one displayed in the Content Explorer) of navons…
(we do this using) an input field transform on the sys_title field using the sys_CloneTitle extension, passing {0} (navon) for the Pattern parameter and PSXSingleHtmlParameter/displaytitle for the InsertionItem0 parameter.
In the 6.7 implementation I am working with I see no option of sys_CloneItem in the drop down list of extensions for an input field transform on the sys_title field of rffNavon. And the only reference I have found to sys_CloneItems in the doucmentation is in relation to Relationship Types.
Hence I was wondering if anyone else has implemented this solution or could provide further feedback as it would be perfect if we could get this implemented.
Cheers Diane