Okay, after some more googling, I found this: How To Build Custom Forminator Add-ons Using The Developer API.
So I’ll check that out. Thanks, WPMU, you ROCK!
I was able to create a custom plugin, but could not create a custom Forminator addon. Is that restricted to the Pro version?
Hi @jamminjames
I hope you are doing well today.
I pinged our Forminator developers to get more data in this matter. We will post an update here as soon as more information is available.
Kind Regards,
Kris
Hello @jamminjames ,
Forminator API is for creating integrations with Forminator, not custom plugins.
You can check examples of code snippets for Forminator https://gist.github.com/search?q=forminator – maybe something will help you in writing your custom addon.
kind regards,
Kasia
But the WPMU blog post talks about creating an addon, as you also say. How can that addon be made accessible in the admin menu? I don’t see in the examples I scanned how to do that.
Hi @jamminjames
It seems we have, unintentionally, create some confusion here, mostly due to wording used.
Let me sort that out a bit:
1. the article is referring to “add-ons” but it only means a “custom code or plugin that extends Forminator or interacts with it”.
It doesn’t mean an add-on that is actually “registered” with the plugin and used “inside” it (as “add-on” barebone example that you can find inside plugin files – that’s internal)
2. The API can actually be used in your plugins – what Kasia meant is that it’s not created as tool to create add-ons entirely; it’s just a set of API functions that can be used in our own plugins or custom code; it’s mostly used in codes that are created for custom integrations but it’s not restricted to that.
However, there are no functions to register an add-on in that meaning that it becomes “integratl part of Forminator”. We don’t have such features/functions and we don’t use that kind of add-ons (except ones created by us/internally).
You are free to create your own plugins that work using Forminator API or data and interact with it (using Forminator API and/or filter/action hooks available) but those need to be separate plugins.
3. What you can do, however, is
– to check if Forminator is active in your own plugin (see: is_plugin_active()), to avoid your plugin execution if Forminator is not there
– and you can place your plugin menu as a submenu under “Forminator” menu – that doesn’t require Forminator API, it’s only a matter of how you add your menu (see: add_submenu_page())
Kind regards,
Adam
Great, thanks for the clarification!
