Text Field Allowed Content not working - help!

6 posts by 2 authors in: Forums > CMS Builder
Last Post: October 26, 2010   (RSS)

I have CMS Builder version 2.05.
I have a text field set up for 'only allow characters' and the chars I am allowing are 1324567890.,
When I pull up the field when adding a new entry, I can enter all kinds of characters. Not just the 1234567890,.
I have tested all three options and can't seem to get it to work. Any trick to this?

Re: [dougdrury] Text Field Allowed Content not working - help!

By Damon - October 26, 2010

Hi Doug,

I tested this and it works for me.

Can you send in a 2nd level support request so I can take a look and try this out with your installation?

Here is the link:
https://www.interactivetools.com/support/email_support_form.php

Also, please indicate the section and field that to use.

Thanks!
Cheers,
Damon Edis - interactivetools.com

Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/

Re: [Damon] Text Field Allowed Content not working - help!

Damon,
Thank for the response. This installation is inside an Intranet, so you would not be able to get to it. Would you mind telling me what you entered in the fields for the 'allow only' to work? Did I miss a separate by comma requirement or something?

Thanks,
Doug

Re: [dougdrury] Text Field Allowed Content not working - help!

By Damon - October 26, 2010 - edited: October 26, 2010

Hi,

I used the same setting as you:

Set the Allow Content dropdown to "Only allow characters:"

And the characters entered are: 1234567890,.

[img]http://www.interactivetools.com/iforum/Products_C2/CMS_Builder_F35/Text_Field_Allowed_Content_not_working_-_help%21_P84179/gforum.cgi?do=post_attachment;postatt_id=3210;t=search_engine[/img]
Cheers,
Damon Edis - interactivetools.com

Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/

Re: [Damon] Text Field Allowed Content not working - help!

Shoot. That is what I have. I am testing in FireFox 3. Is it maybe a JavaScript Issue?