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

Drupal subsite status report not showing correct profile #2930

Closed
arun9989 opened this issue Jul 4, 2018 · 8 comments
Closed

Drupal subsite status report not showing correct profile #2930

arun9989 opened this issue Jul 4, 2018 · 8 comments
Labels
Support A support request

Comments

@arun9989
Copy link

arun9989 commented Jul 4, 2018

My system information:

  • Operating system type: Mac
  • Operating system version: Sierra
  • BLT version: BLT 9.1.0-alpha1

When I run this command:

blt setup --site=mysite

I get the following output:

In the sub site status report it showing installed profile as lightning.

I have installed a Drupal site with lightning profile and exported all the configuration in to /config/default folder using drush config-export command.

After that I have created a subsite(using blt recipes:multisite:init ) and the subsite is installed with a custom profile which depends on lightning profile.

But after installation in subsite status report it is showing that Installed profile is 'lightning' instead of my custom profile.

Am I missing anything? Is there any additional parameters to be added in custom profile?

@ba66e77
Copy link
Contributor

ba66e77 commented Jul 5, 2018

So "mysite" is the name of your default site? What's the name of your subsite and what command are you running to get the "subsite status report"?

@ba66e77 ba66e77 added Support A support request 9.1.x labels Jul 5, 2018
@arun9989
Copy link
Author

arun9989 commented Jul 5, 2018

"mysite" is my subsite. I didn't change the name for default site.

For status report, after install the site I login using drush uli and checked /admin/reports/status page.

@ba66e77
Copy link
Contributor

ba66e77 commented Jul 5, 2018

First place I would check then is to make sure the "mysite" instance is connecting to the correct database. The multisite init process currently does not update the db credentials for a new site, so those have to be done manually (See the "Running...currently does not" section in http://blt.readthedocs.io/en/latest/multisite/#multisite).

@arun9989
Copy link
Author

arun9989 commented Jul 5, 2018

Yes, you are right. BLT does not update docroot/sites/{newsite}/settings/local.settings.php. But I updated this file manually. But this configuration is not picking up for my subsite. Subsite is loading db settings from docroot/sites/default/settings/local.settings.php. After update the db settings in default/settings/local.settings.php only subsite is loading with correct db. But still in status report it showing installed profile as lightning.

@ba66e77
Copy link
Contributor

ba66e77 commented Jul 5, 2018

Did you also set up the sites.php file? That's another one that's in the "doesn't do" category but is needed for multisites.

If you're connecting to the correct database and the status report still shows Lightning as the profile, then I'd feel pretty confident that's what was setup on the site. How did you confirm the subsite was installed with the custom profile you expected?

@arun9989
Copy link
Author

arun9989 commented Jul 5, 2018

sites.php exist in docroot/sites/sites.php. I didn't made any change in this file. How I confirmed is my profile split is getting installed during setup also blt setup showing :
[Acquia\Blt\Robo\Tasks\DrushTask] Running /var/www/myproject/vendor/bin/drush @mysite.local site-install customprofile install_configure_form.update_status_module='array(FALSE,FALSE)' install_configure_form.enable_update_status_module=NULL --sites-subdir=mysite --site-name=MySite --site-mail=no-reply@acquia.com --account-name=ukTssgQkm8 --account-mail=no-reply@acquia.com --locale=en --uri=mysite -v --ansi in /var/www/myproject/docroot

@lcatlett
Copy link
Contributor

This bug was fixed in #2997 but the revert in #3028 re-introduced it. This will block running blt setup drupal:install, displaying accurate blt doctor output, and using any drush alias locally and on Acquia until the fixes in #2997 are re-merged or another approach is implemented. This is a breaking change for deploys and updates.

@lcatlett
Copy link
Contributor

lcatlett commented Dec 5, 2018

this was fixed in #3231

@lcatlett lcatlett closed this as completed Dec 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support A support request
Projects
None yet
Development

No branches or pull requests

3 participants