Home>Support>Advanced Custom Fields conflict with Page Builder

Advanced Custom Fields conflict with Page Builder

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

There seems to be a conflict with Advanced Custom Fields. The page builder rows are disappearing in the WordPress editor. De-activating ACF solves the problem. I never noticed this confict before, and have duplicated the problem in 2 different themes.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 10 years, 10 months ago Andrew Misplon
    Hi, I Work Here

    Hi Al

    Thanks for the long wait here. We have had this reported before but believe it to be a three-way conflict. Can you perhaps confirm for us, does the error still occur if you de-activate all of your plugins except for Page Builder and ACF?

  2. 10 years, 10 months ago Al Arthur

    Thanks Andrew,
    So, It seems that the conflict has been resolved, because the problem has disappeared! Page builder appears to be working perfectly in harmony with ACF and all the other plugins. I checked a few sites, and I can no longer duplicate the problem on any of them. Thanks for the help and for the great plugin!
    cheers,
    Al

  3. 10 years, 10 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for checking for us and reporting back, we appreciate the effort. If something like this occurs again please let us know and we’ll take it from there.

    All the best.

  4. 10 years, 8 months ago Primož Cigler

    Hi,

    We are encountering the same problem, I first thought the problem was one of the other plugins, but at the end I tried to disable the ACF and then it works.

    I don’t know yet if the problem is ACF or your page builder, but I will do some research now and will let you know what I find out.

    • 10 years, 8 months ago Andrew Misplon
      Hi, I Work Here

      Hi Primož

      That’ll be great. Thanks!

      If you could please report your findings in a new forum thread that’ll help get a quick response, most likely on Monday.

      Page: New Thread

      Thanks again.

  5. 10 years, 8 months ago Cleidson Rodrigues

    I am having the same problem, the edit boxes of some page, I can not edit the page.

    • 10 years, 8 months ago Andrew Misplon
      Hi, I Work Here

      Hi Cleidson

      Please crank open a new thread for us and we’ll be with you ASAP.

      Page: New Thread

      Most likely on Monday.

      We appreciate the feedback.

  6. 10 years, 8 months ago Cleidson Rodrigues

    appreciate the attention friend where I open the call, I’m from Brazil I’m using google translator

  7. 10 years, 8 months ago Andrew Misplon
    Hi, I Work Here

    Google Translate is no problem. Thanks for taking the time to do the translation for us. New thread can be opened from this link here: Page: New Thread. Hope that makes sense.

  8. 10 years, 8 months ago superglue

    I can confirm that this seems to be a three-way conflict. I can reproduce it with the following three plugins installed:

    – SiteOrigin Page Builder
    – Advanced Custom Fields (ACF)
    – Black Studio TinyMCE Widget

    In this case the Page Builder is not displayed when I try to edit a page but reappears once I uncheck Page Builder in the options drawer at the top of the page and then re-check it.

  9. 10 years, 8 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for clearing that up for us. Appreciate the feedback. The dev team is super busy at the moment with the Page Builder 2.0 launch coming this year. We’re going to push that. Then re-check this and see where we stand. There is a good chance it will be resolved. Sorry I don’t have hotfix for right now.

  10. 10 years, 8 months ago superglue

    I think I might have a fix. I habe bought a license for the new ACF Pro and installed it and at least for now everything works as it should.

  11. 10 years, 8 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for sharing. Glad to hear that resolved the conflict.

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.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More