I’ve got the dreaded “Unable to save your template as a text file” error.
Can’t save new template files, can’t update old template files.
This happened after I moved the site over from the staging site to the production site. Worked fine on staging, fails on production. Both the staging site and production site are on a Mediatemple DV. Both sites are set up with same configuration.
The template_files directory, template group directory and template files are set 777 with equivalent user & groups on staging & production. Changing the user / group to “apache” made no difference.
4 drwxrwxrwx 2 staginguser psacln template_group
4 drwxrwxrwx 2 productionuser psacln template_group
php safe_mode is off on both:
off | off
off | off
php open_basedir is set up equivalent on both:
/var/www/vhosts/staging.com/httpdocs:/tmp | no value
/var/www/vhosts/production.com/httpdocs:/tmp | no value
The EE Basepath to Template File is equivalent on both ***
/var/www/vhosts/staging.com/httpdocs/template_files/
/var/www/vhosts/production.com/httpdocs/template_files/
**** NOTE **** Be very careful editing the “Basepath to template File” value. My EE system decided to revert to displaying ALL the templates saved in the DB rather than saved files…. resulting in a Live production site showing a mix of old templates from the DB…. I had to scramble to load the template “files” into the DB to get the site back to normalcy… The site looked like crap for about 15+ min in the middle of launch day….. ******be &%$%& careful! ******
I tried editing the cp.templates.php file per Robin S.‘s instructions in this thread: http://ellislab.com/forums/viewthread/83163/
and it resulted in “2”.
This has halted production on the site. Where should I start looking for a solution?
This question may be related to a resolved thread.