For development purpose, I run all templates as text files.  Now I have migrated the site to a live server.  Is there a performance hit or should I turn it off?

If I should turn it off on the live site, what’s are the recommended steps?  Do I go to every single template to reload the content, un-click the “Save Template as File” checkbox and save it into database.

Don’t have any thread pointers but from everything I’ve read, there is no performance hit of any consequence, if at all.

There is additional disk i/o for the file, of course, but it’s just read access, so unless you have an unusually high traffic site, I don’t think even anyone monitoring the server closely would notice a blip.  And if you _do_ have an unusually high traffic site, it’s likely that you already have a server environment with a disk array that can handle it.

That said, there is convenience to keeping it all in the database on a production site.  If your host (or you) make regularly scheduled database backups, then the templates are included with such a backup.  Perhaps not a big deal if you also make regular file backups, but I prefer to keep everything in one place when I can.

Thanks to all.  I will leave the templates as text files then as it makes porting the template changes over much easier via FTP.

Once a site is live and stable, I usually take it into the database as I’m rarely accessing with anything major. It is kind of a pain as you need to visit every template, switch the file save off and refresh. Wished there was a master switch :-)

A master query, perhaps?

Untested, so use at your own risk

Thanks Ingmar, don’t have anything to test on at the moment but have the code so will try when possible.

Well, you still need to save via the form, or EE will serve the potentially-stale database version of the template.

Ouch, good catch there. So, there’s no way to fully automate that, Derek?

Well, no one-line way.  A quick PHP script in a template could handle it, grabbing content from files of all saved templates, and updating the database.