Issue Bug Closed

#103803Inaccessible Settings and Maintenance module when settings.php is not writable

Patrick Schriner 05/07/24, 21:19 updated 08/01/24, 18:44

Description

If settings.php is not writable both modules can become inaccessible if a silentConfigurationUpdate has to be performed.

This can be the case e.g. in a highly secure hosting env. with old extension configuration.

Reviews 1

History 34

  1. Gerrit Code Review pushed patch set 1 for main to change 84154 status New Under Review 05/07/24, 21:30

  2. Andreas Kießling commented 05/10/24, 13:32

    The current behavior caused me some trouble in v12 too: i installed typo3/cms-styleguide via composer require —dev since i only need it for my local instance to check on the registered icons.
    Thus i got configuration in settings.php that was only valid for my local setup, but not the deployed instance since we skip dev dependencies.
    settings.php is not writeable due to selinux and the backend module just crashed since it could not remove that section from settings.php

    So if you put such config in a condition in additional.php you can’t really use the backend config module properly etc., you risk accidental commits that reintroduce the config.
    Having readonly config for production environments is a big plus, but currently it causes more problems than it solves

  3. Patrick Schriner commented 08/01/24, 18:43

    kann ich nicht mehr reproduzieren

  4. Georg Ringer commented and changed status Under Review Closed 08/01/24, 18:44

    closed as can’t be reproduced anymore