Mike Benner
Hmmm, need something catchy for here...
When Is A Fork Not A Fork?
Jan 29 by Michael Benner
When it is a straight path with no branches. I know, that makes about as much sense as telling IIS that root path is X and Coldfusion that the root path is Y. What is worse X = Y, except when it doesn't...
Good, I think you are now officially as lost as I was earlier when trying to move my Coldbox site to a domain name on
a multi site IIS server.
I had Coldbox setup and running perfect on this machine. It was going as well as you'd expect so then I decide to roll a domain name over and that is when the error messages began. After an hour or so of experimentation I headed over to the forums @ coldboxframework.com and asked for help. Luis suggested a few things and then Sana jumped in and we worked for at least an hour on this thing. We all knew it HAD to be mapping issues, but where and how?
Well, after walking away I came back to it and noticed that there was one thing I did not try. I removed the default root mapping from CF 8. Suddenly the rest of the sites on that server died, but my new Coldbox site was running.
So, after scrambling to fix the mappings on my other sites in Beta, I sat to think about why this happened. From what I can tell, IIS whenever you setup a new site, makes that site's folder the root for that domain. Coldfusion mapping, however, is global to ALL sites using CF. This leads to the confusion you experienced earlier and that Coldbox experienced. It has two directions that were the same in nature but very different in instruction and simply couldn't find what it needed.
So, the morale of this brain teaser of a day, NEVER EVER use a generic root mapping for convenience, always, removed that mapping and be specific.
Sana and Luis, thank you for the time you spent with me on this issue. It is the (usual) ease of Coldbox and support from dedicated guys like you that make this the best framework in my book.
There are no comments for this entry.
[Add Comment]