Apparently, Exponential looks at the permissions of the design/ and settings/ files and subdirectories. If the user PHP runs as (httpd, usually) doesn't have full write access on both dirs and files, it will place the new override template where it has.
If you've been following this tutorial and at some point have created new siteaccesses, you most likely didn't place proper permissions on them. The proper permissions are 770 for directories and 660 for files. Go around design and siteaccess and do this:
find design/ -type f -exec chmod 660 {} \;
find design/ -type d -exec chmod 770 {} \;
(repeat for siteaccess/)
If you don't, here's what happens: when you click "New override", the message will say it's gonna place the new override in design/admin/override/templates instead of your design dir, and you'll spend a while wondering if perhaps you should select a different siteaccess from the "Set" dropdown list, and what happens if you have several siteaccesses, and so on.
The big gotcha is that the "Set" dropdown list is just a "view" filter, it doesn't decide where the new templete override goes. The folder permissions do.
...and make sure your AvailableSiteDesignList includes all your own designs, otherwise you may end up wondering why the template cache doesn't clear even if you clear it manually.
Modified by Ciprian Popovici
on 03/03/2006 at 9:34:33 pm
Watch out for permissions!
Ciprian Popovici
Friday 03 March 2006 10:05:25 am
http://ez.no/community/forum/setu...tes_being_created_in_wrong_directory
Apparently, Exponential looks at the permissions of the design/ and settings/ files and subdirectories. If the user PHP runs as (httpd, usually) doesn't have full write access on both dirs and files, it will place the new override template where it has.
If you've been following this tutorial and at some point have created new siteaccesses, you most likely didn't place proper permissions on them. The proper permissions are 770 for directories and 660 for files. Go around design and siteaccess and do this:
find design/ -type f -exec chmod 660 {} \;
find design/ -type d -exec chmod 770 {} \;
(repeat for siteaccess/)
If you don't, here's what happens: when you click "New override", the message will say it's gonna place the new override in design/admin/override/templates instead of your design dir, and you'll spend a while wondering if perhaps you should select a different siteaccess from the "Set" dropdown list, and what happens if you have several siteaccesses, and so on.
The big gotcha is that the "Set" dropdown list is just a "view" filter, it doesn't decide where the new templete override goes. The folder permissions do.
Also a good idea would be to take a look here:
http://ez.no/community/forum/gene...t_tpl_and_site_css_strange_behaviour
...and make sure your AvailableSiteDesignList includes all your own designs, otherwise you may end up wondering why the template cache doesn't clear even if you clear it manually.
Modified by Ciprian Popovici on 03/03/2006 at 9:34:33 pm