Skip Navigation

[Resolved] Front-End Post Edit Form

This support ticket is created 4 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 2 replies, has 2 voices.

Last updated by mikaelD 4 years, 11 months ago.

Assisted by: Luo Yang.

Author
Posts
#1414995

I am trying to:

I created a front-end form that has a multi-select "Checkbox " field for a custom post type.

I expected to see:

The post fields on the back-end to be updated inside the post to reflect the checkboxes that were checked on the front-end.

Instead, I got:

The post on the back-end doesn't update. If I go back to the front-end edit form I can see the values are checked in the form, but the checkboxes are empty when I go into the post through the WP-ADMIN editor.

Steps to replicate:
1) Login here:
2) Click "Edit My Profile"
3) Check of some boxes at the bottom of the form and Submit the Form
4) Click the "Edit My Profile" button at the top of the Profile page
5) Confirm boxes are still checked
6) Login with Admin Credentials
7) View the "Provider Profiles" custom post type
8) Edit the Profile "Daniel Tomas"
9) The checkboxes will not be filled in

All other fields on the form work, it is just the checkboxes.

#1415841

Hello,

It is a known issue, see the errata here:
https://toolset.com/errata/toolset-form-doesnt-save-checkboxes-field-values/

Currently, please try the patch file of above errata link, and test again.

And I have edited your thread to remove the credentials, it is not safe to share them publicly.

#1416619

The patch fixed the issue. Thank you LUO!