Local Links should include dynamic titles too? #11881
markadrake
started this conversation in
Features and ideas
Replies: 1 comment 1 reply
-
Could make it <a href="/{localLink:umb://document/26ec07a2a35c43218b0f3e79ae7517a3}"
title="{localName:umb://document/26ec07a2a35c43218b0f3e79ae7517a3}">
{localName:umb://document/26ec07a2a35c43218b0f3e79ae7517a3}
</a> This could also open for something like |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
MiloW on Umbraco Forums has identified something that I'm surprised I haven't come across before.
Is there already a solution I don't know about?
The Issue
He is working on a multi-lingual site and is using an RTE to link text to a local node in Umbraco. This is referred to in the code base as a
localLink
and is obvious when you see the syntax:The issue MiloW points out is that the title / label for the link is not dynamic as well. The issue is obvious when you are working in a multi-lingual site and the titles of each page are slightly different.
The simplest user story is:
Current behavior
There are property value converters for text, grid, markdown, rich text, and rte macros that support parsing these values to their HREF/URL equivalents.
There's also the backoffice UI to consider. When you leave the values blank for link, anchor, link title, etc and simply select a content node... These values are then pre-filled.
The example above results in the following markup:
Proposed Behavior
To jump start this conversation, if we were to implement other dynamic values perhaps we could do something like this:
If
localTitle
is discovered we would replace it with the current content node's title as it stands for the current language/culture. There a host of other UI blunders ahead. Say if someone decides to edit the text for the link in the RTE, do we respect that or throw it away? Fun!Beta Was this translation helpful? Give feedback.
All reactions