> I already have CF 2016 running on my laptop. This is the server that I wish to continue using.
I understand and appreciate that. What I was suggesting was that if you’re having issues getting ColdBox running inside your existing server, playing around in a temporary sandbox to get a better understanding of how it works might be beneficial. You’ll also likely find that using CommandBox is way easier than messing with installers. I haven’t “installed” CF or Lucee in years but I use them every day
> The ‘Coldbox’ folder is placed right into my site, along with all the other folders (handler,model, view, layout etc).
It’s not a requirement that ColdBox be in the same folder as your site. It’s a requirement that /coldbox maps to the coldbox folder. That means, it either needs to be in the webroot, or you need a mapping. This isn’t a ColdBox thing per se, just the basic way that ColdFusion looks up CFCs. Since I’m unclear on whether your ColdBox app (handlers, models, etc) are in the web root or in a subfolder off the web root, I can’t comment on if you’re existing setup should work or not.
> I just want to know why I’m getting all these “can’t find this and can’t find that” type of errors that Coldbox is throwing.
I’d love to know that too but right now you really haven’t provided enough information Start by confirming /coldbox resolves to the framework folder. It’s usually just that simple. So long as the framework can be found, the app should work. Without knowing your entire directory structure, the exact URLs you’re hitting, and the exact errors you’re getting, I can only guess as to what’s happening.
What I do often times see, is people will try and put their ColdBox app in a subfolder off the web root and they’ll stick the ColdBox framework in that subfolder, but neglect to create any sort of mapping. What will happen is the bootstrap in Application.cfc will “find” the “coldbox.system.Bootstrap” class because it’s in the same relative folder which will cause the framework to start to load, but as soon as another file not in the root of the app tries to create a CFC like “coldbox.system.foo” then it errors out because there’s still no mapping and the 'same folder" rule doesn’t apply. ColdBox can’t control any of that, though. That’s just the rules that ColdFusion uses when trying to resolve CFC paths.
ColdBox/CommandBox Developer Advocate
Ortus Solutions, Corp
ColdBox Platform: http://www.coldbox.org