Problem/Motivation

Currently, the process of exporting a single configuration on the /admin/config/development/configuration/single/export page involves manually copying changes, searching for the file name in the configurations, and pasting the copied changes—a cumbersome task. This feature request suggests adding a "Download" or "Export" button on the /admin/config/development/configuration/single/export page for improved user/admin convenience. This enhancement would allow users to either directly place/override the selected configuration in the configured configuration folder or download it as a file to their system.

Steps to reproduce

  1. Navigate to /admin/config/development/configuration/single/export.
  2. Choose a "Configuration type," such as "Simple Configuration."
  3. Select a "Configuration name," for example, "node.settings."
  4. Currently, the only option is to manually copy/paste the changes, with no direct export capability to the configuration folder or download option.

Proposed resolution

  1. Introduce an "Export" button that exports the content from the "Here is your configuration:" field to the respective configuration file in the codebase.
  2. Implement a "Download" button that downloads the content from the "Here is your configuration:" field to the user's computer with the respective configuration file name.

Remaining tasks

To be determined.

User interface changes

To be determined.

API changes

Not applicable.

Data model changes

Not applicable.

Release notes snippet

Not applicable.

Thank you.

Comments

Prashant.c created an issue. See original summary.

cilefen’s picture

cilefen commented
Issue tags: -Configuration system
Related issues: +#3201567: Add a download button on single export configuration page, +#2218917: Load configuration by URL arguments in single export form, +#3191067: Contextual config export links

This may duplicate or overlap these prior requests.

prashant.c’s picture

prashant.c
he/him
Primary language English
Location Dharamshala
commented
Status: Active » Postponed

@cilefen

Appreciate the provided links to related issues. The issue https://www.drupal.org/project/drupal/issues/3201567 seems to cover one of the requirements. Another requirement is to include an option like "Export," which would directly export changes to the codebase in the configuration folder if feasible.

However, we may want to wait until other issues are resolved. As of now, I'll mark this as "Postponed."

Thank you.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.