Problem

When I export my config as a tar.gz then import it to it’s destination it expands in a subdirectory which is not visible to the destination site (there is also no feedback that an error has occurred, see image below). This appears to be a bug.

screenshot

As you can see, thought the DSM says the configuration is ready to sync there is no config to sync! It is there, it's just one level dow in the directory structure.

The workaround is to extract the tar and then re-compress it from within the directory as a list of files (tar -cvzf config-myconfigpath.tar.gz .) then import it.

Proposed resolution

Add a step to the process of extracting the tar that removes the files from the archive directory.

CommentFileSizeAuthor
Screen Shot 2015-12-29 at 12.13.14 PM.png129.48 KBtkoleary
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tkoleary created an issue. See original summary.

tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

xjm’s picture

Version: 8.0.1 » 8.0.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.0.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

Status: Needs work » Closed (outdated)
Issue tags: -Configuration system +Bug Smash Initiative

@tkoleary,Thank you for reporting this problem.

I tested this on 10.0.x and was not able to reproduce this error. I followed the steps given in the Issue Summary. Then I made a change to the maintenance message and re-imported the previously saved config tar. That worked as expected, reporting that 'system.maintenance' was changed.

I don't know when this was fixed so, closing as outdated. If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").

Thanks!