Yeap!
It looks like we have an interim solution:
I’ve figured out the problem:
In the production DB, the “news/.single-entry” template has a “template_type” of “undefined”.
In the developmnt DB, the “news/.single-entry” template has a “template_type” of “webpage”.
This means that the dev install looks for a file called “.single-entry.html”
The production install, however,looks for a file called “.single-entry”
Proposed solution:
In the production database ‘ee’,
UPDATE exp_templates
SET template_type = ‘webpage’
WHERE group_id = 5 AND template_name = ‘.single-entry’
Then the production DB will be looking for the dev DB’s template file with the proper file extension.
We’ll get the upgrade to 2.5.2 on our calendar pronto.