Path

7x / documentation / exponential / technical manual / 5.x / templates / the template override system / please make it easier to un...


Caution: This documentation is for Exponential, from version 3.x to 6.x.
For 5.x documentation covering Platform see Exponential Platform Documentation, for difference between legacy and Platform see 5.x Architecture overview.

Please make it easier to understand

Hello,
I want to learn how to override a template...
Great, I've created the new folder...created a duplicate of pagelayout.tpl....

I can see this line saying...
"The template overrides must be defined in the "override.ini.append.php" file of a siteaccess".

Why can't i find anything that tells me where to create override.ini.append.php.
It also doesn't explain if these .ini files are needed per template or if you have one file that handles the whole lot. It also doesn't tell me if this can be done via admin, rather than manually.
It also doesn't tell me how to create overrides via the admin area as I see a "New Override" option.

I'm really confused...
It's like you're telling me steps 3 and 4 with the assumtion that I know 1 and 2 like yourself....


Hope you can help,
Thanks
  • Re: Please make it easier to understand

    "The template overrides must be defined in the "override.ini.append.php" file of a siteaccess".

    This means that the file should be created in the /siteaccess/your_site/ folder, next to the site.ini.append.php file, which resides in the same folder.
    So, for every site access, you have one override.ini.append.php file.

    The templates that you create to override the standard templates, are placed in the /design/your_design/override/templates folder (create it if nescessary).

    Custom pagelayout templates however, can just be placed in the design/your_design/templates folder. There is no need to create a override.ini.append.php for those. If templates exist in the /design/your_design/templates folder, they will always be used instead of the /design/standard/templates folder.
    See also: <url>http://ez.no/doc/ez_publish/techn...igns/design_combinations</url>

    The special thing with override templates is that they can *conditionally* override default templates, only if cetain conditions are met, like node id or object class, using the Match specifier.
    • Re: Re: Please make it easier to understand

      "The template overrides must be defined in the "override.ini.append.php" file of a siteaccess".

      This means that the file should be created in
      [exponentialdir]/settings/siteaccess/[yoursitedir]/override.ini.append.php

Anonymous User (05/01/2006 4:07 pm)

Anonymous User (05/01/2006 4:10 pm)


Comments

  • Re: Please make it easier to understand

    "The template overrides must be defined in the "override.ini.append.php" file of a siteaccess".

    This means that the file should be created in the /siteaccess/your_site/ folder, next to the site.ini.append.php file, which resides in the same folder.
    So, for every site access, you have one override.ini.append.php file.

    The templates that you create to override the standard templates, are placed in the /design/your_design/override/templates folder (create it if nescessary).

    Custom pagelayout templates however, can just be placed in the design/your_design/templates folder. There is no need to create a override.ini.append.php for those. If templates exist in the /design/your_design/templates folder, they will always be used instead of the /design/standard/templates folder.
    See also: <url>http://ez.no/doc/ez_publish/techn...igns/design_combinations</url>

    The special thing with override templates is that they can *conditionally* override default templates, only if cetain conditions are met, like node id or object class, using the Match specifier.
    • Re: Re: Please make it easier to understand

      "The template overrides must be defined in the "override.ini.append.php" file of a siteaccess".

      This means that the file should be created in
      [exponentialdir]/settings/siteaccess/[yoursitedir]/override.ini.append.php