Versioning

This is a draft.

With the release of Ninja Forms THREE (v3.x), marketplace add-ons will need to adhere to a new versioning policy. For the purpose of auto-detecting compatibility, add-on version should follow the pattern of:

NinjaForms.Major.minor

The first number should represent the major version of Ninja Forms with which the add-on is compatible. This does not mean that add-ons cannot be backwards compatible, rather backwards compatibility is currently maintained through deprecating the previous version of the plugin file for conditional loading. Major version backwards compatibility should be included for one year, where applicable.

The second number should represent the major updates of the add-on itself. This includes the addition of major feature and user interface changes.

The third number should represent the minor updates of the add-on. This includes bug fixes and other tweaks.

Everything you need to build everything you want

Quick Start Guides

I want to pre-fill form fields

I want to integrate with a third party service

I want to connect to a third-party like Slack, Trello, Mail Chimp, etc. using their API. How do I hook into the Ninja Forms processing system to send data to those services?

I want to create a custom field for my users

I need to collect specific data or present fields to a user that aren’t native to Ninja Forms. How can I create something that will be reusable and won’t require me to mess with the code once it’s written?

I want to display submission information on the front-end

I’d like to display submissions on the front-end for my users.

I want to send submissions to another database

I have another database that I would like to store Ninja Forms data in.

Translation Ready

Want Ninja Forms in another language? The framework is translation-ready, making it as easy as possible for you. Special incentives for translators who want to join the team.