CiviCRM Community Forums (archive)

Moving a CiviCRM/Drupal site to a new location is an excruciating experience. And it may actually be getting worse. At this point, I'm up to at least three things that have to be done under the hood to successfully move an installation (or do a test restore from a backup, which is something we should all be doing periodically):

1. Manually NULL civicrm_domain.config_backend in the database.
2. Clean out files/civicrm/templates_c
3. Delete files/civicrm/upload/Config.IDS.ini (which I only had to start doing recently)

Apparently there's a fourth thing as well, because the main CiviCRM menu is cached somewhere. I get it to update to the new URLs eventually, but I'm not sure how. It's possible the cache just finally expires overnight.

Is there any way CiviCRM could notice that it has moved and instead of crashing and burning in several imaginative ways say "You appear to have moved this installation. Would you like me to update our internal state to complete the move?"