Skip Navigation

[Resuelto] CRED checkbox validation fails after WP 5.6 update

This support ticket is created hace 3 años, 11 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
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Este tema contiene 4 respuestas, tiene 2 mensajes.

Última actualización por diyanK hace 3 años, 10 meses.

Asistido por: Nigel.

Autor
Mensajes
#1870683

Hi,

I was forced to turn off my GDPR compliance generic checkbox because users can no longer register on my website after the 5.6 update. It seems like it does not get the input from user no matter checked or not.

Here is my code:

<div class="gdpr-wrapper">[cred_generic_field type='checkbox' field='gdpr-agreed' class='agreed']
{
"required":1,
"default":"",
"label":"Съгласен съм"
}
[/cred_generic_field]с <a href="<em><u>enlace oculto</u></em>">политиката за поверителност и усовията за ползване</a>.</div>

Thanks in advance!

#1871463

Nigel
Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

I tested that on my own site and can confirm it is not working, although when I tested it with earlier plugin versions pre-5.6 it also was not working, so I'm not sure when the problem began.

In any case, it is confirmed, and I've escalated it to the developers so that it can be fixed.

I'll let you know when there is a solution to share.

#1871465

I can confirm that it did work prior to installing the pre-5.6 related Toolset updates.

It is a fresh feature that I just added, it was tested and confirmed working.

Thanks for the update and I hope to get a quick solution due to the sensitivity of the topic.

#1913125

Nigel
Supporter

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+00:00)

Hi there

I have an update from the developer, who says it fails because there is no setting provided for the default value.

Add a value for the option—anything, e.g. 0—and then the field should work correctly.

They are going to make some changes to handle this correctly, but if you provide a value for the default this will work, and I think we can close here.

#1913153

Okay, I changed

"default":"",

to

"default":"0",

And it worked!

Thanks!