Proper error message when Private file system path not set

Created on 20 October 2021, over 3 years ago
Updated 25 September 2024, 7 months ago

Problem/Motivation

When I tried to import a .tar.gz file, I kept bumping into the following error:

The file could not be uploaded.

The logs showed:

The upload directory private://content_synchronizer for the file field archive could not be created or is not accessible. A newly uploaded file could not be saved in this directory as a consequence, and the upload was canceled.

When checking /admin/config/media/file-system, it turned out I did not yet set a "Private file system path".

Steps to reproduce

In a new Drupal installation (without a Private file system path), try to import a content .tar.gz file.

Proposed resolution

It would be nice if the import page would first check whether or not the Private file system path has been set. If not, it should not allow for importing, but instruct the user to first make sure that path is set.

Feature request
Status

Active

Version

4.0

Component

Logs

Created by

🇧🇪Belgium BenVercammen

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

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