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.

Sequence of the override files

Sunday 31 July 2005 12:20:01 am

Josh Luo

When a siteaccess is in use, it seems more LOGIC for eZ publish to read the configuration files using the following sequence:

1. Default configuration settings (/settings/*.ini)
2. Global overrides (/settings/override/*.ini.append.php)
3. Siteaccess settings (/settings/siteaccess/[name_of_siteaccess]/*.ini.append.php)

I think, for example, that the database settings in the global override directory SHOULD be overrided by the database settings in the siteaccess. Otherwise if we have several databases for multisites, the different databases settings in the different siteaccess are overrided by the same database sittings in the global overrides, some sites would't work.

  • Re: Sequence of the override files

    Friday 12 August 2005 10:48:32 pm

    Kyle Lady

    "I think, for example, that the database settings in the global override directory SHOULD be overrided by the database settings in the siteaccess. Otherwise if we have several databases for multisites, the different databases settings in the different siteaccess are overrided by the same database sittings in the global overrides, some sites would't work."

    In that case, you should not use the global override to set the database settings. You would have to set the database settings in every site's siteaccess file.

    • Re: Re: Sequence of the override files

      Wednesday 31 August 2005 2:20:20 pm

      Josh Luo

      Supposing multisites include many sites with the same database, for instance, 10 sites. I can set the database db in the global overrides only one time. Some day I want to site1 with a separate database db1. How can I do?

      According to your sequence to read the configuration files:
      1. Default configuration settings (/settings/*.ini)
      2. Siteaccess settings (/settings/siteaccess/[name_of_siteaccess]/*.ini.append.php)
      3. Global overrides (/settings/override/*.ini.append.php)

      I have to:
      --- set the db1 in this siteaccess setting file for site1;
      --- delete the db settings in the global override file, or db1 will be overrided by db settings;
      --- set the same db one by one in other siteaccess setting files, 9 files for this example.

      But according to the following sequence to read the configuration files:
      1. Default configuration settings (/settings/*.ini)
      2. Global overrides (/settings/override/*.ini.append.php)
      3. Siteaccess settings (/settings/siteaccess/[name_of_siteaccess]/*.ini.append.php)

      I only need set the db1 in this siteaccess setting file for site1, that's all.

      I needn't delete the db settings in the global override file, because the db will be overrite by db1. Also I don't worry about other sites. Do nothing for other 9 sites.

      Think about other setting parameters, there is the same situation. That's why I think the latter seems more LOGIC.

      • Re: Re: Re: Sequence of the override files

        Friday 12 September 2008 10:35:27 pm

        JB

        I'm sorry but I'm not agree with you, because as kyle says, you can solve your problem by deleting database settings in the global override and managing this settings per site access.

        On the other side I have exactly the opposite need, and you couldn't find a solution if global settings are overrided by siteaccess settings :

        I need to allow my siteaccess owners to modify their templates and settings (including site.ini) but I don't want they use another database, and I don't want they know my database password. They must use the same database for all siteaccesses.
        It's just a different LOGIC ! ;-)



Anonymous User (30/07/2005 10:20 pm)

Anonymous User (30/07/2005 11:11 pm)

Comments

  • Re: Sequence of the override files

    Friday 12 August 2005 8:48:32 pm

    Kyle Lady

    "I think, for example, that the database settings in the global override directory SHOULD be overrided by the database settings in the siteaccess. Otherwise if we have several databases for multisites, the different databases settings in the different siteaccess are overrided by the same database sittings in the global overrides, some sites would't work."

    In that case, you should not use the global override to set the database settings. You would have to set the database settings in every site's siteaccess file.

    • Re: Re: Sequence of the override files

      Wednesday 31 August 2005 12:20:20 pm

      Josh Luo

      Supposing multisites include many sites with the same database, for instance, 10 sites. I can set the database db in the global overrides only one time. Some day I want to site1 with a separate database db1. How can I do?

      According to your sequence to read the configuration files:
      1. Default configuration settings (/settings/*.ini)
      2. Siteaccess settings (/settings/siteaccess/[name_of_siteaccess]/*.ini.append.php)
      3. Global overrides (/settings/override/*.ini.append.php)

      I have to:
      --- set the db1 in this siteaccess setting file for site1;
      --- delete the db settings in the global override file, or db1 will be overrided by db settings;
      --- set the same db one by one in other siteaccess setting files, 9 files for this example.

      But according to the following sequence to read the configuration files:
      1. Default configuration settings (/settings/*.ini)
      2. Global overrides (/settings/override/*.ini.append.php)
      3. Siteaccess settings (/settings/siteaccess/[name_of_siteaccess]/*.ini.append.php)

      I only need set the db1 in this siteaccess setting file for site1, that's all.

      I needn't delete the db settings in the global override file, because the db will be overrite by db1. Also I don't worry about other sites. Do nothing for other 9 sites.

      Think about other setting parameters, there is the same situation. That's why I think the latter seems more LOGIC.

      • Re: Re: Re: Sequence of the override files

        Friday 12 September 2008 8:35:27 pm

        JB

        I'm sorry but I'm not agree with you, because as kyle says, you can solve your problem by deleting database settings in the global override and managing this settings per site access.

        On the other side I have exactly the opposite need, and you couldn't find a solution if global settings are overrided by siteaccess settings :

        I need to allow my siteaccess owners to modify their templates and settings (including site.ini) but I don't want they use another database, and I don't want they know my database password. They must use the same database for all siteaccesses.
        It's just a different LOGIC ! ;-)