Embeddables - Widget Configuration

In Embeddable Studio, is your embeddable defined to be “Embeddable anywhere”, or only within specific content types?

Interestingly enough; i see it on one widget config window, but not another one:

Interesting. I got it to work by coping the config from the Generic Content widget, however now the embeddable are not rendering:

Ah, yes reviewing again, I see that the Generic Content widget defines its html field's content type id as DF237622-6CC3-4FC2-8555-EF4FB2656444, which is the Page content type if further limited within the Embeddable's definition availability and/or enablement. That would help explain the use within a widget's config. 

But as for rendering - any exceptions when it renders the raw [embed] tags?

Ok, so heres what I did.

I created a embeddable that centered items. I gave that embeddable a WYSWIYG editor and added in my embeddable there:


For testing sake, I also copied the embeddable code into the Generic Content WYSIWYG:

The Center Embeddable didn't render, however the single embeddable did. I then tried using the $core_v2_ui.Render function which did nothing.

What's the best way to center things on the page, should I just make a widget that mimics Generic Content but centers everything?

Embeddables in embeddables are not currently supported. While you can get the embed option within the editor by providing a valid content type identifier, they will not be parsed/saved (which requires server-side logic) and will not be renderable (because they were never parsed).

Stephen Vicino said:

should I just make a widget that mimics Generic Content but centers everything?

That is an option. 

Hi Ben Tiedt  we ran into something interesting!

We got this to work; slightly. When the Config name of the HTML input is html; then we can decode and render; if it is not; it will not render correctly. is there a way to get this to work for multiple HTML inputs?

Thanks for this it also solved an issue I has when using a html config property in a custom widget and ottb embeddable such as emojis were not being rendered 

For ref we needed to use

<property id="calloutBody" labelResourceName="calloutBodyName" dataType="html" template="html" enableRichEditing="true" rows="20" columns="40" contentTypeId="DF237622-6CC3-4FC2-8555-EF4FB2656444" />

$core_v2_ui.Render($core_v2_widget.GetHtmlValue('calloutBody', 'tbc')))