ColbyCosh.com

Exactly what is this setting you reference?
I've been using MT for years, and have absolutely no idea what you're talking about.

You know if you create a folder called something like "mywork" and use the :link this template to a file" you'll always have a saved copy to revert to.

Yeah, now I can't even find what the hell I was griping about. I did definitely lose changes to the main index template after saving them, but in the learning process maybe I've forgotten whatever ineptitude led to that? So far none of the problems I've encountered have proven ultimately resistant to my fumbling animalistic efforts at repair, and I think I've gotten almost all the major bugs out of the way.

Except for forgetting to put the Sitemeter badge in the individual-entry template so I can find out why certain entries are suddenly being hammered with referrals on a Monday morning...

I'm betting you hit the "refresh template" button instead of the "save template" at some point...?

The capability is certainly there, but you have to work to invoke it.

Also, your css and template are completely seperate, so losing cahnges to your template (content) shouldn't have had any effect on how it eventually displayed. (wrong template or not.

I well know the feeling of doing so much mucking around taht in teh end you can't really nail down exactly what was done to cause the problem.

As mentioned, good backups of both template and stylesheet can save much hair-pulling later. "Do I want to understand what went wrong, or just get the damn thing back to where it was in less than 5 minutes?" I often need to opt for the latter, because it's somebody else's blog I've borked.

Paul
Making IT work for you

Gah, hit post instead of preview - here's the corrected version:

I'm betting you hit the "refresh template" button instead of the "save template" at some point...?

The capability is certainly there, but you have to work to invoke it.

Also, your css and template are completely separate, so losing changes to your template (content) shouldn't have had any effect on how it eventually displayed. (wrong template or not.

I well know the feeling of doing so much mucking around that in the end you can't really nail down exactly what was done to cause the problem.

As mentioned, good backups of both template and stylesheet can save much hair-pulling later. "Do I want to understand what went wrong, or just get the damn thing back to where it was in less than 5 minutes?" I often need to opt for the latter, because it's somebody else's blog I've borked.

Paul
Making IT work for you

Paul: There's no such button. Template Refresh requires highlighing the template in question on the listing screen, selecting Refresh Templates from the plugin action drop-down, and clicking the Go button. By mistake. And that creates a clearly-labeled backup of the "lost" template in the process, anyway.

All of which is irrelevant, as the implication in the post is that this happened on its own upon editing an entry, as a result of a global setting. Go look at how many of those there are; and this certainly didn't come from the config file.

Quite simply: No way. Which is why I asked for specifics. I'm not debating whether something went wrong; I'm sure it did. But it's not likely anything remotely like what's described above. The only cases I'm aware of where templates have not updated properly(not even talking about reverting to default) involve the file-association glitch that I think has been fixed.

But even after that, aren't you glad you finally converted to a better way of publishing your site? Feels nice, eh?