Support » Plugin: Advanced Custom Fields: Extended » Another plugin causes a conflict with ACF-E

  • Resolved laymonk


    Hi Konrad,

    Just reporting this, so you are aware.

    Another plugin (Document Embedder) that I find very useful has an effect on ACF-E that prevents ACF-E forms editing screens from being able to access the field group definitions. Once that plugin is activated, visiting any ACF-E forms definition (even existing and functional forms definitions) displays the message:

    No field groups are currently mapped

    The one positive thing in the situation is that existing add/update forms seem to keep working. So, this problem is isolated to the forms creation/edit admin UI of ACF-E.

    I have reported this to the plugin’s support page.

    Making you aware just in case there is anything that seems obvious to you. It’s a really useful plugin and would be great if one can use it alongside ACF-E.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author hwk-fr


    Hello @laymonk,

    Thanks for the feedback! Yes I received a notification since you mentioned ACF Extended on a support thread 🙂

    I took a look at the report and installed the said plugin. ACF Extended Form works correctly here, Field Groups are visible, they are correctly mapped and the form is displayed on the front-end.

    I’m not quite sure to understand what is going on on your environment, but you may want to try to test it on a blank WP install with a blank theme (maybe there’s a incompatibility with an another plugin or theme code?).

    You also mention that this is an “another plugin causing conflict”. Have you noticed an another plugin conflict with ACF Extended?

    Edit: I managed to reproduce the problem, you need to have at least one document added in the Document Embedder UI. I will take a look a bit deeper later see what I can find.


    Thread Starter laymonk


    Thanks a million for being on the ball as usual, Konrad.

    In my own case, the documents I have added to document embedder are all also used within ACF field groups that are connected to ACF-E forms … and I wondered whether that was the reason. Seems not, since you reproduced it probably without being setup that way.

    Also, as part of the conflict with document embedder, I found that cloned subfields of field-type text could not be edited within ACF-E forms (and also even in the backend).

    Plugin Author hwk-fr



    After further investigations it looks like Document Embedder hijack the global $post object during ajax request (and probably in other situations too). This is probably what cause those problems since WordPress recognize a wrong post.

    I’ll post an answer on the topic of the plugin. Since the problem also occurs without ACF Extended (only with ACF), I’ll have to close the topic here because I can’t debug others plugins.

    Have a nice day!


    Thread Starter laymonk


    Konrad, million thanks for your efforts and for spotting those issues. I am sure the plugin author will appreciate. I am glad I mentioned it here.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Another plugin causes a conflict with ACF-E’ is closed to new replies.