header

Information About Enterprise Edition (EE) Patches for Apache Solr

This article lists patches that Magento Support has made available for Magento EE versions 1.10.1.0 and later. The patches themselves are available on the Magento EE support portal.

To get the patches:

  1. Log in to http://magento.com with your Magento EE credentials.
  2. Click Downloads in the left navigation.
  3. In the right pane, expand Magento Enterprise Edition 1.x.
  4. Expand Support Patches and Security Patches > Solr Search Engine patches.

Following is a list of available patches:

Magento EE Solr Patch for EE 1.12.0.x (ID: SUPEE-111)

Magento EE Version(s) Affected

This fix affects Magento EE 1.12.0.0, 1.12.0.1, and 1.12.0.1

Issues Fixed in the Magento EE 1.12.0.x Patch

Installation Instructions

To install this fix:

  1. Stop Solr if it's currently running.
  2. Download the patch .sh and transfer it to your Magento installation root directory.
    For example, /var/www/html/magento.
  3. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-111_EE_1.12.0.0_v6.sh

    Note: The patch version—indicated by _v6 in this example—is subject to change. The version you get might be different.
    A message such as the following displays to confirm the patch installed successfully:
    Patch was applied/reverted successfully.
  4. To reapply ownership to the files changed by the patch:
    1. Find the web server user: ps -o "user group command" -C httpd,apache2
      The value in the USER column is the web server user name.
      Typically, the Apache web server user on CentOS is apache and the Apache web server user on Ubuntu is www-data.
    2. As the owner of the files in the Magento installation directory or as a user with root privileges, enter the following command from the Magento installation directory:
      chown -R web-server-user-name . For example, on Ubuntu where Apache usually runs as www-data, enter chown -R www-data .
  5. Copy the updated configuration files from Magento to your Solr configuration directory.
    1. Back up the files in your current Solr configuration directory.
    2. Enter the following command:
      cp magento-install-root/lib/Apache/Solr/conf/* solr-config-dir
      For example, if Magento is installed in /var/www/magento and Solr configuration files are located in /etc/apache-solr-3.5.0/mysolrapp/solr/conf, enter
      cp /var/www/magento/lib/Apache/Solr/conf/* /etc/apache-solr-3.5.0/mysolrapp/solr/conf
  6. Start Solr.
  7. Log in to the Admin Panel as an administrator.
  8. Click System > Cache Management.
  9. Click Flush Magento Cache.
  10. Click System > Configuration.
  11. In the left navigation bar, from the CATALOG group, click Catalog.
  12. In the right pane, expand Catalog Search.
  13. From the Indexation Mode list, click Final Commit.
    This is the setting Magento recommends. For a description of the other options, see the Magento EE User Guide.
  14. Click System > Index Management.
  15. Click the Reindex Data link in the Catalog Search row.
  16. Reindex other indexers if necessary.

Reverting the Patch

If applying the patch results in errors, contact Magento Support. If you are instructed to do so, revert the patch:

  1. Change to your Magento installation directory.
  2. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-111_EE_1.12.0.0_v6.sh -R

Troubleshooting

If you get an error when you run the patch, use the following suggestions:

Magento EE Solr Patch for EE 1.11.1.0 (ID: SUPEE-107)

Magento EE Version(s) Affected

This fix affects Magento EE 1.11.1.0.

Issues Fixed in the Magento EE 1.11.1.0 Patch

Installation Instructions

To install this fix:

  1. Stop Solr if it's currently running.
  2. Download the patch .sh and transfer it to your Magento installation root directory.
    For example, /var/www/html/magento.
  3. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-107_EE_1.11.1.0_v1.sh

    Note: The patch version—indicated by _v6 in this example—is subject to change. The version you get might be different.
    A message such as the following displays to confirm the patch installed successfully:
    Patch was applied/reverted successfully.
  4. To reapply ownership to the files changed by the patch:
    1. Find the web server user: ps -o "user group command" -C httpd,apache2
      The value in the USER column is the web server user name.
      Typically, the Apache web server user on CentOS is apache and the Apache web server user on Ubuntu is www-data.
    2. As the owner of the files in the Magento installation directory or as a user with root privileges, enter the following command from the Magento installation directory:
      chown -R web-server-user-name . For example, on Ubuntu where Apache usually runs as www-data, enter chown -R www-data .
  5. Copy the updated configuration files from Magento to your Solr configuration directory.
    1. Back up the files in your current Solr configuration directory.
    2. Enter the following command:
      cp magento-install-root/lib/Apache/Solr/conf/* solr-config-dir
      For example, if Magento is installed in /var/www/magento and Solr configuration files are located in /etc/apache-solr-3.5.0/mysolrapp/solr/conf, enter
      cp /var/www/magento/lib/Apache/Solr/conf/* /etc/apache-solr-3.5.0/mysolrapp/solr/conf
  6. Start Solr.
  7. Log in to the Admin Panel as an administrator.
  8. Click System > Cache Management.
  9. Click Flush Magento Cache.
  10. Click System > Configuration.
  11. In the left navigation bar, from the CATALOG group, click Catalog.
  12. In the right pane, expand Catalog Search.
  13. From the Indexation Mode list, click Final Commit.
    This is the setting Magento recommends. For a description of the other options, see the Magento EE User Guide.
  14. Click System > Index Management.
  15. Click the Reindex Data link in the Catalog Search row.
  16. Reindex other indexers if necessary.

Reverting the Patch

If applying the patch results in errors, contact Magento Support. If you are instructed to do so, revert the patch:

  1. Change to your Magento installation directory.
  2. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-107_EE_1.11.1.0_v1.sh -R

Troubleshooting

If you get an error when you run the patch, use the following suggestions:

Magento EE Solr Patch for EE 1.11.0.x (ID: SUPEE-108)

Magento EE Version(s) Affected

This fix affects Magento EE 1.11.0.0, 1.11.0.1, and 1.11.0.2.

Issues Fixed in the Magento EE 1.11.0.x Patch

Installation Instructions

To install this fix:

  1. Stop Solr if it's currently running.
  2. Download the patch .sh and transfer it to your Magento installation root directory.
    For example, /var/www/html/magento.
  3. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-108_EE_1.11.0.2_v1.sh

    Note: The patch version—indicated by _v1 in this example—is subject to change. The version you get might be different.
    A message such as the following displays to confirm the patch installed successfully:
    Patch was applied/reverted successfully.
  4. To reapply ownership to the files changed by the patch:
    1. Find the web server user: ps -o "user group command" -C httpd,apache2
      The value in the USER column is the web server user name.
      Typically, the Apache web server user on CentOS is apache and the Apache web server user on Ubuntu is www-data.
    2. As the owner of the files in the Magento installation directory or as a user with root privileges, enter the following command from the Magento installation directory:
      chown -R web-server-user-name .
      For example, on Ubuntu where Apache usually runs as www-data, enter
      chown -R www-data .
  5. Copy the updated configuration files from Magento to your Solr configuration directory.
    1. Back up the files in your current Solr configuration directory.
    2. Enter the following command:
      cp magento-install-root/lib/Apache/Solr/conf/* solr-config-dir
      For example, if Magento is installed in /var/www/magento and Solr configuration files are located in /etc/apache-solr-3.5.0/mysolrapp/solr/conf, enter
      cp /var/www/magento/lib/Apache/Solr/conf/* /etc/apache-solr-3.5.0/mysolrapp/solr/conf
  6. Start Solr.
  7. Log in to the Admin Panel as an administrator.
  8. Click System > Cache Management.
  9. Click Flush Magento Cache.
  10. Click System > Configuration.
  11. In the left navigation bar, from the CATALOG group, click Catalog.
  12. In the right pane, expand Catalog Search.
  13. From the Indexation Mode list, click Final Commit.
    This is the setting Magento recommends. For a description of the other options, see the Magento EE User Guide.
  14. Click System > Index Management.
  15. Click the Reindex Data link in the Catalog Search row.
  16. Reindex other indexers if necessary.

Reverting the Patch

If applying the patch results in errors, contact Magento Support. If you are instructed to do so, revert the patch:

  1. Change to your Magento installation directory.
  2. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-108_EE_1.11.0.2_v1.sh -R

Troubleshooting

If you get an error when you run the patch, use the following suggestions:

Magento EE Solr Patch for EE 1.10.1.x (ID: SUPEE-110)

Magento EE Version(s) Affected

This fix affects Magento EE 1.10.1.0 and 1.10.1.1.

Issues Fixed in the Magento EE 1.10.1.x Patch

Installation Instructions

To install this fix:

  1. Download the patch .sh and transfer it to your Magento installation root directory.
    For example, /var/www/html/magento.
  2. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-110_EE_1.10.1.1_v2.sh

    Note: The patch version—indicated by _v2 in this example—is subject to change. The version you get might be different.
    A message such as the following displays to confirm the patch installed successfully:
    Patch was applied/reverted successfully.
  3. To reapply ownership to the files changed by the patch:
    1. Find the web server user: ps -o "user group command" -C httpd,apache2
      The value in the USER column is the web server user name.
      Typically, the Apache web server user on CentOS is apache and the Apache web server user on Ubuntu is www-data.
    2. As a user with root privileges, enter the following command from the Magento installation directory:
      chown -R web-server-user-name .
      For example, on Ubuntu where Apache usually runs as www-data, enter
      chown -R www-data .
  4. If Solr is running, stop it.
  5. Copy the updated configuration files from Magento to your Solr configuration directory.
    1. Back up the files in your current Solr configuration directory.
    2. Enter the following command:
      cp magento-install-root/lib/Apache/Solr/conf/* solr-config-dir
      For example, if Magento is installed in /var/www/magento and Solr configuration files are located in /etc/apache-solr-3.5.0/mysolrapp/solr/conf, enter
      cp /var/www/magento/lib/Apache/Solr/conf/* /etc/apache-solr-3.5.0/mysolrapp/solr/conf
  6. Start Solr.
  7. Log in to the Admin Panel as an administrator.
  8. Click System > Cache Management.
  9. Click Flush Magento Cache.
  10. Click System > Configuration.
  11. In the left navigation bar, from the CATALOG group, click Catalog.
  12. In the right pane, expand Catalog Search.
  13. From the Indexation Mode list, click Final Commit.
    This is the setting Magento recommends. For a description of the other options, see the Magento EE User Guide.
  14. Click System > Index Management.
  15. Click the Reindex Data link in the Catalog Search row.
  16. Reindex other indexers if necessary.

Reverting the Patch

If applying the patch results in errors, contact Magento Support. If you are instructed to do so, revert the patch:

  1. Change to your Magento installation directory.
  2. Enter the following command as a user with sufficient privileges to write to Magento files (typically, the web server user or root):
    sh PATCH_SUPEE-110_EE_1.10.1.1_v2.sh -R

Troubleshooting

If you get an error when you run the patch, use the following suggestions: