We have filed a bug over here: http://bugs.movabletype.org/default.asp?105377
We upgraded to 4.3 to 4.35 and now this seems to happen randomly. It took about 2 weeks for it to happen again so we're not sure why it's happening. The older case was a template tag that caused an error on PREVIEW that used the Individual Entry Archive (our custom one) after the error that template would now be filled with this:
Now we saw this happen again with no ERROR sometime in the last 24 hours. I do know that the save feature on linked templates was updated at some 4.3x release so that on initial save it would make sure and get the edits. Other than that - I'm not sure what tag or error would cause this.
Since it's random and effects our individual archives - yuck. Any thoughts or ideas would be amazing.
Does anyone know where or how it would just overwrite the linked template with:
Maybe a work around would be to put our individual archive template wherever that is coming from? In all the years we've been using MT (7 years +) this is the only problem we've had and without a repro now it's really concerning.
Reported on Movable Type 4.3
It looks like this default template code is coming from /tmpl/cms/preview_entry_content.tmpl.
Looking at the code for previewing an entry, I think this bug must occur because of the following code, which is called when the attempt to preview results in an error:
my $tmpl_plain = $app->load_tmpl('preview_entry_content.tmpl');
$tmpl->text( $tmpl_plain->text );
$tmpl here is the actual individual entry archive template. While it's not explicitly saved, if the template is linked to a file on disk, calling ->text causes a flag to be set that makes MT think it needs to be resynced to disk. So I'd guess that some combination of circumstances could cause it to actually perform that sync at the end of the request cycle, resulting in the preview_entry_content template getting written to the disk file and thence to the template in the database.