Ah, disregard my previous e-mail -- found you also need to update <cfapplication name=""...>. Cool... workee now. Thanks.
Well, you are partially correct. Yes you fixed it by renaming the application name (which is good habit), but thats not what was needed to fix it.
Many of the application variables in Farcry are only set once (on the first page load). Then a conditional statement checks to verify that they are set. If yes, they are not set again (to help save on system resources).
Because you changed the values of some of these application variables you would need to either restart CF services or wipe the application variables manually (using StructDelete();).
Instead, you renamed the application name all-together. Thus when the conditional statement checks for their existance it would see that they did not exist (under the new application name) and Farcry would recreate them.
Don't get me wrong. What you did (renaming the application name) wasn't incorrect (its best to keep the names consitant throughout you app for other developers) it just wasn't required to fix your issue (it wasn't required in order for Farcry to function correctly. You can name the application name anything you like... as long as its not the same as another application name for another website).
Regards,
Jeff C.
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
