Re: re[2]: [Phpwebsite-developers] Directory structure for themes and templates

[Matthew M. <ma...@tu...>]

> Now, I am truly confused. I figured that the reason for having the theme
> and template files in, for example, the calendar module directories was
> so that I could customize the look of the calendar separately.

Correct.

> If the
> system looks in the theme directory and then in the mod directory, how
> do you customize an individual module?

Go to your theme directory.
Create a directory under your templates directory named after the module
(e.g. /themes/kickButtTheme/templates/myModuleName/)
Copy the templates from the module's template directory
(e.g. cp -r mod/myModuleName/templates/*
/themes/kickButtTheme/templates/myModuleName/)
Edit the theme's new templates.

Part of the problem is a lack of documentation which is our fault.

> But, this still doesn't address the issue of having these files that get
> written distributed across the directory structure. This seems to be
> architecturally weird - sort of like mixing programs and data in the
> same directories.

I am not understanding your concern. You can copy these files to your
theme if you want to make sure you do not edit the defaults or you just
want different display styles for different themes.

For example, if I had a high contrast theme, I might want to make sure
that none of the calendar cells are highlighted with light colors. If I
alter the default templates, then my normal theme would suffer. By editing
the template in the theme only, I make sure those changes are only seen
when that theme is used.

Does that help any? If not, please continue, especially if I am confusing
(which I have been blamed of being). :)

Matt


Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
phpwebsite.appstate.edu
ess.appstate.edu