Here's a weird one. First time using MX, and it goes stupid over certain templates in the site, telling me they don't exist. I politely explain that they bloody well do exist and perhaps it would like to deliver them. CFMX declines and carries on telling me they aint there.
Then I find out its because of the lock files! Huh? I use dreamweaver Check-in / Check-out all the time so that I can happily collaborate with other developers without getting all gnarled up... so if CFMX stops serving pages just because it's got an associated lock file, this is no good at all! (For those of you who don't know what I'm on about, dreamweaver has a check in-out system that lets you know when a file is checked out by another person, and who's got it. When you check out file MyFile.cfm, all it does is put a small file up called MyFile.cfm.LCK which has the details of who's got it. It does not remove or rename the template on the site for obvious reasons.) So why is MX doing this? Is it a known issue, and if so, is there a way around it? Taz
