Skip to main content
Updated to current state
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
RecentlyEvery last patch Magento EE 1.14.2 washas also released new versions of Magento CE and I checked ifEE already containing the changes inspecific latest patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE See the (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to downloadRelease Archive tab on theirthe download pageMagento download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the Check this sheet, maintained by JH, for which patches to install for which Magento CE 1.9.2and EE version,: released somewhere in June/July.https://docs.google.com/spreadsheets/d/1MTbU9Bq130zrrsJwLIB9d8qnGfYZnkm4jBlfNaBF19M

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
Recently Magento EE 1.14.2 was released and I checked if the changes in patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to download on their download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the CE 1.9.2 version, released somewhere in June/July.

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE:
Every last patch Magento has also released new versions of Magento CE and EE already containing the specific latest patch. See the Release Archive tab on the Magento download page.

Check this sheet, maintained by JH, for which patches to install for which Magento CE and EE version: https://docs.google.com/spreadsheets/d/1MTbU9Bq130zrrsJwLIB9d8qnGfYZnkm4jBlfNaBF19M

replaced http://magento.stackexchange.com/ with https://magento.stackexchange.com/
Source Link

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
Recently Magento EE 1.14.2 was released and I checked if the changes in patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to download on their download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the CE 1.9.2 version, released somewhere in June/Julyreleased somewhere in June/July.

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
Recently Magento EE 1.14.2 was released and I checked if the changes in patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to download on their download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the CE 1.9.2 version, released somewhere in June/July.

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
Recently Magento EE 1.14.2 was released and I checked if the changes in patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to download on their download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the CE 1.9.2 version, released somewhere in June/July.

added 61 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch formatunified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
Recently Magento EE 1.14.2 was released and I checked if the changes in patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to download on their download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the CE 1.9.2 version, released somewhere in June/July.

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
Recently Magento EE 1.14.2 was released and I checked if the changes in patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to download on their download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the CE 1.9.2 version, released somewhere in June/July.

Applying patches manually with no SSH access

You have a good point here. The patches are supplied as .sh files and there is no solution offered by Magento for FTP only websites.

I suggest one would copy his website's code to a local environment through FTP (you would probably have that already). Then apply the patch by running the .sh file.

Now you need to find out which files you need to upload again. If you would open the .sh patch file, then you will see it consist of two sections:

  1. Bash shell code to apply the patch. This code is general for every patch.
  2. The actual patch in the form of a unified patch format. This indicates only the lines in files that were changed (including some context lines). This starts below the line __PATCHFILE_FOLLOWS__

From the second section you could read which files were/are affected by the patch. You need to upload these files again to your FTP or... you could just upload everything.

Applying manually without bash/shell

  1. If you can't run .sh files (in Windows), then you could extract the second section of the patch (the unified patch) and apply it manually with a patching tool (or for example through PHPStorm).
  2. The website Magentary.com provides ZIP files for each Magento version containing the patched files only.

Patches in current & future releases?

The patches that are released right now apply to all versions that were already released. Of course, might Magento release a new version (major or minor). Then they will contain all security patches as Magento will also apply the patches to their development code base naturally (these patches even originate from that code base ;)).

UPDATE (Apr 29):
Recently Magento EE 1.14.2 was released and I checked if the changes in patch SUPEE-5344/SUPEE-5345 were in it and they are...

UPDATE (May 4):
Magento has patched CE 1.9.1 as new patch version CE 1.9.1.1 and made it available to download on their download page.

UPDATE (May 15):
Magento has release patch SUPEE-5994. This is not in the latest EE 1.14.2 version and not in the latest CE 1.9.1.1 patch version. It will be in the CE 1.9.2 version, released somewhere in June/July.

Added update around SUPEE-5994
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 105 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 43 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 191 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 8 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 221 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 149 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 51 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
deleted 3 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
added 102 characters in body
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading
Source Link
7ochem
  • 7.6k
  • 14
  • 52
  • 80
Loading