How easily extend Rendering Variants
Is there a way to easily extend rendering variants logic?
My goal is to display the name of a parent item. Let's imagine that I'm using a Page List rendering and beside values from current context item fields I would like also to display the name of a parent item (the name can, for example, indicate my custom category name of something).
Is there a way to achieve this?
sxa
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
add a comment |
Is there a way to easily extend rendering variants logic?
My goal is to display the name of a parent item. Let's imagine that I'm using a Page List rendering and beside values from current context item fields I would like also to display the name of a parent item (the name can, for example, indicate my custom category name of something).
Is there a way to achieve this?
sxa
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
add a comment |
Is there a way to easily extend rendering variants logic?
My goal is to display the name of a parent item. Let's imagine that I'm using a Page List rendering and beside values from current context item fields I would like also to display the name of a parent item (the name can, for example, indicate my custom category name of something).
Is there a way to achieve this?
sxa
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
Is there a way to easily extend rendering variants logic?
My goal is to display the name of a parent item. Let's imagine that I'm using a Page List rendering and beside values from current context item fields I would like also to display the name of a parent item (the name can, for example, indicate my custom category name of something).
Is there a way to achieve this?
sxa
sxa
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
asked Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
3,458321
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Yes, this is possible. There is an easy way to extend/add logic which is missing by implementing custom Variant Token.
This is an example implementation of ResolveParentName processor:
public class ResolveParentName : ResolveVariantTokensProcessor
{
public override string Token => "$parentName";
public override void ResolveToken(ResolveVariantTokensArgs args)
{
// this if statement is quite important in order to support this token in JSON Variants
if (args.ResultControl != null)
{
args.ResultControl.Controls.Add(new LiteralControl
{
Text = args.ContextItem.Parent.Name
});
}
else
{
args.Result = args.ContextItem.Parent.Name;
}
}
}
Do not forget about registering this processor:
<pipelines>
<resolveVariantTokens>
<processor type="YOUR_NAMESPAVE.ResolveParentName, YOUR_ASSEMBLY" resolve="true" />
</resolveVariantTokens>
</pipelines>
Here is an example usage:
As you can see this is great place to add a lot of custom logic and extend Rendering Variants. In the above example, I'm just using one args.ContextItem.Parent.Name property but you can do whatever you need there.
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "664"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f16037%2fhow-easily-extend-rendering-variants%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, this is possible. There is an easy way to extend/add logic which is missing by implementing custom Variant Token.
This is an example implementation of ResolveParentName processor:
public class ResolveParentName : ResolveVariantTokensProcessor
{
public override string Token => "$parentName";
public override void ResolveToken(ResolveVariantTokensArgs args)
{
// this if statement is quite important in order to support this token in JSON Variants
if (args.ResultControl != null)
{
args.ResultControl.Controls.Add(new LiteralControl
{
Text = args.ContextItem.Parent.Name
});
}
else
{
args.Result = args.ContextItem.Parent.Name;
}
}
}
Do not forget about registering this processor:
<pipelines>
<resolveVariantTokens>
<processor type="YOUR_NAMESPAVE.ResolveParentName, YOUR_ASSEMBLY" resolve="true" />
</resolveVariantTokens>
</pipelines>
Here is an example usage:
As you can see this is great place to add a lot of custom logic and extend Rendering Variants. In the above example, I'm just using one args.ContextItem.Parent.Name property but you can do whatever you need there.
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
add a comment |
Yes, this is possible. There is an easy way to extend/add logic which is missing by implementing custom Variant Token.
This is an example implementation of ResolveParentName processor:
public class ResolveParentName : ResolveVariantTokensProcessor
{
public override string Token => "$parentName";
public override void ResolveToken(ResolveVariantTokensArgs args)
{
// this if statement is quite important in order to support this token in JSON Variants
if (args.ResultControl != null)
{
args.ResultControl.Controls.Add(new LiteralControl
{
Text = args.ContextItem.Parent.Name
});
}
else
{
args.Result = args.ContextItem.Parent.Name;
}
}
}
Do not forget about registering this processor:
<pipelines>
<resolveVariantTokens>
<processor type="YOUR_NAMESPAVE.ResolveParentName, YOUR_ASSEMBLY" resolve="true" />
</resolveVariantTokens>
</pipelines>
Here is an example usage:
As you can see this is great place to add a lot of custom logic and extend Rendering Variants. In the above example, I'm just using one args.ContextItem.Parent.Name property but you can do whatever you need there.
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
add a comment |
Yes, this is possible. There is an easy way to extend/add logic which is missing by implementing custom Variant Token.
This is an example implementation of ResolveParentName processor:
public class ResolveParentName : ResolveVariantTokensProcessor
{
public override string Token => "$parentName";
public override void ResolveToken(ResolveVariantTokensArgs args)
{
// this if statement is quite important in order to support this token in JSON Variants
if (args.ResultControl != null)
{
args.ResultControl.Controls.Add(new LiteralControl
{
Text = args.ContextItem.Parent.Name
});
}
else
{
args.Result = args.ContextItem.Parent.Name;
}
}
}
Do not forget about registering this processor:
<pipelines>
<resolveVariantTokens>
<processor type="YOUR_NAMESPAVE.ResolveParentName, YOUR_ASSEMBLY" resolve="true" />
</resolveVariantTokens>
</pipelines>
Here is an example usage:
As you can see this is great place to add a lot of custom logic and extend Rendering Variants. In the above example, I'm just using one args.ContextItem.Parent.Name property but you can do whatever you need there.
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
Yes, this is possible. There is an easy way to extend/add logic which is missing by implementing custom Variant Token.
This is an example implementation of ResolveParentName processor:
public class ResolveParentName : ResolveVariantTokensProcessor
{
public override string Token => "$parentName";
public override void ResolveToken(ResolveVariantTokensArgs args)
{
// this if statement is quite important in order to support this token in JSON Variants
if (args.ResultControl != null)
{
args.ResultControl.Controls.Add(new LiteralControl
{
Text = args.ContextItem.Parent.Name
});
}
else
{
args.Result = args.ContextItem.Parent.Name;
}
}
}
Do not forget about registering this processor:
<pipelines>
<resolveVariantTokens>
<processor type="YOUR_NAMESPAVE.ResolveParentName, YOUR_ASSEMBLY" resolve="true" />
</resolveVariantTokens>
</pipelines>
Here is an example usage:
As you can see this is great place to add a lot of custom logic and extend Rendering Variants. In the above example, I'm just using one args.ContextItem.Parent.Name property but you can do whatever you need there.
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
answered Jan 16 at 9:43
Dawid RutkowskiDawid Rutkowski
3,458321
3,458321
add a comment |
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f16037%2fhow-easily-extend-rendering-variants%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
