CiviCRM Community Forums (archive)

I have been running 3.1 w/ Drupal 6 on a PHP 5.2 server. The server essentially went up in flames, and we were forced on short notice to bring in a new server. The server is great except it's PHP 5.3, so we've got to upgrade Civi (we've been waiting because we have quite a few custom modules reliant on Civi, as well as some custom ubercart integration with it).

I've now got a dev server on a separate url up and running with my Drupal site on PHP 5.3. Now I want to upgrade Civi. Problem is, config_backend db var still has all the configs set to my live site url. And if I try to run the script to fix it (/index.php?q=civicrm/admin/setting/updateConfigBackend&reset=1), I can't submit that page of course because of PHP 5.3 not being compatible with Civi 3.1 and I get a fatal error. And if I set config_backend = NULL and clear my templates and all, it doesn't take on the Civi side again and after hitting any other page that var gets set to 'N;' in the db instead of getting filled correctly, and my Global Settings Resource URLs and directories still reflect the live site.

How can I proceed so that I can test my upgrades on this dev server?

Thanks so much,
Emily