Path

7x / documentation / ez publish / technical manual / 3.9 / concepts and basics / configuration / extension siteaccess settings

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

Extension siteaccess settings

The extension siteaccess settings makes it possible to place siteaccess specific settings in the extensions.

The directory structure must be as follows :
extension/<my_extension>/settings/siteaccess/<my_siteaccess>/<file.ini.append.php>

Example:
extension/ezno/settings/siteaccess/ezno/override.ini.append.php :

<?php /*
 
[article_full_ezno]
Source=node/view/full.tpl
MatchFile=article/full.tpl
Match[class_identifier]=article
Subdir=templates
 
*/ ?>

Note:
All settings except debug settings and including/activating extensions can be set this way.

Kåre Høvik (05/05/2006 8:38 am)

Kåre Høvik (05/05/2006 8:38 am)

Comments

  • Order of reading settings

    Friday 10 August 2007 3:36:25 pm

    Harry Oosterveen

    Suppose you have four extensions, two of them are specified as ActiveAccessExtensions in the siteaccess site.ini (local extensions), two as AccessExtensions in the override/site.ini (global extensions). Then the folders are read in this order:

    1. settings
    2. extension/<local_extension_2>/settings/siteaccess/<my_access>
    3. extension/<local_extension_2>/settings
    4. extension/<local_extension_1>/settings/siteaccess/<my_access>
    5. extension/<local_extension_1>/settings
    6. extension/<global _extension_2>/settings/siteaccess/<my_access>
    7. extension/<global _extension_1>/settings/siteaccess/<my_access>
    8. settings/siteaccess/<my_access>
    9. extension/<global _extension_2>/settings
    10. extension/<global _extension_1>/settings
    11. settings/override

    Settings for extensions are read in the reverse order in which they are listed.

    It does not look very consistent to me:
    - local extensions are read extension by extension, but for global extensions, first all siteaccess settings are read, then the normal settings
    - siteaccess settings are read after the global settings, but for extensions the siteaccess settings are read first (so why would one place siteaccess specific settings in the extensions? They can as well be placed in the normal siteaccess folder)

    Important note: you can override local extension settings with siteaccess settings (using the normal siteaccess folder), but you can not override settings for global extensions.