using the right technology at the right time
Here’s a little tip to keep anyone in your organization using Google Analytics from accidentally reloading your ColdFusion on Wheels application in the wrong environment.
I was trying to add file uploading to my Wheels + Railo application. But I kept getting this error message when trying to use <cffile action="upload">:
Form field [asset[file]] doesn’t exist or has no content
After a couple hours of beating my head against the wall, I realized that I didn’t set enctype="multipart/form-data" on the form tag.
Fortunately, this is a fairly simple fix using the Wheels startFormTag() form helper and its multipart argument.
Russ Johnson reported a bug with my ColdFISH on Wheels plugin. The bug affected the formattedCode() function’s wrapperElement and wrapperClass arguments, which were being ignored accidentally.
I finally squashed the bug tonight in version 0.7 of the plugin. Be sure to download the new version if you’re planning on using the plugin in your application.
I’ll be presenting about migrating existing applications to the ColdFusion on Wheels framework tomorrow night, February 10, on the Online ColdFusion Meetup.
I’ve been working on a plan for migrating a Fusebox application to Wheels, and it’s been a pretty challenging task to think through it all. I don’t care what framework or platform you’re migrating to. It’s not easy. It’s much easier to start anew, but most of us do not have that leisure.
Every now and then, someone asks how to build an admin section into their ColdFusion on Wheels application. If they want for it to be in an admin folder, does that mean that you can only have an admin controller that stores everything needed?
Fortunately, one approach allows for you to split your admin section up into as many controllers as you need using inheritance and a feature called routes. Let’s discuss how.
I spent some time last night making some security updates to the PluginManager plugin and making sure that all of the plugins that I’ve submitted to cfwheels.org are compatible with the newly released ColdFusion on Wheels 1.1.
Read on for links to the plugins and descriptions that I entered in their change logs:
I was excited to finally take some time to add the ability for people to upload screenshots in the ColdFusion on Wheels Site Directory when I ran into a big problem. When I started sending large screenshots to ColdFusion’s ImageScaleToWidth(), it would take 30+ seconds to do the processing. Unacceptable.
Read on to see how I ended up tackling this problem with <cfthread>
Just over a year ago, I blogged about my implementation of the RSS aggregator for cfwheels.org using Yahoo! Pipes, FeedBurner, <cffeed>, and Wheels partials. Now that ColdFusion on Wheels version 1.1 is in beta (and almost complete), there is a new piece of functionality involving partials that makes my solution simpler.
Read on to learn more about automatic data functions for partials in Wheels and how it helped simplify my application.
Another small enhancement added to the upcoming ColdFusion on Wheels 1.1 (now in beta). You can now add messages to the Flash from redirectTo() instead of needing to call flashInsert() separately.
Less code FTW! Read on for an example.
The upcoming ColdFusion on Wheels 1.1 (now in beta) offers a new setting called assetQueryString that can help you more easily manage caching on the client side for assets like images, stylesheets, and JavaScript includes.
Read on for more information about the new setting and the problem that it helps solve.
About MeI'm Chris Peters, and I'm a lover of web design and development. I'm based in Columbus, Ohio. Follow me as I have successes and struggles in this fast-moving technology environment.
