The reason for the core and custom to be in the template directory, is that each template set might be completely different.

To prevent accidental crashes, it might be a good idea to have a "default" css in the /static directory, but to then name the template CSS to

core_<%t%>.css and custom_<%t%>.css within those template directories.

Since they are only called in the common_head file, it's not a real issue, but it can prevent accidental corruption or overwriting the wrong css file, which could be disasterous.

So, there would be 3 css files. A "default" css, to prevent any real issues. Based on the luna/default set is ok, or even a new .css that presents it all in a simple clean interface.

Then, load the core (template default) css:

<link type="text/css" rel="stylesheet" media="screen" href="<%config.db_static_url%>/<%t%>/core_<%t%>.css" />

and then the custom template css:

<link type="text/css" rel="stylesheet" media="screen" href="<%config.db_static_url%>/<%t%>/custom_<%t%>.css" />

These files should also be part of any backup, since they can take a whole site down if they are missing or corrupt. That is the real problem with css.

And, mixing css with php could lead to disaster.... putting so much into a template. But that's another issue.



Time to do this is NOW... before the release is set in stone. This is only a change to 1 file, and the file names, and can prevent a lot of grief later.


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.