Inicio›Toolset Professional Support›[Escalado a 2º nivel] Problem with saving required fields that are conditional and hidden – follow up
[Escalado a 2º nivel] Problem with saving required fields that are conditional and hidden – follow up
This support ticket is created hace 2 años, 10 meses. 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.
Hoy no hay técnicos de soporte disponibles en el foro Juego de herramientas. Siéntase libre de enviar sus tiques y les daremos trámite tan pronto como estemos disponibles en línea. Gracias por su comprensión.
Sun
Mon
Tue
Wed
Thu
Fri
Sat
-
10:00 – 13:00
10:00 – 13:00
10:00 – 13:00
10:00 – 13:00
10: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/Kolkata (GMT+05:30)
Este tema contiene 13 respuestas, tiene 3 mensajes.
Hi Nigel,
thanks for your reply. I needed some time to run some tests. I think there are still some issues with required fields. Please see below four usecases.
Thanks!
Marc
Usecase #1.
- In one field group i created a required text field and a checkbox.
- The text field is shown when the checkbox is set to TRUE
Saving is possible when:
- The checkbox is set to FALSE ( = expected behaviour)
- The checkbox is set to TRUE and the textfield is filled ( = expected behaviour)
- The checkbox is first set to TRUE and the textfield is filled and saved. And than the textfield is emptied and the checkbox is set to FALSE. (= expected behaviour)
Usecase #2
- In one field group i created a repeatable field group.
- The RFG is holding a text field and a checkbox.
- The text field is shown when the checkbox is set to TRUE.
Saving is possible when:
- The checkbox is set to FALSE ( = expected behaviour)
- The checkbox is set to TRUE and the textfield is filled ( = expected behaviour)
Saving is not possible when:
- The checkbox is first set to TRUE and the textfield is filled and saved. And than the textfield is emptied and the checkbox is set to FALSE. (= issue)
Usecase #3
- I created a checkbox in fieldgroup A and a required text field in fieldgroup B.
- Fieldgroup B shows up when the checkbox is set to TRUE.
- When checkbox is set to FALSE, saving is resulting in an incorrect notification (Field "Text field test #3" not updated: This field is required.) (= Issue).
- When the checkbox is first set to TRUE and the textfield is filled and saved. And than the textfield is emptied and the checkbox is set to FALSE it's resulting in an error where field cannot be saved empty. (= issue)
Usecase #4
- I created a checkbox in Fieldgroup A and a required text field in fieldgroup B
- The textfield in fieldgroup B shows up when the checkbox is set to TRUE.
- It follows the same scenario as Usecase #1.
Hello. Thank you for contacting the Toolset support.
Can you please share problem URL where I can see the issue and with what field group and with what field you are having the issue.
I will require to review your current setup first to check everything is setup as expected and then I will give a shot to reproduce the issue. Please share the steps I should follow to reproduce the issue.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Ah sorry Minesh, i just had a clean install of WP and Toolset on twenty twenty. So nothing fancy at all. I removed the test environment directly after the above post. You can just follow the above usecases; it's easy. If any unclear; please let me know.
Thanks!
Marc
Well, actually no problems in usecase 1 and 4, it was just to show that i think the previous issue is fixed. However, there are still issues with required fields. I explain those in usecase 2 and 3.
Ok?
