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

Patches for Multiple Magento EE Versions

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

• General Magento Connect Patches
• Magento Install Page Displays After SOAP v2 Index Page Refresh
• Multiple Simultaneous Magento Administrators
• Discover Card Validation Patch Available
• PHP 5.4 Patch Available
• How to get Patches for Magento EE

Note: 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

• When you install a community-created translation package, the translation provided by the package overwrites any existing translations for the same items. This enables you to more easily install packages with translations.
• To improve security, Magento Connect now uses HTTPS by default to download extensions, rather than FTP.
• Extension developers can now create an extensions with a dash character in the name. Merchants can install those extensions without issues.
• Magento administrators who attempt to install an extension with insufficient file system privileges are now informed. Typically, the Magento Admin Panel runs as the web server user. If this user has insufficient privileges to the your Magento install dir/app/code/community directory structure, the Magento administrator sees an error message in the Magento Connect Manager.
  To set file system permissions appropriately, see After You Install Magento: Recommended File System Ownership and Privileges.

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 1.9.1.1 through 1.13.1.0.

To get a fix for the issue, see Discover credit card validation issue: Magento EE 1.9.1.1–1.13.1.0 and CE 1.4.2.0–1.8.1.0.

Important: 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 11.0.0.0–1.13.1.0.

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 1.13.1.0 Release Notes

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

• Highlights
• Security Enhancements
• Potential Issue After Upgrading to EE 1.13.1.0
• Changes in This Release
• Tax Calculation Fixes
• Fixes in Magento EE 1.13.1.0

Highlights

Magento EE 1.13.1.0 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 1.13.1.0 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:

• VAT tax calculation issues for cross-border trade
• Tax rounding issues when multiple taxes are applied
• VAT and FPT calculation issues for bundled products
• Support for the Waste Electrical and Electronic Equipment (W.E.E.E.) recycling tax in the EU

Functional Improvements

EE 1.13.1.0 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 1.13.1.0 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:

• Improved the password hashing algorithm.
  Magento thanks Bjorn Kraus for contributing to this fix.
• Resolved issues that could have resulted in Cross-Site Request Forgery (CSRF) in the web store.
• Resolved potential issues when issuing Return Materials Authorizations (RMAs).
  Magento thanks Ivan Chepurnyi for contributing to this fix.
• Resolved a session fixation issue when registering a user with the web store.
• Resolved a cross-site scripting (XSS) issue reported in EE 1.13.0.0.
  Magento thanks Myke Hines, Fox, and Opteros for contributing to this fix.
• Resolved issues with the expiration of file-based user sessions.
• Resolved issues that could have resulted in Remote File Inclusion (RFI) vulnerabilities.
• Addressed vulnerabilities in OAuth code.
• Closed a potential loophole that enables another user to possibly access personal information when viewing billing agreements.
  Magento thanks Darryl Adie and Ampersand Commerce for contributing to this fix.
• Resolved a remote code execution vulnerability that enabled an attacker to delete files and directories on the Magento installation. (The attack required access to the Admin Panel as a Magento administrator.)
• Fixed the security settings for the frontend cookie to protect user sessions.

Potential Issue After Upgrading to EE 1.13.1.0

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

Solution:

1. Close the Admin Panel browser window.
2. As a user with root privileges, delete all files except config.xml from the following directory:
   

   magento-install-dir/app/code/core/Mage/GoogleCheckout/etc

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:

• EE's Payment Bridge module has been updated to the latest version.
  For more information, see this Magento blog post.
• A tax configuration option for Fixed Product Tax (FPT) has changed. This option is in the Admin Panel at System > Configuration > SALES > Tax > Fixed Product Taxes, option FPT Tax Configuration. This option replaces the Apply Tax to FPT option in earlier EE releases.
  This option specifies how FPT is calculated as follows:
  
  • Not Taxed: Click this option if your taxing jurisdiction does not tax FPT. (For example, the state of California does not tax FPT.)
  • Taxed: Click this option if your taxing jurisdiction does tax FPT. (For example, Canada taxes FPT.)
  • Loaded and Displayed with Tax: Click this option if FPT is added to the order total before applying tax (for example, in EU countries).
• You can now specify a 0% tax rate. (In the Admin Panel, click Sales > Tax > Manage Tax Zones & Rates.).
  For more information, see the Magento User Guide.
• Magento changed its recommended setting for System > Configuration > SALES > Tax > Calculation Settings, option Apply Discount On Prices as follows:
  • US and Canadian merchants: Set the value of Apply Discount On Prices to Excluding Tax.
  • EU merchants: Set the value of Apply Discount On Prices to Including Tax.
• Magento strongly recommends all merchants set Apply Customer Tax to After Discount, regardless of all other tax-related settings. This avoids issues with calculating the total product price.
• When you specify a tax rate, the State list is now available whenever you choose a country that has states.
• You can now specify the asterisk (*) wildcard character for the value of State when you set up a new tax rate. This enables you to apply the same tax rate to all states or provinces in a particular country.
• Stores now display in the Admin Panel in System > Manage Stores as a three-column hierarchy, with the website in the left column, all stores associated with the website in the center column, and all store views associated with the store in the right column.
  This makes it easier for you to browse your stores and understand which websites, store views, and stores are associated with each other. The updated Manage Stores page also displays the root category for each store and the code for each website and store view.
  Magento thanks Fabrizio Branca for contributing to this fix. For more information, see Fabrizio's blog post.
• For the DHL (Deprecated) shipping method to work, you must change the gateway URL as follows:
  1. Log in to the Admin Panel as an administrator.
  2. Click System > Configuration > SALES > Shipping Methods.
  3. In the right pane, expand DHL (Deprecated).
  4. Change the value of the Gateway URL field to the following:
     

     http://xmlapi.dhl-usa.com/ApiLanding.asp

     .
  5. In the upper right corner, click Save Config.

