The other day, I was recoding some work that involved ColdFusion files being called using CFModule. I had gotten it to the point where the new code was in place, but was breaking. I had the old code stored as a .BAK file. I wanted to test to see if the new code was breaking or if the old code would have broken also, but I didn't want to rename any files to make this test happen. Just for fun, not so much thinking it would work, I tried to use the .BAK file directly into the CFModule tag as such:
- <!--- Run BAK file using CFModule. --->
Much to my delight, this ran without a problem. Not much of a tip, but I think this is useful when you are debugging code and you want to compare one set of code to a backed up set of code.
Moral of the store: just as with CFInclude, CFModule does not care about file extensions.
Looking For A New Job?
- Lead Programmer 7+ Years Experience- ColdFusion/Expert Web Designer at AtPrime Media Services
- Senior Developer at Quality Bicycle Products
- ColdFusion Developer at WRIS Web Services
- Coldfusion Developer at Cavulus
- Web Developer at Townsend Communications, Inc.
From your title, I thought you were talking about .PHP .JSP or any other working within CFMODULE directly.
I suppose that's because everything is already running (and being parsed) by the CF engine. You could use any file extension and it'll probably work.
Of course everything operates as a 'custom tag' would, including doubling the output if you close the cfmodule etc
Oh sorry, I didn't even think of that :( Yeah, I just meant file extensions.
Off topic from the post, but possibly useful to the previous comment, I believe that Sean Corfield was working on a project to handle PHP files within Coldfusion using a java library. Might be work looking at if that's something you need.
I think he was working on a library that would run PHP scripts inline... not sure if it would work for PHP files.
I use that from time to time on .sql files, when i have a REALLY complicated SQL query.
It's easier to build it in an .sql file, let Query Analyzer check it for syntax/QA, then just have ColdFusion call the very same .sql file when it's ready for my app to use. Saves a bit of copy/paste work. :)
Ben you might enjoy this old post from Mark Kruger about importing whole libraries of non-ColdFusion tags: http://tinyurl.com/adaptive-tags. Have never found much use for it - but it's a pretty slick trick.
I saw that a while back. I agree - very slick, but not sure how useful it is.