Hi Dan,

I think it will help if you provide much more info as you are leaving us too 
much to guess at.

1. Are your local and staging development environments the same? Same drives, 
mappings, etc?
2. Are did you run the development site through cf_2cfmodule before deploying 
to your staging server?



I would be the error is caused from something in the login form and the ValidateInput tag can't swallow it. Since the login form is tied to the PlumUser table via the Security.cfc, maybe it has something to do with the mods you have made to the PlumUser table over the past couple days.


v/r,

Jeff

Dan wrote:
A follow up to my prior post/question/problem

On my staging server I opened the custom tag ValidateInput.cfm and added /> to the unpaired CFCASE tag:

<cfcase value="integer" />

Now when running loginform.cfm I get this error. It must have something to do with a difference in my staging server environment than my dev server. The same files do not produce an error here.

What information do I need to gather to help my find the cause and solution for this problem?


  *Context validation error for tag cfswitch. *

        

The start tag must have a matching end tag. An explicit end tag can be provided by adding </cfswitch>. If the body of the tag is empty you can use the shortcut <cfswitch .../>.

        

The error occurred in *C:\websites\bccdev\customtags\ValidateInput.cfm: line 67*

65 :
66 :           <!--- Perform validation of type --->

*67 :           <cfswitch 
expression="#ListFirst(Application.Formatting.GetDataType(Attributes.validationType), 
'(),')#">*

68 :
69 :                   <!--- Numeric --->

Thanks,

Dan Kaufman

//An Elephant Never Forgets//

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>


**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:

http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************

Reply via email to