Version 1.2.4

Fixes the KulaHub emailsubscribe field being rejected by the API.

Fixed

• Contact.emailsubscribe is now sent as a Boolean. The AddForm endpoint types Contact.Emailsubscribe as a Boolean, but the plugin was sending the string "True", so submissions from forms with an opt-in field were rejected.
• A "No" answer is now respected. The previous Boolean conversion used !empty(), so any non-empty answer on a yes/no radio field, including "No", resolved to true.
• API errors now report the reason KulaHub returned, including ASP.NET validation documents, instead of logging "Unknown API error".
• title and address3 are routed into Contact alongside the other contact fields, matching the field list published to integrators.
• Version number corrected. The plugin header was left at 1.2.0 across the 1.2.1 to 1.2.3 releases, so WordPress kept offering an update that was already installed. The stale readme.txt stable tag is corrected too.
• The updater now names the Converta-Agency repository directly rather than relying on a GitHub redirect from the old path.

How emailsubscribe is resolved

Field type	Rule
Checkbox or consent	Ticked is true, unticked is false
Radio, select or text	Yes, True, 1, On, Opt in give true; No, No thanks, False, 0, Off, Opt out, Unsubscribe give false; an empty answer is false

Upgrading: required if any of your forms map a field to emailsubscribe.

Version: 1.2.3

Persist all form settings

Version: 1.2.2

Persist the selected account

Version: 1.2.1

fix issue with adding new api key where it adds 2 rows instead of 1

Version: 1.2

Adding functionality to support multiple KulaHub accounts from one installation.

Version: 1.1.3

Check php and WordPress version for compatibility and for WP directory compliance

Version: 1.1.2

testing updater

Initial release

Initial release