[Resolved] Using Avada's Fusion Builder on any WYSIWYG field

[Author]

Posts

[josephQ]

I am trying to: enable the Avada Fusion Builder (a WYSIWYG page composer) on any WYSIWYG / rich text editor custom field.

Link to a page where the issue can be seen: See attached screenshot. I created a custom field named "Body (shared)," but I don't have the option of toggling between the Fusion Builder and the native WP rich text editor.

I expected to see: a blue button that says "Use Fusion Builder" above any WYSIWYG / rich text editor custom field.

Instead, I got: no blue button, just the native WP rich text editor.

I also looked at the following support tickets / URLs prior to contacting support:
https://toolset.com/forums/topic/avada-fusion-builder/
https://toolset.com/forums/topic/wp-views-extension-breaks-avada-fusion-builder-fusion-slider/
https://toolset.com/forums/topic/avada-fusion-builder-for-content-template/
https://toolset.com/errata/content-templates-are-not-editable-using-fusion-builder-when-allowed-post-types-are-set-in-avada-settings/

[Nigel Supporter Languages: English (English ) Spanish (Español ) Timezone: Europe/London (GMT+01:00)]

Hi Joseph

Toolset includes a specific integration to allow you to use Fusion Builder to edit the body of a Content Template, but it doesn't include any other integration to allow you to use Fusion Builder to edit any wysiwyg field.

To be honest I think that is a question for Avada.

I did some searching to see if there was a published solution to do the same with ACF wysiwyg fields, for example, thinking it might be possible to employ something similar with Types wysiwyg fields, but didn't find anything.

I doubt that it is a use that Avada have anticipated, but they should be able to advise whether it is possible and what is required.

If they give you some directions and you have trouble implementing them, let me know.

[josephQ]

Thanks, Nigel. I've opened a support ticket with the Avada folks and am awaiting a response. Will let you know what they say!

[josephQ]

Nigel,

I heard back from Avada Support. What I wanted isn't possible. The work-around is to create an element in a Fusion Builder-enabled field, copy the shortcode, and paste it into the desired non-Fusion Builder-enabled field.

Saul