So Adobe caught wind of my troubles and went out of their way to contact me (through e-mail and on the phone) to try and fix the issues I was having. There were a few times when I think we were both gonna lose it (to be honest I’m just glad the same problems I had been having were arising for him), but after 75 arduous minutes, we were able to establish that ColdFusion 10 did in fact install (I knew this), indeed it was working (that was a revelation to me), but was not configuring IIS correctly with a previous iteration of ColdFusion having been on the server (CF9 in this case).
In my particular case (of both my win2008r2 servers), CF10 did in fact install, but did NOT update the mappings in IIS. The key to my sites not working lied within the IIS Handler Mappings. When installing CF10, none of the handler mappings were changed to CF10, it retained the old CF9 handler mappings. This is both when I installed CF10 with CF9 already on the server and when I had removed CF9 from the server before installing CF10, in which the CF9 uninstall did not remove the IIS mappings (you get all that? lol). Also worth noting is ColdFusion now uses ports on the 8007 and 8012… ports on my development server that were being used (each site in IIS had it’s own port to make it unique for development on the 8000 block of ports… I moved my stuff to the 8100 block). Bear in mind that if you have a lot of sites (and I have like 20+ on each server), that changing all these mappings is a VERY time consuming and tedious process. I had fixed IIS to the point it would render ColdFusion, but that was it (couldn’t render PHP or even basic HTML anymore). Seeing no easy way to fix everything in a timely manner after tearing IIS apart with Adobe to find problems, I concluded a fresh reinstall of Win2008r2 was a better route to take (I tried removing and re-adding the IIS server role, but even that was gonna take some internal work to completely reset… bleh… reinstall). Read more
Before we get into the tags, I’d first like to mention I firmly believe SES URLs need to somehow make their way into ColdFusion. The root of ColdFusion is making development life simple, and there is nothing simple about setting up SES URLs, particularly if you don’t know regular expressions. I think this should be enabled/disabled at the application scope level and be a well thought out, simple process that doesn’t require IIS or Apache URL rewriting… it’s all done seamlessly in CFX.
With that said, here are some new tags I’d like to see:
- CFTRAIL – This will leave a breadcrumb trail. I initially thought this would be a feature that would require the use of SES URLs in the application scope, but thinking further, I think it could still be done with the developer providing parameters.
- CFBROWSER – Web browser detection baby!
And while we’re at it lets add some parameters to CFLOCATION to allow delayed cflocating:
<CFLOCATION from="now()" delay="dd:hh:mm:ss" />
Lets also add a parameter to CFDIV to allow that loading icon to be customized:
<CFDIV icon="/images/yourAnimatedIcon.gif" />
This being ideal for loading user custom-created pages from a database, I think one of the features I would use the most is the ability to loop over cfcase in a cfswitch:
And finally some new functions I’d also like to see:
dollarformat() – oops! Already exists.
Coming next week
CFX: Feature Requests Part 3 – Everything Else
Even though I was unable to attend, Max 2011 produced some good things in the way of announcements for ColdFusion 10 (I like CFX better). Most of what was announced though seemed like obvious steps forward of things that needed to be addressed, and not necessarily features that will make you jump out of your seat to line up and buy the product the second it’s released. And I don’t really want to cover these features which can be easily found via Google.
Seeing as I’m not part of the alpha/beta of Zeus, what I do want to cover are some things that I believe would make CFX the product that would make you get in line and a product you can’t live without.
Today’s software and programming world is plagued with modularization. It is no longer just the language that is chosen for a project, but also the framework on which it’s built.
I am an anti-framework guy. I honestly don’t get the buzz or see the benefit. Inheriting someone else’s mistakes and relying on them because I’m too lazy to code the features myself isn’t a blessing for me or any of my clients. It may save time to slap together a site in a few minutes, but does it really save time in the long run (and then have to keep that framework up-to-date… no thanks)? Having jumped from framework to framework I’ve become a naysayer. However, for the world of framework-lovers and the fact that ColdFusion is for everyone, lets modularize: Read more