Skip to content
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

ddev pull fails on Wordpress Pantheon site (doesn't pull files) #1736

Closed
rfay opened this issue Jul 27, 2019 · 0 comments
Closed

ddev pull fails on Wordpress Pantheon site (doesn't pull files) #1736

rfay opened this issue Jul 27, 2019 · 0 comments

Comments

@rfay
Copy link
Member

rfay commented Jul 27, 2019

Describe the bug

If you try to do a ddev pull on a properly configured Wordpress Pantheon site, you get

An existing user-managed wp-config.php file has been detected!
Project ddev settings have been written to:

/Users/rfay/workspace/ddevwptest/wp-config-ddev.php

Please comment out any database connection settings in your wp-config.php and
add the following snippet to your wp-config.php, near the bottom of the file
and before the include of wp-settings.php:

// Include for ddev-managed settings in wp-config-ddev.php.
$ddev_settings = dirname(__FILE__) . '/wp-config-ddev.php';
if (is_readable($ddev_settings) && !defined('DB_USER')) {
  require_once($ddev_settings);

Even if you then add the settings as requested there, it continues to pester (and apparently to return a failure)

To Reproduce

Basically, this will happen with any existing wp-config.php. (You don't need pantheon).

Removing the wp-config.php and ddev config or ddev config pantheon will get you going just fine (ddev will then create its own file)

I used the ddevwptest Pantheon project (available to the drud account and my own) and was easily able to demonstrate this, even though in the end it's not about Pantheon. But it does prevent the project files from being downloaded, because the config process fails.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Version and configuration information (please complete the following information):

  • Host computer OS and Version: [e.g. Windows 10, macOS High Sierra]
  • Docker version information (use docker version) and insert it here.
  • ddev version information (use ddev version)
  • config.yaml contents for the misbehaving project
  • Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? If so, have you tried without them?

Additional context
Add any other context about the problem here. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant