-
-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[config:export] broken in 1.9.4 #4198
Comments
The issue lies in the src/Command/Config/ExportCommand.php file, this is lines 95 to 118...
You'll see that the $drupal_root is being added by default to the directory passed in to the function at line 98, which precludes specifying a full system path (in other words, you can now only pass a relative path to the export function). The $drupal_root variable is then also being added again at line 110, so even with a relative path it will still be wrong. Also, the $drupal_root variable itself is being defined twice (lines 97 & 102). I believe these lines should look more like this...
I'm happy to be corrected though! |
same issue. Downgrading to 1.9.3 as suggested by @erilot works. |
Could be linked to #4195 |
Thank you for your contribution |
[config:export] broken in 1.9.4
Problem
After upgrading to console 1.9.4,
config:export
incorrectly calculates the directory path for the export files, creates those incorrect directories, and doesn't export any files. No error is thrown.May be related to #4195.
I am using a web docroot on Ubuntu 18.04 local development environment (Lando/Pantheon recipe), and
What I expect to see: execute
drupal ce
, accept the default directory (/app/config
). All config files are exported to/config
. (Note with a web docroot this is parallel to theweb
directory containing the drupal site). This worked as expected until upgrading to 1.9.4.What happens instead:
Which creates an
/app/app/config
directory with no files in it:Replacing the default with
/config
generates an/app//config
directory structure with no files in it.Replacing the default with
/
destroys the site. Do not recommend.How to reproduce
Workaround
Revert to 1.9.3, which works as expected
The text was updated successfully, but these errors were encountered: