CiviCRM Community Forums (archive)

I am moving CiviCRM 3.2.3 from a working installation on a subdomain (sub.example.com) to a top-level domain (example.com), running CentOS 5, Apache 2.2, PHP 5.2.10. I have followed the directions here (wiki.civicrm.org/confluence/display/CRMDOC33/Moving+an+Existing+Installation+to+a+New+Server+or+Location) and also here (forum.civicrm.org/index.php?topic=11538.0) but consistently run into a problem at step #6, running example.com/index.php?q=civicrm/admin/setting/updateConfigBackend&reset=1, attempting to get things configured correctly on the new site.

To summarize, I followed steps 1-5 above, doing a clean installation of the same 3.2.3 version of CiviCRM (I'll upgrade once this works), exporting the working database (minus the 5 tables listed), importing the database (which drops the old tables first) on the new server, to the point of clearing out the files under the templates_c directory. So far, so good.

This is where the problems start. I could not load the example.com/index.php?q=civicrm/admin/setting/updateConfigBackend&reset=1 page at all, getting only a white screen with no errors. I have tried to things to fix the problem, neither of which have worked. First, I attempted to edit the "config_backend" field in the `civicrm_domain` table and manually set the new URL (from subdomain to TLD) and correct the filesystem settings. This gets me to the point where I can load the ConfigBackend script, but it generates dozens of errors:

warning: array_key_exists() [function.array-key-exists]: The second argument should be either an array or an object in /var/www/vhosts/example.com/httpdocs/sites/all/modules/civicrm/CRM/Core/BAO/Setting.php on line 182.

The second thing I tried was manually resetting the config_backend:

UPDATE civicrm_domain SET config_backend = null;

Neither of these attempts to resolve the problem have worked, I can get as far as the display of errors but none of the rest of the civicrm webapp works, just white screens.

I have reviewed this forum post (forum.civicrm.org/index.php?topic=15672.0) but was not able to resolve the problem. I have reviewed the civicrm.settings.php and everything appears to be set correctly. File permissions are what they should be, config directories are set correctly.

I am at a loss for what configuration I may be missing. Any help would be greatly appreciated.

I don't 100% follow your first post but I would suggest the following:

1. Install a fresh, empty CiviCRM on your top level domain example.com
2. Replace the CiviCRM (and Drupal) database(s) with your existing one from the subdomain.
3. Run UPDATE civicrm_domain SET config_backend = null;
Then see what happens.

My advice is the same--remove your civicrm.settings.php file from example.com and install a fresh, empty CiviCRM on that site.

Once you have a working CiviCRM there, then just:

1. Replace the CiviCRM database on example.com with your existing one from the subdomain.
2. Run UPDATE civicrm_domain SET config_backend = null;
That should do it.

No need to touch any Drupal DBs.

Still no luck. I switched to Garland but things did not improve. Any ideas?

Okay, trying again from the top, brand new civicrm database, installing CiviCRM 3.3.5 using the installation script to an existing Drupal 6 site that was installed using the Acquia install profile. I'm attempting to put the civicrm module in modules/acquia where all the rest of the custom modules I have installed are located.

Note that this site uses a custom theme without a left sidebar block area, meaning the CiviCRM blocks get disabled after install. I am using the Drupal civicrm_theme module to set Garland as the CiviCRM theme, which appears to work well. I can browse through the CiviCRM install and it looks good. There are no other CiviCRM modules enabled, just the core module and the CiviCRM Theme. Any ideas? Thanks for the help!

But the joy ends when I try to add a new Individual:

DB Error: constraint violation
Database Error Code: Cannot add or update a child row: a foreign key constraint fails (`mysite_civicrm/civicrm_acl_cache`, CONSTRAINT `FK_civicrm_acl_cache_contact_id` FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE), 1452
Additional Details:

Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -3
    [message] => DB Error: constraint violation
    [mode] => 16
    [debug_info] => INSERT INTO civicrm_acl_cache (contact_id , acl_id ) VALUES ( 1 ,  2 )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`mysite_civicrm/civicrm_acl_cache`, CONSTRAINT `FK_civicrm_acl_cache_contact_id` FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE)]
    [type] => DB_Error
    [user_info] => INSERT INTO civicrm_acl_cache (contact_id , acl_id ) VALUES ( 1 ,  2 )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`mysite_civicrm/civicrm_acl_cache`, CONSTRAINT `FK_civicrm_acl_cache_contact_id` FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE)]
    [to_string] => [db_error: message="DB Error: constraint violation" code=-3 mode=callback callback=CRM_Core_Error::handle prefix="" info="INSERT INTO civicrm_acl_cache (contact_id , acl_id ) VALUES ( 1 ,  2 )  [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`mysite_civicrm/civicrm_acl_cache`, CONSTRAINT `FK_civicrm_acl_cache_contact_id` FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE)]"]
)


It was a fresh DB, dropped the db completely, then recreated it. I'm trying again but will give the database a new name as well, though it would be surprising if there was anything residual about the database name when doing a clean installation.

When running the install script, it needs the database, user and password for both the CiviCRM database and the Drupal database. What does it do with the Drupal database? Are any changes made to it that might affect the installation/reinstallation process?

Now I don't even get to the Configuration Checklist page - it loads but has the same DB Error: constraint violation. This is with the brand new CiviCRM database.
Database Error Code: Cannot add or update a child row: a foreign key constraint fails (`mysite_civicrm3/civicrm_acl_cache`, CONSTRAINT `FK_civicrm_acl_cache_contact_id` \
FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE), 1452

What is the wisdom of continuing with the system in example.com, recreating user accounts on the Drupal side, giving them the appropriate permissions for CiviCRM and pretending nothing happened?

Worse sins have and will be committed so I wouldn't worry too much.

Seriously, however, the backend settings do not necessarily preclude basic features from working. Since actually all settings in your backend should be compatible for both sites (directories and URLs exist for both sites) except the base URL, it should be OK to do what you are doing. I think so anyhow.

Perhaps it's wisest to get another opinion. You might want to post another thread to gain fresh attention.