Magento 1.x Software Support Notice

For Magento Commerce 1, Magento is providing software support through June 2020. Depending on your Magento Commerce 1 version, software support may include both quality fixes and security patches. Please review our Magento Software Lifecycle Policy to see how your version of Magento Commerce 1 is supported.

For Magento Open Source 1.5 to 1.9, Magento is providing software security patches through June 2020 to ensure those sites remain secure and compliant. Visit our information page for more details about our software maintenance policy and other considerations for your business.

Magento Enterprise Edition (EE) Release Notes (1.13 and later)

Table of Contents

These Release Notes contain the following information:

Patches for Multiple Magento EE Versions

Magento has the following patches available for multiple Magento EE versions.

noteNote: Some of the patches discussed in this section have EE_1.14.0.1 in the name. These patches were all tested against EE 1.13.x as well.

General Magento Connect Patches

Patch name: PATCH_SUPEE-3941_EE_1.14.0.1_v1-2014-08-12-12-10-06.sh

Magento Install Page Displays After SOAP v2 Index Page Refresh

Patch name: PATCH_SUPEE-3762_EE_1.14.0.1_v1.sh. Refreshing the SOAP v2 index page (http://your-magento-host-name/index.php/api/v2_soap/index/) results in all administrators and customers viewing the Magento installation page.

Multiple Simultaneous Magento Administrators

Patch name: PATCH_SUPEE-3819_EE_1.14.0.1_v1.sh. Multiple Magento administrators can simultaneously add new products; or edit descriptions, edit prices, or edit stock quantities of existing products without causing deadlocks, key violations, or critical data errors. Together with applying the patch, you must set all indexers to Update when scheduled as follows:

  1. Log in to the Magento Admin Panel as an administrator.
  2. Click System > Configuration.
  3. In the left navigation bar, from the ADVANCED group, click Index Management.
  4. Expand Indexing Options.
  5. From each list, click Update when scheduled.
  6. Click Save Config in the upper right corner of the page.

Discover Card Validation Patch Available

Magento has fixed an issue that prevented some Discover credit cards from validating properly. The issue was that certain Discover credit card number ranges were not recognized as being valid. As a result of the fix, all Discover cards should validate properly.

The issue affects EE versions through

To get a fix for the issue, see Discover credit card validation issue: Magento EE– and CE–

importantImportant: This is not a security threat. No data has been compromised or misused. It affects only the ability to validate certain credit card number ranges as valid Discover card numbers.

PHP 5.4 Patch Available

You can use PHP 5.4 with Magento EE versions–

To get the patch, see Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community Edition (CE).

For more information about PHP 5.4, see the PHP migration page and the PHP changelog.

How to get Patches for Magento EE

This section discusses how to get patches referenced in these Release Notes. Magento has other patches available from the EE support portal and the partner portal; you can use the following instructions to install any of those patches as well.

To get patches for Magento EE:

  1. Log in to www.magentocommerce.com.
  2. In the left pane, click Downloads.
  3. In the right pane, click Magento Enterprise Edition.
  4. Follow the prompts on your screen to download a patch for your version of EE.
  5. Apply the patch as discussed in How to Apply and Revert Magento Patches.

Magento EE Release Notes

See the following sections for information about changes in this release:


Magento EE helps advance overall product quality and ease operations by providing significant tax calculation improvements, a wide range of bug fixes, and several security enhancements.

Tax Calculation Improvements

EE resolves Value Added Tax (VAT) and Fixed Product Tax (FPT) issues so that Magento administrators can create invoices and credit memos to give merchants merchants access to accurate and consistent tax calculations and displays. We've also addressed:

Functional Improvements

EE includes bug fixes across important feature areas, including the shopping cart, checkout, content management system, and product import and export function. Many of these updates came from a hackathon held with Magento community developers, which demonstrates the vitality of our development community and their powerful ability to help us advance the platform.

Security Enhancements

EE includes several security enhancements that were identified through our rigorous security assessment process. Magento complements its own comprehensive internal testing with quarterly penetration testing by expert consultants and actively works with the development community to identify security issues in order to harden the platform against potential threats.

Security Enhancements

Magento addressed the following security issues:

Potential Issue After Upgrading to EE

There is a known issue after upgrading to EE 1.13.1 that affects you only if you do not follow the recommended procedure to upgrade to a new environment as discussed in Getting Ready For Your Upgrade.

Symptom: After completing the upgrade, when you log in to the Admin Panel and click System > Configuration, a fatal error similar to the following displays in your browser:

Class 'Mage_Googlecheckout_Helper_Data' not found in /var/www/html/magento/app/Mage.php on line 547


  1. Close the Admin Panel browser window.
  2. As a user with root privileges, delete all files except config.xml from the following directory:
  3. When you log back in to the Admin Panel, everything works as expected.
    If you're still encountering errors, see Getting Help With Your Installation or Upgrade.

Changes in This Release

See the following sections for a discussion of changes in this release:

Tax Calculation Fixes

Tax calculation issues can be divided into the following sections:

General Tax Notes

The following general fixes were made to Magento tax configuration and calculations:

Rounding Issues

The following tax rounding issues were resolved:

Display Issues

The following issues relate to the incorrect display of tax information in the Admin Panel or in your Magento web store:

Bundled Products Issues

Fixed Product Tax (FPT) Issues

Fixes in Magento EE

Fixes in this release can be divided into the following categories:

  • Shopping Cart and Checkout Fixes
  • Import and Export Fixes
  • Shipping Fixes
  • Payment Fixes
  • Other Fixes
  • Shopping Cart and Checkout Fixes

    Import and Export Fixes

    Shipping Fixes

    Payment Fixes

    Other Fixes

    Magento EE Release Notes

    In response to customer feedback about EE and EE, Magento has modified the functionality to smooth the migration path from earlier EE versions and support duplicate category URL keys.

    See the following sections for a discussion of changes in this release:


    Search Engine Optimization in Magento EE

    This section discusses how search engine optimization (SEO) works in EE This section is not intended to be a tutorial on SEO.

    See one of the following for more information:

    Comparing EE with EE

    The following sections quickly summarize the changes you'll see in EE

    Product URL key uniqueness

    The main difference introduced in EE is that product URL keys must be globally unique among all websites, stores, and views. You can no longer have two different products that have the same URL key.
    A single URL leads uniquely to a product page.

    In EE 1.12, it was possible to have multiple products with the same URL key; however, every time the indexer ran, it silently assigned a numerical suffix to duplicates (for example, shoes became shoes-1 and so on).

    Every time this happened, another URL rewrite was created, resulted in a set of chained redirects for the same product. Having multiple URLs for a product dilutes the effectiveness of URL in search engine weightings, especially if you enabled canonical URLs. (As discussed in this article on Google's blog, a canonical URL is a public specification of your preferred URL. The canonical URL is used by any search engine when crawling and indexing your site.)

    This behavior was not clear to merchants and had the effect of diluting search engine weightings.

    In EE, there is a single, unique way to access a product (or multiple ways if you use the category path in URLs).

    No more chained redirects

    Magento addressed the indexer issue that resulted in suffixes being silently added to products with duplicate URL keys. In EE, duplicate URL keys are not allowed.
    Search engines recognize the canonical URL, which improves the product's weighting in search results. (All of the weighting goes to the canonical URL.)

    Per-entity indexing

    EE uses per-entity indexing that indexes custom URL redirects, categories, and products—as opposed to a global indexer.

    Similar to chained redirects, in EE 1.12, if a product had the same URL key as its parent category, the indexer assigned an incrementing numeric suffix to either the category or the product. This was done without the merchant's knowledge and was confusing as well.


    In EE 1.12, if you named a top-level category slippers and had product also named slippers, the indexer allowed to access to the category using a URL like the following: http://www.example.com/slippers-1

    In EE, the same product can be accessed using a URL like: http://www.example.com/slippers

    There is a new Admin Panel setting to specify how indexing should be prioritized. This setting, System > Configuration > CATALOG > Catalog > Search Engine Optimizations > Priority for Duplicated URL Keys, is discussed in more detail in Prioritizing URL Resolution.

    URL Key Uniqueness Rules in Magento EE

    The following entities can be indexed and therefore have a requirement for URL key uniqueness:

    Uniqueness rules for each entity type follow:

    Entity type Uniqueness rule
    Product, including custom URL redirects All product URL keys must be globally unique.

    Category URL keys must be unique only in the same level in the hierarchy; for example

        root category
          store view
            category tree
              *category name*

    Note: Uniqueness rules apply to inactive categories as well. You cannot use the same URL key for both an active and inactive category at the same level in the category hierarchy.

    CMS CMS URL keys, like category URL keys, must be unique only in the same level in the hierarchy.

    †—Custom URL redirect refers to a product's Create Custom Redirect for old URL option.

    URL Key Examples

    The following table shows category URL keys that are allowed. (The URL key is shoes for all entities in the table.)

    URL examples Reason allowed
    Different category hierarchies.
    Different domains.
    http://example.com/shoes (store view 1)
    http://example.com/shoes (store view 2)
    Different store views.


    Prioritizing URL Resolution

    Suppose you have the following set of URL keys. All of them are allowed because they're for different entity types.

    Entity type Entity name URL key Sample URL
    Category shoes shoes http://www.example.com/shoes.html
    Product shoes shoes http://www.example.com/shoes.html
    Custom URL redirects shoes shoes http://www.example.com/shoes.html

    Question: What happens when a web store visitor requests http://www.example.com/shoes.html?

    Answer: You control the response in the Admin Panel. Click System > Configuration > CATALOG > Search Engine Optimizations. In the right pane, click an option from the Priority for Duplicated URL Keys list. Some examples follow:

    Priority setting Result
    Default setting:
    1. Redirect
    2. Category
    3. Product
    Custom URL redirect
    1. Category
    2. Redirect
    3. Product
    Shoes category

    †—Custom URL redirect refers to a product's Create Custom Redirect for old URL option.

    The other options are:

    In the event no URL key matches your priority setting, Magento continues through the priorities in order until a match is found.

    noteNote: CMS URL keys are always prioritized last.

    For More Information about SEO

    For more information about SEO, see:

    Known Issue in EE

    After changing the value for product or category suffix, previous suffixes do not work.

    For example, if a category URL suffix was set to .html and you change it to .php, categories that had been using the .html suffix display an HTTP 404 (Not Found) error in your web store.

    (In the Admin Panel, click System > Configuration > CATALOG > Catalog > Search Engine Optimizations. In the right pane, the options are named Product URL Suffix and Category URL Suffix.)

    Patch Available for EE

    The United States Postal Service (USPS) changed the names of their Priority and Express shipping options in their API on Sunday, July 28, 2013. Magento has a patch available; however, this patch is not included in new EE installations.

    noteNote: If you applied the patch before you upgraded to EE, you don't have to do anything.

    For new EE installations to continue utilizing USPS Priority and Express mail methods, you must install the patch we've created to address the issue.

    Get the patch from the EE support portal by logging in to magentocommerce.com.

    Changes in EE

    For more information, see Magento Enterprise Edition 1.13 Benchmarking

    Tax Calculation Fixes

    Tax calculation issues can be divided into the following sections:

    General Tax Notes

    The following general fixes were made to Magento tax configuration and calculations:

    For details, see the Magento User Guide.

    Rounding Error Fixes

    The following issues relate to one-cent rounding errors in the web store or shopping cart:

    Fixed Product Tax (FPT) Fixes

    The following issues relate to errors in calculating taxes that include FPT in the web store or shopping cart:

    Discount Calculation Fixes

    The following issues relate to price calculations when coupon codes or other discounts are applied in the web store or shopping cart:

    Display Fixes

    The following issues relate to the incorrect display of tax information in the Admin Panel or in your Magento web store:

    API Fixes

    The following are fixed in the Magento SOAP v2.0 APIs (with exceptions noted):


    Fixes in this release can be divided into the following categories:

    Web Store and Shopping Cart Fixes

    Promotional Price Rule Fixes

    The following fixes relate to administering and using shopping cart price rules and catalog price rules:

    Administrative Ordering and Credit Memo Fixes

    Import Fixes

    Payment Fixes