Capsule has released their new API v2 and they will be dropping v1 in January. So what does that mean for you users of the Ninja Forms Capsule extension? Hopefully nothing! I’ve been working diligently to migrate things over in the background so that the transition for you will be seamless.
There is one big item to note: Capsule is moving to an Open Auth process for access. That’s a big enough deal that I’ll write a separate post on that. For new users, that’s all you’ll ever see in the dashboard so no surprises for you.
For existing users, you’ll notice that your old credentials no longer appear. They aren’t lost, they just aren’t being shown anymore. I added a feature that would detect the credentials of existing users and use those to get updated Open Auth credentials so you won’t have any interruption in performance and it will be invisible to you. That being said, it’s probably best that you at least familiarize yourselves with the new dashboard so that you aren’t surprised the next time you visit.
Another relatively minor change in how the API behaves is that Organisation names must now be unique. In v1, each form submission that mapped to an Organisation would create a new Organisation, even if the name were identical to an existing one. Now, in v2, that is no longer allowed. If a site visitor types in the name of an existing Organisation, it won’t be created. The Person and all other modules will work exactly as before.
I made a design decision to NOT connect the new Person to the existing Organisation because that would give any person with access to your form to add entries to your organisations that are unintended. The default work flow will be that, if you truly did intend to link a new Person to an existing Organisation, you will do that from your Capsule dashboard.
As always, if you have any questions, feel free to contact me.
