<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/cfcheckform/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/cfcheckform/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 27 Sep 2001 12:26:32 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/cfcheckform/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>bug in CheckMask function</title><link>https://sourceforge.net/p/cfcheckform/bugs/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;If you are using custom error messages, the mask test &lt;br /&gt;
never returns an error.&lt;/p&gt;
&lt;p&gt;need to set the error variable to true (error = true;) &lt;br /&gt;
if the mask.test statement (line 118 of &lt;br /&gt;
CheckMask_Javascript.cfm) returns false.  The current &lt;br /&gt;
error=true statement is currently only set when &lt;br /&gt;
message_type is not custom - see line 126.&lt;/p&gt;
&lt;p&gt;Looks like the error = true; statement should be below &lt;br /&gt;
the '}' on the line below!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 27 Sep 2001 12:26:32 -0000</pubDate><guid>https://sourceforge.net1af2b54fcd0f023990df44bf6c18421ca305fb15</guid></item><item><title>JS Error when submitting radio buttons.</title><link>https://sourceforge.net/p/cfcheckform/bugs/12/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The script returns an error stating that 'type is not &lt;br /&gt;
an object' apparently coming from &lt;br /&gt;
the &amp;amp;quot;CheckRequired_javascript.cfm&amp;amp;quot; page when radio &lt;br /&gt;
buttons are used and validated with CF_CheckForm.&lt;/p&gt;
&lt;p&gt;This problem only arises when used with the javascript &lt;br /&gt;
validation.  The server side validation in Cold Fusion &lt;br /&gt;
works just fine.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Trevor Wise</dc:creator><pubDate>Mon, 02 Jul 2001 20:06:58 -0000</pubDate><guid>https://sourceforge.net0c00bebcff16be62b3f9b450ef0ea3eac7582541</guid></item><item><title>Even easier to user engine</title><link>https://sourceforge.net/p/cfcheckform/bugs/11/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Alright, thinking a little further on the idea of using&lt;br /&gt;
structures (to replace the need to remember that [0] &lt;br /&gt;
is for the field name and [1] is the description and&lt;br /&gt;
[...]),  I've come up with an idea that John had once&lt;br /&gt;
mentionned to me.  Make use of nested custom tag.&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;CF_CheckForm_FORM name=&amp;amp;quot;...&amp;amp;quot; method=&amp;amp;quot;...&amp;amp;quot; ...&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;CF_CheckForm_INPUT name=&amp;amp;quot;...&amp;amp;quot; .../&amp;amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;amp;lt;/CF_CheckForm_FORM&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;When the page is processed and get to CF_CheckForm_FORM&lt;br /&gt;
it would check for a validation=&amp;amp;quot;yes&amp;amp;quot; attribute. If it&lt;br /&gt;
finds one then it creates a javascript function to&lt;br /&gt;
validate this form.  It would also initialize arrays&lt;br /&gt;
of structures for all the validation methods.&lt;/p&gt;
&lt;p&gt;When it executes a form field type tag such as &lt;br /&gt;
CF_CheckForm_INPUT it would store the tag's attribute&lt;br /&gt;
into the appropriate array/structure.&lt;/p&gt;
&lt;p&gt;When the end tag for the custom tag form is executed&lt;br /&gt;
it would output all the relevant information (arrays&lt;br /&gt;
into the javascript validation method for that form)&lt;br /&gt;
into the javascript section of the page head tag.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric André Gravel</dc:creator><pubDate>Wed, 28 Mar 2001 15:08:40 -0000</pubDate><guid>https://sourceforge.netbb2d2cb934031f1695579f7b84f2dac13768c828</guid></item><item><title>Simplified Data Array</title><link>https://sourceforge.net/p/cfcheckform/bugs/10/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be simpler for developers to code the tag's &lt;br /&gt;
definition data array using structures instead of &lt;br /&gt;
array index ro represent a field name or a error &lt;br /&gt;
message type.&lt;/p&gt;
&lt;p&gt;IE:&lt;/p&gt;
&lt;p&gt;StructInsert( requiredCheck, &amp;amp;quot;fieldType&amp;amp;quot;, &amp;amp;quot;text&amp;amp;quot; );&lt;/p&gt;
&lt;p&gt;is easier to code then&lt;/p&gt;
&lt;p&gt;requiredCheck[i][3] = &amp;amp;quot;text&amp;amp;quot;;&lt;/p&gt;
&lt;p&gt;It's easier in the sense that you know what that array &lt;br /&gt;
element is for and it allows you to insert any new &lt;br /&gt;
fields without worrying how it'll look at that &lt;br /&gt;
position.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric André Gravel</dc:creator><pubDate>Tue, 27 Mar 2001 15:00:30 -0000</pubDate><guid>https://sourceforge.net71c6d822063aec29549b28de8ffb38f31b6e6ecb</guid></item><item><title>Too many array parameters too pass to CheckForm()</title><link>https://sourceforge.net/p/cfcheckform/bugs/9/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;For each validation routine you add you also add a new parameter to the CheckForm() list of in parameters.  You might not use all of them so it would preferable to provide the means to give only the arrays you need checked and it figures out which ones to call.&lt;/p&gt;
&lt;p&gt;To do this we would have an in parameter that contains all the arrays in a 2 dimension array.  Dimension 1 would be the array name expected by CheckForm and the second dimension would be the array that would end up being passed to the validation routine.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric André Gravel</dc:creator><pubDate>Fri, 23 Feb 2001 14:53:10 -0000</pubDate><guid>https://sourceforge.netcb311051f6683b9d39a320cd1e5a04c722569e51</guid></item><item><title>Minimum Value Length Check</title><link>https://sourceforge.net/p/cfcheckform/bugs/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Had a validation for minimum value checks.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric André Gravel</dc:creator><pubDate>Wed, 14 Feb 2001 20:25:42 -0000</pubDate><guid>https://sourceforge.netf2f2220946a88ad26681896ef6c1e15477922268</guid></item><item><title>note potential problems with mixed-case form field names</title><link>https://sourceforge.net/p/cfcheckform/bugs/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I discovered that I had problems getting length and checkbox validation to work in Netscape 4.6 until I converted my form field names to all lowercase instead of mixed case.  I am not sure why this was a problem, but I know that WDDX converts variable names to all lower-case when deserializing to JavaScript because ColdFusion is case-insensitive, so it may be the culprit (but then I would expect it to show up in Netscape 6 and IE5 as well, which wasn't the case).  You might want to make note of it in the docs.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 31 Jan 2001 18:59:37 -0000</pubDate><guid>https://sourceforge.netcd2a616f1be6c28cd208f0f6ed8b028916923a60</guid></item><item><title>typo in variable name causes error</title><link>https://sourceforge.net/p/cfcheckform/bugs/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;CheckLength_coldfusion.cfm: line 72, changed Required -&amp;amp;gt; Length&lt;br /&gt;
(it looks like this is just a typo; it caused an error until I fixed it)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 31 Jan 2001 18:58:18 -0000</pubDate><guid>https://sourceforge.net9a889160174e56190ecb9124a978cd6b039e39a7</guid></item><item><title>add words &amp;quot;at least&amp;quot; to clarify meaning of error message</title><link>https://sourceforge.net/p/cfcheckform/bugs/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;CheckForm_lang_EN.cfm: line 153, add &amp;amp;quot;At least&amp;amp;quot; because it is possible to check more than the minimum number of checkboxes.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 31 Jan 2001 18:54:52 -0000</pubDate><guid>https://sourceforge.net05f227e6a98a52539f9ea6a17e36cf159c222653</guid></item><item><title>change &amp;quot;then&amp;quot; to &amp;quot;than&amp;quot;</title><link>https://sourceforge.net/p/cfcheckform/bugs/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The proper word in a few sentences in the english version is &amp;amp;quot;than&amp;amp;quot; (meaning &amp;amp;quot;in comparison with&amp;amp;quot;) instead of &amp;amp;quot;then&amp;amp;quot; (meaning &amp;amp;quot;at that time&amp;amp;quot;)&lt;/p&gt;
&lt;p&gt;CheckForm_lang_EN.cfm: line 172, then -&amp;amp;gt; than&lt;br /&gt;
CheckForm_lang_EN.cfm: line 69, then -&amp;amp;gt; than&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 31 Jan 2001 18:45:48 -0000</pubDate><guid>https://sourceforge.netce48c823f57debda430e37c7ba3ecd1c29e05ca3</guid></item></channel></rss>