[Assigned] "For" in label for radio button does not take correct value 2

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.

You are not logged in. You can view support threads, but not post.
If you are already logged in, please refresh your browser.

Related documentation: Front-end Content Submission and Editing Forms

This topic contains 12 replies, has 5 voices, and was last updated by  Jason Lorje 1 month, 1 week ago. The support staff assigned to this topic is Shane.

Viewing 13 posts - 1 through 13 (of 13 total)
Author
Posts
#548749

Hi Shane,

This is a continuation of this support thread - https://wp-types.com/forums/topic/for-in-label-for-radio-button-does-not-take-correct-value/.

While I found a workaround to make "for" attribute of labels to have the same value as input ID, this workaround is not working if the form is inside a pop-up (bootstrap modal dialog) or inside a bootstrap tab.

In fact, even if I use default styling, the "for" attribute takes some random value.

Besides, it not only messes up the fields built with the Toolset, but also the fields I added into the form manually. It replaces the "for" I specified for the label in php with a random value.

Please test it on your side and confirm (or not) the issue.

Thanks.

#549005

Beda
Forum moderator

Supporter languages: English (English ) Spanish (Español ) German (Deutsch )

Supporter Timezone: Europe/Zurich (GMT+02:00)

I assigned this Ticket to Shane since you requested his help.

I think we have internally something filed for it, and I already gave Shane a Hint on the internal issue tracker.

If that reported issue/request does not exactly match your issue, Shane will debug this with you and either file a Feature Request or a BUG Report.

I just wanted to let you know that CRED uses a lot of "random" values.
In ID's and other attributes.
Those change either per-form or even each time you load a form.
This is due to the uniqueness of each form/Field.
If we would not do that, fields and posts can get overwritten.

This is of course not related to the "for" attribute, but it is for the ID of several things.
And that we cannot easily change.

Anyway, Shane will be with you on Monday.

#549549

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Valeria,

It seems that there was a feature request opened for this and a document shared. I've requested permissions to view this document and will let you know if the request was added or not.

Thanks,
Shane

#549590

Hi Shane,

Thanks for the update. The good news is that the site is still in development, so I have time to wait for the fix. At the same time, remembering my last request, it took you guys 1.5 months to give some news, so I hope this is not going to be the same case.

Looking forward for your news about it.

#551094

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Valeria,

I havn't gotten an update on this one as yet. I've posted a reminder in the escalated ticket for this one.

Thanks,
Shane

#553770

Hi Shane,

I've got a reminder from your cleanup robot this morning (4 times for some reason) to update this thread.

The issue is still very hot and I'm looking forward to hearing your good news about it as it affects almost a half of the sites I've built with Toolset.

Thank you.

#553946

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Valeria,

I can confirm that it has been added to our list of CRED requests and waiting for the appropriate steps to be taken for this to be discussed with our development team.

Thanks,
Shane

#556869

Hi Shane,

Your cleanup robot keeps reminding me of this ticket. I'm still waiting for your news. Is there any?

Thanks.

#557279

Christian Cox
Forum moderator

Supporter languages: English (English )

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

Hi, Shane is currently unavailable but will return tomorrow to continue working on this request. Thanks for your patience.

#557768

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Valeriia,

There's not much in news I can provide after the feature request has been added to our list since it is out of my hands whether it will be added or not.

I can only give information when the status of the request is approved.

Thanks,
Shane

#559279

Hi Shane,

In order for my ticket not to get closed automatically while I'm waiting for the solution, I guess it makes sense if you don't reply to this message and it does not take status "Waiting for user confirmation". Please reply only if you have any news.

Otherwise I'm forced to write to you every week.

Thanks.

#559539

Shane
Forum moderator

Supporter languages: English (English )

Supporter Timezone: America/Jamaica (GMT-05:00)

Hi Valeriia,

The issue is that the ticket cannot sit idle in the queue 🙁

Usually once a feature request has been made and the customer is informed that this request has been made then there really isn't anything else that we as support can do but to inform of the request.

Thanks,
Shane

#562137

Hi Valeria

I was trying to solve the same problem, what worked for me was instead of:

input[type=radio] {display:none !important;}

enter

input[type=radio] {visibility:hidden;}

Hope it works for you too.

Cheers,
Jason

Viewing 13 posts - 1 through 13 (of 13 total)

You are not logged in. You can view support threads, but not post.
If you are already logged in, please refresh your browser.

Known issues and their solutions

We document known issues and their solutions in Toolset erratas. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.

Support Policy

Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.

Please make sure to issue only one topic per each support ticket.

For more information, read our full Customer Support Policy.

Need custom programming work for your site? Check out our certified partners.