Home ›
User could not connect to database in making a site with a there-then-missing installation profileUser could not connect to database in making a site with a there-then-missing installation profile
Submitted by Benjamin Melançon on September 20, 2007 - 1:06am
OK, you're not likely to run into this problem.
However, if you do things the Agaric way, and point a domain at a server, and Apache sends it to a valid Drupal installation with a custom installation profile option, and you select that installation profile, and then realize you really want Apache pointing your domain to a different, 5.2 installation.
You may get an error about the user being rejected for the database table. And you can keep trying this page with reset passwords and anything and keep getting the same error. It's weird, but that's what happened to us.
Of course, it's 2 a.m., and we may be hallucinating.
It's the Agaric way.
Resolution
More like this
- On the site as connection space, user interface drafts
- Steps to Follow on All Agaric Sites (default configuration destined for an installation profile)
- Install profiles don't work in nested subdirectories
- Migrating a Shared-user Multisite install
- Five second Feature Server with drush_make my install profile | mig5.net


Comments
Post new comment