Private files path is not detected correctly

Created on 22 July 2024, 12 months ago
Updated 8 August 2024, 11 months ago

Problem/Motivation

Since πŸ› PrivateFiles check may fail or give misleading results for alternate stream wrappers Fixed , we get this message for the private_files check:

Private files is not enabled.

But we do have $settings['file_private_path'] defined in settings.php.

Steps to reproduce

Add this to settings.php:

$settings['file_private_path'] = '../private/default/';

Run the private_files check.

Proposed resolution

PrivateStream::getUri() seems to always return NULL.
This seems to happen when the stream_wrapper.private is fetched directly from the container.
Using StreamWrapperManager::getViaScheme() instead sets the URI correctly.

πŸ› Bug report
Status

Fixed

Version

3.0

Component

Code

Created by

πŸ‡«πŸ‡·France prudloff Lille

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024