View topic: Validating a year field

To	× pt	For
temp1024	80	Sup…
curtisbrew	50	Hel…
Fletch	500	Sup…
Fletch	100	The…
Duck	200	Pro…
Fletch	100	The…
Chris Graham	100	Hel…
Fletch	100	The…
Fletch	100	The…
Duck	100	Rea…

Rishi Saravanan	44,540
BobS	24,825
Fletch	24,348
Jean	19,312
amichan	16,801

Home » Forum home » Deploying » View topic

Login / Search

Posted 14 June 2011, 9:03 PM

Rating:

#70463 (In Topic #14908)

BobS

Community saint

I have a field in my Image Galleries catalog which I would like to validate to a 4-digit number start with "19" (ideally, I'd like to be able to specify a min year and max year). I saw the form-field filter tutorial but can't seem to make it work.

My URL is:

Code


http://xxxxxxxxx.com/cms/cms_catalogues/add_entry.htm?catalogue_name=image_galleries&category_id=18&keep_session=4715205&redirect=http%3A%3Aslash%3A%3Aslash%3Axxxxxxxxx.com%3Aslash%3Acatalogues%3Aslash%3Acategory%3Aslash%3Aimage-gallery%3Aslash%3Aportraits.htm%3Fcatalogue%3Dimage_gallery%3Aamp%3Akeep_session%3D4715205xxxxxxxxx

I tried creating a form-field filter in /data_custom/fields.xml as follows:

Code


<qualify pages="cms_catalogues" types="add" fields="Year painted">
      <minLength error="Entry too short">4</minLength>
      <maxLength error="Entry too long">4</maxLength>
   <!--   <possibilitySet error="Incorrect year">xxxx</possibilitySet>  -->
   </qualify>

Am I even close to getting this to work? Also, what would I use for the possibilitySet to make sure I get a year starting with "19" and containing all numbers?

Thanks for any help.

Bob

Posted 15 June 2011, 10:48 AM

Rating:

#70488

Chris Graham

ocStaff (admin)

<qualify pages="cms_catalogues" types="ad,_ad" fields="field_14">
       <minLength error="Entry too short">4</minLength>
       <maxLength error="Entry too long">4</maxLength>
    </qualify>

The possibilitySet value list would have to be 100 items long to work for what you wanted, we don't have support for any kind of regular expresion/wildcards here. For it to be a number, just make it a numeric field.

Become a fan of ocPortal on Facebook or add me as a friend.

Was I helpful?

If not, please let us know how we can do better (please make suggestions that are economically viable and scalable, not just requests to do more for free).
If so, please let others know about ocPortal whenever you see the opportunity.

Follow me on Twitter

This information has not loaded yet. It will be generated in the background, please come back later.

If I answered something that you think should be in the documentation, please take the initiative and add it to the community documentation. We really need people to help out here and build a well-organised large support resource.

Posted 15 June 2011, 5:53 PM

Rating:

#70510

BobS

Community saint

Thanks, Chris.

Silly that I didn't make the year an integer value since I had changed another field to to be a dropdown menu.

How much overhead is there in processing a possibilitySet with 90 to 100 entries?

Bob

Posted 15 June 2011, 6:02 PM

Rating:

#70511

Chris Graham

ocStaff (admin)

No immediate answer comes to mind, sorry

Become a fan of ocPortal on Facebook or add me as a friend.

Was I helpful?

If not, please let us know how we can do better (please make suggestions that are economically viable and scalable, not just requests to do more for free).
If so, please let others know about ocPortal whenever you see the opportunity.

Follow me on Twitter

This information has not loaded yet. It will be generated in the background, please come back later.

Posted 15 June 2011, 6:13 PM

Rating:

#70512

BobS

Community saint

I'll just give it a try and see what happens. Since it is only an issue when entering new catalog entries, it won't matter too much if it takes a bit longer. I just want to make sure that people don't accidentally turn a 20th century painter into an Old World master.

Thanks for your help.

Posted 16 June 2011, 12:11 AM

Rating:

#70556

temp1024

Community saint

Chris, how about adding a "fieldsAsInt" type attribute on the qualify tag as a simple fix.

That should be a trivial enhancement that can force type conversion where explicitly specified while maintaining comparability with existing xml filters.

Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .

Posted 16 June 2011, 12:27 AM

Rating:

#70559

BobS

Community saint

<qualify pages="cms_catalogues" types="ad,_ad" fields="field_14">
         <minLength error="Entry too short">4</minLength>
         <maxLength error="Entry too long">4</maxLength>
      </qualify>

Where do you find the field number? Is it only available when Short URLs is disabled?

Bob

Posted 16 June 2011, 12:41 AM

Rating:

#70561

temp1024

Community saint

Hover your mouse over the "edit this" link and you will see ".../_edit_entry/7" etc.

Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .

Posted 16 June 2011, 12:45 AM

Rating:

#70563

BobS

Community saint

But isn't that the catalog record id rather than the catalog field id?

Posted 16 June 2011, 1:05 AM

Rating:

#70564

temp1024

Community saint

Ah yes, sorry about that, miss read your question.

OK, the correct answer is: click on "edit this" and view the html of the edit page, and search for label for="field_ and that will take you directly to the fiend number and its name. Repeat search for each field as required.

Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .

Posted 16 June 2011, 1:35 AM

Rating:

#70565

BobS

Community saint

Thanks, temp. Now to try out by new field validation.

Bob

Posted 16 June 2011, 2:40 AM

Rating:

#70567

BobS

Community saint

I am getting the following error when trying to validate a field:

Code


fields.xml: not well-formed (invalid token)

This is the validation code which I copied from above, adjusting the field:

Code


<qualify pages="cms_catalogues" types="ad,_ad" fields="field_45">
      <minLength error="Entry too short>4</minLength>
      <maxLength error="Entry too long">4</maxLength>
   </qualify>

Can anyone point me in the right direction?

Thanks for any help.

Bob

Posted 16 June 2011, 2:54 AM

Rating:

#70568

temp1024

Community saint

Missing quotes.

Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .

Posted 16 June 2011, 3:12 AM

Rating:

#70569

BobS

Community saint

Thanks, temp.

Made that change and no longer getting the XML warning. But the field is still not validating.

Below is the relevant source from the catalog entry page:

Code


<td id="required__field_45" class="dottedborder_barrier_b_required">
      <div id="error_field_45" style="display: none" class="input_error_here"></div>
      
      
         <div class="accessibility_hidden"><label for="field_45">Year painted</label></div>
      
      
         <input type="hidden" name="label_for__field_45" value="Year painted" />

So "field_45 is correct but I was still able to enter a three-digit year.

Below is the corrected validation code:

Code


<qualify pages="cms_catalogues" types="ad,_ad" fields="field_45">
      <minLength error="Entry too short">4</minLength>
      <maxLength error="Entry too long">4</maxLength>
   </qualify>

Any thoughts?

Bob

Posted 16 June 2011, 3:43 AM

Rating:

#70573

temp1024

Community saint

I haven't looked at field validation before, but if I'm reading the xml as expected then I would have though you need to use a min/max lengths of 2 instead of 4.

Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .

Posted 16 June 2011, 3:50 AM

Rating:

#70575

BobS

Community saint

The field is "Year painted" so I would expect them to enter a 4-digit year (e.g., 1964).

At least, that's what I am trying to accomplish.

Bob

Posted 16 June 2011, 4:14 AM

Rating:

#70576

temp1024

Community saint

Of course. I read too way too much into your "Old World master" & "still able to enter a three-digit year" comments and though you were trying to restrict it to double digits.

It sounds like the its not even associating the xml to the right field. So while the field name make be correct, maybe its the page name. How did you determine the page name?

Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .

Posted 16 June 2011, 4:42 AM

Rating:

#70578

BobS

Community saint

temp1024 said

It sounds like the its not even associating the xml to the right field. So while the field name make be correct, maybe its the page name. How did you determine the page name?

Copied from Chris's first post in the thread. He seemed to be correcting my initial take on it.

Bob