Resolved
Reported for: Toolset Forms 2.5.3
Resolved in: 2.5.4
If you have a form that features a custom Checkboxes field created using Toolset Types, the form fails to save the field value when submitting it on the front-end.
Please note that this problem was introduced by an internal change in WordPress 5.3.1, so older versions will not be affected. There is a ticket to fix this in a future version of WordPress, but there is no estimated release date for it yet.
Please use this patch if yo are experiencing this problem. It is safe to use with WordPress 5.3.1, with previous versions and with any core update that gets released to address the issue.
To apply the patch, unzip the file and upload its contents to your Toolset Forms installation, under /library/toolset/cred/embedded/models/.
So how to I do this where is this /library/toolset/cred/embedded/models/. you are talking about? is it in the wordpress siteo toolset. please assist me because I dont know where to upload the files
The full path is wp-content/plugins/cred-frontend-editor/library/toolset/cred/embedded/models/
If you download and extract the patch you will find it contains 3 files, and you should replace the existing same 3 files in that folder.
So, should we expect the long term solution to come from WP or in a, hopefully soon to be released, Toolset update?
And if WP fix, how do we handle updates from Toolset? Will they overwrite the patch?
That issue was resolved and fixed in Toolset Forms 2.5.4 version (latest) please make sure you have the Forms updated and if then the issue still exists the best would be to report that to our supporters so we can take a look at what’s going on.
Thanks!
So, should we expect the long term solution to come from WP or in a, hopefully soon to be released, Toolset update?
And if WP fix, how do we handle updates from Toolset? Will they overwrite the patch?
@ken this has been fixed already in Forms 2.5.4 . We don’t know when this version will be released but of course, you will get notified when we launch this release.
There is a new forms update, 2.5.4, this will solve this issue