I am starting with the creats_65 template in a new install on 6.5 Pro.
At the bottom of the template.php file I noticed these.

// custom entries
define('TEMPLATE_FS_CUSTOM_INCLUDES',DIR_FS_CATALOG . DIR_WS_TEMPLATES . TEMPLATE_NAME . '/includes/');
define('TEMPLATE_BUTTONS_USE_CSS','true');
define('TEMPLATE_FS_CUSTOM_MODULES',TEMPLATE_FS_CUSTOM_INCLUDES . 'modules/');


there is only a single file in the create_65 template in the includes directory.
I believe it is something like menu.php.

Can anyone help me understand the logice here.

I am trying to follow the post from mindhaze where he describes the ATS templates vs. otr and the impact of the template.php file.
http://creloaded.org/forum/topic.html?f=16&t=26794&p=118958&hilit=template.php+legacy#p118958

As good as that above doc is, it doesnt outline every possibility.

Thanks fro the help.
BK

template.php = defines for template name, page dimensions, paths, template-specific overrides like extra_html_output.php and switches eg infobox images like corners on boxes

menu.php = language defines for certain menu items in the template header

If you have a template that has different requirements over the default configurations, here is where you can define them.

Simon

template.php is basically a configuration file for the template.

That document is a slightly modified version of one written by Tom O'Neill back when we were designing the ATS.

One repeated element of ATS is a series of fall back paths which allow for custom template elements to be added by writing an appropriate component file then dropping it into a designated location.

TEMPLATE_FS_CUSTOM_INCLUDES and TEMPLATE_FS_CUSTOM_MODULES reflect this element and should both be File System paths, as indicated by the FS element of the definition name.

The absence of these folders should not affect the templates presentation, as the system should check to see if these folders exist, then drop back to another folder serving the same purpose if they don't.

TEMPLATE_BUTTONS_USE_CSS is a switch, probably specific to this template or a series of related templates which toggles button treatment in some fashion.


any other questions??

Sheesh, don't encourage him David - he's looking for 'every possibility' eh? Lol.

Simon