Tax Calculation Fixes

Tax calculation issues can be divided into the following sections:

• General Tax Notes
• Rounding Issues
• Display Issues
• Bundled Products Issues
• Fixed Product Tax (FPT) Issues

General Tax Notes

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

• Canadian customers now receive an e-mail with the correct totals for invoices and credit memos that include Provincial Sales Tax (PST) and Goods and Services Tax (GST).
• Resolved issues with incorrect prices and incorrect tax amounts when a custom price is used together with the configuration setting System > Configuration > SALES > Tax > Calculation Settings, option Apply Tax On set to Original price only.
• The tax amount is calculated correctly when:
  • The customer is in a different taxing jurisdiction than the web store
  • The configuration option System > Configuration > SALES > Tax > Calculation Settings, option Catalog Prices is set to Including Tax
  • The configuration option System > Configuration > SALES > Tax > Calculation Settings, option Tax Calculation Method Based On is set to Unit Price
• The row total including tax displayed in the shopping cart is calculated correctly when:
  • The configuration option System > Configuration > SALES > Tax > Calculation Settings, option Catalog Prices is set to Excluding Tax
  • The configuration option System > Configuration > SALES > Tax > Calculation Settings, option Tax Calculation Method Based On is set to Row Total
• The row subtotal displays the correct amount when reordering a product that includes a discount coupon.
• Multiple tax rates for a product display correctly in the Admin Panel when creating an invoice or credit memo.
• Resolved calculation errors when tax and currency conversion are applied. As a result, the price the customer views on a catalog or product page is the same as the price displayed in the shopping cart.
• A customer can now place an order when two tax rules are applied to a product, even if the tax rules specify the same tax rate.
• Resolved issues with calculating taxes on orders that are shipped to different countries that have different tax rates.
• Product prices, including taxes, display on category and product pages the same for a guest customer as for a logged-in customer. (A guest customer is a customer who does not log in to your web store; this customer belongs to the NOT LOGGED IN customer group.)

Rounding Issues

The following tax rounding issues were resolved:

• Resolved a rounding issue in the tax detail display in the shopping cart when more than one tax rule is used.
• Resolved an issue reported on stackoverflow where a calculation error resulted from the following configuration:
  System > Configuration > SALES > Tax > Calculation Settings, option Tax Calculation Method Based On set to Total
  System > Configuration > SALES > Tax > Calculation Settings, option Catalog Prices set to Including Tax
• As a result of allowing a 0% tax rate, rounding errors related to different VAT jurisdictions have been resolved. For example, if a product originates in a country with VAT but is shipped to another country that has no VAT, correct prices display in the shopping cart.
• Row totals display correctly in the shopping cart when:
  • A shopping cart discount is applied
  • The following configuration options are set in System > Configuration > SALES > Tax > Calculation Settings:
    • Catalog Prices is set to Including Tax
    • Tax Calculation Method Based On is set to Excluding Tax
    • Apply Customer Tax is set to After Discount
    • Apply Discount On Prices is set to Including Taxes

Display Issues

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

• Shipping prices including tax display properly in the shopping cart.
• A special price now displays correctly on the product view page.
• Values displayed in PDFs for invoices and credit memos no longer overlap each other.
• Orders, invoices, and credit memos for downloadable and virtual products display the correct row total when viewed in the Admin Panel.
• Orders display the FPT in the Admin Panel when the full tax summary is specified.
• Fixed-price bundled products that include FPT now display only one price for both From and To values, regardless of how you configured the products.

Bundled Products Issues

• The price of a dynamic bundled product is calculated correctly after being customized by the customer.
• The price of a dynamic bundled product with tiered pricing is calculated correctly after being customized by the customer.
• Resolved issues with calculating the value displayed for the price including tax for bundled products.
• The price excluding tax of a bundle product to which a discount is applied is the same:
  • When viewed on the customization page
  • after adding the bundled product to the shopping cart.
• A dynamically-priced bundled product's prices displayed for Unit Price in the shopping cart (that is, the price including tax and the price excluding tax) are now correct. Before the fix, the prices were equal, which was incorrect.
• The price of a bundled product displayed on the product view page and in the shopping cart are the same.
• The grand total including tax and the subtotal including tax displayed in the shopping cart are now identical when you specify that catalog prices include tax and the shopping cart is set to display prices with and without taxes for a dynamic bundled product that consists of two simple products.

Fixed Product Tax (FPT) Issues

• Resolved issues in calculating FPT on a credit memo.
• With both discounts and FPT enabled (and FPT is taxable), the subtotal including tax displayed in the shopping cart is correct.
• FPT calculation for bundled products that have FPT applied to them now are now correct for all FPT configuration settings.
• The invoice total is calculated correctly for an order that has both FPT and a shopping cart discount.
• The FPT amount is now included in the Subtotal (Incl.Tax) row for partial invoice.
• Resolved an issue that resulted in FPT being applied twice to the grand total in the shopping cart.

Fixes in Magento EE 1.13.1.0

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

Shopping Cart and Checkout Fixes

• Abandoned cart e-mails are sent at the scheduled time.
• Resolved a new customer registration issue that enabled a user to register and see another customer's dashboard.
• Resolved issues with breadcrumbs disappearing or displaying incorrectly.
• With the following configuration, gift pricing is applied properly for more than one item.
  The following options are available in the Admin Panel in System > Configuration > SALES > Sales > Gift Options:
  Allow Gift Wrapping on Order Level set to No
  Allow Gift Wrapping for Order Items set to Yes
