I’m using ACF as well as Ninja Forms, and it seems there’s a small conflict between the two in the back-end: Ninja Forms has an “Add form” button above any text editor (both native WYSIWYG and those added by ACF fields), which shows a modal for chosing which form you want to place in the text via shortcode.
There are two topics about this on the Ninja Forms Github, and I’ve replied to both to dump them, but they’ve not picked up any traction. The issue is not that common, so maybe it’s a niche thing.
Is there anything on the ACF side that could cause this? I’m posting this publicly because it may help others with this issue. Any help appreciated.
I’ve got a quick fix for this, but it’s not ideal. The problem is that Ninja Forms creates a unique modal that is associated specifically the main content region, and it doesn’t support multiple of that modal of one page. When ACF is installed, the modal gets duplicated to account for custom WYSIWYG fields, but that causes a bunch of issues due to the duplication.
Simple solution is to just remove the fields from ACF fields. Obviously this means you need to manually insert Ninja Forms when using custom fields, but it’s a reasonable compromise.
There are several plugins that add to the wysiwig that are not multiple editor compatible. I have not had much luck getting these plugin authors to alter them so that they are.
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
Advanced Custom Fields @wp_acf is a great plugin for managing custom fields and other meta information. Check out the recording of @GUAlumni's talk at #WPCampus to learn how it can now help you build #Gutenberg blocks! #WordPress #HigherEd #EdTech #heweb https://t.co/MXuCTTsX3b— WPCampus (@wpcampusorg) November 16, 2019
© 2019 Advanced Custom Fields. Subscribe