1   2   3

5. Testing patch applicability (Step 1 of 2). First, X-Cart will check the presence of executable permissions for the patch tool, then patch checksums and permissions for each file the upgrade patch must be applied to. In progress this check will look something like this:

Picture 3: Testing patch applicability (write permissions are not set).

Then the results of patch applicability testing will be shown to you in the 'Applying patch' form.

Picture 4: Applying patch (Step 1 of 2: Testing patch applicability and generation of a list of files).

If your Patch/Upgrade center detects any problems (errors - marked in red), you will not be able to proceed with upgrading your X-Cart software until these problems are resolved. You will have to go back, make the necessary corrections and run the patch applicability test once again.

In our case the problem is the absence of write permissions for the files that need to be patched. To set write permissions on Unix-based servers with a terminal access, issue the command:

> chmod 0666 script_file.php

If you have FTP access only, set write permissions using your FTP client.

After write permissions for all the necessary files have been set, next time you run the patch applicability test, it will look something like this:

Picture 5: Testing patch applicability (write permissions are set).

If no more problems are encountered during the test, the test results will look something like this:

Picture 6: Applying patch (Step 1 of 2: Testing patch applicability and generation of a list of files).

This is the conclusion of the testing stage. Now you can proceed to actually applying your upgrade patch. Click on Apply patch to go to the following step in the upgrade process.

But what if after setting write permissions you still get errors?

For example, you have set the necessary write permissions. While running the patch applicability test you get the 'could not patch' error:

Picture 7: Testing patch applicability ('could not patch' error).

The applicability test results warn you that during the test some files got the status 'could not patch', which means that the upgrade patch cannot be applied to these files automatically.

Picture 8: Applying patch (Step 1 of 2: Testing patch applicability and generation of a list of files).

At this point it should be noted that an upgrade patch includes several hunks. It means that even though one or more files got the status 'could not patch', you still can try to automatically apply at least some of the patch hunks to these files. If you want to try this option, select the 'Tick here if you want to try to apply the patch to these files' check box (that is what we have done in our example).

Again, it is the conclusion of the testing stage. Now you can proceed to actually applying your upgrade patch. Click on Apply patch to go to the following step in the upgrade process.

If in the process of testing patch applicability one or more files get 'already patched' status, there is nothing wrong with it and you can continue with the upgrade.

Picture 9: Testing patch applicability ('already patched' warning).

Revision date: Jan 31, 2006

1   2   3