Be the first to post a text review of xacting form validation service. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Code committed

  imagic01 committed patchset 2 of module xfvs-dev to the xacting form validation service CVS repository, changing 42 files

  posted by imagic01 2557 days ago

• Code committed

  imagic01 committed patchset 1 of module xfvs-dev to the xacting form validation service CVS repository, changing 42 files

  posted by imagic01 2557 days ago

• Released: v 0.0.4

  First public release. working software. Required ColdFusion 5.0 build on windows 2k

  posted by imagic01 2604 days ago

• File released: /xvfs-dev/xfvs-0.0.4a/xfvs_0.0.4.zip

  posted 2604 days ago

• Initializing project site

  While I upload all the stuff and get comfortable in my new home, please refer to project page at xacting.com http://www.xacting.com/developers/projects/xfvs/

  posted by imagic01 2604 days ago

• xvfs-dev xfvs-0.0.4a file released: xfvs_0.0.4.zip

  CHANGE LOG --------------------------------------- AUTHOR: Sean Brown <sbrown@xacting.com> CONTRIBUTORS: VERSION HISTORY: ----- 0.0.4a ----- implemented wddx postback including hooks for multiple postback package formats. includes ability support Javascript disabled clients with flag xfvs_postBackSupportNoJS flipped to "Yes". updated tests and moved docs into a docs/ folder implemented mailto.basic dispatch method with predictable input, application now can, verify clients licensing, validate forms (including conditional checks, and format checks), postback errors to client for display (see complete_form.cfm for elaborate working example), dispatch a form for fulfillment, use mailto.basic to foward on the data. yippe!! incrementing to 0.0.4a [18hrs to date] ----- 0.0.3a ----- - smb - moved the UDFs out of Application.cfm and into app_udfs.cfm partially due to this tip on evolt.org <tip type="ColdFusion Optimization" author="rory"> If you are making a UDF (User Defined Function or Custom Function) and need to employ it in a number of your templates, you read to documentation to discover that you should put it in the Application.cfm tag. However, this causes multithreading issues, and to use it, you should, really and honestly, cflock the bugger. To avoid this bit of tedium and performance hit, try putting the UDFs in a "library file" and cfincluding that in the Application.cfm file. Since the server stays in a multi-threaded condition, the performance is increased and, more importantly, cflocks no longer grow like the pestilent weed in your carefully cultivated code. </tip> fixed bug in ValidateConditionalRequirements - wasn't accurately checking for the *value* of the related field. fixed bug in xfvs - wasn't calling setVariableDefaults before call to ValidateConditionalRequirements added udf: print(s) a short-hand for writeOutput. added hook for multiple fullfilment dispatchers (optional param xfvs_dispatchMethod) future versions can add in support for db storage, textfile storage etc.. ----- 0.0.1a ----- - smb - basic framework established. licensing scheme and security architecture implemented, test cases started (as pre-configures forms in tests/) README, DEVELOPERS, CHANGELOG seeded, gen_key, crack_key working for generating a valid license key based on client,clientUrl,version and displaying the contents of a given key, bannedKeys established as a struct in Application scope, customTags to handle displaying error messages, logging errors to a textfile, and validating conditional requirements, basis for dynamic field format validation inplace (currently includes functions for validating email, safeText, safeHtml, CreditCard Numbers and US ZipCodes, begining of the public API inplemented and documented in complete_form.cfm and xfvs.cfm, correctly validates basic required fields, and conditional requirements (doesn't postBack yet, just objectDumps out the Request scope to verify), began custom error handling scheme with the wddx exception handling in and around CF_ValidateConditionalRequirments. lots of progress incrementing version to 0.0.3a

  posted 2604 days ago

• xfvs-stable xfvs-0.0.4 file released: xfvs_0.0.4.zip

  CHANGE LOG --------------------------------------- AUTHOR: Sean Brown <sbrown@xacting.com> CONTRIBUTORS: VERSION HISTORY: ----- 0.0.4a ----- implemented wddx postback including hooks for multiple postback package formats. includes ability support Javascript disabled clients with flag xfvs_postBackSupportNoJS flipped to "Yes". updated tests and moved docs into a docs/ folder implemented mailto.basic dispatch method with predictable input, application now can, verify clients licensing, validate forms (including conditional checks, and format checks), postback errors to client for display (see complete_form.cfm for elaborate working example), dispatch a form for fulfillment, use mailto.basic to foward on the data. yippe!! incrementing to 0.0.4a [18hrs to date] ----- 0.0.3a ----- - smb - moved the UDFs out of Application.cfm and into app_udfs.cfm partially due to this tip on evolt.org <tip type="ColdFusion Optimization" author="rory"> If you are making a UDF (User Defined Function or Custom Function) and need to employ it in a number of your templates, you read to documentation to discover that you should put it in the Application.cfm tag. However, this causes multithreading issues, and to use it, you should, really and honestly, cflock the bugger. To avoid this bit of tedium and performance hit, try putting the UDFs in a "library file" and cfincluding that in the Application.cfm file. Since the server stays in a multi-threaded condition, the performance is increased and, more importantly, cflocks no longer grow like the pestilent weed in your carefully cultivated code. </tip> fixed bug in ValidateConditionalRequirements - wasn't accurately checking for the *value* of the related field. fixed bug in xfvs - wasn't calling setVariableDefaults before call to ValidateConditionalRequirements added udf: print(s) a short-hand for writeOutput. added hook for multiple fullfilment dispatchers (optional param xfvs_dispatchMethod) future versions can add in support for db storage, textfile storage etc.. ----- 0.0.1a ----- - smb - basic framework established. licensing scheme and security architecture implemented, test cases started (as pre-configures forms in tests/) README, DEVELOPERS, CHANGELOG seeded, gen_key, crack_key working for generating a valid license key based on client,clientUrl,version and displaying the contents of a given key, bannedKeys established as a struct in Application scope, customTags to handle displaying error messages, logging errors to a textfile, and validating conditional requirements, basis for dynamic field format validation inplace (currently includes functions for validating email, safeText, safeHtml, CreditCard Numbers and US ZipCodes, begining of the public API inplemented and documented in complete_form.cfm and xfvs.cfm, correctly validates basic required fields, and conditional requirements (doesn't postBack yet, just objectDumps out the Request scope to verify), began custom error handling scheme with the wddx exception handling in and around CF_ValidateConditionalRequirments. lots of progress incrementing version to 0.0.3a

  posted 2604 days ago

• Code committed

  Anonymous committed patchset 1 of module CVSROOT to the xacting form validation service CVS repository, changing 11 files

  posted by nobody 2605 days ago

• Forum thread added

  Anonymous created the Welcome to Open Discussion forum thread

  posted by nobody 2605 days ago

• Forum thread added

  Anonymous created the Welcome to Developers forum thread

  posted by nobody 2605 days ago