Contrib.social

Do not throw exception when default_content_deploy_content_directory is not configured

Open on Drupal.org →
Created on 17 January 2024, over 1 year ago
Updated 6 February 2024, over 1 year ago

Problem/Motivation

If default_content_deploy_content_directory is not configured and the user visits admin/config/development/dcd/import or admin/config/development/dcd/export, it will throw an exception.

The throw happens in DeployManager::getContentFolder().

Proposed resolution

Have DeployManager::getContentFolder() return NULL and not throw when default_content_deploy_content_directory is not configured.

It may be desirable to have Importer::getFolder() and Exporter::getFolder() throw if they do not have a value to return.

Remaining tasks

Implement.

User interface changes

Removal of WSOD.

API changes

DeployManager::getContentFolder() may return NULL.

Data model changes

None.

🐛 Bug report
Status

Fixed

Version

2.0

Component

Code

Created by

🇨🇦Canada Liam Morland Ontario, CA 🇨🇦

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

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024