Skip to end of metadata
Go to start of metadata

Step 1 - Create the patch with the admin patcher page

Login as admin, go to "Patcher" > "Create Patch";
1. Login as admin, go to "Patcher" > "Create Patch";
2. A few things to note at filling in the blanks:

  • How to find out "ATutor Patch ID": go to http://update.atutor.ca/patch/2_0_3/patch_list.xml, find the highest atutor_patch_id and increment by 1.
  • At adding a file that is NOT in the ATutor root directory in which case the "Directory" field is left empty, don't forget the ending back slash (tick) . ToDo: The patcher script can be improved to handle this.
  • When adding a file at "alter" mode, make sure the uniqueness of the "Code To Replace From".

3. Click on "Save" button to download the patch zip file.

Step 2 - Test the patch

1. Test at the own localhost ATutor

  • Produce the bug(s) that is(are) intended to be fixed by the patch;
  • Login as ATutor admin, go to "Patcher", at "upload the patch zip file", upload and apply the patch;
  • Re-test to make sure the bug(s) haven been fixed.

Step 3 - Publish the patch

1. Go to http://atutor.ca, login as admin;
2. Select the link "ATutor Administrator" -> ATutor Patch Upload;
3. Upload the patch;
4. Done. Now all the ATutor installations are able to see this published patch thru their admin "Patcher" page.

Step 4 - Test the published patch

1. Test at the own localhost ATutor

  • Locate the scripts that have been modified by the patcher at the previous patch test, revert the modifies by overwriting them with the backup files that were created by the patcher in the previous test;
  • Repeat the procedure at "Step 2" to test the published patch.

2. Repeat the above steps at ATutor demo site (http://atutor.ca/atutor/demo/login.php) to apply the published patch, which is also a good test case.

Step 5 - Push the fixes up to the github and close the mantis bug report

  • No labels