Form Field Manager
Fixes
- Adding an action hook using the Do Action field does not produce an error.
Tweaks
- Improved Fields API integration in preparation for GiveWP 3.0
Fixes
- Resolved a compatibility issue with GiveWP 2.27.3, update to this version and GiveWP 2.28.0.
Fixes
- Section fields do not break manual donations.
Tweaks
- The repeater field uses the new GiveWP validation api introduced in 2.24.0.
Fixes
- 1/3 and 2/3 column fields now display correctly on the Multi-Step forms
- Date fields now save and validate properly upon donation submission
- Took care of a pesky notice that showed up when using the Editor field
- Add a check when saving to make sure all custom fields have a label to prevent weird issues
Fixes
- Resolved an error if using the less than condition
- Cleared up a notice thrown by the Repeater field
- Custom field classes are now correctly added to the field
Fixes
- Took care of a memory leak in field registration
Features
- Field conditions! Conditionally display a field based on the donation amount or another field!
Tweaks
- All fields are new registered via the new Field API
- Field markup has changed to match the Field API, so existing custom styles may break! Test before updating on production!
Features
- Added support for the new plugin telemetry introduced in GiveWP 2.10.0
Fixes
- Field labels now display correctly on the Multi-Step Form template
- Rich textarea field now works when the Form display option is set to Modal or Button
- PayPal Donation no longer ignores required checkbox and radio fields
Features
- Rewrote the form field rendering so its faster and preserves values when gateways change
- Fields now match the styling of the multi-step form using placeholders in fields for labels
Fixes
- Corrected a JS error on forms that did not have any custom fields when add-on was active
Fixes
- When the FFM fields are updated on the backend, e.g adding new dropdown options, that change was not reflected on the front-end if the user was populating the donation form FFM fields before adding new options on the backend. This was due to a caching issue that has been resolved. #321