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.
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.
The fields.xml has the base as delivered which I have kept for reference and my entry at the very top. I am including it as an attachment since the word filter catches some of what the base includes.
Hmm, it did work for me - I submitted and got an 'Entry too long' error when I put 5 digits into the field. Maybe the 'xml_fields' addon is not installed?
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.
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.
Pretty much. Look at the URLs present, can't remember off-hand what it is, but it is whatever type= is set to in the URL (or if short URLs are on, it's part of the path).
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.
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.
<qualify pages="cms_catalogues" types="ad,_ad,_edit_entry,edit_entry" fields="field_45"> <minLength error="Entry too short">3</minLength> <maxLength error="Entry too long">4</maxLength> <possibilitySet error="Year too early or too late!">1930,1931,1932,1933,1934,1935,1936,1937,1938,1939,1940,1941,1942,1943,1944,1945,1946,1947,1948,1949,1950,1951,1952,1953,1954,1955,1956,1957,1958,1959,1960,1961,1962,1963,1964,1965,1966,1967,1968,1969,1970,1971,1972,1973,1974,1975,1976,1977,1978,1979,1980,1981,1982,1983,1984,1985,1986,1987,1988,1989,1990,1991,1992,1993,1994,1995,1996,1997,1998,1999,2000</possibilitySet> </qualify>
It works properly when adding an item however when editing the item, it does not validate the number on save. If I select "Edit this" immediately after, I do get an error message. I don't get any error message if I select "Edit one".
Also, I seem to always get the possibilitySet error message even if the year is too short. How is precedence handled? Should I put the possibiltySet first?
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.
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.
I made the change you suggested to the qualify in fields.xml but the error described above continues:
It works properly when adding an item however when editing the item, it does not validate the number on save. If I select "Edit this" immediately after, I do get an error message. I don't get any error message if I select "Edit one"
I get no error message when editing the year to 196 but do get the error when I use the "Edit this" immediately afterwards.
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.
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.
Well, I realized this is not going to work because one of the potential answers is "Unknown" which means I need to change this from a numeric field to a text field with no Comcode cupport. My problem now is that the year is padded by leading 0s and displayed that way.
Shouldn't a text field be displayed as it is entered?
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.
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.
The problem with this is that these fields are entered by members and I'd prefer not to validate each entry because I want the results immediately available.
