The cfide has caused so many security issues that it is best to simply avoid using it all and do not even have it in your site. The other issue is that you are reliant on this virtual dir. I have seen many customers who were oblivious to this requirement when they moved their hosting and as a result all their form validation on their site was broken since day 1. I have seen customers run for years like this and ended up forms being used for spam and websites defaced as a result.
The results ptoduced by cfform are also generally considered poor and bloated. It is best to use code and libraries that are part of your site and can be easily updated. Russ Michaels www.michaels.me.uk cfmldeveloper.com cflive.net cfsearch.com On 4 Mar 2014 09:06, "Mike K" <afpwebwo...@gmail.com> wrote: > > Gerald, I used to use CFFORM, and it quickly got outdated as HTML and CSS > and Javascript and jquery moved on. These days HTML5 is the go with > CSS3. CFFORM doesnt produce those. Therefore things like client side > validation, placeholder text, cross-browser issues, mobile devices are > all possible but much more difficult to allow for with CFFORM than with the > newer HTML5/CSS3 approach. Those new features are all built in with > the new HTML5/CSS3 approach. > > Believe me, you'll get a much better result if you go to the trouble of > converting to HTML/CSS3. You will have more control over the displayed > result, you'll have better client-side scripting with inbuilt html > features and jquery and the resulting form on a mobile device will be a > far better product. > > As I said, I used to use CFFORM and at the time, it seemed like the bees > knees. But now it just seems SOO old fashioned. > > I inherited a site that had CFFORM and the java applets all over it (CFGRID > etc) and it pretty soon showed that it was a nightmare to do updates on, > and as more and more of our users wanted to use devices that didnt have > flash and java on them, we got more and more problems. It soon proved > that we needed to change to a pure HTML/CSS3/jquery approach for all > client-side stuff, leaving ColdFusion to handle the backend server-side > stuff, which is where CFML really struts its stuff and knocks everything > else out of the park. (Sorry about the mixed metaphor!) > > Cheers > Mike Kear > Windsor, NSW, Australia > Adobe Certified Advanced ColdFusion Developer > AFP Webworks > http://afpwebworks.com > ColdFusion Enterprise, PHP, ASP, ASP.NET hosting from AUD$15/month > > > On Tue, Mar 4, 2014 at 5:26 PM, Wil Genovese <jugg...@trunkful.com> wrote: > > > > > There is always better ways to do things than using the client side CF > > code. I have not looked at the output of CFFORM JavaScript in ages, but > if > > it has not been updated at all there's a good chance it's not fully > > compatible with today's browsers. > > > > There are also form validation frameworks. One that I know of is > > ValidateThis http://www.validatethis.org/ I'm not sure if this will > work > > in your case. It's worth at least looking into it. > > > > There are options and most will be better than CFFORM. > > > > Regards, > > > > > > Wil Genovese > > Sr. Web Application Developer/ > > Systems Administrator > > CF Webtools > > www.cfwebtools.com > > > > wilg...@trunkful.com > > www.trunkful. > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:357830 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
