This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Conflict with Advanced Custom Fields Wysiwyg field

Resolved 3 replies pluginplugin-page-builder
10 years ago · Last reply by Andrew Misplon 10 years ago

Hello. I’ve read some of the other conflicts with ACF but I didn’t find my specific issue and wondered if anyone might have a fix.
I’m using the SiteOrigin Page Builder in my normal content window, works fine. However I have a second Advanced Custom Field WYSIWYG window for additional text. When editing it is all working fine (TinyMCE, Add Media, etc.), however when viewing the page it is duplicating the content from the Page Builder where the ACF field is supposed to appear. So I see the Page Builder content twice and don’t see the content from that ACF field at all.
Here is what I am doing in my template to call these elements.

This shows the normal content from the Page Builder

This should show the ACF field, but instead duplicates the Page Builder content.
When I change the ACF field to something instead of WYSIWYG, it outputs fine. When I continue to use the ACF WYSIWYG field and try other widgets in Page Builder, it does the same thing (Visual Composer, Text) – just duplicates the Page Builder content in both places.
Anyone else ever had this issue? Is there a work-around other than not using the ACF WYSIWYG field?
Site is in development and not public, so I can’t supply an URL.
Thanks for your help.

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

3
  1. jberg1 10 years, 5 months ago

    Sorry it stripped my code:

    Here is what I am doing in my template to call these elements.

    the_content();

    This shows the normal content from the Page Builder

    echo the_field('custom_field_name');

    This should show the ACF field, but instead duplicates the Page Builder content.

  2. jberg1 10 years, 5 months ago

    Nevermind. I found my issue.
    I am using a function to add content filters to all ACF WYSIWYG fields.

    apply_filters('the_content')

    Apparently that is causing the Page Builder content to output in my ACF WYSIWYG fields.

  3. Andrew Misplon Staff 10 years, 5 months ago

    Hi Jberg1

    Thanks for reporting and for the details. As far as I know, Page Builder does use the_content to output. I’ll ask one of our developers if they can take a look early next week. I’m not sure we’d be able to offer any hotfix though. Chat then.

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread