Repeatable fields always be prompted as update error

This support ticket is created 3 years, 6 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
8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-	-
13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-	-

Supporter timezone: America/New_York (GMT-04:00)

Tagged: Setting up custom fields, Types plugin

This topic contains 3 replies, has 2 voices.

Last updated by Christian Cox 3 years, 6 months ago.

Assisted by: Christian Cox.

Author

Posts

August 8, 2021 at 9:41 am #2136757

kelvinL-2

Dear Sir/Madam,

I have a custom post "Course" with a "Repeatable Group" custom field. Every time when I update the custom field, it always prompts an error about the field is required and not updated.

There are 3 required fields but all of them are set with a conditional display. 3 fields are Google Drive Link, Google Form Link, and PDF Link, only I select the Materials Type as one of them then I will fill the url link.

If I update other fields, all these fields will be prompted the error, if I just click one of them without changing anything and update, the other two will be prompted the error.

I assume there is no need to check the field if I don't select them. I usually ignore the error but how can I fix the error?

Best regards,

Kelvin

August 9, 2021 at 4:05 pm #2137959

Christian Cox

Hello, it looks like there may be a problem in field validation of repeatable field groups when required fields are hidden. If it is okay, I would like to create a clone of the site using the All-in-One WP Migration plugin already installed on the site. I will try to reproduce the problems in a local copy of the site and troubleshoot further, then escalate to my 2nd tier support team for additional investigation. The recent Types 3.4.11 release introduced a known issue in custom field validation: https://toolset.com/errata/conditional-display-of-custom-fields-broken-in-types-3-4-11/
However, it looks like this site is still running Types 3.4.10 so this may be a separate issue.

Please let me know if you approve and I will create the site clone for further analysis.

August 13, 2021 at 4:13 pm #2142171

kelvinL-2

Dear Christian Cox,

Sure, please do so.

August 15, 2021 at 9:49 pm #2143277

Christian Cox

Okay thank you, I was able to replicate this issue in my local test site in a similar test. Required fields that are hidden by conditional logic are producing validation messages in the legacy post editor screen. Luckily they are not preventing the post from being saved, so this is not preventing you from working on the site. However, it should be resolved. I have escalated the problem to my 2nd tier support team for further investigation and escalation to the developers. I'll let you know if a patch or other workaround becomes available.