Created on 1 April 2015, over 9 years ago
Updated 4 June 2024, 6 months ago

Problem/Motivation

PHP only reads .htaccess when it is running as an Apache module. Running PHP as an Apache module is becoming obsolete. It is now more common to run PHP as a CGI script. When running as a CGI, PHP configuration settings need to be in .user.ini. PHP settings should be in both files, because mod_php does not read from .user.ini.

Original report by stefan.r β†’

As per Damien Tournoud in https://www.drupal.org/node/2455465#comment-9783185 β†’ , we may want to consider copying/moving PHP settings into a .user.ini file:

Please move *all* of those into a .user.ini file. They just don't belong into .htaccess, and when there they only apply to mod_php installation, which should be a infinite part of the PHP production installations nowadays (including all major cloud platforms, which are all using PHP-FPM).

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

  • There is now a default .user.ini file in the site root. Site owners who have their own .user.ini file should save it under a different name before this update and add its settings to the default .user.ini using a drupal-scaffold entry in composer.json.
πŸ“Œ Task
Status

Needs work

Version

11.0 πŸ”₯

Component
OtherΒ  β†’

Last updated about 7 hours ago

Created by

πŸ‡³πŸ‡±Netherlands stefan.r

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024