Topic: Templates and events/actions Questions

[Black]

When following the documentation I noticed there's a couple Templates Folders

templates
templates-custom
templates-default
templates.metadata
templates-user
templates-user-custom


My main problem is that the HELP Files everyone seems to point the newbies to Do Not reflect these type of changes.

Why are there so many of those folders?

The help file talk about a Server-Manager Panel AND a Password panel. where is this Password panel?

Why was this removed and why is it still in the help file?

When making a addition to a template how do you go about numbering it? S80, S70, S95?? The manual never really tells you this..

[arthurhanlon]

Hi there,

The documentation on this site for the customisation of the templates is pretty extensive and gives you and overview of how to edit and add template fragments. Check the following link http://no.longer.valid/phpwiki/index.php/Key%20concepts (Check also "Architecture Overview" from within this link)

As for the password panel, there is a panel that allows any user to change his/her password at any time they like. This is available at http://server-name/user-password/

Hope this helps,

Arthur

[Black]

Thanks for the reply! I didn't see anywhere in the documentation about how to get to the user-passwd webbased setting.

I also didn't see anything about all those template directorys?

I've been combing over and over those papers and it's still confusing about the S80, S85,S90 etc..

What if I wanted to Ban a IP Address coming to my site as an example?

[arthurhanlon]

Woah there, you got me.

Never actually had a need to edit any templates myself so couldn't even hazard a guess for fear of you wrecking your server. I dare say that it's not something that can be picked up and it'll need a little trial and error to get the jist.

This is the next step for me, customisation. I got a working server, now it's time to break it  

Arthur

[pfloor]

I also didn't see anything about all those template directorys?

I've been combing over and over those papers and it's still confusing about the S80, S85,S90 etc..

templates > Here is where all the main templates reside DO NOT TOUCH THESE!
templates-custom > Here is where you would put any custom templates that will add to OR override the main templates.
templates-default > These are system default templates. DO NOT TOUCH THESE!
templates-user and templates-user-custom > Don't really know what these are, someone else will have to answer that.

The templates in the template directory control the corosponding configuration files.  The numbers on the template fragments tell the system in what order to place the fragments in the configuration file.  So for instance, if you place a fragment called 93Gallery in /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/ the change would be placed between fragment 92ProxyPassPassword and 95AddType00PHP2ibays that are in the main template directory.

S90 would actually be placed at the end of the configuation file as letters come after numbers and the fragment would start with a letter.

If you name your custom template fragment the same as an existing template fragment, the custom template fragment will totally override the original template fragment.

It's a bit more complex than this but at least this should give you the general idea.

Hope this helps.

[gordonr]

templates

Standard templates, installed via RPM. These may either be installed by the normal system install, or by add-on packages which don't conflict with the system installed templates.

The files in this tree should not be modified by hand. The changes will be lost in the next system upgrade.

Contrib developers - your templates should go here, unless they conflict with a standard template. If so, please raise a bug so that the conflict can be resolved. There are cases where the templates should be split, but unless you raise a bug nobody is going to know.

templates-custom

Hand-installed templates (local hacks) or templates which conflict with/override the system installed templates.

Each template here must be checked for relevance and compatibility with each system upgrade. The overridden template may have changed or ceased to be.

templates-default

Simple headers/footers for template expansions in various languages - e.g. html, php, etc.

templates.metadata

Extra configuration parameters for template expansion, when required - e.g. to set ownership, permissions or paths when the defaults aren't sufficient. These are used quite a lot in 7.0 in preference to simple conf-* scripts which just expand a template with specific permissions, ownership, etc. The templates.metadata method is far more efficient.

templates-user

Templates which expand relative to user's home directories, e.g. /etc/e-smith/templates-user/.qmail

templates-user-custom

The equivalent of templates-custom for the user templates.

Gordon

[Black]

Ok thanks. That wasn't explained in any of the manuals I have been reading here. I wish there was a course or some people to get together with and hack in this. I feel like I dont know anything about it and i've been running it for a year

[gordonr]

Ok thanks. That wasn't explained in any of the manuals I have been reading here.

Some of this (e.g. templates.metadata) is new in 7.0 development.

I wish there was a course or some people to get together with and hack in this. I feel like I dont know anything about it and i've been running it for a year

I'd be quite happy to run a course, but I'm not in your neighbourhood

[Black]

What about doing Video Screen Capture on your PC? Like they do on vtc.com