• State Verified Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 1001 views
  • Users 0 members are here
Options
Related

Bug or Expected Behaviour: Tip Embeddable does not Render in Email

starksk

When using a tip from the insert menu, it is rendered as plain text

Pardon the testing to see how this platform handles it vs my test upgrade to 12.0.1.15778.

In my instance, the email for Forum Thread which hasn't changed in several updates, renders the tip as plain text of the content of the tip and does not indicate it is a tip at all. Is that expected or do I have something wrong/out of date on my instance?

Parents
  • +1

    Hi . This should probably be classified as a bug. Embeddables support target-specific rendering with the context_v2_embeddable.RenderTarget  API. While the Tip and Pull Quote embeddables are not yet doing this, the Navigation List embeddable does vary its output based on whether the RenderTarget == 'Web'.

    I've logged it.

    TE-16844: Tip and Pull Quote embeddables should render alternate output for non-web targets

    Completed for 12.1, 12.0.3

    For a workaround, you can edit the Tip embeddable to detect the target:

    #set ($content = false)
#set ($content = $core_v2_widget.GetStringValue('message', ''))
#if (!$content)
    $core_v2_widget.Hide()
#end

#set ($type = $core_v2_widget.GetStringValue('type', 'information'))

#if ($context_v2_embeddable.RenderTarget != 'Web')
    <hr />
    <strong>$core_v2_language.GetResource($type)</strong>
    <p class="message $core_v2_encoding.HtmlAttributeEncode($type)">$core_v2_encoding.HtmlEncode($content)</p>
    <hr />
#else
    <div class="message $core_v2_encoding.HtmlAttributeEncode($type)">$core_v2_encoding.HtmlEncode($content)</div>
#end

    Thanks for the report!

Reply
  • +1

    Hi . This should probably be classified as a bug. Embeddables support target-specific rendering with the context_v2_embeddable.RenderTarget  API. While the Tip and Pull Quote embeddables are not yet doing this, the Navigation List embeddable does vary its output based on whether the RenderTarget == 'Web'.

    I've logged it.

    TE-16844: Tip and Pull Quote embeddables should render alternate output for non-web targets

    Completed for 12.1, 12.0.3

    For a workaround, you can edit the Tip embeddable to detect the target:

    #set ($content = false)
#set ($content = $core_v2_widget.GetStringValue('message', ''))
#if (!$content)
    $core_v2_widget.Hide()
#end

#set ($type = $core_v2_widget.GetStringValue('type', 'information'))

#if ($context_v2_embeddable.RenderTarget != 'Web')
    <hr />
    <strong>$core_v2_language.GetResource($type)</strong>
    <p class="message $core_v2_encoding.HtmlAttributeEncode($type)">$core_v2_encoding.HtmlEncode($content)</p>
    <hr />
#else
    <div class="message $core_v2_encoding.HtmlAttributeEncode($type)">$core_v2_encoding.HtmlEncode($content)</div>
#end

    Thanks for the report!

Children

About
Privacy Policy
Terms of use
Copyright 2024 Verint, Inc.
Powered by Verint Community