Expand my Community achievements bar.

SOLVED

rich text editor in a multi field widget

Avatar

Level 1

Hi,

i have a requirement to configure a rich text editor in to a multi field custom widget. can you please help

Thanks in advance

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You need to specific xtype to your field config node of your multi field widget.

For example check this path

/libs/foundation/components/carousel/dialog/items/static/items/pages/fieldConfig

on the fieldConfig node instead of pathfield xtype use rich text type

View solution in original post

2 Replies

Avatar

Level 10

You can have rte in multi field. But please try to use a textfield instead of a richtext in a multifield. If you decide to use rte,   [1] will help to fix some of issue.

[1]  http://aemfaq.blogspot.com/2013/04/richtext-in-multifield-widget.html

Avatar

Correct answer by
Former Community Member

You need to specific xtype to your field config node of your multi field widget.

For example check this path

/libs/foundation/components/carousel/dialog/items/static/items/pages/fieldConfig

on the fieldConfig node instead of pathfield xtype use rich text type

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----