This method does work. However, I am not sure why it doesn't work as designed out of the box.  This worked fine under CF5 and is supposed to work the same way under CFMX.  We should not have to move those files under the web root. Also, I still have the issue with GetCurrentTemplatePath() including the path above the symbolic link.  Did MX change the way it interprets symbolic links?  This is a huge problem for our architecture.  We were expecting code changes to convert from CF5 to CFMX like named parameters on stored procs, but not things dealing with path information.

Thanks in advance.

>I added this to my site (www.actcfug.com) back in September. Hope it
>assists.
>
>>>
>
>My CFFORM are creating JS errors at the browser level in a ColdFusion MX
>hosted environment. Why?
>Thursday, 18 September, 2003
>
>In a dedicated or hosted ColdFusion environment you will more often than
>not, for security reasons, find that your host has "moved" some crucial
>folders required by MX from an area directly accessible from your own web
>root.
>
>There are many valid reasons for doing this - but a key side-affect is that
>whenever you use the CFMX built-in form validation of the CFFORM tag - your
>page will produce JS errors because the location CF expects the crucial
>_javascript_ libraries is no longer accessible.
>
>Under CFMX the "scriptsrc" tag is a new feature added to the CFFORM tag, for
>example:
>
><cfform scriptsrc="lib/cfform.js" name="MembersLogin"
>action=""> >
>But I just discovered an easier way that will allow you to continue to
>freely use the CFFORM functions of field validation WITHOUT having to -
>unless extreme circumstances - use it as we did with CF5 and earlier. I ran
>into this problem with a rather large application (over 5Mb compressed)
>called "FuseTalk" (http://www.fusetalk.com) but fixed the problem by doing
>the following:
>
>1. In your "wwwroot\mysite\" folder create a folder called "cfide".
>
>You should now have, say a c:\inetpub\wwwroot\cfide\ folder.
>
>2. As a sub directory in this folder create a folder called "scripts".
>
>You should now have, say a c:\inetpub\wwwroot\cfide\scripts\ folder.
>
>3. Copy the two key .js files that CFMX already puts in the
>wwwroot\cfide\scripts folder and copy them up to your current
>development/production site. Copy ONLY those two files.
>
>Your own "cfforms" should now work as intended by Macromedia - and FuseTalk
>also without have to finde/replace any instance of CFFORM and add the
>SCRIPTSRC attribute. I'm sure MANY FuseTalk templates use the CFFORM tag so
>this is the best way to make sure ALL of your apps, not just FuseTalk, will
>work with no more form validation/_javascript_ errors.
>
>My next step is to put my own scripts in the same folder -
>wwwroot\mysite\cfide\scripts\ and see what happens.
>
>NOTE: Linux/Unix users may need to retain CASE for folder names. CFIDE is
>uppercase but the SCRIPTS and script filenames are lowercase.
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to