Ninja Forms Developer Melbourne: Support and an Honest Look at the Add-On Bill

Something changed, and on a Ninja Forms site the usual candidate is an add-on that has not been updated in a long time meeting a new PHP or WordPress version. The licence lapsing is invisible at the time it happens, so the cause and the symptom can be a year apart. We check the add-on inventory and licence status first because it resolves this more often than anything else.

Only if the arithmetic says so. Add up the annual add-on renewals and compare it against a single licence elsewhere plus the one-off cost of rebuilding what you have. If you run two add-ons and everything works, staying is the right answer and we will tell you that. If you are renewing six, the maths usually points the other way inside two years.

Yes, as long as they are exported before anything is uninstalled. Ninja Forms keeps submissions in the site and can download them form by form as a spreadsheet file, so do that for every form first. Then check the plugin's uninstall setting, because it can be told to delete all of its data on removal. With the files safe, whether to import them into the new plugin or simply archive them is a separate and usually cheaper decision.

Yes, provided it is kept current. It is actively maintained, and the serious vulnerability in its past was patched and force-pushed to sites precisely so that it would not linger. The real risk on any older form plugin is not the vendor, it is a site that stopped receiving updates because a licence lapsed or nobody was responsible for applying them.

Almost always duplicated actions. Somebody added a second email action while troubleshooting a delivery problem that was actually caused by the site sending unauthenticated mail, the original started working later, and now both fire. Reading the actions resolves it in minutes, and it is worth fixing the underlying sending at the same time so it does not recur.

Yes, through the payment add-on for your gateway, which becomes another line on the renewal list, so count it before you buy. The rest of the work is in the edges: what the customer receives after paying, how a refund is handled, and making sure each submission can be matched to its gateway record when someone later queries a charge.

That is the normal situation and it is exactly what the diagnostic is for. Between what is installed on the site, what is active, and what is still being billed, there are usually discrepancies in both directions: something paid for and not used, or used and quietly lapsed. You get the list written down and it is yours regardless of what you decide afterwards.

It can contribute, particularly when its assets load on pages with no form on them and when several add-ons each add their own. It is rarely the main cause of a slow site, though. Limiting its assets to the pages that carry a form is a small change, and we measure before and after rather than assume it helped.

Yes, and you do not need their cooperation: admin and hosting access is enough. The first job is working out how the forms are actually assembled: which add-ons are involved, what the actions do, where submissions go and which licences exist. Until that map exists, any quote for further work would be a guess.