CiviCRM Community Forums (archive)

http://forum.civicrm.org/index.php/topic,18537.0.html documents the saga of trying to move a functioning CiviCRM 3.3.5 installation from Drupal 6 on subdomain.example.com to a functioning Drupal 6 on example.com. Short story: I never did figure out what was causing the WSOD and bizarre foreign key constraints on clean installations using fresh databases. After installing CiviCRM 3.3.5 cleanly on example.com there were foreign key constraint errors that I could not resolve, but when I switched the CiviCRM settings in civicrm.settings.php on the example.com server to use the working CiviCRM database in use at subdomain.example.com (same db, user and password), everything appears to be working as expected... from both sites. Records created from the example.com/civicrm are visible in subdomain.example.com/civicrm.

The ConfigBackend script form both sites reflects the correct values for those sites (though the site name is /sites/default/ for both, but I am not going to mess with that at the moment), with the URL and base directory correctly reflecting the different settings for the TLD site and the subdomain site.

I intend to shutdown the subdomain.example.com site as soon as I have created all the user accounts on the example.com Drupal server and linked them to the correct accounts in the CiviCRM database. Here's my question:

Should I expect bad things to happen at some undefined point in the future if I simply continue on with the example.com/civicrm setup? Or if it is working now, should it continue to work as expected?