Sanity question: If there is both an Application.cfc and an Application.cfm file (In cf adobe 2018) the Application.cfm file gets ignored by default and only the Application.cfc is used correct? Is there any instance/circumstance that the system could use the Application.cfm or is it safe to just delete at this point. Application.cfc has existed in the same directory for a few years now. unfortunately I don't have a coverage of tests to test all the calls to verify in all instances the app.cfm file isn't being used.

@deactivateduser Put a dump/abort or some logging at the top of the application.cfm file to ensure it's never getting hit.

I know the cfc is always being called and cfm isn't for currently tested calls, just can't test every scenario to see if cfm may somehow get called.

One thing to be careful of (I sadly found this myself in a production codeset) is that the application.cfm is not being cfincluded in the .cfc at some point. That was how one of my old clients "transitioned" to using application.cfc. They didn't understand exactly how the execution order was supposed to work so they just put an include inside of the requestStart. I twitched so hard when I saw it that my car unlocked itself.

Thanks, didn't think of that. Will run a quick search but I don't think we are doing that. Like 70% sure on that