I am finally upgrading the CiviCRM on a website I didn't develop. It is running on Drupal 7.50, (upgraded from 7.37), and is currently version 4.3.8. Planning to upgrade to 4.7.13.
Here's the thing: it was set up outside of the Drupal docroot, using symlinks and some other setting changes. It works, but it's more complex than the usual setup. Due to the already heavy nature of our Drupal site, it is my understanding that this setup would help with performance issues. I want to both upgrade it and move it into the Drupal sites/all/modules directory.
Aside from the usual steps to perform the upgrade up so many versions, I wanted to see if anyone could anticipate any upgrade problems I might have and evaluate my plan outlined below to complete the upgrade, due to this unique situation? Let me know if this is out of the scope of this forum, and I'll remove it, though it might be helpful if someone else finds themselves in the same boat. I am going to try these steps out on a dev copy before attempting it on production.
CiviCRM root is in /var/www/html along with our Drupal Docroot, and all components are as such:
Symlink to Codebase:
<drupal home>/sites/all/modules/civicrm -> <civicrm root>/v.4.3.8-d7
define( 'CIVICRM_CONFDIR', '/var/www/html/drupal/docroot/sites' );
Back up the Drupal and CiviCRM codebase and database into '/var/www/html/backups'
Login to Drupal site and put website into maintenance mode; stay logged in
Disable Drupal CiviCRM integration modules
*Delete symlink in
<drupal home>/sites/defaultdirectory writeable to the server
Download and unpack v4.7.13 to
Backup and move civicrm.settings.php file
Clear browser cache and all files in
Run the install:
http://<drupal home>/civicrm/upgrade?reset=1(for clean URLS)
Update the CiviCRM Resource URL
Re-enable Drupal CiviCRM integration modules
Check Drupal role settings
Pull the site out of maintenance mode
*extra or modified steps I added to the usual ones listed in the upgrade guide: