site.ini [ConfigurationSettings] #

The block [ConfigurationSettings] of settings/site.ini, with 1 setting(s).

Never edit settings/site.ini itself: an update replaces it. Put the settings you change in an override, which wins over the shipped file:

• settings/override/site.ini.append.php for every siteaccess,
• settings/siteaccess/<siteaccess>/site.ini.append.php for one siteaccess,
• extension/<extension>/settings/site.ini.append.php in an extension (read when the extension is active).

ManagedByDeployment #

enabled: the configuration of this siteaccess is managed by the deployment
(version control) and the admin interface does not change it on the server.
In a web request the views that write settings, templates, generated code or
packages (settings/edit, toolbar and menu editors, template editor, setup
wizards and code generators, package upload/install/uninstall/create/export;
the list is expManagedConfiguration::LOCKED_VIEWS) answer like a view switched
off in [SiteAccessRules] and are hidden from the menus, and neither
eZINI::save() nor expIniEditor::save() writes a settings file. This holds
for PHP-FPM, Apache and the application servers that run PHP on the command
line (Velocity, the built-in server). Read-only views stay available. Command
line scripts are not affected. Set it in a versioned settings file, never
from the admin. See doc/eng-us/features/6.0/managed-by-deployment.md.

Default: disabled.

<?php /* #?ini charset="utf-8"?
# settings/override/site.ini.append.php
[ConfigurationSettings]
ManagedByDeployment=disabled
*/ ?>

Related #

• All blocks of site.ini
• All INI files
• The settings page

Generated by ./console exp:help:examples from settings/site.ini. Do not edit this page: change the source and generate again (how). Free documentation: GFDL 1.3 or later.