Scholarly:Upgrade to version 2.1.1 for Drupal 7

From MtTWiki

This document will guide you to upgrade your Drupal 7 Scholarly 2.0.1 installation to Scholarly 2.1.1 for Drupal 7.

The steps that are tagged [Commerce] are relevant only to the Scholarly Commerce 7.x distribution and should be skipped if you are running the simple Scholarly 7.x distribution. The Scholarly Commerce 7.x distribution is only available in the Scholarly Pro & Scholarly Enterprise products. You can find out more about the Scholarly Commerce distribution at the Scholarly product page http://www.morethanthemes.com/?q=themes/scholarly

Prepare your workbench

1. Create a temporary installation of Drupal 7 Scholarly 2.1.1 using our installation profile. You will use this as a reference to guide you.

Backup

1. Backup everything.
2. Just in case, make sure you backed up everything =) (besides, it's always a good idea).

Put your website in maintenance mode

1. Login to your Drupal installation as administration user
2. Navigate to admin/config/development/maintenance
3. Enable the "Put site into maintenance mode" option
4. Save your configuration

Update Drupal core

Take a breath and read Drupal's Upgrading from previous versions first. This upgrade will update your Drupal core to the version 7.39. We assume that you are currently using a 7.x version so it's about a "Minor update procedure".

1. Locate the root folder of your site. This is Drupal's root folder, where the index.php file is located.
2. Delete all Drupal files and folders except the [sites] folder.
3. Copy all Drupal files and folders from your temporary installation except the [sites] folder.
4. Run the update.php file calling a url like http://www.example.com/update.php or http://www.example.com/test_site/update.php, if your site is located under a subdirectory.

Update extra modules

Scholarly comes with several extra modules required to achieve its functionality. The following process will update them to the latest (by the time these lines are written) version, as marked below:

• Update Chaos tool suite (ctools) to latest version 7.x-1.9
• Update Date (date) to latest version 7.x-2.9
• Update Entity API (entity) to latest version 7.x-1.6
• Update Field Group (field_group) to latest version 7.x-1.3
• Update jQuery Update (jquery_update) to latest version 7.x-2.6
• Update Twitter (twitter) to latest version 7.x-5.10
• Update Views (views) to latest version 7.x-3.11
• Update Webform (webform) to latest version 7.x-3.24

1. Locate the extra modules folder of your site, usually at [sites/all/modules].
2. Delete the folders ctools, date, entity, field_group, jquery_update, twitter, views, webform that belong to the Scholarly distribution. If there are any extra module folders that have been installed by you later, you should leave them untouched or update them later manually, which is beyond the scope of this guide
3. Copy the latest version of the deleted module from your temporary installation.
4. Run the update.php file calling a url like http://www.example.com/update.php or http://www.example.com/test_site/update.php, if your site is located under a subdirectory.

[Commerce] Update Commerce modules

Scholarly comes with several extra Commerce modules required to achieve its functionality. The following process will update them to the latest (by the time these lines are written) version, as marked bellow:

• [Commerce] Update Address Field (addressfield) to latest version 7.x-1.1
• [Commerce] Update Drupal Commerce (commerce) to latest version 7.x-1.11
• [Commerce] Update Rules (rules) to latest version 7.x-2.9

1. Locate the extra modules folder of your site, usually at [sites/all/modules/contrib].
2. Delete the folders , addressfield, commerce, rules that belong to the Scholarly distribution. If there are any extra module folders that have been installed by you later, you should leave them untouched or update them later manually, which is beyond the scope of this guide.
3. Copy the latest version of the deleted module from your temporary installation.
4. Run the update.php file calling a url like http://www.example.com/update.php or http://www.example.com/test_site/update.php, if your site is located under a subdirectory.

Patch your Scholarly theme files

1. Locate our theme folder in your temporary installation. Usually at [sites/all/themes/scholarly]
2. Locate our theme folder in your drupal 7 site. Usually at [sites/all/themes/scholarly]
3. Add the following file in your installation, using the corresponding source file from the temporary installation

• js/jquery.browser.min.js

1. Replace the following files or folders in your installation, using the corresponding source files from the temporary installation (folders should be first deleted and finally copied from your temp installation).

• node--mt_event.tpl.php
• node.tpl.php
• scholarly.info
• style.css
• template.php
• theme-settings.php
• bootstrap
• fonts

Update your Scholarly theme configuration

The following process will ensure that the correct version of jQuery is selected.

1. Navigate to admin/config/development/jquery_update
2. Select the 1.10 option of the Default jQuery version select box
3. Select the 1.7 option of the Alternate jQuery version for administrative pages select box
4. Save your configuration

Import/Update views

1. Go to Home » Administration » Structure » Views in your temporary installation.
2. Export (OPERATIONS select list) each of the following views (View name [machine_name]) and import those to your installation by selecting the option "Replace an existing view if one exists with the same name". Make sure to save the changes after the import.

• Courses [courses]
• Events [events]
• Faculty Staff [faculty_staff]
• Features [mt_features]
• Featured articles [mt_latest_news]
• Students [students]

Clear all cached data

This step is important in order to force your template to be informed for the changes you have made in the template files.

To do this navigate to admin/config/development/performance and click the "Clear all caches" button

Disable maintenance mode

1. Navigate to admin/config/development/maintenance
2. Disable the "Put site into maintenance mode" option.
3. Save your configuration