What's the difference between the 'standard' and the 'base' directory?

Next topic

Author	Message
Igor Paffen	Monday 30 August 2004 10:37:38 am I use "The Scandinavian Check Mates" website for learning the system. When no specific template is made in the 'TSCM' directory, sometimes the 'standard' directory is used and sometimes the 'base' directory. What's the difference between the 'base' directory and the 'standard' directory?
Lazaro Ferreira	Monday 30 August 2004 10:58:05 am Hi, AFAIK, the base directory is used to support ezp custom setup, i.e : At the time of setup you can ask ezp to install some modules, like foruns, polls, feedback form, and the likes, behind the scene ezp setup add a lot of customization code in form of templates, override settings, etc, as result you get a lot of ready to use ezp funcionality On the other hand, the standard ezp directory is the place where every ezp functionality found a default, a last resource where ezp can fall back, in case no override or customization exist This is at the heart of ezp filosophy, every module, object or component supported by the system has a default way to present or appear, that's the standard way in the standard directory I'm not sure but if you ask EZP to do a plain installation, (no custom module), you will probably get only the standard directory Lazaro Ferreira http://www.mzbusiness.com Lazaro http://www.mzbusiness.com

Author

Message

Monday 30 August 2004 10:37:38 am

I use "The Scandinavian Check Mates" website for learning the system. When no specific template is made in the 'TSCM' directory, sometimes the 'standard' directory is used and sometimes the 'base' directory. What's the difference between the 'base' directory and the 'standard' directory?

Lazaro Ferreira

Monday 30 August 2004 10:58:05 am

Hi,

AFAIK, the base directory is used to support ezp custom setup, i.e : At the time of setup you can ask ezp to install some modules, like foruns, polls, feedback form, and the likes, behind the scene ezp setup add a lot of customization code in form of templates, override settings, etc, as result you get a lot of ready to use ezp funcionality

On the other hand, the standard ezp directory is the place where every ezp functionality found a default, a last resource where ezp can fall back, in case no override or customization exist

This is at the heart of ezp filosophy, every module, object or component supported by the system has a default way to present or appear, that's the standard way in the standard directory

I'm not sure but if you ask EZP to do a plain installation, (no custom module), you will probably get only the standard directory

Lazaro Ferreira
http://www.mzbusiness.com

Lazaro
http://www.mzbusiness.com