• Category and subcategory names display correctly. Before the issue was resolved, subcategory names that were significantly longer than the category name did not display properly.
• If a customer adds more than one product that requires products to be purchased in increments, only the products that meet the increment requirements are added. Before the fix, all products were added.
• Scheduled payments work properly.
  Magento thanks Sylvain Raye for contributing to this fix.
• If a bundled or configurable product is out of stock, it's no longer available to check out.
  Magento thanks Francesco Marangi for contributing to this fix.
• Placing an order in the Admin Panel correctly sets the order status to Pending.
  Magento thanks GitHub user elframan for contributing to this fix.

Import and Export Fixes

• Scheduled export works properly.
• You can now export a shipment to CSV after printing its shipping label.
  Magento thanks Florinel Chis for contributing to this fix.

Shipping Fixes

• You are not required to enter a declared value to ship with FedEx.
• FedEx shipping labels print properly; addresses are not truncated.
• Fix for the USPS change to the names of their Priority and Express shipping options in their API made on Sunday, July 28, 2013.

Payment Fixes

• The PayFlow Pro payment method now allows line items with a negative value.
• You can now use the GSI Payment Service with Magento Payment Bridge.
• Made the following fixes to eWay Direct:
  • Updated the Payment Bridge console for eWay Direct.
  • You can now process credit memos for eWay Direct.
  • Capture for eWay direct now works as expected (that is, after the order is placed, the transaction is not captured but can be refunded.
• ( Because refunds are not supported by the Paybox Direct method, you cannot process refunds using the Admin Panel.
• After creating a refund for a First Data transaction, the transaction is closed.
• You can now pay for an order using Sagepay.
• You can now pay for an order using Worldpay.
• Line item details are now available for orders placed using Sage Pay.
• Authorize.net sends only one validation request per transaction with Customer Information Management (CIM) enabled.

Other Fixes

• Resolved issues that caused spurious errors in the Magento exception log:
  'Zend_Date_Exception' with message 'Invalid year, it must be between -10000 and 10000'
• Merging CMS pages no longer results in errors.
• Widgets display properly on the CMS.
• Previewing a CMS page works properly.
• The product attribute option Use Default Value works properly when used in a non-default store view.
• A category attribute set to store view scope displays in layered navigation.
• A store set for British Pound Sterling currency units now displays the correct currency in payment logs.
• Resolved an issue with the Mage_Catalog_Block_Product_Abstract class that caused errors to display on product view pages in your web store.
• Fixed issues with customer segments.
• Back-in-stock e-mails contain the correct content.
• You can now manage product ratings and reviews from the Admin Panel as well as from the web store.
  Magento thanks Fabian Blechschmidt Schrank for contributing to this fix.
• Resolved an issue with Mage_Page_Block_Template_Links::addLinkBlock to enable you to sort an array of results by position.
  Magento thanks Benjamin Marks for contributing to this fix.

Magento EE 1.13.0.2 Release Notes

In response to customer feedback about EE 1.13.0.0 and EE 1.13.0.1, 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 1.13.0.2
• Known Issue in EE 1.13.0.2
• Patch Available for EE 1.13.0.2
• Changes in EE 1.13.0.2
• Fixes in Magento EE 1.13.0.2

Important:

• Perform all new installations and upgrades to Magento EE 1.13.0.2—not to Magento EE 1.13.0.0 or 1.13.0.1—to avoid issues with missing products on your web store due to duplicate URL key issues during the upgrade.
• The upgrade to EE 1.13.0.2 involves tasks not required for other EE upgrades. For more information, see Important Information About Upgrading to Magento Enterprise Edition (EE) 1.13.0.2.

Search Engine Optimization in Magento EE 1.13.0.2

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

See one of the following for more information:

• Comparing EE 1.13.0.2 with EE 1.12.0.2
• URL Key Uniqueness Rules in Magento EE 1.13.0.2
• URL Key Examples
• Prioritizing URL Resolution
• For More Information about SEO

Comparing EE 1.13.0.2 with EE 1.12.0.2

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

• Product URL key uniqueness
• No more chained redirects
• Per-entity indexing

Product URL key uniqueness

Description:

The main difference introduced in EE 1.13.0.2 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.

Benefit:

A single URL leads uniquely to a product page.

Discussion:

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 1.13.0.2, 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

Description:

Magento addressed the indexer issue that resulted in suffixes being silently added to products with duplicate URL keys. In EE 1.13.0.2, duplicate URL keys are not allowed.

Benefit:

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

Description:

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

Benefit:

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.

Discussion:

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 1.13.0.2, 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 1.13.0.2

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

• Categories
• Products (including custom URL redirects)
• Content Management System (CMS)

Uniqueness rules for each entity type follow:

†—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.)

Notes:

• You cannot have the same category URL key for two categories at the same level in the same store view.
• You can optionally add the store code to the URL path (in the Admin Panel, click System > Configuration > GENERAL > Web, Add Store Code to Urls).

Prioritizing URL Resolution

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

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:

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

The other options are:

• Redirect - Product - Category
• Category - Product - Redirect
• Product - Redirect - Category
• Product - Category - Redirect

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

Note: CMS URL keys are always prioritized last.

For More Information about SEO

For more information about SEO, see:

• Magento SEO
• Magento SEO forum
• SearchEnglineLand—What is Search Engine Optimization?
• Google—Search Engine Optimization Guide (PDF)
• Google—Demystifying the "duplicate content penalty"

Known Issue in EE 1.13.0.2

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 1.13.0.2

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 1.13.0.2 installations.

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

For new EE 1.13.0.2 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 1.13.0.2

• You now have the option of specifying a store view when creating a URL redirect. There is also a Store column on the Catalog > URL Redirects page.
  This column specifies the store view for which the URL redirect is defined.
• Root categories have no URL Key field. The root category URL key was never used, so the field was eliminated.
• Validation for the URL key field was improved. URL keys can only contain alphanumeric characters (a-z, 0-9) and the hyphen or dash character (-).
• Categories and products in categories display with the full category path if the following setting is made in the Admin Panel: System > Configuration > CATALOG > Catalog. Set the option named Use Categories Path for Product URLs to Yes.
• When setting up a product URL redirect, the name of the button on the category selection page has changed from Skip choosing category to Skip Category Selection.
• There is a new setting in the Admin Panel to set the priority for resolving duplicate URLs for different entities (that is, custom URL redirects, categories, and products). For more information, see Prioritizing URL Resolution.
• URL key 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.
• The Google sitemap for products and categories is updated with new or updated URL keys at the interval you specify in the Admin Panel: System > Configuration > CATALOG > Google Sitemap. In the right pane, expand Generation Settings.
• The following apply to new products when you do not explicitly set a value for the URL key field:
  • Duplicating a results in a URL key with an appended index number. For example, if you duplicate a product with a URL key of testurlkey, the new product's URL key might is testurlkey-1.
  • If you create a new product with a name that matches an existing URL key, the new product's URL key has the product ID appended to it. For example, if there is currently a product with a URL of product1 and you create a new product with the name Product1 and the product has an ID of 500, the new product's URL key is product1-500.
    
    Note: To avoid having Magento specify a URL key for you, you can enter one yourself. Make sure the URL key you specify is unique among all products, including products across store views.
• The following apply to enabling the canonical meta tag options for categories and products:
  • If Use Canonical Meta Tag for Categories is enabled, the category page on your web store includes a canonical URL to the full category URL. For example, http://www.example.com/mens/shoes
  • If Use Canonical Meta Tag for Products is enabled, the product page includes a canonical URL to domain-name/product-url-key because product URL keys must be globally unique.
    If you also enable the option Use Categories Path for Product URLs, the canonical URL is still domain-name/product-url-key but the product can also be accessed using its full URL (including the category hierarchy). Examples:
    If the product URL key is producturlkey and it's assigned to the Apparel > Womens > Purses category, the product can be accessed using both of the following URLs:
    http://www.example.com/producturlkey
http://www.example.com/apparel/womens/purses/producturlkey
    The canonical URL for the product is http://www.example.com/producturlkey.

    Notes:

    • The canonical URL options are available in the Admin Panel by clicking System > Configuration > CATALOG > Catalog. In the right pane, expand Search Engine Optimizations. The options are named Use Canonical Link Meta Tag For Categories and Use Canonical Link Meta Tag For Products.
    • The option to add the category path to a product URL is available in the same location in the Admin Panel. The option name is Use Categories Path for Product URLs.

  Fixes in Magento EE 1.13.0.2

  This section discusses fixes made in EE 1.13.0.2.

  • Resolved a critical database deadlock in the URL rewrite indexer. The deadlock resulted in the following message in the exception log: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock.
  • The following layered navigation issues were addressed:
    • If a subcategory contains a product that is associated with the parent category, you can view the subcategory in your web store.
    • Clicking a link for a product attribute in an anchor category works.
  • You can now install or upgrade to EE 1.13.0.2 if your Magento database had a table prefix (for example, all tables start with mage_ because you specified a tables prefix during installation).
  • Resolved the following upgrade issues:
    • After upgrading from an earlier version like EE 1.12.0.2, errors such as the following no longer display in the Magento exception log: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry
    • Resolved an issue that prevented web store users from viewing products that had duplicate URL keys before upgrading.
  • Resolved the following issues with URL keys in store views:
    • Changing the store view no longer results in product or category 404 (Not Found) errors.
    • Resolved an issue that categories created from a store view had the wrong URL format in the web store. Examples follow:
      Incorrect (before the fix): /catalog/category/view/s/newcategory/id/36/
      Correct: /catalog/newcategory/
  • Resolved an issue where a product could be viewed using a category to which it was not assigned.
    This behavior was associated with the following Admin Panel setting: System > Configuration > CATALOG > Catalog.
  • Moving a category no longer results in HTTP 404 (Not Found) errors viewing a category's product in the web store.
  • Categories display in the web store with the correct URL key, even if the category was previously deleted and added back with the same URL key.
  • A customer can view a product from the Recently Viewed Products list if the product is associated with a different category than the one the customer is currently viewing.
  • Any product page displays properly when the user accesses it from the site map on your web store.
    This includes the case when an administrator sets the following option to Yes: System > Configuration >CATALOG > Catalog > Search Engine Optimizations, option named Use Categories Path for Product URLs.
  • The category is not included in the URL to a product in your web store when an administrator sets following option to No: System > Configuration >CATALOG > Catalog > Search Engine Optimizations, option named Use Categories Path for Product URLs.
  • The URLs for the same category and product, when assigned to multiple store views, are as expected.
    Category URL example: /parent-category/category-2/
    Product URL example: /parent-category/category-2/product-1
  • With the option to Add Store Code to URLs option enabled, store codes properly display in URLs and the store view displays properly.
  • After duplicating a product, the product's URL key updates successfully.
  • A product URL key is correct in your web store even if there is a category with the same URL key as the product.
  • Adding products without specifying a value for the URL Key field no longer results in the exception log entry SQLSTATE[23000]: Integrity constraint violation.
  • You can create two or more categories with the same URL key without encountering the exception log entry SQLSTATE[23000]: Integrity constraint violation.
  • The value of a product's URL Key field is properly validated.
    A URL key can contain only alphanumeric characters (a-z, A-Z, 0-9) and the dash or hyphen character.
  • A caching error that affected changing URL redirects was fixed.
  • URL redirects work properly when products are assigned to categories in different store views but using the same request path.
  • You can successfully import data and reindex with the import behavior set to Append Complex Data.
  • After moving a category to another location in the category hierarchy, the category's URL and breadcrumbs update successfully.
  • The options to create a custom redirect for a category and product work properly.
    (In the Admin Panel, click System > Configuration > CATALOG > Catalog > Search Engine Optimizations. In the right pane, from the Create Permanent Redirect for URLs if URL Key Changed, click Yes.
  • Switching store views enables you to navigate to products and categories on that store view as expected. HTTP 404 (Not Found) errors no longer display and the specified category and product URL keys are correct.
    In earlier EE versions, incorrect behavior was reported when the setting System > Configuration > GENERAL > Web, Add Store Code to Urls was set to Yes.
  • A remote code execution vulnerability was fixed.
  • On a clean installation, display errors are hidden.

  Magento EE 1.13.0.0 Release Notes

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

  • Highlights
  • Security Enhancements
  • Security Advisory
  • Upgrade Limitation
  • Performance Improvements
  • Tax Calculation Fixes
  • API Fixes
  • Fixes
  • Changes

  Highlights

  • Major overhaul of tax calculation formulas, correction of rounding errors, and additional assistance with configuration
  • Most indexing processes now run only to update products, categories, URL redirects, and so on that have changed—eliminating the need for manual full reindexing
  • Additional option of using Redis NoSQL for cache and session storage in multi-host deployments (recommended for new deployments)
    To set up and use Redis with Magento, see Using Redis with Magento Community Edition (CE) and Enterprise Edition (EE).
  • Full page caching now invalidates only pages that are affected by product or category changes
  • Optimized cache adapters for single-server systems
  • Elimination of many types of database deadlocks

  Security Enhancements

  • The Magento Admin Panel and web stores no longer allow web browsers to store usernames or passwords.
  • The Magento web store has additional Cross Site Request Forgery (CSRF) protections, meaning an imposter can no longer impersonate a newly registered customer and perform actions on the customer's behalf.
  • In earlier versions, Magento was vulnerable to a session fixation attack during the registration process. After logging in to their account, a registered user's session ID did not change. Therefore, if an attacker had knowledge of an unauthorized session ID and if that user successfully registers, the attacker was able to take over the newly registered account.
    Now, the session ID changes after successful registration, making unauthorized use of an account impossible.
  • The cryptographic methods used to store passwords were improved to enhance security.

  Security Advisory

  Magento has identified a potential vulnerability that might affect you if both of the following are true:

  • Your store uses custom code that calls Magento full page caching functions
  • You enabled the Use SID on Frontend configuration option
    (In the Admin Panel, System > Configuration > WEB > Session Validation Settings, Use SID on Frontend.)
  Note: The potential vulnerability exists only if both of the preceding are true. Default Magento installations or installations that enable Use SID on Frontend but have no custom code with full page caching are at no risk.

  If both of the preceding are true, Magento can be subjected to cross-site scripting (XSS) attacks—a type of injection issue, which means that malicious code is injected into otherwise trusted websites, generally in the form of a browser-side script.

  Issue: Magento is subject to XSS attacks because the SID cookie value is not sanitized by default.

  Suggested solution: Either disable Use SID on Frontend or output-encode any usage of the SID cookie value before using it or passing it as a parameter to any page cache helper functions.

  Additional references:

  • XSS Prevention Cheat Sheet
  • HttpOnly reference
  • Open Web Application Security Project (OWASP) Code Review Guide V2.0
  • Reviewing Code for Cross-Site Scripting
  • HTTP Input and Output on php.net

  Upgrade Limitation

  Magento EE 1.13—unlike earlier versions—does not allow duplicate URL keys for products or categories. An issue has been identified that causes problems during upgrades if you already have duplicate URL keys. The issue is being addressed; until a solution is announced, Magento recommends you test your upgrade but do not try to deploy it to a production environment.

  For more information about upgrading in a development environment, see Upgrading to and Verifying Magento Community Edition (CE) 1.8 and Enterprise Edition (EE) 1.13.

  Performance Improvements

  • Limited the way Magento performs large database lookups.
  • Checkout performance improvements achieved by:
    • Eliminating unnecessary calls to gift wrapping when loading the Shipping Method checkout step
    • Eliminating unnecessary RSS cache cleanups when RSS functionality is disabled
    • The locale used to send a new order confirmation e-mail now first checks to see if the customer's locale is the same as the store's locale before attempting to localize the e-mail.
    • Improving the overall checkout process performance by loading the progress information for the current checkout step only
  • You can load a large number of tax codes (35,000 or so) without impacting performance.
  • Magento uses MySQL database triggers to improve access to the database during reindexing.

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
• Rounding Error Fixes
• Fixed Product Tax (FPT) Fixes
• Discount Calculation Fixes
• Display Fixes

General Tax Notes

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

• Based on Magento testing and merchant experience, certain tax configuration settings have been determined to be susceptible to rounding issues and can be confusing to buyers. To help you avoid issues with those settings, warning messages display in the Admin Panel if you attempt to save such a configuration.
  Administrative users can choose to dismiss the messages and can still save the configuration; however, Magento strongly recommends you change the configuration in a way recommended by the details displayed in the message.
  For details, see the Magento User Guide.
  
• Bundle pricing is more consistent as follows:
  • The calculation formula is: Sub item price = Sub item base price * Applicable tiered price adjustment or discount, then rounded Bundle price = Sum (round(sub item price * qty))
  • When non-integer quantities are multiplied by a product price, Magento rounds the resulting subtotal is as follows: round(unit price * non-integer quantity)
• All product price information on which taxation is based are rounded to two digits of precision regardless of how many digits of precision have been loaded into the database (for example, $10.24 instead of $10.2385). This situation can occur when certain integrations enable third-party applications to send four-digit precision prices to Magento.
  Starting with this release those additional digits will have no impact on customer facing prices. Forcing two digits of precision enables more exact calculations involving Fixed Product Tax (FPT), discounts, and taxes—among other concerns.
• For certain Canadian provinces and localities, calculations and methods were updated to support changing legal requirements in Canada:
  • Provincial Sales Tax (PST)
  • Goods and Services Tax (GST)
  • Taxe de vente du Québec (TVQ)—also referred to as Quebec Sales Tax (QST)

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:

• Calculating taxes for bundled products with tiered pricing.
• Calculating the price before customization for bundled products.
• Calculating the grand total of items added to a cart in a different order.
• Viewing an order when taxes are calculated after a discount using either row-based or unit price.
• Applying a discount to an order with a shipping address different than the billing address.
• Calculating the grand total based on the order in which products are added to the shopping cart.
• Specifying that prices display in the web store excluding tax and setting a 20% tax rate (or discount rate) now calculates the grand total correctly. It is now possible to have grand totals in amounts like 6.99, 9.99, or 99.99—regardless of the currency units used in the web store.
• Adding multiple items to a cart does not affect the accuracy with which taxation is calculated.
• Subtotal (Incl. Tax) is now correct when catalog and shipping prices include tax. Both tax and discounts are applied after tax.
• Prices displayed in the cart and on the catalog page are consistent and correct when catalog prices include tax, and when items in the catalog are set to display both including and excluding tax.
  (In the Admin Panel, click System > Configuration > SALES > Tax. In the right pane, expand Calculation Settings.)
• Error in calculating the Grand Total Excl. Tax was resolved. This error occurred in a specific configuration: tax is applied to FPT, FPT is included in the subtotal, and the customer selects non-taxable flat rate shipping.

Fixed Product Tax (FPT) Fixes

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

• Price in the cart displays the correct before-tax price and grand total.
• Subtotals displayed in the cart—both Including Tax and Excluding Tax—are now correctly calculated when FPT is applied.
• Free shipping offers are now processed correctly when FPT is applied.
• FPT taxes are calculated correctly when a discount is applied.

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:

• The Row Subtotal displayed in the cart is calculated correctly (that is, both Excl. Tax and Incl. Tax are correct).
• The price for bundled items now displays with tax included if the bundle is configured to do so.
• Taxation is now correctly calculated on a product with a discounted price.
• Taxation on discounts is now calculated correctly when the ship-to country is different from the web store's default country.

Display Fixes

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

• Row Subtotal displays correctly in the shopping cart when:
  • FPT is applied.
  • A discount is applied to a situation where the tax the customer pays is different from the tax specified for the web store's locale (for example, when the shipping origin is different than the shipping address).
• Subtotal including tax on a credit memo is correct when one or more items in the memo includes FPT.
• Item subtotal displays correctly when a discount is applied to a purchase that includes FPT.
• If the administrator sets catalog prices to exclude tax and to display product prices in catalog as including tax, the price of the product in your web store includes applicable taxes.
  (In the Admin Panel, click System > Configuration > SALES > Tax. In the right pane, expand Calculation Settings.)
• When Minimum Advertised Price (MAP) is enabled and the customer examines the price of a product in a gift registry, the price includes all of the following: price, actual price, price including tax, and price excluding tax.
• The amount of tax displayed in the Order Totals section of the shopping cart is now correct when free shipping and a shopping cart rule discount are applied.

API Fixes

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

• Requesting a product using a call like the following returns the product with the specified numeric SKU value (8888 in the following example): $result = $client->call($sessionId, 'catalog_product.info', '8888', null, null, 'sku');
• Order status is changed correctly using salesOrderAddComment.
• The shoppingCartProductMoveToCustomerQuote method works properly.
• You can now use from-to complex filters to perform "window" filtration on a single field. For example, you can use from and to on the created_at return a list of sales orders using the salesOrderList.
• When you use the SOAP API v.2.0 with WS-I Compliance enabled to retrieve sales orders information, the server responds with the correct Content-Length header.
• The productGetSpecialPrice method returns special price information for a product, whether or not WS-I Compliance is enabled.
• The shoppingCartPaymentList method returns the list of the available payment methods for the shopping cart appropriately. The following error is no longer returned: SOAP-ERROR: Encoding: object has no 'code' property in name
• The following issues with WSDL and WS-I Compliance are resolved:
  • The productAttributeAddOption and catalogProductAttributeUpdate methods are now supported when WS-I Compliance is enabled.
  • The WSDL declaration for salesOrderCreditmemoCreate is now correct; that is, it matches the code.
  • You can now add a C# web reference in Microsoft Visual Studio 2010 using the Magento WSDL.
    For example, this command no longer fails:
    C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin> wsdl /out:Magento.cs /v http://magentohost/api/v2_soap/?wsdl
  • The WS-I Compliance mode WSDL now includes catalogProductAttributeInfo.
• XML-RPC API: Using the product_custom_option.add operation with multicall no longer results in redundant options.

Fixes

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

• Web Store and Shopping Cart Fixes
• Promotional Price Rule Fixes
• Administrative Ordering and Credit Memo Fixes
• Import Fixes
• Payment Fixes
• Other Fixes

Web Store and Shopping Cart Fixes

• A customer's account created date is correct.
• When a product price is set with website scope and an administrative user has access to only one website, the default price is taken from that website scope. Also, when saving the product on the website scope, the price is updated only in that scope and not in the default scope.
• An error no longer displays on your web store after a customer places an order. (The error message was There has been an error processing your request. Please contact us or try again later).
• Restricted coupon codes work properly, even if the customer has selected the Remember me checkbox.
• Using the Table Rates shipping option, free shipping options work properly. (In the Admin Panel, click System > Configuration > SALES > Shipping Methods. In the right pane, expand Table Rates.)
• Issues with shipping table rates have been resolved.
• Reward Points are now granted one time per order, even when comments are added to the order later.
• Entering a value such as 10,50 (using a comma character and not a period) for Adjustment Fee now results in the correct amount of credit being applied to the transaction.
• Unit price for bundled products is now calculated correctly.
• The tiered price of bundled items now displays properly on the web store.
• Composite products can be successfully reordered.
• You can now use special characters in a product URL key.
• After a customer visits the sitemap, web stores URLs are no longer prepended by /sitemap/catalog/string.
• Welcome messages now display properly in the web store after a customer's profile information is changed.
• Recently viewed products now display updates properly.
• Armed Forces Middle East is now available for State when checking out.
• Gift wrapping charges now display properly in a PDF invoice.
• Searching for a customer's orders and returns works properly.
• Shipping is calculated correctly if you select Using origin weight (few requests) for Packages Request Type. (In the Admin Panel, click System > Configuration > SALES > Shipping Methods > DHL (Deprecated)).
• Free shipping is no longer available to a customer during checkout if the option was disabled by an administrator. (In the Admin Panel, click System > Configuration > Sales > Shipping Method > DHL(Deprecated), click one or more options from the Allowed Methods list, and, from the Free Shipping with Minimum Order Amount list, click No.)
• A user can navigate your web store while downloading a downloadable product.
• You can now specify weight units in kilograms (kg) using the FedEx shipping method.
• FedEx shipping rates are now consistent with Magento discounted rates.
• Fixed issues with United Parcel Service (UPS) shipping rates.
• An issue that caused a fatal error in the web store for an item in a gift registry has been resolved. The issue occurred when the item was removed from a website after a user had added the item to their gift registry.
• UPS shipping labels have the word SAMPLE printed on them only when you request a sample label.
• Changes made to United States Post Office (USPS) APIs and rates have been incorporated in Magento.
• You can now process a return materials authorization (RMA) for an order that was shipped to multiple addresses.
• The products in a customer's wish list no longer disappear after one or more products are edited by an administrator.
• Administrators can view the contents of a customer's shopping cart.
• The price of a simple product now displays properly when category permissions are enabled. (To set category permissions in the Admin Panel, click Catalog > Categories > Manage Categories, select a category, and click the Category Permissions tab.)
• Issues with purchasing a product using a gift card created with a custom option have been resolved.
• When a customer selects a product on your web store, the assigned category is selected in the navigation menu.
• With both flat index options enabled and set to update on save, mass attribute updates now display properly in your web store.
  For more information about flat catalog options, see the Magento User Guide.
• With both flat index options disabled, after adding a product to many websites and assigning it to one or more categories, the product displays in the appropriate websites and categories in the web store.
• You can now use multiple selection attributes in a customer segment.

Promotional Price Rule Fixes

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

• Shopping cart price rules applied to specific customer groups work properly.
• Catalog price rules are applied properly to customer groups.
• The scope of a product attribute is now honored by a catalog price rule.
• Discounts specified by a shopping cart price rule are applied properly when a particular order is shipped to multiple addresses.
• You can add a gift card to an order that qualifies for a 100% purchase price discount specified by a shopping cart price rule.
• A discount specified by a shopping cart price rule that allows for more than one use per customer is applied the correct number of times if the customer has their orders shipped to more than one address.
• When an administrative user whose role is restricted to only viewing catalog price rules, the user cannot add or edit catalog price rules.
• Shopping cart price rules now work properly with bundled products.

Administrative Ordering and Credit Memo Fixes

• When you create an order using the Admin Panel and you have multiple stores, the State/Province field updates appropriately for the country in which the order is placed.
• When you create an order using the Admin Panel and you have specified a default billing address and a default shipping address, the addresses are used correctly.
• Orders placed by an administrator display in a customer's last order list.
• Product comparisons now display properly when an administrator makes a change using the Admin Panel (for example, deleting a product from a customer's comparison list).
• You can now cancel an order using the Admin Panel.
• Orders and invoices that include taxable shipping—when created in the Admin Panel—now calculate the shipping taxes properly.
• Products added to a customer's wish list by an administrator display properly.
• Issues with the incorrect number of reward points being credited when issuing credit memos have been resolved.

Import Fixes

• The quantity (QTY) of all products imports correctly.
• The value of Maximum Qty Allowed in Shopping Cart (use_cfg_max_sale_qty) is correct.
• The product displays correctly in layered navigation.
• Importing customer lists with capitalization variations in the e-mail address now imports the customer only once (for example, user@example.com and User@example.com).
• Issues with importing products with Append Complex Data selecting from a comma-separated value (.csv) file have been resolved.

Payment Fixes

• Resolved issue sending customer e-mail when using Payflow Link.
• Security issues with Google Checkout payments have been resolved.
• Security issues with Authorize.net payments have been resolved.
• Magento conforms to the latest version of the PayPal Instant Payment Notification (IPN) guidelines.
• The contents of a shopping cart are unaffected by canceling a PayPal payment.
• Issues with not being able to continue checkout after switching payment methods have been resolved.
• You can now process partial refunds and invoices for orders that were placed using Payflow Pro.
• Payflow Link and Payments Advance now capture IPN transactions properly.
• Special characters (such as e-mail addresses) are now handled properly by the Magento Payflow API integration.
• Resolved errors with orders placed using the Website Payments Pro payment method.
• PayPal Express Checkout payments are handled properly when a shopping cart price rule is specified.
• Any PayPal Name-Value Pair (NVP) payment method no longer automatically refunds an order when a chargeback is initiated. Magento now allows the dispute to be resolved before taking the appropriate action.
  PayPal NVP payment methods include: PayPal Payments Pro (including PayPal Payments Pro Hosted), Payments Standard, and all Payflow methods.
• PayPal Pro now correctly processes the shipping address for an order.
• PayPal Express Checkout and PayPal Pro now handle partial refunds properly.
• Fixed rounding errors that were preventing PayPal Express Checkout transactions from completing. The error occurred with the following configuration:
  • tax calculation method based on the total
  • tax calculated based on the shipping address
  • catalog prices exclude tax
  • shipping prices exclude tax
  • customer discount applied after a discount
  • discount applied to prices excluding tax
  • tax applied to a custom price if available
    (In the Admin Panel, click System > Configuration > SALES > Tax. In the right pane, expand Calculation Settings.)
• The order status Suspected Fraud is now supported by PayPal Payments Pro (hosted) when PayPal fraud protection is enabled. Using the Magento Admin Panel, the merchant can also accept or deny any Suspected Fraud orders and have that decision applied to the PayPal transaction.
• When sending payments in the United Kingdom, PayPal Payments Pro (hosted) now sends the value for state correctly. (Before the fix, city was sent as the value for state.)
• Using the Ogone payment method, transactions display in the Magento Admin Panel after you capture them.
• When an administrator places an order and uses PSi Gate, then cancels the order, the PSi Gate gateway displays both the order and the void transactions.
• The following fields related to PayPal's Payflow Pro Gateway payment method are now implemented properly:
  • [custref] is the Magento customer's ID
  • [INVNUM] is Magento's order number
• Fixed spurious Gateway error: Void error: V18A4B18E0F9 has been captured errors when canceling partially invoiced orders when the Payflow Pro processor was used to process the payment.
• 3-D secure fixes that affect UK merchants only:
  • 3-D Secure for UK merchants implementing Direct Payment works properly.
  • SagePay Direct with 3-D secure payments are processed correctly.
• The Braintree payment method can now be configured properly.
• Partial captures are now supported for the following PayPal payment methods: Express Checkout, Payments Pro Payflow Edition, and PayPal Standard.
• Using the PayPal Express Checkout method, a recently added customer can check out without the error This customer email already exists.

Other Fixes

• MySQL database deadlock issues were resolved.
• EE 1.13 is now World Wide Web Consortium (W3C) compliant.
• A fatal error in GiftRegistry/Model/Item/Option.php has been resolved.
• When an administrative user whose role is restricted to managing products attempts to edit Inventory settings (Catalog > Manage Products, Inventory), only the available options display.
• Related product information updates appropriately in the Admin Panel.
• Issues with editing product inventory settings and category attributes using the Google Chrome web browser have been resolved.
• Rolling back after a backup now works properly. (The Magento backup and rollback options are available in the Admin Panel in System > Tools > Backup.)
• You can now fetch data for a PayPal Settlement Report using a custom Secure FTP (SFTP) server.
• Using the Solr search engine with price navigation calculation step set to manual now displays search results properly on your web store. (A fatal error was fixed.)
  (To set price navigation step options in the Admin Panel, click System > Configuration > CATALOG > Catalog > Layered Navigation. From the Price Navigation Step Calculation list, click Manual.)
  For more information about using the Solr search engine with Magento EE, see the Magento User Guide.
• You can now save a category with the option Available Product Listing Sort By: Best value or Price enabled.
• The following fixes relate to full page caching:
  • Breadcrumbs to a product work for all categories with which the product is associated.
  • The correct customer name displays on a gift card.
  • Product tags display properly.
  • Related products display properly.
  • magento-install-dir/app/code/core/Enterprise/PageCache/Model/Config.php was modified to enable you to set specific lifetimes for certain blocks.
  • Automated e-mail marketing reminder rules work properly.
  • Issues with session cookies have been resolved.

Changes

This release includes the following changes to support the changes in indexing:

• As a result of the optimizations made to reindexing, you can no longer have a duplicate:
  • URL key for any two products
  • URL key for any two categories
  • Request Path for any URL Redirect (formerly referred to as URL Rewrite
• There is a new management page in the Admin Panel: System > Configuration > ADVANCED > Index Management.
• The options on the System > Index Management are significantly different. In particular, because manual reindexing is no longer required for most indexers, there are fewer checkboxes and the page mostly displays status information.
• In the Admin Panel, Catalog > Manage Products > edit-product > General tab page option Create Permanent Redirect for old URL if URL key changed changes to Create Custom Redirect for old URL.
  The feature behaves the same way; namely, selecting Yes creates a redirect for the old URL that points to the new URL if a page is moved.
  
  Note: The wording of this option is expected to change back to the previous wording in a subsequent release.
• The options Product URL Suffix and Category URL Suffix return an error if anything except alphanumerical characters or the underscore character are entered. (In the Admin Panel, click System > Configuration > CATALOG > Catalog > Search Engine Optimizations.)
• The catalog_product_entity_url_key and catalog_category_entity_url_key database tables for the corresponding url_key attributes have been added.

For more information about indexing changes, see the Magento User Guide.