From 53fc9b547e1e7cf499dc95489a7a7606b2e615fd Mon Sep 17 00:00:00 2001 From: Fiona Hoyer Date: Thu, 6 Aug 2020 15:45:56 +0200 Subject: [PATCH 1/4] devdocs-m1 ausgecheckt --- guides/m1x/.gitignore | 4 + guides/m1x/LICENSE.txt | 48 + guides/m1x/api/rest-api-index.html | 48 +- .../Resources/Orders/order_addresses.html | 62 +- .../rest/Resources/Orders/order_comments.html | 12 +- .../rest/Resources/Orders/order_items.html | 12 +- .../rest/Resources/Orders/sales_orders.html | 14 +- .../Products/product_categories.html | 14 +- .../Resources/Products/product_images.html | 86 +- .../Resources/Products/product_websites.html | 34 +- .../api/rest/Resources/Products/products.html | 50 +- .../m1x/api/rest/Resources/get_filters.html | 10 +- guides/m1x/api/rest/Resources/inventory.html | 36 +- .../resource_customer_addresses.html | 34 +- .../rest/Resources/resource_customers.html | 30 +- guides/m1x/api/rest/Resources/resources.html | 24 +- .../authentication/oauth_authentication.html | 6 +- .../authentication/oauth_configuration.html | 32 +- .../api/rest/common_http_status_codes.html | 6 +- guides/m1x/api/rest/get_filters.html | 10 +- guides/m1x/api/rest/http_methods.html | 2 +- guides/m1x/api/rest/introduction.html | 305 +- .../attributes_configuration.html | 2 +- .../permission_settings.html | 8 +- .../roles_configuration.html | 2 +- guides/m1x/api/rest/response_formats.html | 14 +- .../m1x/api/rest/testing_rest_resources.html | 153 +- guides/m1x/api/soap-api-index.html | 395 +- guides/m1x/api/soap/catalog/catalog.html | 9 +- .../catalogCategory/catalogCategory.html | 5 +- .../catalog_category.assignProduct.html | 8 +- .../catalog_category.assignedProducts.html | 10 +- .../catalog_category.create.html | 8 +- .../catalog_category.currentStore.html | 6 +- .../catalog_category.delete.html | 8 +- .../catalog_category.info.html | 10 +- .../catalog_category.level.html | 6 +- .../catalog_category.move.html | 8 +- .../catalog_category.removeProduct.html | 8 +- .../catalog_category.tree.html | 10 +- .../catalog_category.update.html | 8 +- .../catalog_category.updateProduct.html | 8 +- ...talog_category_attribute.currentStore.html | 6 +- .../catalog_category_attribute.list.html | 10 +- .../catalog_category_attribute.options.html | 10 +- .../categoryAttributes.html | 3 +- .../catalogProduct/catalogProduct.html | 4 +- .../catalog_product.create.html | 8 +- .../catalog_product.currentStore.html | 4 +- .../catalog_product.delete.html | 8 +- .../catalog_product.getSpecialPrice.html | 10 +- .../catalogProduct/catalog_product.info.html | 10 +- .../catalogProduct/catalog_product.list.html | 12 +- ...og_product.listOfAdditionalAttributes.html | 8 +- .../catalog_product.setSpecialPrice.html | 8 +- .../catalog_product.update.html | 8 +- .../catalogProductAttribute.html | 2 +- .../catalog_product_attribute.options.html | 10 +- .../product_attribute.addOption.html | 4 +- .../product_attribute.create.html | 4 +- .../product_attribute.currentStore.html | 4 +- .../product_attribute.info.html | 6 +- .../product_attribute.list.html | 10 +- .../product_attribute.options.html | 10 +- .../product_attribute.remove.html | 8 +- .../product_attribute.removeOption.html | 4 +- .../product_attribute.types.html | 6 +- .../product_attribute.update.html | 4 +- ...atalog_product_attribute_media.create.html | 8 +- ..._product_attribute_media.currentStore.html | 4 +- .../catalog_product_attribute_media.info.html | 10 +- .../catalog_product_attribute_media.list.html | 10 +- ...atalog_product_attribute_media.remove.html | 8 +- ...catalog_product_attribute_media.types.html | 9 +- ...atalog_product_attribute_media.update.html | 8 +- .../productImages.html | 2 +- .../productAttributeSet.html | 2 +- .../product_attribute_set.attributeAdd.html | 8 +- ...product_attribute_set.attributeRemove.html | 8 +- .../product_attribute_set.create.html | 8 +- .../product_attribute_set.groupAdd.html | 8 +- .../product_attribute_set.groupRemove.html | 8 +- .../product_attribute_set.groupRename.html | 8 +- .../product_attribute_set.list.html | 10 +- .../product_attribute_set.remove.html | 8 +- .../product_custom_option.add.html | 8 +- .../product_custom_option.info.html | 10 +- .../product_custom_option.list.html | 10 +- .../product_custom_option.remove.html | 8 +- .../product_custom_option.types.html | 10 +- .../product_custom_option.update.html | 8 +- .../product_custom_option_value.add.html | 8 +- .../product_custom_option_value.info.html | 10 +- .../product_custom_option_value.list.html | 10 +- .../product_custom_option_value.remove.html | 8 +- .../product_custom_option_value.update.html | 7 +- .../product_downloadable_link.add.html | 8 +- .../product_downloadable_link.list.html | 10 +- .../product_downloadable_link.remove.html | 8 +- .../catalogProductLink.html | 2 +- .../catalog_product_link.assign.html | 8 +- .../catalog_product_link.attributes.html | 10 +- .../catalog_product_link.list.html | 10 +- .../catalog_product_link.remove.html | 8 +- .../catalog_product_link.types.html | 10 +- .../catalog_product_link.update.html | 8 +- .../catalogProductTag/catalogProductTag.html | 2 +- .../catalogProductTag/product_tag.add.html | 8 +- .../catalogProductTag/product_tag.info.html | 10 +- .../catalogProductTag/product_tag.list.html | 10 +- .../catalogProductTag/product_tag.remove.html | 8 +- .../catalogProductTag/product_tag.update.html | 8 +- .../catalogProductTierPrice.html | 2 +- ...log_product_attribute_tier_price.info.html | 12 +- ...g_product_attribute_tier_price.update.html | 8 +- .../catalog_product_type.list.html | 10 +- .../catalogProductTypes/productTypes.html | 2 +- .../api/soap/catalogInventory/Inventory.html | 6 +- .../cataloginventory_stock_item.list.html | 10 +- .../cataloginventory_stock_item.update.html | 8 +- .../api/soap/checkout/cart/cart.create.html | 8 +- guides/m1x/api/soap/checkout/cart/cart.html | 3 +- .../m1x/api/soap/checkout/cart/cart.info.html | 8 +- .../api/soap/checkout/cart/cart.license.html | 10 +- .../api/soap/checkout/cart/cart.order.html | 6 +- .../api/soap/checkout/cart/cart.totals.html | 10 +- .../checkout/cartCoupon/cart_coupon.add.html | 8 +- .../cartCoupon/cart_coupon.remove.html | 8 +- .../cartCustomer/cart_customer.addresses.html | 8 +- .../cartCustomer/cart_customer.set.html | 6 +- .../cartPayment/cart_payment.list.html | 4 +- .../cartPayment/cart_payment.method.html | 8 +- .../cartProduct/cart_product.add.html | 8 +- .../cartProduct/cart_product.list.html | 10 +- .../cart_product.moveToCustomerQuote.html | 2 +- .../cartProduct/cart_product.remove.html | 8 +- .../cartProduct/cart_product.update.html | 8 +- .../cartShipping/cart_shipping.list.html | 8 +- .../cartShipping/cart_shipping.method.html | 8 +- guides/m1x/api/soap/checkout/checkout.html | 1 - guides/m1x/api/soap/create_your_own_api.html | 42 +- .../api/soap/customer/customer.create.html | 8 +- .../api/soap/customer/customer.delete.html | 8 +- guides/m1x/api/soap/customer/customer.html | 3 +- .../m1x/api/soap/customer/customer.info.html | 10 +- .../m1x/api/soap/customer/customer.list.html | 12 +- .../api/soap/customer/customer.update.html | 8 +- .../customerAddress/customerAddress.html | 2 +- .../customer_address.create.html | 8 +- .../customer_address.delete.html | 8 +- .../customer_address.info.html | 10 +- .../customer_address.list.html | 10 +- .../customer_address.update.html | 8 +- .../m1x/api/soap/customer/customer_group.html | 10 +- guides/m1x/api/soap/directory/directory.html | 1 - .../directory/directory_country.list.html | 10 +- .../soap/directory/directory_region.list.html | 10 +- .../cartGiftCard/cart_giftcard.add.html | 8 +- .../cartGiftCard/cart_giftcard.list.html | 10 +- .../cartGiftCard/cart_giftcard.remove.html | 8 +- .../enterprise_giftCard.html | 8 +- .../giftcard_account.create.html | 8 +- .../giftcard_account.info.html | 10 +- .../giftcard_account.list.html | 12 +- .../giftcard_account.remove.html | 8 +- .../giftcard_account.update.html | 8 +- .../giftcard_customer.info.html | 10 +- .../giftcard_customer.redeem.html | 8 +- .../enterpriseGiftMessage/giftMessage.html | 2 +- .../giftmessage.setForQuote.html | 10 +- .../giftmessage.setForQuoteItem.html | 10 +- .../giftmessage.setForQuoteProduct.html | 8 +- .../customerBalance/storecredit.balance.html | 8 +- .../customerBalance/storecredit.history.html | 10 +- .../enterprise_customerbalance.html | 10 +- .../storecredit_quote.removeAmount.html | 8 +- .../storecredit_quote.setAmount.html | 8 +- guides/m1x/api/soap/introduction.html | 18 +- .../api/soap/miscellaneous/magento.info.html | 10 +- .../api/soap/miscellaneous/store.info.html | 12 +- .../api/soap/miscellaneous/store.list.html | 10 +- .../api/soap/sales/salesOrder/salesOrder.html | 4 +- .../salesOrder/sales_order.addComment.html | 8 +- .../sales/salesOrder/sales_order.cancel.html | 8 +- .../sales/salesOrder/sales_order.hold.html | 8 +- .../sales/salesOrder/sales_order.info.html | 10 +- .../sales/salesOrder/sales_order.list.html | 12 +- .../sales/salesOrder/sales_order.unhold.html | 8 +- .../salesOrderCreditMemo.html | 4 +- .../sales_order_creditmemo.addComment.html | 8 +- .../sales_order_creditmemo.cancel.html | 2 +- .../sales_order_creditmemo.create.html | 8 +- .../sales_order_creditmemo.info.html | 10 +- .../sales_order_creditmemo.list.html | 12 +- .../salesOrderInvoice/salesOrderInvoice.html | 2 +- .../sales_order_invoice.addComment.html | 8 +- .../sales_order_invoice.cancel.html | 2 +- .../sales_order_invoice.capture.html | 8 +- .../sales_order_invoice.create.html | 8 +- .../sales_order_invoice.info.html | 10 +- .../sales_order_invoice.list.html | 12 +- .../salesOrderShipment.html | 2 +- .../sales_order_shipment.addComment.html | 8 +- .../sales_order_shipment.addTrack.html | 8 +- .../sales_order_shipment.create.html | 8 +- .../sales_order_shipment.getCarriers.html | 10 +- .../sales_order_shipment.info.html | 8 +- .../sales_order_shipment.list.html | 12 +- .../sales_order_shipment.removeTrack.html | 8 +- guides/m1x/api/soap/wsi_compliance.html | 6 +- guides/m1x/ce18-ee113-home.html | 25 +- guides/m1x/ce18-ee113/EE113-benchmark.html | 26 +- .../m1x/ce18-ee113/ce1.8_release-notes.html | 1972 ++++--- .../m1x/ce18-ee113/ee1.13_release-notes.html | 3059 ++++++---- .../ce18-ee113/ht_magento-ce-sample.data.html | 4 +- guides/m1x/ce18-ee113/using_redis.html | 4 +- guides/m1x/ce19-ee114-home.html | 114 +- guides/m1x/ce19-ee114/RWD_dev-guide.html | 46 +- .../m1x/ce19-ee114/RWD_responsive_emails.html | 949 ++-- .../m1x/ce19-ee114/ce1.9_release-notes.html | 195 +- .../m1x/ce19-ee114/ee1.14_release-notes.html | 1825 +++--- guides/m1x/ce19-ee114/ios-instrux.html | 11 +- .../images/2167-Benchmark-Config-Doc-R1.png | Bin 0 -> 2002873 bytes ...13_Benchmark_Report_Shopper_Flows_r1v1.png | Bin 0 -> 9237 bytes ...179-1.13_Benchmark_Report_Catalog_r3v1.png | Bin 0 -> 11396 bytes ...enchmark_Report_Partial_Reindexingr2v1.png | Bin 0 -> 6197 bytes ..._Benchmark_Report_Full_Reindexing_r1v1.png | Bin 0 -> 2243 bytes ...mark_Report_Individual_Reindexing_r1v1.png | Bin 0 -> 4427 bytes ...13_Benchmark_Report_Checkout_Flow_r1v1.png | Bin 0 -> 9408 bytes ...chmark_Report_Registered_Checkout_r1v1.png | Bin 0 -> 9951 bytes ...-1.13_Benchmark_Report_Page_Views_r2v1.png | Bin 0 -> 14170 bytes ...nchmark_Report_Software_Component_r1v1.png | Bin 0 -> 13825 bytes guides/m1x/images/30737051.png | Bin 0 -> 10255 bytes guides/m1x/images/30737052.png | Bin 0 -> 9346 bytes guides/m1x/images/35619336.png | Bin 0 -> 14477 bytes guides/m1x/images/EE-spt-portal.png | Bin 0 -> 61231 bytes guides/m1x/images/Magento_MVC.pdf | Bin 0 -> 70048 bytes guides/m1x/images/NumberOfVisitors.png | Bin 0 -> 6890 bytes guides/m1x/images/RWD_icon_sprite.psd | Bin 0 -> 2927767 bytes guides/m1x/images/RWD_social_icons.psd | Bin 0 -> 5048975 bytes .../m1x/images/admin-panel-custom-theme.png | Bin 0 -> 25459 bytes guides/m1x/images/appsec-900_confirm.png | Bin 0 -> 309992 bytes guides/m1x/images/blend-toc.png | Bin 0 -> 84 bytes .../m1x/images/custom-theme-dir-structure.png | Bin 0 -> 7413 bytes .../custom-theme-dir-structure_image.ai | 4975 +++++++++++++++++ .../custom-theme-dir-structure_image.png | Bin 0 -> 17327 bytes guides/m1x/images/custom_skin-dir.png | Bin 0 -> 3030 bytes guides/m1x/images/disable-cache-confirm.png | Bin 0 -> 23339 bytes guides/m1x/images/disable-cache.png | Bin 0 -> 26153 bytes .../ht_magento-REST-API_add_new_rest_role.png | Bin 0 -> 11833 bytes .../ht_magento-REST-API_cache_management.png | Bin 0 -> 23982 bytes .../ht_magento-REST-API_dir-structure.png | Bin 0 -> 3506 bytes ...agento-REST-API_disable-cache-magement.png | Bin 0 -> 28406 bytes ...nto-REST-API_disable-cache-magementMock.ai | 4603 +++++++++++++++ ...-REST-API_edit_rest_role_api_resources.png | Bin 0 -> 20746 bytes ..._magento-REST-API_edit_rest_role_users.png | Bin 0 -> 14173 bytes ...t_magento-REST-API_manage_coupon_codes.png | Bin 0 -> 32527 bytes .../ht_magento-REST-API_new-coupon-codes.png | Bin 0 -> 1263 bytes ...ht_magento-REST-API_new_oauth_consumer.png | Bin 0 -> 17500 bytes ..._magento-REST-API_oauth-request-access.png | Bin 0 -> 45651 bytes .../ht_magento-REST-API_phpinfo-oauth.png | Bin 0 -> 3950 bytes ...t_magento-REST-API_rest-api-attributes.png | Bin 0 -> 18600 bytes .../ht_magento-REST-API_rest_rule_actions.png | Bin 0 -> 12084 bytes .../ht_magento-REST-API_rest_rule_info.png | Bin 0 -> 9637 bytes ...ento-REST-API_shopping_cart_price_rule.png | Bin 0 -> 24095 bytes ...ento-REST-API_verify_view-coupon-codes.png | Bin 0 -> 31952 bytes ...o-REST-API_verify_view-coupon-codesMock.ai | 4799 ++++++++++++++++ ...-REST-API_verify_view-coupon-codesMock.png | Bin 0 -> 37205 bytes .../images/ht_magento-solr_catalog-search.png | Bin 0 -> 22067 bytes .../ht_magento-solr_catalog-searchMock.png | Bin 0 -> 28180 bytes .../ht_magento-solr_catalog-searchMock.png.ai | 4746 ++++++++++++++++ .../ht_magento-solr_default-search1.png | Bin 0 -> 48505 bytes .../images/ht_magento-solr_refresh-fpc.png | Bin 0 -> 25468 bytes .../ht_magento-solr_reindex_catalog.png | Bin 0 -> 29877 bytes .../images/ht_magento-solr_solr-search1.png | Bin 0 -> 50320 bytes .../images/ht_magento-solr_solr-search2.png | Bin 0 -> 50134 bytes .../ht_magento-solr_test-connect_fail.png | Bin 0 -> 1268 bytes .../ht_magento-solr_test-connect_succeed.png | Bin 0 -> 1098 bytes guides/m1x/images/icon-caution.png | Bin 0 -> 887 bytes guides/m1x/images/icon-important.png | Bin 0 -> 943 bytes guides/m1x/images/icon-note.png | Bin 0 -> 1469 bytes guides/m1x/images/icon-tip.png | Bin 0 -> 2022 bytes ...ndex-management_product-url-key-attrib.png | Bin 0 -> 8608 bytes .../images/install_configuration_database.png | Bin 0 -> 5922 bytes guides/m1x/images/install_confirm.png | Bin 0 -> 14667 bytes guides/m1x/images/install_confirm_mock.ai | 4611 +++++++++++++++ guides/m1x/images/install_confirm_mock.png | Bin 0 -> 17207 bytes .../images/install_create-admin-account.png | Bin 0 -> 11920 bytes guides/m1x/images/install_first-page.png | Bin 0 -> 27893 bytes guides/m1x/images/install_localization.png | Bin 0 -> 13644 bytes .../m1x/images/install_myphpadmin_change.png | Bin 0 -> 12452 bytes .../images/install_myphpadmin_edit-icon.png | Bin 0 -> 281 bytes guides/m1x/images/install_myphpadmin_edit.png | Bin 0 -> 12570 bytes .../m1x/images/install_myphpadmin_results.png | Bin 0 -> 14002 bytes .../m1x/images/install_myphpadmin_search.png | Bin 0 -> 12091 bytes guides/m1x/images/install_session-storage.png | Bin 0 -> 1727 bytes guides/m1x/images/install_verify-version.png | Bin 0 -> 3341 bytes .../m1x/images/install_verify-version_mock.ai | 4608 +++++++++++++++ .../images/install_verify-version_mock.png | Bin 0 -> 4624 bytes .../m1x/images/install_web-access-options.png | Bin 0 -> 13262 bytes guides/m1x/images/m1xheader.png | Bin 0 -> 1378 bytes guides/m1x/images/new.png | Bin 0 -> 446 bytes guides/m1x/images/permissions2.png | Bin 0 -> 11130 bytes .../m1x/images/resp_email_header-template.png | Bin 0 -> 22843 bytes guides/m1x/images/resp_email_logo.png | Bin 0 -> 34499 bytes .../m1x/images/resp_email_template_scope.png | Bin 0 -> 5588 bytes guides/m1x/images/resp_email_using-header.png | Bin 0 -> 28805 bytes guides/m1x/images/rest-intro1.png | Bin 0 -> 48671 bytes guides/m1x/images/rest_attributes-conf.png | Bin 0 -> 26521 bytes guides/m1x/images/rest_oauth-config2.png | Bin 0 -> 9346 bytes guides/m1x/images/rest_oauth-config3.png | Bin 0 -> 19801 bytes guides/m1x/images/rest_oauth-config4.png | Bin 0 -> 19801 bytes guides/m1x/images/rest_oauth1.png | Bin 0 -> 6124 bytes guides/m1x/images/rest_oauth2.png | Bin 0 -> 25929 bytes guides/m1x/images/rest_oauth_config1.png | Bin 0 -> 10255 bytes guides/m1x/images/rest_permissions1.png | Bin 0 -> 13455 bytes guides/m1x/images/rest_permissions2.png | Bin 0 -> 15673 bytes guides/m1x/images/rest_roles-conf.png | Bin 0 -> 11962 bytes guides/m1x/images/rest_test1.png | Bin 0 -> 11934 bytes guides/m1x/images/rest_test10.png | Bin 0 -> 12890 bytes guides/m1x/images/rest_test11.png | Bin 0 -> 9334 bytes guides/m1x/images/rest_test12.png | Bin 0 -> 28799 bytes guides/m1x/images/rest_test3.png | Bin 0 -> 9516 bytes guides/m1x/images/rest_test4.png | Bin 0 -> 17403 bytes guides/m1x/images/rest_test5.png | Bin 0 -> 5455 bytes guides/m1x/images/rest_test6.png | Bin 0 -> 31665 bytes guides/m1x/images/rest_test7.png | Bin 0 -> 11807 bytes guides/m1x/images/rest_test8.png | Bin 0 -> 14147 bytes guides/m1x/images/rest_test9.png | Bin 0 -> 10444 bytes guides/m1x/images/rest_test_authheader.png | Bin 0 -> 32432 bytes guides/m1x/images/rest_test_insert.png | Bin 0 -> 47381 bytes guides/m1x/images/rest_test_oauth_tab.png | Bin 0 -> 42634 bytes guides/m1x/images/soap_wsdl-wsi.png | Bin 0 -> 27554 bytes guides/m1x/images/soap_wsdl.png | Bin 0 -> 24863 bytes guides/m1x/images/soap_wsi-config.png | Bin 0 -> 5561 bytes .../m1x/images/upgrade_index-management.png | Bin 0 -> 33413 bytes .../m1x/images/upgrade_index-management2.png | Bin 0 -> 30580 bytes .../images/upgrade_index-management_after.png | Bin 0 -> 22700 bytes ...pgrade_index-management_when-scheduled.png | Bin 0 -> 12725 bytes guides/m1x/images/upgrade_log.png | Bin 0 -> 14589 bytes guides/m1x/images/upgrade_url-redirects.png | Bin 0 -> 20267 bytes guides/m1x/index.html | 32 +- .../install/installer-privileges_after.html | 16 +- .../install/installer-privileges_before.html | 12 +- guides/m1x/install/installing.html | 27 +- guides/m1x/install/installing_install.html | 68 +- .../install/installing_req-prereq_centos.html | 22 +- .../install/installing_req-prereq_ubuntu.html | 51 +- ...stalling_upgrade_ce18_upgrade-roadmap.html | 12 +- .../install/installing_upgrade_details.html | 92 +- .../installing_upgrade_from-ee112.html | 38 +- ...installing_upgrade_from-ee11300-or-01.html | 12 +- .../install/installing_upgrade_landing.html | 63 +- guides/m1x/magefordev/mage-for-dev-1.html | 112 +- guides/m1x/magefordev/mage-for-dev-2.html | 25 +- guides/m1x/magefordev/mage-for-dev-3.html | 57 +- guides/m1x/magefordev/mage-for-dev-4.html | 25 +- guides/m1x/magefordev/mage-for-dev-5.html | 39 +- guides/m1x/magefordev/mage-for-dev-6.html | 36 +- guides/m1x/magefordev/mage-for-dev-7.html | 43 +- guides/m1x/magefordev/mage-for-dev-8.html | 33 +- guides/m1x/other/appsec-900_addhandler.html | 18 +- .../m1x/other/discover-card-validation.html | 12 +- guides/m1x/other/ee_connect_patches.html | 15 +- .../m1x/other/ht_extend_magento_rest_api.html | 64 +- guides/m1x/other/ht_install-patches.html | 14 +- guides/m1x/other/ht_magento-solr.html | 1068 ++-- guides/m1x/other/ios-instrux.html | 10 +- guides/m1x/other/payflow.html | 13 +- guides/m1x/other/php5.4_patch.html | 8 +- guides/m1x/other/remote-code-exploit.html | 18 +- guides/m1x/other/solr-ee-patches.html | 17 +- guides/m1x/system-requirements.md | 27 +- 373 files changed, 36224 insertions(+), 5355 deletions(-) create mode 100644 guides/m1x/.gitignore create mode 100644 guides/m1x/LICENSE.txt create mode 100644 guides/m1x/images/2167-Benchmark-Config-Doc-R1.png create mode 100644 guides/m1x/images/2178-1.13_Benchmark_Report_Shopper_Flows_r1v1.png create mode 100644 guides/m1x/images/2179-1.13_Benchmark_Report_Catalog_r3v1.png create mode 100644 guides/m1x/images/2180-1.13_Benchmark_Report_Partial_Reindexingr2v1.png create mode 100644 guides/m1x/images/2182-1.13_Benchmark_Report_Full_Reindexing_r1v1.png create mode 100644 guides/m1x/images/2183-1.13_Benchmark_Report_Individual_Reindexing_r1v1.png create mode 100644 guides/m1x/images/2184-1.13_Benchmark_Report_Checkout_Flow_r1v1.png create mode 100644 guides/m1x/images/2185-1.13_Benchmark_Report_Registered_Checkout_r1v1.png create mode 100644 guides/m1x/images/2186-1.13_Benchmark_Report_Page_Views_r2v1.png create mode 100644 guides/m1x/images/2187-1.13_Benchmark_Report_Software_Component_r1v1.png create mode 100644 guides/m1x/images/30737051.png create mode 100644 guides/m1x/images/30737052.png create mode 100644 guides/m1x/images/35619336.png create mode 100644 guides/m1x/images/EE-spt-portal.png create mode 100644 guides/m1x/images/Magento_MVC.pdf create mode 100644 guides/m1x/images/NumberOfVisitors.png create mode 100644 guides/m1x/images/RWD_icon_sprite.psd create mode 100644 guides/m1x/images/RWD_social_icons.psd create mode 100644 guides/m1x/images/admin-panel-custom-theme.png create mode 100644 guides/m1x/images/appsec-900_confirm.png create mode 100644 guides/m1x/images/blend-toc.png create mode 100644 guides/m1x/images/custom-theme-dir-structure.png create mode 100644 guides/m1x/images/custom-theme-dir-structure_image.ai create mode 100644 guides/m1x/images/custom-theme-dir-structure_image.png create mode 100644 guides/m1x/images/custom_skin-dir.png create mode 100644 guides/m1x/images/disable-cache-confirm.png create mode 100644 guides/m1x/images/disable-cache.png create mode 100644 guides/m1x/images/ht_magento-REST-API_add_new_rest_role.png create mode 100644 guides/m1x/images/ht_magento-REST-API_cache_management.png create mode 100644 guides/m1x/images/ht_magento-REST-API_dir-structure.png create mode 100644 guides/m1x/images/ht_magento-REST-API_disable-cache-magement.png create mode 100644 guides/m1x/images/ht_magento-REST-API_disable-cache-magementMock.ai create mode 100644 guides/m1x/images/ht_magento-REST-API_edit_rest_role_api_resources.png create mode 100644 guides/m1x/images/ht_magento-REST-API_edit_rest_role_users.png create mode 100644 guides/m1x/images/ht_magento-REST-API_manage_coupon_codes.png create mode 100644 guides/m1x/images/ht_magento-REST-API_new-coupon-codes.png create mode 100644 guides/m1x/images/ht_magento-REST-API_new_oauth_consumer.png create mode 100644 guides/m1x/images/ht_magento-REST-API_oauth-request-access.png create mode 100644 guides/m1x/images/ht_magento-REST-API_phpinfo-oauth.png create mode 100644 guides/m1x/images/ht_magento-REST-API_rest-api-attributes.png create mode 100644 guides/m1x/images/ht_magento-REST-API_rest_rule_actions.png create mode 100644 guides/m1x/images/ht_magento-REST-API_rest_rule_info.png create mode 100644 guides/m1x/images/ht_magento-REST-API_shopping_cart_price_rule.png create mode 100644 guides/m1x/images/ht_magento-REST-API_verify_view-coupon-codes.png create mode 100644 guides/m1x/images/ht_magento-REST-API_verify_view-coupon-codesMock.ai create mode 100644 guides/m1x/images/ht_magento-REST-API_verify_view-coupon-codesMock.png create mode 100644 guides/m1x/images/ht_magento-solr_catalog-search.png create mode 100644 guides/m1x/images/ht_magento-solr_catalog-searchMock.png create mode 100644 guides/m1x/images/ht_magento-solr_catalog-searchMock.png.ai create mode 100644 guides/m1x/images/ht_magento-solr_default-search1.png create mode 100644 guides/m1x/images/ht_magento-solr_refresh-fpc.png create mode 100644 guides/m1x/images/ht_magento-solr_reindex_catalog.png create mode 100644 guides/m1x/images/ht_magento-solr_solr-search1.png create mode 100644 guides/m1x/images/ht_magento-solr_solr-search2.png create mode 100644 guides/m1x/images/ht_magento-solr_test-connect_fail.png create mode 100644 guides/m1x/images/ht_magento-solr_test-connect_succeed.png create mode 100644 guides/m1x/images/icon-caution.png create mode 100644 guides/m1x/images/icon-important.png create mode 100644 guides/m1x/images/icon-note.png create mode 100644 guides/m1x/images/icon-tip.png create mode 100644 guides/m1x/images/index-management_product-url-key-attrib.png create mode 100644 guides/m1x/images/install_configuration_database.png create mode 100644 guides/m1x/images/install_confirm.png create mode 100644 guides/m1x/images/install_confirm_mock.ai create mode 100644 guides/m1x/images/install_confirm_mock.png create mode 100644 guides/m1x/images/install_create-admin-account.png create mode 100644 guides/m1x/images/install_first-page.png create mode 100644 guides/m1x/images/install_localization.png create mode 100644 guides/m1x/images/install_myphpadmin_change.png create mode 100644 guides/m1x/images/install_myphpadmin_edit-icon.png create mode 100644 guides/m1x/images/install_myphpadmin_edit.png create mode 100644 guides/m1x/images/install_myphpadmin_results.png create mode 100644 guides/m1x/images/install_myphpadmin_search.png create mode 100644 guides/m1x/images/install_session-storage.png create mode 100644 guides/m1x/images/install_verify-version.png create mode 100644 guides/m1x/images/install_verify-version_mock.ai create mode 100644 guides/m1x/images/install_verify-version_mock.png create mode 100644 guides/m1x/images/install_web-access-options.png create mode 100644 guides/m1x/images/m1xheader.png create mode 100644 guides/m1x/images/new.png create mode 100644 guides/m1x/images/permissions2.png create mode 100644 guides/m1x/images/resp_email_header-template.png create mode 100644 guides/m1x/images/resp_email_logo.png create mode 100644 guides/m1x/images/resp_email_template_scope.png create mode 100644 guides/m1x/images/resp_email_using-header.png create mode 100644 guides/m1x/images/rest-intro1.png create mode 100644 guides/m1x/images/rest_attributes-conf.png create mode 100644 guides/m1x/images/rest_oauth-config2.png create mode 100644 guides/m1x/images/rest_oauth-config3.png create mode 100644 guides/m1x/images/rest_oauth-config4.png create mode 100644 guides/m1x/images/rest_oauth1.png create mode 100644 guides/m1x/images/rest_oauth2.png create mode 100644 guides/m1x/images/rest_oauth_config1.png create mode 100644 guides/m1x/images/rest_permissions1.png create mode 100644 guides/m1x/images/rest_permissions2.png create mode 100644 guides/m1x/images/rest_roles-conf.png create mode 100644 guides/m1x/images/rest_test1.png create mode 100644 guides/m1x/images/rest_test10.png create mode 100644 guides/m1x/images/rest_test11.png create mode 100644 guides/m1x/images/rest_test12.png create mode 100644 guides/m1x/images/rest_test3.png create mode 100644 guides/m1x/images/rest_test4.png create mode 100644 guides/m1x/images/rest_test5.png create mode 100644 guides/m1x/images/rest_test6.png create mode 100644 guides/m1x/images/rest_test7.png create mode 100644 guides/m1x/images/rest_test8.png create mode 100644 guides/m1x/images/rest_test9.png create mode 100644 guides/m1x/images/rest_test_authheader.png create mode 100644 guides/m1x/images/rest_test_insert.png create mode 100644 guides/m1x/images/rest_test_oauth_tab.png create mode 100644 guides/m1x/images/soap_wsdl-wsi.png create mode 100644 guides/m1x/images/soap_wsdl.png create mode 100644 guides/m1x/images/soap_wsi-config.png create mode 100644 guides/m1x/images/upgrade_index-management.png create mode 100644 guides/m1x/images/upgrade_index-management2.png create mode 100644 guides/m1x/images/upgrade_index-management_after.png create mode 100644 guides/m1x/images/upgrade_index-management_when-scheduled.png create mode 100644 guides/m1x/images/upgrade_log.png create mode 100644 guides/m1x/images/upgrade_url-redirects.png diff --git a/guides/m1x/.gitignore b/guides/m1x/.gitignore new file mode 100644 index 0000000000..7674aac7d7 --- /dev/null +++ b/guides/m1x/.gitignore @@ -0,0 +1,4 @@ +# OS Files +.DS_Store +.vscode +thumbs.db diff --git a/guides/m1x/LICENSE.txt b/guides/m1x/LICENSE.txt new file mode 100644 index 0000000000..49dc8ec82e --- /dev/null +++ b/guides/m1x/LICENSE.txt @@ -0,0 +1,48 @@ + +Open Software License ("OSL") v. 3.0 + +This Open Software License (the "License") applies to any original work of authorship (the "Original Work") whose owner (the "Licensor") has placed the following licensing notice adjacent to the copyright notice for the Original Work: + +Licensed under the Open Software License version 3.0 + + 1. Grant of Copyright License. Licensor grants You a worldwide, royalty-free, non-exclusive, sublicensable license, for the duration of the copyright, to do the following: + + 1. to reproduce the Original Work in copies, either alone or as part of a collective work; + + 2. to translate, adapt, alter, transform, modify, or arrange the Original Work, thereby creating derivative works ("Derivative Works") based upon the Original Work; + + 3. to distribute or communicate copies of the Original Work and Derivative Works to the public, with the proviso that copies of Original Work or Derivative Works that You distribute or communicate shall be licensed under this Open Software License; + + 4. to perform the Original Work publicly; and + + 5. to display the Original Work publicly. + + 2. Grant of Patent License. Licensor grants You a worldwide, royalty-free, non-exclusive, sublicensable license, under patent claims owned or controlled by the Licensor that are embodied in the Original Work as furnished by the Licensor, for the duration of the patents, to make, use, sell, offer for sale, have made, and import the Original Work and Derivative Works. + + 3. Grant of Source Code License. The term "Source Code" means the preferred form of the Original Work for making modifications to it and all available documentation describing how to modify the Original Work. Licensor agrees to provide a machine-readable copy of the Source Code of the Original Work along with each copy of the Original Work that Licensor distributes. Licensor reserves the right to satisfy this obligation by placing a machine-readable copy of the Source Code in an information repository reasonably calculated to permit inexpensive and convenient access by You for as long as Licensor continues to distribute the Original Work. + + 4. Exclusions From License Grant. Neither the names of Licensor, nor the names of any contributors to the Original Work, nor any of their trademarks or service marks, may be used to endorse or promote products derived from this Original Work without express prior permission of the Licensor. Except as expressly stated herein, nothing in this License grants any license to Licensor's trademarks, copyrights, patents, trade secrets or any other intellectual property. No patent license is granted to make, use, sell, offer for sale, have made, or import embodiments of any patent claims other than the licensed claims defined in Section 2. No license is granted to the trademarks of Licensor even if such marks are included in the Original Work. Nothing in this License shall be interpreted to prohibit Licensor from licensing under terms different from this License any Original Work that Licensor otherwise would have a right to license. + + 5. External Deployment. The term "External Deployment" means the use, distribution, or communication of the Original Work or Derivative Works in any way such that the Original Work or Derivative Works may be used by anyone other than You, whether those works are distributed or communicated to those persons or made available as an application intended for use over a network. As an express condition for the grants of license hereunder, You must treat any External Deployment by You of the Original Work or a Derivative Work as a distribution under section 1(c). + + 6. Attribution Rights. You must retain, in the Source Code of any Derivative Works that You create, all copyright, patent, or trademark notices from the Source Code of the Original Work, as well as any notices of licensing and any descriptive text identified therein as an "Attribution Notice." You must cause the Source Code for any Derivative Works that You create to carry a prominent Attribution Notice reasonably calculated to inform recipients that You have modified the Original Work. + + 7. Warranty of Provenance and Disclaimer of Warranty. Licensor warrants that the copyright in and to the Original Work and the patent rights granted herein by Licensor are owned by the Licensor or are sublicensed to You under the terms of this License with the permission of the contributor(s) of those copyrights and patent rights. Except as expressly stated in the immediately preceding sentence, the Original Work is provided under this License on an "AS IS" BASIS and WITHOUT WARRANTY, either express or implied, including, without limitation, the warranties of non-infringement, merchantability or fitness for a particular purpose. THE ENTIRE RISK AS TO THE QUALITY OF THE ORIGINAL WORK IS WITH YOU. This DISCLAIMER OF WARRANTY constitutes an essential part of this License. No license to the Original Work is granted by this License except under this disclaimer. + + 8. Limitation of Liability. Under no circumstances and under no legal theory, whether in tort (including negligence), contract, or otherwise, shall the Licensor be liable to anyone for any indirect, special, incidental, or consequential damages of any character arising as a result of this License or the use of the Original Work including, without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses. This limitation of liability shall not apply to the extent applicable law prohibits such limitation. + + 9. Acceptance and Termination. If, at any time, You expressly assented to this License, that assent indicates your clear and irrevocable acceptance of this License and all of its terms and conditions. If You distribute or communicate copies of the Original Work or a Derivative Work, You must make a reasonable effort under the circumstances to obtain the express assent of recipients to the terms of this License. This License conditions your rights to undertake the activities listed in Section 1, including your right to create Derivative Works based upon the Original Work, and doing so without honoring these terms and conditions is prohibited by copyright law and international treaty. Nothing in this License is intended to affect copyright exceptions and limitations (including 'fair use' or 'fair dealing'). This License shall terminate immediately and You may no longer exercise any of the rights granted to You by this License upon your failure to honor the conditions in Section 1(c). + + 10. Termination for Patent Action. This License shall terminate automatically and You may no longer exercise any of the rights granted to You by this License as of the date You commence an action, including a cross-claim or counterclaim, against Licensor or any licensee alleging that the Original Work infringes a patent. This termination provision shall not apply for an action alleging patent infringement by combinations of the Original Work with other software or hardware. + + 11. Jurisdiction, Venue and Governing Law. Any action or suit relating to this License may be brought only in the courts of a jurisdiction wherein the Licensor resides or in which Licensor conducts its primary business, and under the laws of that jurisdiction excluding its conflict-of-law provisions. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any use of the Original Work outside the scope of this License or after its termination shall be subject to the requirements and penalties of copyright or patent law in the appropriate jurisdiction. This section shall survive the termination of this License. + + 12. Attorneys' Fees. In any action to enforce the terms of this License or seeking damages relating thereto, the prevailing party shall be entitled to recover its costs and expenses, including, without limitation, reasonable attorneys' fees and costs incurred in connection with such action, including any appeal of such action. This section shall survive the termination of this License. + + 13. Miscellaneous. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. + + 14. Definition of "You" in This License. "You" throughout this License, whether in upper or lower case, means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License. For legal entities, "You" includes any entity that controls, is controlled by, or is under common control with you. For purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. + + 15. Right to Use. You may use the Original Work in all ways not otherwise restricted or conditioned by this License or by law, and Licensor promises not to interfere with or be responsible for such uses by You. + + 16. Modification of This License. This License is Copyright (C) 2005 Lawrence Rosen. Permission is granted to copy, distribute, or communicate this License without modification. Nothing in this License permits You to modify this License as applied to the Original Work or to Derivative Works. However, You may modify the text of this License and copy, distribute or communicate your modified version (the "Modified License") and apply it to other original works of authorship subject to the following conditions: (i) You may not indicate in any way that your Modified License is the "Open Software License" or "OSL" and you may not use those names in the name of your Modified License; (ii) You must replace the notice specified in the first paragraph above with the notice "Licensed under " or with a notice of your own that is not confusingly similar to the notice in this License; and (iii) You may not claim that your original works are open source software unless your Modified License has been approved by Open Source Initiative (OSI) and You comply with its license review and certification process. diff --git a/guides/m1x/api/rest-api-index.html b/guides/m1x/api/rest-api-index.html index a4a336ecb8..29ad407d26 100644 --- a/guides/m1x/api/rest-api-index.html +++ b/guides/m1x/api/rest-api-index.html @@ -6,40 +6,40 @@

Welcome to the Magento 1.x REST API home page.

\ No newline at end of file diff --git a/guides/m1x/api/rest/Resources/Orders/order_addresses.html b/guides/m1x/api/rest/Resources/Orders/order_addresses.html index 1b0bd68f3c..ce36d34a85 100644 --- a/guides/m1x/api/rest/Resources/Orders/order_addresses.html +++ b/guides/m1x/api/rest/Resources/Orders/order_addresses.html @@ -9,26 +9,26 @@

@@ -43,10 +43,10 @@

Allows you to retrieve information about billing and shipping addresses of the required order.

-

URL Structure: http://magentohost/api/rest/orders/:orderid/addresses
+

URL Structure: http://magentohost/api/rest/orders/:orderid/addresses
Version: 1

-

HTTP Method: GET
+
HTTP Method: GET

Description: Allows you to retrieve information on billing and shipping addresses from the required order.
Notes: Customers can retrieve addresses only from their orders.

@@ -58,12 +58,12 @@
HTTP Method: GE

Example:

- +
GET http://magentohost/api/rest/orders/32/addresses

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -102,21 +102,21 @@ 
HTTP Method: GE
-
HTTP Method: POST
+
HTTP Method: POST

Description: Not allowed.

-
HTTP Method: PUT
+
HTTP Method: PUT

Description: Not allowed.

-
HTTP Method: DELETE
+
HTTP Method: DELETE

Description: Not allowed.

URI: /orders/:orderid/addresses/billing

-
HTTP Method: GET
+
HTTP Method: GET

Description: Allows you to retrieve information on the order billing address.
Notes: Customers can retrieve information on billing addresses only from their own orders.

@@ -128,12 +128,12 @@
HTTP Method: GE

Example:

- +
GET http://magentohost/api/rest/orders/32/addresses/billing

Response example:

-
+
<?xml version="1.0"?>
 <magento_api>
   <region>Palau</region>
@@ -155,22 +155,22 @@ 
HTTP Method: GE
-
HTTP Method: POST
+
HTTP Method: POST

Description: Not allowed.

-
HTTP Method: PUT
+
HTTP Method: PUT

Description: Not allowed.

-
HTTP Method: DELETE
+
HTTP Method: DELETE

Description: Not allowed.

URI: /orders/:orderid/addresses/shipping

-
HTTP Method: GET
+
HTTP Method: GET

Description: Allows you to retrieve information on the order shipping address.
Notes: Customers can retrieve information on shipping addresses only from their own orders.

@@ -182,12 +182,12 @@
HTTP Method: GE

Example:

- +
GET http://magentohost/api/rest/orders/32/addresses/shipping

Response example:

-
+
<?xml version="1.0"?>
 <magento_api>
   <region>Massachusetts</region>
@@ -209,15 +209,15 @@ 
HTTP Method: GE
-
HTTP Method: POST
+
HTTP Method: POST

Description: Not allowed.

-
HTTP Method: PUT
+
HTTP Method: PUT

Description: Not allowed.

-
HTTP Method: DELETE
+
HTTP Method: DELETE

Description: Not allowed.

diff --git a/guides/m1x/api/rest/Resources/Orders/order_comments.html b/guides/m1x/api/rest/Resources/Orders/order_comments.html index 9306f1f6e8..8264051168 100644 --- a/guides/m1x/api/rest/Resources/Orders/order_comments.html +++ b/guides/m1x/api/rest/Resources/Orders/order_comments.html @@ -26,7 +26,7 @@

U

Allows you to retrieve information about comments of the required order.

-

URL Structure: http://magentohost/api/rest/orders/:orderid/comments
+

URL Structure: http://magentohost/api/rest/orders/:orderid/comments
Version: 1

HTTP Method: GET
@@ -40,12 +40,12 @@
HTTP Method: GET

Example:

- +
GET http://magentohost/api/rest/orders/33/comments

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -75,12 +75,12 @@ 
HTTP Method: GET

Example:

- +
GET http://magentohost/api/rest/orders/33/comments

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -145,4 +145,4 @@ 

Order C - + diff --git a/guides/m1x/api/rest/Resources/Orders/order_items.html b/guides/m1x/api/rest/Resources/Orders/order_items.html index cdb99eb12f..c42caad4bc 100644 --- a/guides/m1x/api/rest/Resources/Orders/order_items.html +++ b/guides/m1x/api/rest/Resources/Orders/order_items.html @@ -27,7 +27,7 @@

URI: /o

Allows you to retrieve information about order items.

-

URL Structure: http://magentohost/api/rest/orders/:orderId/items
+

URL Structure: http://magentohost/api/rest/orders/:orderId/items
Version: 1

HTTP Method: GET
@@ -42,12 +42,12 @@
HTTP Method: GETResponse Example: XML

- +
GET http://magentohost/api/rest/orders/410/items

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -118,12 +118,12 @@ 
HTTP Method: GETResponse Example: XML

- +
GET http://magentohost/api/rest/orders/410/items

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -175,4 +175,4 @@ 
HTTP Method: DEL - + diff --git a/guides/m1x/api/rest/Resources/Orders/sales_orders.html b/guides/m1x/api/rest/Resources/Orders/sales_orders.html index c54d6284e0..74247b8cc1 100644 --- a/guides/m1x/api/rest/Resources/Orders/sales_orders.html +++ b/guides/m1x/api/rest/Resources/Orders/sales_orders.html @@ -37,7 +37,7 @@

URI: /orders

Allows you to retrieve information on existing order/orders.

-

URL Structure: http://magentohost/api/rest/orders
+

URL Structure: http://magentohost/api/rest/orders
Version: 1

HTTP Method: GET /orders
@@ -50,11 +50,11 @@
HTTP Method

Response Example: XML

- +
GET http://magentohost/api/rest/orders
-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item_1>
@@ -231,7 +231,7 @@ 

URI: /orders/:id<

Allows you to retrieve information on a single order.
The list of attributes that will be returned for the order is configured in the Magento Admin Panel.

-

URL Structure: http://magentohost/api/rest/orders/:id
+

URL Structure: http://magentohost/api/rest/orders/:id
Version: 1

HTTP Method: GET /orders/:id
@@ -242,11 +242,11 @@
HTTP Me

Response Example: XML

- +
GET http://magentohost/api/rest/orders/32
-
+
<?xml version="1.0"?>
 <magento_api>
   <customer_id>3</customer_id>
@@ -364,4 +364,4 @@ 
HTTP - + diff --git a/guides/m1x/api/rest/Resources/Products/product_categories.html b/guides/m1x/api/rest/Resources/Products/product_categories.html index baf0b6bc4a..4366fd409c 100644 --- a/guides/m1x/api/rest/Resources/Products/product_categories.html +++ b/guides/m1x/api/rest/Resources/Products/product_categories.html @@ -30,7 +30,7 @@

http://magentohost/api/rest/products/productid/categories
+

URL Structure: http://magentohost/api/rest/products/productid/categories
Version: 1

HTTP Method: GET
@@ -45,12 +45,12 @@
HTTP Method:

Example:

- +
GET http://magentohost/api/rest/products/8/categories

Response Body:

-
+
{
      category_id: 8
 }
@@ -92,12 +92,12 @@
HTTP Method

Example:

- +
POST http://magentohost/api/rest/products/8/categories

Request Body:

-
+
{
 "category_id":"2"
 }
@@ -122,7 +122,7 @@
HTTP Meth

Example:

- +
DELETE http://magentohost/api/rest/products/8/categories/2

Possible HTTP Status Codes

@@ -152,4 +152,4 @@

Pos - + diff --git a/guides/m1x/api/rest/Resources/Products/product_images.html b/guides/m1x/api/rest/Resources/Products/product_images.html index f79264cb0f..50210923e8 100644 --- a/guides/m1x/api/rest/Resources/Products/product_images.html +++ b/guides/m1x/api/rest/Resources/Products/product_images.html @@ -10,28 +10,28 @@ @@ -46,10 +46,10 @@

Allows you to manage images of the required product.

-

URL Structure: http://magentohost/api/rest/products/:product_id/images
+

URL Structure: http://magentohost/api/rest/products/:product_id/images
Version: 1

-

HTTP Method: GET
+
HTTP Method: GET

Description: Allows you to retrieve information about all images of a specified product.
Notes: If there are custom attributes with the Catalog Input Type for Store Owner option set to Media Image, these attributes will be also returned in the response as an image type.

@@ -62,12 +62,12 @@
HTTP Method: GET

Example:

- +
GET http://magentohost/api/rest/products/8/images

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -97,7 +97,7 @@ 
HTTP Method: GET
-
HTTP Method: POST
+
HTTP Method: POST

Description: Allows you to add an image for the required product.

@@ -143,12 +143,12 @@
HTTP Method: PO

Example:

- +
POST http://magentohost/api/rest/products/1/images

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <file_mime_type>image/jpeg</file_mime_type>     <file_content>iVBORw0KGgoAAAANSUhEUgAAACgAAAAoCAYAAACM/rhtAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAWtJREFUeNpi/P//P8NgBkwMgxyMOnDUgTDAyMhIDNYF4vNA/B+IDwCxHLoakgEoFxODiQRXQUYi4e3k2gfDjMRajsP3zED8F8pmA+JvUDEYeArEMugOpFcanA/Ef6A0CPwC4uNoag5SnAjJjGI2tKhkg4rLAfFGIH4IxEuBWIjSKKYkDfZCHddLiwChVhokK8YGohwEZYy3aBmEKmDEhOCgreomo+VmZHxsMEQxIc2MAx3FO/DI3RxMmQTZkI9ALDCaSUYdOOrAIeRAPzQ+PxCHUM2FFDb5paGNBPRa5C20bUhxc4sSB4JaLnvxVHWHsbVu6OnACjyOg+HqgXKgGRD/JMKBoD6LDb0dyAPE94hwHAw/hGYcujlwEQmOg+EV9HJgLBmOg+FMWjsQVKR8psCBoDSrQqoDSSmoG6Hpj1wA6ju30LI9+BBX4UsC+Ai0T4BWVd1EIL5PgeO+APECmoXgaGtm1IE0AgABBgAJAICuV8dAUAAAAABJRU5ErkJggg==</file_content>
@@ -164,10 +164,10 @@ 

http://magentohost/api/rest/products/:product_id/images/store/:store_id
+

URL Structure: http://magentohost/api/rest/products/:product_id/images/store/:store_id
Version: 1

-

HTTP Method: GET
+
HTTP Method: GET

Description: Allows you to retrieve information about product images for a specified store view.
Notes: Images can have different labels for different stores. For example, image label "flower" in the English store view can be set as "fleur" in the French store view. If there are custom attributes with the Catalog Input Type for Store Owner option set to Media Image, these attributes will be also returned in the response as an image type.

@@ -180,12 +180,12 @@
HTTP Method: GET

Example:

- +
GET http://magentohost/api/rest/products/8/images/store/2

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -206,7 +206,7 @@ 
HTTP Method: GET
-
HTTP Method: POST
+
HTTP Method: POST

Description: Allows you to add an image for the required product with image settings for a specific store.
Notes: The image is added on the Global level; specified image parameters are set for a specific store.

@@ -252,12 +252,12 @@
HTTP Method: PO

Example:

- +
POST http://magentohost/api/rest/products/8/images/store/3

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <file_mime_type>image/jpeg</file_mime_type>    <file_content>iVBORw0KGgoAAAANSUhEUgAAACgAAAAoCAYAAACM/rhtAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAWtJREFUeNpi/P//P8NgBkwMgxyMOnDUgTDAyMhIDNYF4vNA/B+IDwCxHLoakgEoFxODiQRXQUYi4e3k2gfDjMRajsP3zED8F8pmA+JvUDEYeArEMugOpFcanA/Ef6A0CPwC4uNoag5SnAjJjGI2tKhkg4rLAfFGIH4IxEuBWIjSKKYkDfZCHddLiwChVhokK8YGohwEZYy3aBmEKmDEhOCgreomo+VmZHxsMEQxIc2MAx3FO/DI3RxMmQTZkI9ALDCaSUYdOOrAIeRAPzQ+PxCHUM2FFDb5paGNBPRa5C20bUhxc4sSB4JaLnvxVHWHsbVu6OnACjyOg+HqgXKgGRD/JMKBoD6LDb0dyAPE94hwHAw/hGYcujlwEQmOg+EV9HJgLBmOg+FMWjsQVKR8psCBoDSrQqoDSSmoG6Hpj1wA6ju30LI9+BBX4UsC+Ai0T4BWVd1EIL5PgeO+APECmoXgaGtm1IE0AgABBgAJAICuV8dAUAAAAABJRU5ErkJggg==</file_content>
@@ -272,11 +272,11 @@ 

http://magentohost/api/rest/products/:product_id/images/:image_id
+

URL Structure: http://magentohost/api/rest/products/:product_id/images/:image_id
Version: 1

-

HTTP Method: GET
+
HTTP Method: GET

Description: Allows you to retrieve information about a specified product image.
Notes: If there are custom attributes with the Catalog Input Type for Store Owner option set to Media Image, these attributes will be also returned in the response as an image type.

@@ -289,12 +289,12 @@
HTTP Method: GET

Example:

- +
GET http://magentohost/api/rest/products/8/images/7

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <id>7</id>
@@ -311,7 +311,7 @@ 
HTTP Method: GET
-
HTTP Method: PUT
+
HTTP Method: PUT

Description: Allows you to update information for the specified product image.
Notes: When updating information, you need to pass only those parameters that you want to be updated. Parameters that were not passed in the request, will preserve the previous values.

@@ -386,12 +386,12 @@
HTTP Method: PUT

Example:

- +
PUT http://magentohost/api/rest/products/8/images/7

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <label>English store image</label>
@@ -413,7 +413,7 @@ 
HTTP Method: PUT -
HTTP Method: DELETE
+
HTTP Method: DELETE

Description: Allows you to remove the specified image from a product.
Notes: The image will not be deleted physically, the image parameters will be set to No Image.

@@ -426,7 +426,7 @@
HTTP Method:

Example:

- +
DELETE http://magentohost/api/rest/products/14/images/6
@@ -435,11 +435,11 @@

http://magentohost/api/rest/products/:product_id/images/:image_id/store/:store_id
+

URL Structure: http://magentohost/api/rest/products/:product_id/images/:image_id/store/:store_id
Version: 1

-

HTTP Method: GET
+
HTTP Method: GET

Description: Allows you to retrieve information about the specified product image from a specified store.
Notes: If there are custom attributes with the Catalog Input Type for Store Owner option set to Media Image, these attributes will be also returned in the response as an image type.

@@ -452,12 +452,12 @@
HTTP Method: GET

Example:

- +
GET http://magentohost/api/rest/products/8/images/7/store/3

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <id>10</id>
@@ -474,7 +474,7 @@ 
HTTP Method: GET -
HTTP Method: PUT
+
HTTP Method: PUT

Description: Allows you to update the specified product image information for s specified store.
Notes: When updating information, you need to pass only those parameters that you want to be updated. Parameters that were not passed in the request will preserve the previous values.

@@ -549,12 +549,12 @@
HTTP Method: PUT

Example:

- +
PUT http://magentohost/api/rest/products/8/images/7/store/3

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <position>3</position>
@@ -569,7 +569,7 @@ 
HTTP Method: PUT -
HTTP Method: DELETE
+
HTTP Method: DELETE

Description: Allows you to remove an image from the required product in the specified store.
Notes: The image will not be deleted physically, the image parameters will be set to No Image for the current store.

@@ -581,7 +581,7 @@
HTTP Method:

Example:

- +
DELETE http://magentohost/api/rest/products/14/images/6/store/3
@@ -648,4 +648,4 @@

Possibl - + diff --git a/guides/m1x/api/rest/Resources/Products/product_websites.html b/guides/m1x/api/rest/Resources/Products/product_websites.html index 44ddde880b..ceb9027f84 100644 --- a/guides/m1x/api/rest/Resources/Products/product_websites.html +++ b/guides/m1x/api/rest/Resources/Products/product_websites.html @@ -37,7 +37,7 @@

Allows you to retrieve information about websites assigned to a product, assign a website to a product, and copy data for a product from a specified store view.

-

URL Structure: http://magentohost/api/rest/products/:product_id/websites
+

URL Structure: http://magentohost/api/rest/products/:product_id/websites
Version: 1

HTTP Method: GET
@@ -52,12 +52,12 @@
HTTP Method: G

Example:

- +
GET http://magentohost/api/rest/products/8/websites

Response Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -104,12 +104,12 @@ 
Website Ass

Example:

- +
POST http://magentohost/api/rest/products/8/websites

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
     <website_id>1</website_id>
@@ -122,7 +122,7 @@ 
Website Ass
-
+
<?xml version="1.0"?>
 <magento_api>
   <success>
@@ -188,12 +188,12 @@ 
http://magentohost/api/rest/products/8/websites
+
POST http://magentohost/api/rest/products/8/websites

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
      <website_id>2</website_id>
@@ -245,12 +245,12 @@ 
Multi-

Example:

- +
POST http://magentohost/api/rest/products/8/websites

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -268,7 +268,7 @@ 
Multi-
-
+
<?xml version="1.0"?>
 <magento_api>
   <success>
@@ -338,12 +338,12 @@ 
http://magentohost/api/rest/products/8/websites
+
POST http://magentohost/api/rest/products/8/websites

Request Body:

-
+
<?xml version="1.0"?>
 <magento_api>
     <data_item>
@@ -373,7 +373,7 @@ 
-
+
<?xml version="1.0"?>
 <magento_api>
   <success>
@@ -407,7 +407,7 @@ 

http://magentohost/api/rest/products/:product_id/websites/:website_id
+

URL Structure: http://magentohost/api/rest/products/:product_id/websites/:website_id
Version: 1

HTTP Method: DELETE
@@ -422,7 +422,7 @@
HTTP Method

Example:

- +
DELETE http://magentohost/api/rest/products/8/websites/1
@@ -484,4 +484,4 @@

Possi - + diff --git a/guides/m1x/api/rest/Resources/Products/products.html b/guides/m1x/api/rest/Resources/Products/products.html index e12d2c1394..85ab7fefcd 100644 --- a/guides/m1x/api/rest/Resources/Products/products.html +++ b/guides/m1x/api/rest/Resources/Products/products.html @@ -35,7 +35,7 @@

URI: /products

Allows you to retrieve the list of all products with detailed information.

-

URL Structure: http://magentohost/api/rest/products
+

URL Structure: http://magentohost/api/rest/products
Version: 1

@@ -52,13 +52,13 @@
HTTP Method: - +
GET http://magentohost/api/rest/products

Response Example: XML

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -112,7 +112,7 @@ 
HTTP Method:
-
+
{"1":{"entity_id":"1","type_id":"simple","sku":"dress_test","status":"1","visibility":"4","tax_class_id":"2","weight":"1.0000","price":"1500.0000","special_price":"1000.0000","name":"Wedding dress","url_key":"dress","country_of_manufacture":"AO","msrp_display_actual_price_type":"2","gift_message_available":"1","news_from_date":"2012-03-21 00:00:00","news_to_date":"2012-03-24 00:00:00","special_from_date":"2012-03-21 00:00:00","special_to_date":"2012-03-24 00:00:00","description":"White wedding dress"},"2":{"entity_id":"2","type_id":"simple","sku":"black_sunglasses","status":"1","visibility":"4","tax_class_id":"2","weight":"0.2000","price":"500.0000","special_price":"300.0000","name":"Sunglasses","url_key":"sunglasses","country_of_manufacture":"AR","msrp_display_actual_price_type":"2","gift_message_available":null,"news_from_date":null,"news_to_date":null,"special_from_date":"2012-03-21 00:00:00","special_to_date":"2012-03-24 00:00:00","description":"Black sunglasses"}}
@@ -127,13 +127,13 @@
HTTP Method: - +
GET http://magentohost/api/rest/products

Response Example: XML

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -179,7 +179,7 @@ 
HTTP Method:
-
+
{"1":{"entity_id":"1","type_id":"simple","sku":"dress_test","description":"White wedding dress","short_description":"dress","meta_keyword":"white, dress","name":"Wedding dress","meta_title":"dress","meta_description":"A nice wedding dress","regular_price_with_tax":1500,"regular_price_without_tax":1500,"final_price_with_tax":1000,"final_price_without_tax":1000,"is_saleable":"1","image_url":"http:\/\/magentohost\/media\/catalog\/product\/cache\/0\/image\/9df78eab33525d08d6e5fb8d27136e95\/1\/2\/wedding_dress.jpg"},"2":{"entity_id":"2","type_id":"simple","sku":"black_sunglasses","description":"Black sunglasses","short_description":"Black sunglasses","meta_keyword":"sunglasses, black","name":"Sunglasses","meta_title":"sunglasses","meta_description":"black sunglasses","regular_price_with_tax":500,"regular_price_without_tax":500,"final_price_with_tax":300,"final_price_without_tax":300,"is_saleable":"1","image_url":"http:\/\/magentohost\/media\/catalog\/product\/cache\/0\/image\/9df78eab33525d08d6e5fb8d27136e95\/a\/l\/sunglasses-1.jpg"}}
@@ -192,13 +192,13 @@
<

In the following example, product with ID=4 has position equal to 7 and the product with ID=3 has position equal to 1. The list of products, therefore, is sorted by the product position in the category.

- +
GET http://magentohost/api/rest/products?category_id=5

Response Example: XML

-
+
<?xml version="1.0"?>
 <magento_api>
   <data_item>
@@ -718,13 +718,13 @@ 
HTTP Method - +
POST http://magentohost/api/rest/products

Request Example: JSON

-
+
{
   "custom_design" : "default/blank",
   "custom_design_from" : "02/16/2012",
@@ -781,7 +781,7 @@ 
HTTP Method
-
+
<?xml version="1.0"?>
 <magento_api>
   <attribute_set_id>4</attribute_set_id>
@@ -808,7 +808,7 @@ 

URI: /products/:id

Allows you to retrieve, update, and delete a specified product in Magento.

-

URL Structure: http://magentohost/api/rest/products/:id
+

URL Structure: http://magentohost/api/rest/products/:id
Version: 1

HTTP Method: GET /products/:id
@@ -823,14 +823,14 @@
HTTP Met No Parameters

- +
GET http://magentohost/api/rest/products/8

Response Example: XML

-
+
<?xml version="1.0"?>
 <magento_api>
   <entity_id>8</entity_id>
@@ -895,7 +895,7 @@ 
HTTP Met
-
+
{"entity_id":"8","attribute_set_id":"4","type_id":"simple","sku":"dress","name":"Dress","url_key":"my-new-dress","country_of_manufacture":"AD","msrp_display_actual_price_type":"2","gift_message_available":"1","price":"2000.0000","weight":"0.5000","status":"1","visibility":"4","tax_class_id":"7","description":"dress","group_price":[{"website_id":"0","cust_group":"1","price":"1400.0000"}],"tier_price":[{"website_id":"0","cust_group":"1","price":"1300.0000","price_qty":"1.0000"}],"stock_data":{"qty":"50.0000","min_qty":"0.0000","use_config_min_qty":"1","is_qty_decimal":"0","backorders":"0","use_config_backorders":"1","min_sale_qty":"1.0000","use_config_min_sale_qty":"1","max_sale_qty":"0.0000","use_config_max_sale_qty":"1","is_in_stock":"1","notify_stock_qty":null,"use_config_notify_stock_qty":"1","manage_stock":"0","use_config_manage_stock":"1","use_config_qty_increments":"1","qty_increments":"0.0000","use_config_enable_qty_inc":"1","enable_qty_increments":"0","is_decimal_divided":"0","use_config_enable_qty_increments":"1"}}
@@ -909,14 +909,14 @@
HTTP Met No Parameters

- +
GET http://magentohost/api/rest/products/8

Response Example: XML

-
+
<?xml version="1.0"?>
 <magento_api>
   <entity_id>1</entity_id>
@@ -949,7 +949,7 @@ 
HTTP Met
-
+
{"entity_id":"1","type_id":"simple","sku":"dress_test","name":"Wedding dress","meta_title":"dress","meta_description":"A nice wedding dress","description":"White wedding dress","short_description":"dress","meta_keyword":"white, dress","tier_price":[],"is_in_stock":"1","regular_price_with_tax":1500,"regular_price_without_tax":1500,"final_price_with_tax":1000,"final_price_without_tax":1000,"is_saleable":"1","image_url":"http:\/\/magento\/media\/catalog\/product\/cache\/0\/image\/9df78eab33525d08d6e5fb8d27136e95\/1\/2\/wedding_dress.jpg","url":"http:\/\/magento\/index.php\/catalog\/product\/view\/id\/1\/s\/dress\/","buy_now_url":"http:\/\/magento\/index.php\/checkout\/cart\/add\/uenc\/aHR0cDovLzEyNy4wLjAuMS9Tb3VyY2VzL2FwaS9yZXN0L3Byb2R1Y3RzLzE,\/product\/1\/","total_reviews_count":"0","has_custom_options":false}
@@ -967,14 +967,14 @@
HTTP Met Enter only those parameters which you want to update.

- +
PUT http://magentohost/api/rest/products/8
+PUT for specific store http://magentohost/api/rest/products/8/store/3

Request Example: JSON

-
+
{
 "attribute_set_id":"4",
 "type_id":"simple",
@@ -1000,7 +1000,7 @@ 
HTTP Met
-
+
<?xml version="1.0"?>
 <magento_api>
   <attribute_set_id>4</attribute_set_id>
@@ -1033,7 +1033,7 @@ 
HTTP Parameters: no parameters
Request Example:

- +
DELETE http://magentohost/api/rest/products/1
@@ -1066,4 +1066,4 @@

Possible HTT - + diff --git a/guides/m1x/api/rest/Resources/get_filters.html b/guides/m1x/api/rest/Resources/get_filters.html index 6e7576b8a4..4b7e15a071 100644 --- a/guides/m1x/api/rest/Resources/get_filters.html +++ b/guides/m1x/api/rest/Resources/get_filters.html @@ -8,18 +8,18 @@
  • filter - specifies the filters for returned data
  • page - specifies the page number which items will be returned
  • order, dir - specifies the sort order of returned items and the order direction: 'asc' - returns items in the ascending order; 'dsc' - returns items in the descending order.
  • limit - limits the number of returned items in the response. Note that by default, 10 items are returned in the response. The maximum number is 100 items.
  • neq - "not equal to" - returns items with the specified attribute that is not equal to the defined value @@ -68,4 +68,4 @@

    http://magentohost/api/rest/products/?order=entity_id&filter[0][attribute]=description&filter[0][in][0]=simple01

    - + diff --git a/guides/m1x/api/rest/Resources/inventory.html b/guides/m1x/api/rest/Resources/inventory.html index 4a1a3b82ad..faa28767c5 100644 --- a/guides/m1x/api/rest/Resources/inventory.html +++ b/guides/m1x/api/rest/Resources/inventory.html @@ -34,7 +34,7 @@
    - importantImportant: The default response for all APIs is JSON; however, this page currently uses mostly XML examples. We don't maintain this documentation much anymore so if you'd like to contribute some JSON, we'll acknowledge your help on this page. Edit this page on GitHub if you can help us out. + importantImportant: The default response for all APIs is JSON; however, this page currently uses mostly XML examples. We don't maintain this documentation much anymore so if you'd like to contribute some JSON, we'll acknowledge your help on this page. Edit this page on GitHub if you can help us out.

    REST API: Stock Items

    @@ -43,7 +43,7 @@

    URI: /stockitemsAllows you to manage existing stock items. Inventory management is available only for Admin.

    -

    URL Structure: http://magentohost/api/rest/stockitems
    Version: 1

    +

    URL Structure: http://magentohost/api/rest/stockitems
    Version: 1

    HTTP Method: GET /stockitems
    @@ -61,7 +61,7 @@
    HTTP Met
    - +
    GET http://magentohost/api/rest/stockitemsGET http://magentohost/api/rest/stockitems
    @@ -70,7 +70,7 @@
    HTTP Met
    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <data_item>
    @@ -130,7 +130,7 @@ 
    HTTP Met
    - +
    GET http://magentohost/api/rest/stockitemsGET http://magentohost/api/rest/stockitems
    @@ -139,7 +139,7 @@
    HTTP Met
    -
    +
    [{"item_id":"1","qty":"100.0000","backorders":"0","min_sale_qty":"1.0000","max_sale_qty":"0.0000","low_stock_date":null,"manage_stock":"0","stock_status_changed_auto":"0","enable_qty_increments":"0"},{"item_id":"2","qty":"100.0000","backorders":"0","min_sale_qty":"1.0000","max_sale_qty":"0.0000","low_stock_date":null,"manage_stock":"0","stock_status_changed_auto":"0","enable_qty_increments":"0"},{"item_id":"3","qty":"1.0000","backorders":"0","min_sale_qty":"1.0000","max_sale_qty":"0.0000","low_stock_date":null,"manage_stock":"0","stock_status_changed_auto":"0","enable_qty_increments":"0"},{"item_id":"4","qty":"0.0000","backorders":"0","min_sale_qty":"1.0000","max_sale_qty":"0.0000","low_stock_date":null,"manage_stock":"0","stock_status_changed_auto":"1","enable_qty_increments":"0"}]
    @@ -335,7 +335,7 @@
    HTTP Met
    - +
    PUT http://magentohost/api/rest/stockitemsPUT http://magentohost/api/rest/stockitems
    @@ -345,7 +345,7 @@
    HTTP Met
    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <data_item item_id="157">
    @@ -383,7 +383,7 @@ 
    HTTP Met
    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <success>
    @@ -441,7 +441,7 @@ 
    HTTP
    - +
    GET http://magentohost/api/rest/stockitems/1GET http://magentohost/api/rest/stockitems/1
    @@ -451,7 +451,7 @@
    HTTP
    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <item_id>1</item_id>
    @@ -492,7 +492,7 @@ 
    HTTP
    -
    GET http://magentohost/api/rest/stockitems/157 + GET http://magentohost/api/rest/stockitems/157
    @@ -503,7 +503,7 @@
    HTTP
    -
    +
    {"item_id":"1","product_id":"1","stock_id":"1","qty":"200.0000","min_qty":"0.0000","use_config_min_qty":"1","is_qty_decimal":"1","backorders":"0","use_config_backorders":"1","min_sale_qty":"1.0000","use_config_min_sale_qty":"1","max_sale_qty":"0.0000","use_config_max_sale_qty":"1","is_in_stock":"1","low_stock_date":null,"notify_stock_qty":"10.0000","use_config_notify_stock_qty":"0","manage_stock":"0","use_config_manage_stock":"1","stock_status_changed_auto":"0","use_config_qty_increments":"1","qty_increments":"0.0000","use_config_enable_qty_inc":"1","enable_qty_increments":"0","is_decimal_divided":"1"}
    @@ -526,7 +526,7 @@
    HTTP
    - +
    PUT http://magentohost/api/rest/stockitems/1PUT http://magentohost/api/rest/stockitems/1
    @@ -536,7 +536,7 @@
    HTTP
    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <qty>99</qty>
    @@ -553,7 +553,7 @@ 
    HTTP
    - +
    PUT http://magentohost/api/rest/stockitems/1PUT http://magentohost/api/rest/stockitems/1
    @@ -563,7 +563,7 @@
    HTTP
    -
    +
    {
     "qty":"99"
     }
    @@ -623,4 +623,4 @@
    H - + diff --git a/guides/m1x/api/rest/Resources/resource_customer_addresses.html b/guides/m1x/api/rest/Resources/resource_customer_addresses.html index 4b4f641621..e65d46693f 100644 --- a/guides/m1x/api/rest/Resources/resource_customer_addresses.html +++ b/guides/m1x/api/rest/Resources/resource_customer_addresses.html @@ -37,7 +37,7 @@

    http://magentohost/api/rest/customers/:customer_id/addresses
    +

    URL Structure: http://magentohost/api/rest/customers/:customer_id/addresses
    Version: 1

    HTTP Method: GET /customers/:customer_id/addresses
    @@ -54,12 +54,12 @@
    http://magentohost/api/rest/customers/1/addresses
    +
    GET http://magentohost/api/rest/customers/1/addresses

    Response Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <data_item>
    @@ -91,7 +91,7 @@ 
    -
    +
     		
     [
    @@ -143,7 +143,7 @@ 
    -
    + +
    POST http://magentohost/api/rest/customers/1/addresses

    Request Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
         <firstname>Johny</firstname>
    @@ -266,7 +266,7 @@ 

    http://magentohost/api/rest/customers/addresses/:address_id
    +

    URL Structure: http://magentohost/api/rest/customers/addresses/:address_id
    Version: 1

    HTTP Method: GET /customers/addresses/:address_id
    @@ -283,12 +283,12 @@
    http://magentohost/api/rest/customers/addresses/2
    +
    GET http://magentohost/api/rest/customers/addresses/2

    Response Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <entity_id>2</entity_id>
    @@ -318,7 +318,7 @@ 
    -
    +
     		
     {
    @@ -352,7 +352,7 @@ 
    -
    + +
    PUT http://magentohost/api/rest/customers/addresses/7

    Request Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <firstname>Johny</firstname>
    @@ -398,7 +398,7 @@ 
    -
    + +
    DELETE http://magentohost/api/rest/customers/addresses/7
    @@ -507,4 +507,4 @@

    Pos - + diff --git a/guides/m1x/api/rest/Resources/resource_customers.html b/guides/m1x/api/rest/Resources/resource_customers.html index ee05a24874..b9fc0619ed 100644 --- a/guides/m1x/api/rest/Resources/resource_customers.html +++ b/guides/m1x/api/rest/Resources/resource_customers.html @@ -39,7 +39,7 @@

    URI: /customers

    Allows you to create and retrieve customers.

    -

    URL Structure: http://magentohost/api/rest/customers
    +

    URL Structure: http://magentohost/api/rest/customers
    Version: 1

    HTTP Method: GET /customers
    @@ -53,12 +53,12 @@
    HTTP Metho No Parameters

    Example

    - +
    GET http://magentohost/api/rest/customers

    Response Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <data_item>
    @@ -88,12 +88,12 @@ 
    HTTP Metho

    response example: json

    - +
    get http://magentohost/api/rest/customers

    response body:

    -
    +
     		
     {
    @@ -237,12 +237,12 @@ 
    HTTP Meth

    Notes: The list of parameters may change depending on the attributes settings in Customers > Attributes > Manage Customer Attributes page in Magento Admin Panel. For example, a required status of the middlename attribute (Middle Name/Initial) may be changed to 'YES". Please note that managing customer attributes is available only in Magento Enterprise Edition.

    Example:

    - +
    POST http://magentohost/api/rest/customers

    Request Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
         <firstname>Earl</firstname>
    @@ -273,7 +273,7 @@ 

    URI: /cu

    Allows you to manage existing customers.

    -

    URL Structure: http://magentohost/api/rest/customers/:customerId
    +

    URL Structure: http://magentohost/api/rest/customers/:customerId
    Version: 1

    HTTP Method: GET /customers/:customerId
    @@ -287,12 +287,12 @@
    No Parameters

    Example:

    - +
    GET http://magentohost/api/rest/customers/2

    Response Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
       <entity_id>2</entity_id>
    @@ -315,7 +315,7 @@ 
    response body:

    -
    +
     		
     {
    @@ -348,12 +348,12 @@ 

    Example:

    - +
    PUT http://magentohost/api/rest/customers/2

    Request Body:

    -
    +
    <?xml version="1.0"?>
     <magento_api>
         <firstname>Earl</firstname>
    @@ -376,7 +376,7 @@ 
    No Parameters

    Example:

    - +
    DELETE http://magentohost/api/rest/customers/2
    - + diff --git a/guides/m1x/api/rest/Resources/resources.html b/guides/m1x/api/rest/Resources/resources.html index 8355b12969..2ab2aae507 100644 --- a/guides/m1x/api/rest/Resources/resources.html +++ b/guides/m1x/api/rest/Resources/resources.html @@ -33,68 +33,68 @@
    Products

    Retrieve the list of products, create, update, delete a product.

    -

    Resource Structure: http://magentohost/api/rest/products

    +

    Resource Structure: http://magentohost/api/rest/products

    Product Categories

    Retrieve the list of categories assigned to a product, assign and unassign the category from a product.

    -

    Resource Structure: http://magentohost/api/rest/products/:id/categories

    +

    Resource Structure: http://magentohost/api/rest/products/:id/categories

    Product Images

    Retrieve the list of images assigned to a product, add, update, remove an image to/from a product.

    -

    Resource Structure: http://magentohost/api/rest/products/:id/images

    +

    Resource Structure: http://magentohost/api/rest/products/:id/images

    Product Websites

    Retrieve the list of websites assigned to a product, assign, unassign a website to/from a product.

    -

    Resource Structure: http://magentohost/api/rest/products/:id/websites

    +

    Resource Structure: http://magentohost/api/rest/products/:id/websites

    Customers

    Retrieve the list of customers, create, delete a customer, and update the customer information.

    -

    Resource Structure: http://magentohost/api/rest/customers

    +

    Resource Structure: http://magentohost/api/rest/customers

    Customer Addresses

    Retrieve the list of customer addresses, create, update, and delete the customer address.

    -

    Resource Structure: http://magentohost/api/rest/customers/:id/addresses

    +

    Resource Structure: http://magentohost/api/rest/customers/:id/addresses

    Inventory

    Retrieve the list of stock items, update required stock items.

    -

    Resource Structure: http://magentohost/api/rest/stockitems

    +

    Resource Structure: http://magentohost/api/rest/stockitems

    Sales Orders

    Retrieve the list of sales orders with detailed information on order addresses, items, and comments.

    -

    Resource Structure: http://magentohost/api/rest/orders

    +

    Resource Structure: http://magentohost/api/rest/orders

    Order Addresses

    Retrieve information on order billing and shipping addresses.

    -

    Resource Structure: http://magentohost/api/rest/orders/:id/addresses

    +

    Resource Structure: http://magentohost/api/rest/orders/:id/addresses

    Order Comments

    Retrieve information on the specified order comments.

    -

    Resource Structure: http://magentohost/api/rest/orders/:id/comments

    +

    Resource Structure: http://magentohost/api/rest/orders/:id/comments

    Order Items

    Retrieve information on specified order items.

    -

    Resource Structure: http://magentohost/api/rest/orders/:id/items

    +

    Resource Structure: http://magentohost/api/rest/orders/:id/items

    - + diff --git a/guides/m1x/api/rest/authentication/oauth_authentication.html b/guides/m1x/api/rest/authentication/oauth_authentication.html index e17baea35b..1813a932df 100644 --- a/guides/m1x/api/rest/authentication/oauth_authentication.html +++ b/guides/m1x/api/rest/authentication/oauth_authentication.html @@ -38,7 +38,7 @@

    Introduction

    The OAuth concept lies in three basic elements that can be easily described in the following picture:

    - +

    To learn more about OAuth, you can visit the official OAuth site.

    @@ -90,7 +90,7 @@

    OAuth Process

  • Getting an Access Token by exchanging the Request Token for it.
  • - +

    The application that requires access to data is known as the Consumer and Magento is the Service Provider.

    @@ -410,7 +410,7 @@

    Retrieve the list of products for Customer user with OAuth authentication

    -
    +
    <?php
     /**
      * Example of retrieving the products list using Customer account via Magento REST API. OAuth authorization is used
    diff --git a/guides/m1x/api/rest/authentication/oauth_configuration.html b/guides/m1x/api/rest/authentication/oauth_configuration.html
    index 984469f055..4a57245088 100644
    --- a/guides/m1x/api/rest/authentication/oauth_configuration.html
    +++ b/guides/m1x/api/rest/authentication/oauth_configuration.html
    @@ -16,18 +16,18 @@
         
  • Working with Tokens (Admin Panel)
  • Working with Tokens (Frontend)
  • Working with Email Templates @@ -52,7 +52,7 @@

    Adding a New ConsumerOn the Magento Admin Panel menu, select System > Web Services > REST - OAuth Consumers.

  • On the OAuth Consumers page, click Add New in the top right corner to add a new consumer.
  • The New Consumer page opens. The Key and Secret fields are filled automatically and cannot be edited. These values are generated automatically and will be used to identify the Consumer in Magento.
    -
  • +
  • Fill in the following fields:
  • - diff --git a/guides/m1x/api/soap/catalog/catalog.html b/guides/m1x/api/soap/catalog/catalog.html index acf7d4eebf..d0edd6577c 100644 --- a/guides/m1x/api/soap/catalog/catalog.html +++ b/guides/m1x/api/soap/catalog/catalog.html @@ -229,7 +229,7 @@

    Product Downloadable Link

    Resource Name: product_downloadable_link

    -

    Methods:
    +
    Methods:
    -
    Methods:
    +
    Methods:
      @@ -275,7 +275,7 @@

      Product Custom Option

    -
    Methods:
    +
    Methods:
    -
    Methods:
    +
    Methods:
    - \ No newline at end of file diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalogCategory.html b/guides/m1x/api/soap/catalog/catalogCategory/catalogCategory.html index a7bdf6b579..4217887a4a 100644 --- a/guides/m1x/api/soap/catalog/catalogCategory/catalogCategory.html +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalogCategory.html @@ -78,7 +78,7 @@

    Faults

    Example 1. Working with categories

    -
    +
    function getSomeRandomCategory(&$categories, $targetLevel, $currentLevel = 0) {
         if (count($categories)==0) {
             return false;
    @@ -128,7 +128,7 @@ 

    Example 1. Workin

    Example 2. Working with assigned products

    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -148,4 +148,3 @@ 

    Example 2. $proxy->call($sessionId, 'category.removeProduct', array($categoryId, 'someProductSku'));

    - \ No newline at end of file diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.assignProduct.html b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.assignProduct.html index b457fa9a76..9538db3eb0 100644 --- a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.assignProduct.html +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.assignProduct.html @@ -89,7 +89,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -108,7 +108,7 @@ 
    Request Ex
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -120,7 +120,7 @@ 
    Request Ex
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -130,4 +130,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -128,7 +128,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -140,7 +140,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -153,7 +153,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -172,4 +172,4 @@ 
    Respon
    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.create.html b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.create.html index 41a4723e14..0758f192c0 100644 --- a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.create.html +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.create.html @@ -207,7 +207,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -245,7 +245,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -283,7 +283,7 @@ 
    Request Example S
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -302,4 +302,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -90,7 +90,7 @@ 
    Request Exa
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
      
    @@ -100,4 +100,4 @@ 
    Request Exa
    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.delete.html b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.delete.html index 6b0f6a6399..aeea8e8f20 100644 --- a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.delete.html +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.delete.html @@ -73,7 +73,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -91,7 +91,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -104,7 +104,7 @@ 
    Request Example S
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -114,4 +114,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -275,7 +275,7 @@ 
    Request Example SOA
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -287,7 +287,7 @@ 
    Request Example SOA
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -300,7 +300,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'category_id' => string '5' (length=1)
       'is_active' => string '1' (length=1)
    @@ -341,4 +341,4 @@ 
    Response Example S
    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.level.html b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.level.html index 40a9c5dad4..e5d627ee68 100644 --- a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.level.html +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.level.html @@ -125,7 +125,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -143,7 +143,7 @@ 
    Request Example SO
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
      
    @@ -156,7 +156,7 @@ 
    Request Example SO
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.move.html b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.move.html
    index d53825d1a1..d8e48284f4 100644
    --- a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.move.html
    +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.move.html
    @@ -87,7 +87,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -105,7 +105,7 @@ 
    Request Example SOA
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -117,7 +117,7 @@ 
    Request Example SOA
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -130,4 +130,4 @@ 

    Note: Please make sure that you are not moving the category to any of its own children. There are no extra checks to prevent doing it through API, and you won’t be able to fix this from the admin interface later.

    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.removeProduct.html b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.removeProduct.html index 642ad6d925..4401fee343 100644 --- a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.removeProduct.html +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.removeProduct.html @@ -85,7 +85,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -103,7 +103,7 @@ 
    Request Ex
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -116,7 +116,7 @@ 
    Request Ex
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -126,4 +126,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -188,7 +188,7 @@ 
    Request Example SOA
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -200,7 +200,7 @@ 
    Request Example SOA
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -213,7 +213,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'category_id' => string '1' (length=1)
       'parent_id' => string '0' (length=1)
    @@ -248,4 +248,4 @@ 
    Response Example S
    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.update.html b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.update.html index b5e3505d56..dc9f093de9 100644 --- a/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.update.html +++ b/guides/m1x/api/soap/catalog/catalogCategory/catalog_category.update.html @@ -207,7 +207,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -245,7 +245,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -284,7 +284,7 @@ 
    Request Example S
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -303,4 +303,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -109,7 +109,7 @@ 
    Request Ex
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -121,7 +121,7 @@ 
    Request Ex
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -132,4 +132,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -89,7 +89,7 @@ 
    R
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
      
    @@ -99,4 +99,4 @@ 
    R
    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.list.html b/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.list.html index 52ecbfe8e5..bf387369fa 100644 --- a/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.list.html +++ b/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.list.html @@ -106,7 +106,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -124,7 +124,7 @@ 
    Request E
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -136,7 +136,7 @@ 
    Request E
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $session = $client->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -150,7 +150,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -176,4 +176,4 @@ 
    Response
    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.options.html b/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.options.html index b822395499..0fccb1de7a 100644 --- a/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.options.html +++ b/guides/m1x/api/soap/catalog/catalogCategoryAttributes/catalog_category_attribute.options.html @@ -99,7 +99,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -118,7 +118,7 @@ 
    Reques
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -130,7 +130,7 @@ 
    Reques
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $session = $client->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -144,7 +144,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -157,4 +157,4 @@ 
    Respo
    - + diff --git a/guides/m1x/api/soap/catalog/catalogCategoryAttributes/categoryAttributes.html b/guides/m1x/api/soap/catalog/catalogCategoryAttributes/categoryAttributes.html index 554d34da94..e9a222d34a 100644 --- a/guides/m1x/api/soap/catalog/catalogCategoryAttributes/categoryAttributes.html +++ b/guides/m1x/api/soap/catalog/catalogCategoryAttributes/categoryAttributes.html @@ -51,7 +51,7 @@

    Examples

    Example 1. Retrieving attributes and options
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $attributes = $proxy->call($sessionId, 'category_attribute.list');
    @@ -64,4 +64,3 @@ 
    - \ No newline at end of file diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalogProduct.html b/guides/m1x/api/soap/catalog/catalogProduct/catalogProduct.html index 37b22e1472..bd93d56051 100644 --- a/guides/m1x/api/soap/catalog/catalogProduct/catalogProduct.html +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalogProduct.html @@ -65,7 +65,7 @@

    Examples

    Example 1. Retrieving the product list
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -81,7 +81,7 @@ 
    Exampl
    Example 2. Creating, viewing, updating, and deleting a product
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.create.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.create.html
    index 11f9987171..a4a9ca8dde 100644
    --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.create.html
    +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.create.html
    @@ -418,7 +418,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -456,7 +456,7 @@ 
    Request Example SO
    Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -492,7 +492,7 @@ 
    Request Example SO
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -513,4 +513,4 @@ 
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.currentStore.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.currentStore.html index 03cd4c1e02..84831649a9 100644 --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.currentStore.html +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.currentStore.html @@ -73,7 +73,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -88,7 +88,7 @@ 
    Request Exam
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
      
    diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.delete.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.delete.html
    index 7e473babbf..e388a461e8 100644
    --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.delete.html
    +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.delete.html
    @@ -80,7 +80,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -98,7 +98,7 @@ 
    Request Example SO
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -111,7 +111,7 @@ 
    Request Example SO
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -121,4 +121,4 @@ 
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.getSpecialPrice.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.getSpecialPrice.html index e2e6901837..4843a100a2 100644 --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.getSpecialPrice.html +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.getSpecialPrice.html @@ -110,7 +110,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -128,7 +128,7 @@ 
    Request E
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -141,7 +141,7 @@ 
    Request E
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -154,7 +154,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'special_price' => string '139.9900' (length=8)
       'special_from_date' => string '2012-03-28 00:00:00' (length=19)
    @@ -162,4 +162,4 @@ 
    Response
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.info.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.info.html index fc7af65d27..b0b7d48e0b 100644 --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.info.html +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.info.html @@ -327,7 +327,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -345,7 +345,7 @@ 
    Request Example SOAP
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -358,7 +358,7 @@ 
    Request Example SOAP
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -371,7 +371,7 @@ 
    <
    Response Example SOAP V1
    -
    +
    array
       'product_id' => string '4' (length=1)
       'sku' => string 'canon_powershot' (length=15)
    @@ -441,4 +441,4 @@ 
    Response Example SO
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.list.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.list.html index 2c4ebf8347..07e0e260db 100644 --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.list.html +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.list.html @@ -126,7 +126,7 @@
    Request Example SOAP
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -145,7 +145,7 @@ 
    <
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -159,7 +159,7 @@ 
    R
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -182,7 +182,7 @@ 
    R
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -196,7 +196,7 @@ 
    <
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -221,4 +221,4 @@ 
    Response Example SO
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.listOfAdditionalAttributes.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.listOfAdditionalAttributes.html index 3c007280ee..908e12126a 100644 --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.listOfAdditionalAttributes.html +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.listOfAdditionalAttributes.html @@ -108,7 +108,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -126,7 +126,7 @@ 
    Reques
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -138,7 +138,7 @@ 
    Reques
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -160,4 +160,4 @@ 
    Respo
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.setSpecialPrice.html b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.setSpecialPrice.html index f34080da82..c8ec85ffc7 100644 --- a/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.setSpecialPrice.html +++ b/guides/m1x/api/soap/catalog/catalogProduct/catalog_product.setSpecialPrice.html @@ -102,7 +102,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -120,7 +120,7 @@ 
    Request E
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -132,7 +132,7 @@ 
    Request E
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -142,4 +142,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -432,7 +432,7 @@ 
    Request Example SO
    Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -464,7 +464,7 @@ 
    Request Example SO
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -479,4 +479,4 @@ 
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/catalogProductAttribute.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/catalogProductAttribute.html index 9238a63c59..e18413a768 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/catalogProductAttribute.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/catalogProductAttribute.html @@ -88,7 +88,7 @@
    Faults:
    Example:
    -
    +
    <pre>
     <?php
     $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/catalog_product_attribute.options.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/catalog_product_attribute.options.html
    index acc278eb64..8d742a2fcc 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/catalog_product_attribute.options.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/catalog_product_attribute.options.html
    @@ -115,7 +115,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -136,7 +136,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -150,7 +150,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -165,7 +165,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       1 =>
         array
    @@ -182,4 +182,4 @@ 
    Respon
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.addOption.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.addOption.html index e4fc4dba1e..ad470bdc82 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.addOption.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.addOption.html @@ -134,7 +134,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -164,7 +164,7 @@ 
    Request Examp
    Request Example SOAP V2
    -
    +
    <?php
     $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.create.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.create.html
    index 69ab8aad10..f7897e3efb 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.create.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.create.html
    @@ -320,7 +320,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    <?php
     
     $client = new SoapClient('http://magentohost/api/soap/?wsdl');
    @@ -370,7 +370,7 @@ 
    Request Example
    Request Example SOAP V2
    -
    +
    <?php
     //ini_set("soap.wsdl_cache_enabled", 0);
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.currentStore.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.currentStore.html
    index 5d911b06a5..7fad6e9e92 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.currentStore.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.currentStore.html
    @@ -71,7 +71,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -86,7 +86,7 @@ 
    Re
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
      
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.info.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.info.html
    index 0402d216af..0b75b0350c 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.info.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.info.html
    @@ -338,7 +338,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -356,7 +356,7 @@ 
    Request Example SO
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -369,7 +369,7 @@ 
    Request Example SO
    Response Example SOAP V1
    -
    +
    array
       'attribute_id' => string '11' (length=3)
       'attribute_code' => string 'new_special_price' (length=17)
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.list.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.list.html
    index 3bd51a9514..b4083b97e0 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.list.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.list.html
    @@ -113,7 +113,7 @@ 
    Request Ex
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -134,7 +134,7 @@ 
    Request Ex
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -147,7 +147,7 @@ 
    Request Ex
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -161,7 +161,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -180,4 +180,4 @@ 
    Response
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.options.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.options.html index acc278eb64..8d742a2fcc 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.options.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.options.html @@ -115,7 +115,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -136,7 +136,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -150,7 +150,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -165,7 +165,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       1 =>
         array
    @@ -182,4 +182,4 @@ 
    Respon
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.remove.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.remove.html index da2327b522..48b0fd2635 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.remove.html @@ -79,7 +79,7 @@
    Request Example
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -98,7 +98,7 @@ 
    Request Example
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -110,7 +110,7 @@ 
    Request Example
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $session = $client->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -121,4 +121,4 @@ 
    Request ex
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -110,7 +110,7 @@ 
    Request ex
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.types.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.types.html
    index 7e96bf5682..cc85764b8b 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.types.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.types.html
    @@ -80,7 +80,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -97,7 +97,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -108,7 +108,7 @@ 
    Request Example S
    Response Example SOAP V1
    -
    +
    array
       0 =>
           'value' => 'text'
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.update.html b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.update.html
    index bd03079b34..389192899a 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.update.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttribute/product_attribute.update.html
    @@ -308,7 +308,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -348,7 +348,7 @@ 
    Request Example
    Request Example SOAP V2
    -
    +
    <?php
     //ini_set("soap.wsdl_cache_enabled", 0);
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.create.html b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.create.html
    index 83592eb0ae..88e30a4d01 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.create.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.create.html
    @@ -157,7 +157,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -181,7 +181,7 @@ 
    Re
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -203,7 +203,7 @@ 
    Re
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -223,4 +223,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -89,7 +89,7 @@ 
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
      
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.info.html b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.info.html
    index d3574ca3e1..c7bcebf980 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.info.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.info.html
    @@ -132,7 +132,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -151,7 +151,7 @@ 
    Requ
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -164,7 +164,7 @@ 
    Requ
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -179,7 +179,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'file' => string '/b/l/blackberry8100_2.jpg' (length=25)
       'label' => string '' (length=0)
    @@ -194,4 +194,4 @@ 
    Res
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.list.html b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.list.html index 8492c205d1..26ed09b4b0 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.list.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.list.html @@ -127,7 +127,7 @@
    Requ
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -146,7 +146,7 @@ 
    Requ
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -160,7 +160,7 @@ 
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -174,7 +174,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -191,4 +191,4 @@ 
    Res
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.remove.html b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.remove.html index f838f49707..4cf0ee7713 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.remove.html @@ -84,7 +84,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -102,7 +102,7 @@ 
    Re
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -116,7 +116,7 @@ 
    Re
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -127,4 +127,4 @@ 
    Req
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -115,7 +115,7 @@ 
    Req
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -127,7 +127,7 @@ 
    Req
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -141,7 +141,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -158,4 +158,3 @@ 
    Re
    - \ No newline at end of file diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.update.html b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.update.html index 3d485de24e..76b1d6787e 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.update.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeMedia/catalog_product_attribute_media.update.html @@ -163,7 +163,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -190,7 +190,7 @@ 
    Re
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -215,7 +215,7 @@ 
    Re
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -231,4 +231,4 @@ 
    Examples
    Example 1. Working with product images
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeSet/productAttributeSet.html b/guides/m1x/api/soap/catalog/catalogProductAttributeSet/productAttributeSet.html
    index 34a2ee7dde..90868d3324 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttributeSet/productAttributeSet.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeSet/productAttributeSet.html
    @@ -117,7 +117,7 @@ 
    Faults:
    Example:
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.attributeAdd.html b/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.attributeAdd.html
    index 78765a5a4a..0945e22b07 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.attributeAdd.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.attributeAdd.html
    @@ -108,7 +108,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -129,7 +129,7 @@ 
    Reques
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -147,7 +147,7 @@ 
    Reques
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -157,4 +157,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -114,7 +114,7 @@ 
    Req
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -126,7 +126,7 @@ 
    Req
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -136,4 +136,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -109,7 +109,7 @@ 
    Request Exam
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -129,7 +129,7 @@ 
    Request Exam
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -139,4 +139,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -102,7 +102,7 @@ 
    Request Ex
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -115,7 +115,7 @@ 
    Request Ex
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://maentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -125,4 +125,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -104,7 +104,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -117,7 +117,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -127,4 +127,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -104,7 +104,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -117,7 +117,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -127,4 +127,4 @@ 
    Reques
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -114,7 +114,7 @@ 
    Reques
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -126,7 +126,7 @@ 
    Reques
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -139,7 +139,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -152,4 +152,4 @@ 
    Respo
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.remove.html b/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.remove.html index 1005a64383..a0322cb810 100644 --- a/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductAttributeSet/product_attribute_set.remove.html @@ -89,7 +89,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -108,7 +108,7 @@ 
    Request Exam
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -121,7 +121,7 @@ 
    Request Exam
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -131,4 +131,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $productId = 1;// Existing product ID
    @@ -289,7 +289,7 @@ 
    Request Example
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login('apiUser', 'apiKey');
    @@ -312,7 +312,7 @@ 
    Request Example
    Request Example SOAP V2 (WS-I Compliance Example)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -332,4 +332,4 @@ 
    Request Exampl
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -206,7 +206,7 @@ 
    Request Exampl
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -219,7 +219,7 @@ 
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -232,7 +232,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'title' => string 'model' (length=5)
       'type' => string 'drop_down' (length=9)
    @@ -259,4 +259,4 @@ 
    Response Exam
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.list.html b/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.list.html index b3f8350dfc..2923199f86 100644 --- a/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.list.html +++ b/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.list.html @@ -119,7 +119,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -137,7 +137,7 @@ 
    Request Exampl
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -149,7 +149,7 @@ 
    Request Exampl
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -162,7 +162,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -174,4 +174,4 @@ 
    Response Exam
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.remove.html b/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.remove.html index 233dce6812..7f09509051 100644 --- a/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.remove.html @@ -77,7 +77,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $optionId  = 1;// Existing option ID
    @@ -95,7 +95,7 @@ 
    Request Exam
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -108,7 +108,7 @@ 
    Request Exam
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -118,4 +118,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -97,7 +97,7 @@ 
    Request Examp
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -110,7 +110,7 @@ 
    Request Examp
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -123,7 +123,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -168,4 +168,4 @@ 
    Response Exa
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.update.html b/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.update.html index 26a7b4ad64..1ccbf77f85 100644 --- a/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.update.html +++ b/guides/m1x/api/soap/catalog/catalogProductCustomOption/product_custom_option.update.html @@ -200,7 +200,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $selectOptionId = 1379;
    @@ -281,7 +281,7 @@ 
    Request Exam
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login('apiUser', 'apiKey');
    @@ -298,7 +298,7 @@ 
    Request Exam
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -312,4 +312,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $productOptionId = 1;// Existing product option ID
    @@ -156,7 +156,7 @@ 
    Request E
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login('apiUser', 'apiKey');
    @@ -179,7 +179,7 @@ 
    Request E
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -195,4 +195,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -171,7 +171,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -183,7 +183,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -197,7 +197,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'option_id' => string '5' (length=1)
       'sku' => string 'slider' (length=6)
    @@ -215,4 +215,4 @@ 
    Respons
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.list.html b/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.list.html index 0309d1b5cd..ffef1c7b72 100644 --- a/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.list.html +++ b/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.list.html @@ -127,7 +127,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -145,7 +145,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -158,7 +158,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -173,7 +173,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -194,4 +194,4 @@ 
    Respons
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.remove.html b/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.remove.html index f4d18ba698..e43899327a 100644 --- a/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductCustomOptionValue/product_custom_option_value.remove.html @@ -81,7 +81,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -104,7 +104,7 @@ 
    Reques
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -118,7 +118,7 @@ 
    Reques
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -128,4 +128,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -169,7 +169,7 @@ 
    Reques
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login('apiUser', 'apiKey');
    @@ -190,7 +190,7 @@ 
    Reques
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -206,4 +206,3 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $filesPath = '/var/www/ws/tests/WebService/etc/Modules/Downloadable/Product/Link';
    @@ -313,7 +313,7 @@ 
    Request Exa
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -332,7 +332,7 @@ 
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -351,4 +351,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -282,7 +282,7 @@ 
    Request Ex
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -295,7 +295,7 @@ 
    Request Ex
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -311,7 +311,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'links' =>
         array
    @@ -352,4 +352,4 @@ 
    Response
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductDownloadableLink/product_downloadable_link.remove.html b/guides/m1x/api/soap/catalog/catalogProductDownloadableLink/product_downloadable_link.remove.html index fcbd25288c..ae259114ee 100644 --- a/guides/m1x/api/soap/catalog/catalogProductDownloadableLink/product_downloadable_link.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductDownloadableLink/product_downloadable_link.remove.html @@ -86,7 +86,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -110,7 +110,7 @@ 
    Request
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -123,7 +123,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -133,4 +133,4 @@ 
    Examples
    Example 1. Working with product links
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.assign.html b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.assign.html
    index ca91e52fd6..9632da851d 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.assign.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.assign.html
    @@ -132,7 +132,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -150,7 +150,7 @@ 
    Request Examp
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -163,7 +163,7 @@ 
    Request Examp
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
     
    @@ -173,4 +173,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -113,7 +113,7 @@ 
    Request E
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -125,7 +125,7 @@ 
    Request E
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
     
    @@ -138,7 +138,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -147,4 +147,4 @@ 
    Response
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.list.html b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.list.html index b0f4feaf4e..90846f2320 100644 --- a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.list.html +++ b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.list.html @@ -125,7 +125,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -143,7 +143,7 @@ 
    Request Example
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -157,7 +157,7 @@ 
    Request Example
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
     
    @@ -170,7 +170,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -189,4 +189,4 @@ 
    Response Examp
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.remove.html b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.remove.html index 2e1392c253..24cfec5d35 100644 --- a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.remove.html @@ -87,7 +87,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -105,7 +105,7 @@ 
    Request Examp
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -117,7 +117,7 @@ 
    Request Examp
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
     
    @@ -127,4 +127,4 @@ 
    Request Exampl
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -88,7 +88,7 @@ 
    Request Exampl
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -102,7 +102,7 @@ 
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
     
    @@ -115,7 +115,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 => string 'related' (length=7)
       1 => string 'up_sell' (length=7)
    @@ -124,4 +124,4 @@ 
    Response Exam
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.update.html b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.update.html index ef88938c2d..7216affc3a 100644 --- a/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.update.html +++ b/guides/m1x/api/soap/catalog/catalogProductLink/catalog_product_link.update.html @@ -134,7 +134,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -161,7 +161,7 @@ 
    Request Examp
    Request Example SOAP V2
    -
    +
    <?php
     
     $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
    @@ -189,7 +189,7 @@ 
    Request Examp
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
     
    @@ -201,4 +201,4 @@ 
    Faults:
    Example:
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $productId = 2;
    diff --git a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.add.html b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.add.html
    index 0626801fe0..855404f74c 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.add.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.add.html
    @@ -122,7 +122,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $data = array('product_id' => 2, 'store' => 'default', 'customer_id' => 10002, 'tag' => "First 'Second tag' Third");
    @@ -142,7 +142,7 @@ 
    Request Example SOAP V1Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login('apiUser', 'apiKey');
    @@ -161,7 +161,7 @@ 
    Request Example SOAP V2Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -176,4 +176,4 @@ 
    Re
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.info.html b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.info.html index 156418e2cc..a01085ec1e 100644 --- a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.info.html +++ b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.info.html @@ -116,7 +116,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -131,7 +131,7 @@ 
    Request Example SOAP V1<
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -144,7 +144,7 @@ 
    Request Example SOAP V2<
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -158,7 +158,7 @@ 
    R
    Response Example SOAP V1
    -
    +
    array
       'status' => string '1' (length=1)
       'name' => string 'digital' (length=7)
    @@ -171,4 +171,4 @@ 
    Response Example SOAP V
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.list.html b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.list.html index 39c77ba17f..396b1fe4a7 100644 --- a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.list.html +++ b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.list.html @@ -106,7 +106,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -121,7 +121,7 @@ 
    Request Example SOAP V1<
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -133,7 +133,7 @@ 
    Request Example SOAP V2<
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -147,7 +147,7 @@ 
    R
    Response Example SOAP V1
    -
    +
    array
       3 =>
         array
    @@ -160,4 +160,4 @@ 
    Response Example SOAP V
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.remove.html b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.remove.html index b3ac9f00f1..c35d3d511b 100644 --- a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.remove.html +++ b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.remove.html @@ -78,7 +78,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -93,7 +93,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -106,7 +106,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -116,4 +116,4 @@ 
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.update.html b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.update.html index ca39266105..f66b639b2a 100644 --- a/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.update.html +++ b/guides/m1x/api/soap/catalog/catalogProductTag/product_tag.update.html @@ -122,7 +122,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -137,7 +137,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -155,7 +155,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -169,4 +169,4 @@ 
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalogProductTierPrice.html b/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalogProductTierPrice.html index 45fc75332a..0477f5aa8f 100644 --- a/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalogProductTierPrice.html +++ b/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalogProductTierPrice.html @@ -52,7 +52,7 @@

    Faults

    Examples

    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    diff --git a/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.info.html b/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.info.html
    index 01ddf1515e..f4dc4c40cd 100644
    --- a/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.info.html
    +++ b/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.info.html
    @@ -112,7 +112,7 @@ 
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -129,7 +129,7 @@ 
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -149,7 +149,7 @@ 
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -165,7 +165,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -180,7 +180,7 @@ 
    Response Example SOAP V2
    -
    +
    array
       0 =>
         object(stdClass)[2]
    @@ -197,4 +197,4 @@ 
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.update.html b/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.update.html index cafc8b8161..bbe49293f8 100644 --- a/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.update.html +++ b/guides/m1x/api/soap/catalog/catalogProductTierPrice/catalog_product_attribute_tier_price.update.html @@ -116,7 +116,7 @@

    Examples<

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -141,7 +141,7 @@ 
    <
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -165,7 +165,7 @@ 
    <
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
     
    @@ -185,4 +185,4 @@ 
    Request Example
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -109,7 +109,7 @@ 
    Request Example
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -122,7 +122,7 @@ 
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -137,7 +137,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -166,4 +166,4 @@ 
    Response Examp
    - + diff --git a/guides/m1x/api/soap/catalog/catalogProductTypes/productTypes.html b/guides/m1x/api/soap/catalog/catalogProductTypes/productTypes.html index a139abc4f1..ae2838f3bc 100644 --- a/guides/m1x/api/soap/catalog/catalogProductTypes/productTypes.html +++ b/guides/m1x/api/soap/catalog/catalogProductTypes/productTypes.html @@ -29,7 +29,7 @@

    Examples

    Example 1. Retrieving the product types
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $types = $proxy->call($sessionId, 'product_type.list');
    diff --git a/guides/m1x/api/soap/catalogInventory/Inventory.html b/guides/m1x/api/soap/catalogInventory/Inventory.html
    index 3c63675c28..f1b3fc0221 100644
    --- a/guides/m1x/api/soap/catalogInventory/Inventory.html
    +++ b/guides/m1x/api/soap/catalogInventory/Inventory.html
    @@ -55,7 +55,7 @@ 

    Examples

    Example 1. Working with stock update
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -71,14 +71,14 @@ 
    Example 1. Work
    Example 2. Listing multiple SKUs' data
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sid = $client->login('apiUser', 'apiKey');
     
     print_r(
         $client->call(
             $sid,
    -Â        'product_stock.list',
    +        'product_stock.list',
             array(
                 array( // Notice the nested array
                     'sku1',
    diff --git a/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.list.html b/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.list.html
    index 4fc624261f..7df367b365 100644
    --- a/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.list.html
    +++ b/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.list.html
    @@ -106,7 +106,7 @@ 
    Request
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -125,7 +125,7 @@ 
    Request
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -139,7 +139,7 @@ 
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -152,7 +152,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -163,4 +163,4 @@ 
    Respons
    - + diff --git a/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.update.html b/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.update.html index 884e102d11..bf6b9d254c 100644 --- a/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.update.html +++ b/guides/m1x/api/soap/catalogInventory/cataloginventory_stock_item.update.html @@ -164,7 +164,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -204,7 +204,7 @@ 
    Reques
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
      
    @@ -222,7 +222,7 @@ 
    Reques
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -236,4 +236,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -74,7 +74,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -88,7 +88,7 @@ 
    Request Example SOAP V2
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -102,4 +102,4 @@ 
    Reques - + diff --git a/guides/m1x/api/soap/checkout/cart/cart.html b/guides/m1x/api/soap/checkout/cart/cart.html index 3ffd38fdfa..0aeb78d89c 100644 --- a/guides/m1x/api/soap/checkout/cart/cart.html +++ b/guides/m1x/api/soap/checkout/cart/cart.html @@ -70,7 +70,7 @@

    Example

    The following example illustrates the work with shopping cart (creation of a shopping cart, setting customer and customer addresses, adding products to the shopping cart, updating products in the shopping cart, removing products from the shopping cart, getting the list of products/shipping methods/payment methods, setting payment/shipping methods,  adding/removing coupon, getting total prices/full information about shopping cart/list of licenses, and creating an order.

    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -209,4 +209,3 @@ 

    Example

    $resultOrderCreation = $proxy->call($sessionId,"cart.order",array($shoppingCartId, null, $licenseForOrderCreation));
    - \ No newline at end of file diff --git a/guides/m1x/api/soap/checkout/cart/cart.info.html b/guides/m1x/api/soap/checkout/cart/cart.info.html index d8c449f407..9e72ce1f2c 100644 --- a/guides/m1x/api/soap/checkout/cart/cart.info.html +++ b/guides/m1x/api/soap/checkout/cart/cart.info.html @@ -901,7 +901,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -916,7 +916,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -929,7 +929,7 @@ 
    Request Example SOAP V2
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -941,4 +941,4 @@ 
    Request
    - + diff --git a/guides/m1x/api/soap/checkout/cart/cart.license.html b/guides/m1x/api/soap/checkout/cart/cart.license.html index e999d3fe2c..6c9e4eaa1a 100644 --- a/guides/m1x/api/soap/checkout/cart/cart.license.html +++ b/guides/m1x/api/soap/checkout/cart/cart.license.html @@ -108,7 +108,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -120,7 +120,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -133,7 +133,7 @@ 
    Request Example SOAP V2
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -146,7 +146,7 @@ 
    Reque
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -161,4 +161,4 @@ 
    Response Example SOAP V1
    - + diff --git a/guides/m1x/api/soap/checkout/cart/cart.order.html b/guides/m1x/api/soap/checkout/cart/cart.order.html index 5d4d6d15b4..b47485a4d1 100644 --- a/guides/m1x/api/soap/checkout/cart/cart.order.html +++ b/guides/m1x/api/soap/checkout/cart/cart.order.html @@ -75,7 +75,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -98,7 +98,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    /**
      * Example of order creation
      * Preconditions are as follows:
    @@ -171,4 +171,4 @@ 
    Request Example SOAP V2
    - + diff --git a/guides/m1x/api/soap/checkout/cart/cart.totals.html b/guides/m1x/api/soap/checkout/cart/cart.totals.html index 0006a0294d..3dba5fa1d1 100644 --- a/guides/m1x/api/soap/checkout/cart/cart.totals.html +++ b/guides/m1x/api/soap/checkout/cart/cart.totals.html @@ -88,7 +88,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -103,7 +103,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -117,7 +117,7 @@ 
    Request Example SOAP V2
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -131,7 +131,7 @@ 
    Reques
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -160,4 +160,4 @@ 
    Response Example SOAP V1
    - + diff --git a/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.add.html b/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.add.html index e330dccdf7..688cea1045 100644 --- a/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.add.html +++ b/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.add.html @@ -72,7 +72,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -92,7 +92,7 @@ 
    Request Example SOAP V1Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -106,7 +106,7 @@ 
    Request Example SOAP V2Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -116,4 +116,4 @@ 
    Re
    - + diff --git a/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.remove.html b/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.remove.html index 024731b8b5..1912e1783c 100644 --- a/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.remove.html +++ b/guides/m1x/api/soap/checkout/cartCoupon/cart_coupon.remove.html @@ -67,7 +67,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -84,7 +84,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -97,7 +97,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -107,4 +107,4 @@ 
    - + diff --git a/guides/m1x/api/soap/checkout/cartCustomer/cart_customer.addresses.html b/guides/m1x/api/soap/checkout/cartCustomer/cart_customer.addresses.html index 09689fa16a..2981cb0014 100644 --- a/guides/m1x/api/soap/checkout/cartCustomer/cart_customer.addresses.html +++ b/guides/m1x/api/soap/checkout/cartCustomer/cart_customer.addresses.html @@ -161,7 +161,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -204,7 +204,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
      
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -230,7 +230,7 @@ 
    Request Example S
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -251,4 +251,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -156,7 +156,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     $session = $client->login('apiUser', 'apiKey');
     
    @@ -175,4 +175,4 @@ 
    Request Example SOAP V2
    - + diff --git a/guides/m1x/api/soap/checkout/cartPayment/cart_payment.list.html b/guides/m1x/api/soap/checkout/cartPayment/cart_payment.list.html index 07eeb291f9..66df77574c 100644 --- a/guides/m1x/api/soap/checkout/cartPayment/cart_payment.list.html +++ b/guides/m1x/api/soap/checkout/cartPayment/cart_payment.list.html @@ -93,7 +93,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -108,7 +108,7 @@ 
    Request Example SOAP V1
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    diff --git a/guides/m1x/api/soap/checkout/cartPayment/cart_payment.method.html b/guides/m1x/api/soap/checkout/cartPayment/cart_payment.method.html
    index e63a394285..111b6ea54c 100644
    --- a/guides/m1x/api/soap/checkout/cartPayment/cart_payment.method.html
    +++ b/guides/m1x/api/soap/checkout/cartPayment/cart_payment.method.html
    @@ -123,7 +123,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -149,7 +149,7 @@ 
    Request Example SOAP
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -175,7 +175,7 @@ 
    Request Example SOAP
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -196,4 +196,4 @@ 
    - + diff --git a/guides/m1x/api/soap/checkout/cartProduct/cart_product.add.html b/guides/m1x/api/soap/checkout/cartProduct/cart_product.add.html index 6c8e329b02..a9a5e6310e 100644 --- a/guides/m1x/api/soap/checkout/cartProduct/cart_product.add.html +++ b/guides/m1x/api/soap/checkout/cartProduct/cart_product.add.html @@ -120,7 +120,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -154,7 +154,7 @@ 
    Request Example SOAP V1<
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
      
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -179,7 +179,7 @@ 
    Request Example SOAP V2<
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -200,4 +200,4 @@ 
    R
    - + diff --git a/guides/m1x/api/soap/checkout/cartProduct/cart_product.list.html b/guides/m1x/api/soap/checkout/cartProduct/cart_product.list.html index 98386e005f..fb290556fa 100644 --- a/guides/m1x/api/soap/checkout/cartProduct/cart_product.list.html +++ b/guides/m1x/api/soap/checkout/cartProduct/cart_product.list.html @@ -115,7 +115,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -130,7 +130,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -145,7 +145,7 @@ 
    Request Example SOAP V2
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -159,7 +159,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -177,4 +177,4 @@ 
    Response Example SOAP
    - + diff --git a/guides/m1x/api/soap/checkout/cartProduct/cart_product.moveToCustomerQuote.html b/guides/m1x/api/soap/checkout/cartProduct/cart_product.moveToCustomerQuote.html index bfd0126380..70ef79e987 100644 --- a/guides/m1x/api/soap/checkout/cartProduct/cart_product.moveToCustomerQuote.html +++ b/guides/m1x/api/soap/checkout/cartProduct/cart_product.moveToCustomerQuote.html @@ -120,7 +120,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    diff --git a/guides/m1x/api/soap/checkout/cartProduct/cart_product.remove.html b/guides/m1x/api/soap/checkout/cartProduct/cart_product.remove.html
    index 6ee458449e..44413c1017 100644
    --- a/guides/m1x/api/soap/checkout/cartProduct/cart_product.remove.html
    +++ b/guides/m1x/api/soap/checkout/cartProduct/cart_product.remove.html
    @@ -120,7 +120,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -164,7 +164,7 @@ 
    Request Example SOAP
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -191,7 +191,7 @@ 
    Request Example SOAP
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -211,4 +211,4 @@ 
    - + diff --git a/guides/m1x/api/soap/checkout/cartProduct/cart_product.update.html b/guides/m1x/api/soap/checkout/cartProduct/cart_product.update.html index a3caa7636e..31cc18dcc0 100644 --- a/guides/m1x/api/soap/checkout/cartProduct/cart_product.update.html +++ b/guides/m1x/api/soap/checkout/cartProduct/cart_product.update.html @@ -117,7 +117,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -163,7 +163,7 @@ 
    Request Example SOAP
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
      
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -189,7 +189,7 @@ 
    Request Example SOAP
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
      
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -209,4 +209,4 @@ 
    - + diff --git a/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.list.html b/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.list.html index 4d7afefb92..d503c905ab 100644 --- a/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.list.html +++ b/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.list.html @@ -114,7 +114,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl'); 
     
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -131,7 +131,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
    @@ -147,7 +147,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -158,4 +158,4 @@ 
    - + diff --git a/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.method.html b/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.method.html index 9a998d4ad9..c89bb4ae53 100644 --- a/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.method.html +++ b/guides/m1x/api/soap/checkout/cartShipping/cart_shipping.method.html @@ -74,7 +74,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     $sessionId = $proxy->login('apiUser', 'apiKey');
    @@ -91,7 +91,7 @@ 
    Request Example SOAP
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login('apiUser', 'apiKey');
    @@ -106,7 +106,7 @@ 
    Request Example SOAP
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -116,4 +116,4 @@ 
    <
    - + diff --git a/guides/m1x/api/soap/checkout/checkout.html b/guides/m1x/api/soap/checkout/checkout.html index 4865423486..1155706d5f 100644 --- a/guides/m1x/api/soap/checkout/checkout.html +++ b/guides/m1x/api/soap/checkout/checkout.html @@ -89,4 +89,3 @@

    Shopping Cart

  • cart.totals - Get all available prices for items in shopping cart, using additional parameters
  • cart.license - Get website license agreement
  • - \ No newline at end of file diff --git a/guides/m1x/api/soap/create_your_own_api.html b/guides/m1x/api/soap/create_your_own_api.html index 64f8d53d87..887cd3c2f7 100644 --- a/guides/m1x/api/soap/create_your_own_api.html +++ b/guides/m1x/api/soap/create_your_own_api.html @@ -20,8 +20,6 @@ - -

    Creating a Custom API or Extending the Core API

    @@ -40,7 +38,7 @@

    <

    Create a file named api.xml in the /etc folder in the customer module. Start with the empty structure, as follows:

    -
    +
    <config>
         <api>
             <resources>
    @@ -71,7 +69,7 @@ 

    2. Adding a Re
    -
    +
    <config>
         <api>
     ....
    @@ -109,7 +107,7 @@ 

    3. Adding Faults

    The resource can return some faults, so add a <faults> element in the customer element, and list the various faults.

    -
    +
    <config>
         <api>
     ....
    @@ -147,7 +145,7 @@ 

    -
    +
    <config>
         <api>
     ....
    @@ -180,7 +178,7 @@ 

    -
    +
    <config>
         <api>
             <resources>
    @@ -222,7 +220,7 @@ 

    5. Creating PHP Code

    Next, write some PHP code to access the resources. Start by creating a class called Mage_Customer_Model_Customer_Api that extends Mage_Api_Model_Resource_Abstract. Save it into a file called api.php.

    -
    +
    class Mage_Customer_Model_Customer_Api extends Mage_Api_Model_Resource_Abstract
     {
     
    @@ -251,7 +249,7 @@ 

    5. Creating PHP Code

    Note that you cannot create method "list" because it’s a PHP keyword, so instead the method is named items. In order to make this work, add a <method> element into the <list> element in api.xml, as shown below.

    -
    +
    <config>
         <api>
             <resources>
    @@ -279,7 +277,7 @@ 

    5. Creating PHP Code

    Create a customer:

    -
    +
    public function create($customerData)
         {
             try {
    @@ -300,7 +298,7 @@ 

    5. Creating PHP Code

    Retrieve customer info:

    -
    +
    public function info($customerId)
         {
             $customer = Mage::getModel('customer/customer')->load($customerId);
    @@ -316,7 +314,7 @@ 

    5. Creating PHP Code

    Retrieve list of customers using filtering:

    -
    +
    public function items($filters)
         {
             $collection = Mage::getModel('customer/customer')->getCollection()
    @@ -345,7 +343,7 @@ 

    5. Creating PHP Code

    Update a customer:

    -
    +
    public function update($customerId, $customerData)
         {
             $customer = Mage::getModel('customer/customer')->load($customerId);
    @@ -363,7 +361,7 @@ 

    5. Creating PHP Code

    Delete a customer:

    -
    +
    public function delete($customerId)
         {
             $customer = Mage::getModel('customer/customer')->load($customerId);
    @@ -389,7 +387,7 @@ 

    Creating a Custom Adap

    In order to create custom webservice adapter, implement the Mage_Api_Model_Server_Adapter_Interface, which is shown below.

    -
    +
    interface Mage_Api_Model_Server_Adapter_Interface
     {
         /**
    @@ -443,7 +441,7 @@ 

    Creating a Custom Adap

    Here is an example implementation for XML-RPC:

    -
    +
    class Mage_Api_Model_Server_Adapter_Customxmlrpc
         extends Varien_Object
         implements Mage_Api_Model_Server_Adapter_Interface
    @@ -533,7 +531,7 @@ 

    Creating a Custom Adap

    The run and fault methods are a native implementation for an XML-RPC webservice. The run method defines webservice logic in this adapter for creating an XML-RPC server to handle XML-RPC requests.

    -
    +
    public function run()
         {
             $this->_xmlRpc = new Zend_XmlRpc_Server();
    @@ -548,7 +546,7 @@ 

    Creating a Custom Adap

    The "fault" method allows you to send fault exceptions for XML-RPC service when handling requests.

    -
    +
    public function fault($code, $message)
         {
             throw new Zend_XmlRpc_Server_Exception($message, $code);
    @@ -566,7 +564,7 @@ 

    Common Error Messages

    For example, in your api.xml file, you might have this:

    -
    +
    <config>
         <api>
             <resources>
    @@ -590,7 +588,7 @@ 

    Common Error Messages

    You should have a corresponding info method in your PHP file.

    -
    +
    class Mage_Checkout_Model_Cart_Api extends Mage_Cart_Model_Api_Resource
     {
         public function info()
    @@ -599,7 +597,7 @@ 

    Common Error Messages

    -
    +

    If you are missing this method, the error "Invalid API path" will be returned.

    - + diff --git a/guides/m1x/api/soap/customer/customer.create.html b/guides/m1x/api/soap/customer/customer.create.html index a74843f053..0dc813cbe8 100644 --- a/guides/m1x/api/soap/customer/customer.create.html +++ b/guides/m1x/api/soap/customer/customer.create.html @@ -138,7 +138,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -156,7 +156,7 @@ 
    Request Example SOAP V1Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -173,7 +173,7 @@ 
    Request Example SOAP V2Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -190,4 +190,4 @@ 
    Re
    - + diff --git a/guides/m1x/api/soap/customer/customer.delete.html b/guides/m1x/api/soap/customer/customer.delete.html index ba2c1ffad1..dfd3de60f4 100644 --- a/guides/m1x/api/soap/customer/customer.delete.html +++ b/guides/m1x/api/soap/customer/customer.delete.html @@ -60,7 +60,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -78,7 +78,7 @@ 
    Request Example SOAP V1Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -91,7 +91,7 @@ 
    Request Example SOAP V2Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -101,4 +101,4 @@ 
    Re
    - + diff --git a/guides/m1x/api/soap/customer/customer.html b/guides/m1x/api/soap/customer/customer.html index e16f9e745c..f98dc02b63 100644 --- a/guides/m1x/api/soap/customer/customer.html +++ b/guides/m1x/api/soap/customer/customer.html @@ -54,7 +54,7 @@

    Examples

    Example 1. View, create, update, and delete a customer
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     $newCustomer = array(
    @@ -101,4 +101,3 @@ 

    Customer Groups

    - \ No newline at end of file diff --git a/guides/m1x/api/soap/customer/customer.info.html b/guides/m1x/api/soap/customer/customer.info.html index b7655f3721..5964c9de5a 100644 --- a/guides/m1x/api/soap/customer/customer.info.html +++ b/guides/m1x/api/soap/customer/customer.info.html @@ -183,7 +183,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -201,7 +201,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2

    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -214,7 +214,7 @@ 
    Request Example SOAP V2
    Request Example SOAP V2 (WS-I Compliance Mode)

    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -227,7 +227,7 @@ 
    Requ
    Response Example SOAP V1
    -
    +
    array
       'customer_id' => string '2' (length=1)
       'created_at' => string '2012-03-29 12:37:23' (length=19)
    @@ -256,4 +256,4 @@ 
    Response Example SOAP V1
    - + diff --git a/guides/m1x/api/soap/customer/customer.list.html b/guides/m1x/api/soap/customer/customer.list.html index 0f30ab6336..8998e8aa39 100644 --- a/guides/m1x/api/soap/customer/customer.list.html +++ b/guides/m1x/api/soap/customer/customer.list.html @@ -163,7 +163,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -182,7 +182,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2 (List of All Customers)

    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -195,7 +195,7 @@ 
    Req
    Request Example SOAP V2 (Complex Filter)
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -219,7 +219,7 @@ 
    Request
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -233,7 +233,7 @@ 
    Requ
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -272,4 +272,4 @@ 
    Response Example SOAP V1
    - + diff --git a/guides/m1x/api/soap/customer/customer.update.html b/guides/m1x/api/soap/customer/customer.update.html index 736491f825..98013d0f55 100644 --- a/guides/m1x/api/soap/customer/customer.update.html +++ b/guides/m1x/api/soap/customer/customer.update.html @@ -135,7 +135,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -153,7 +153,7 @@ 
    Request Example SOAP V1Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -171,7 +171,7 @@ 
    Request Example SOAP V2Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -185,4 +185,4 @@ 
    Re
    - + diff --git a/guides/m1x/api/soap/customer/customerAddress/customerAddress.html b/guides/m1x/api/soap/customer/customerAddress/customerAddress.html index 0db60c7ddd..748351be41 100644 --- a/guides/m1x/api/soap/customer/customerAddress/customerAddress.html +++ b/guides/m1x/api/soap/customer/customerAddress/customerAddress.html @@ -50,7 +50,7 @@

    Examples

    Example 1. Working with customer address
    -
    +
    $proxy = new SoapClient('http://magentohost/api/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    diff --git a/guides/m1x/api/soap/customer/customerAddress/customer_address.create.html b/guides/m1x/api/soap/customer/customerAddress/customer_address.create.html
    index cd5e76f61b..9ffb4d386b 100644
    --- a/guides/m1x/api/soap/customer/customerAddress/customer_address.create.html
    +++ b/guides/m1x/api/soap/customer/customerAddress/customer_address.create.html
    @@ -158,7 +158,7 @@ 

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -176,7 +176,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -193,7 +193,7 @@ 
    Request Example S
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -213,4 +213,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -75,7 +75,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -90,7 +90,7 @@ 
    Request Example S
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -100,4 +100,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -194,7 +194,7 @@ 
    Request Example SOA
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -207,7 +207,7 @@ 
    Request Example SOA
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -221,7 +221,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       'customer_address_id' => string '2' (length=1)
       'created_at' => string '2012-03-29 13:20:08' (length=19)
    @@ -251,4 +251,4 @@ 
    Response Example S
    - + diff --git a/guides/m1x/api/soap/customer/customerAddress/customer_address.list.html b/guides/m1x/api/soap/customer/customerAddress/customer_address.list.html index 49abaa8cbd..a6089c543a 100644 --- a/guides/m1x/api/soap/customer/customerAddress/customer_address.list.html +++ b/guides/m1x/api/soap/customer/customerAddress/customer_address.list.html @@ -172,7 +172,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -191,7 +191,7 @@ 
    Request Example SOA
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -204,7 +204,7 @@ 
    Request Example SOA
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -218,7 +218,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -256,4 +256,4 @@ 
    Response Example S
    - + diff --git a/guides/m1x/api/soap/customer/customerAddress/customer_address.update.html b/guides/m1x/api/soap/customer/customerAddress/customer_address.update.html index 32332f2559..5555cca0ee 100644 --- a/guides/m1x/api/soap/customer/customerAddress/customer_address.update.html +++ b/guides/m1x/api/soap/customer/customerAddress/customer_address.update.html @@ -155,7 +155,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -173,7 +173,7 @@ 
    Request Example S
    Request Example SOAP V2
    -
    +
    $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     // If some stuff requires API authentication,
    @@ -190,7 +190,7 @@ 
    Request Example S
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -212,4 +212,4 @@ 
    Examples
    Request Example SOAP V1
    -
    +
    $client = new SoapClient('http://magentohost/api/soap/?wsdl');
     
     // If somestuff requires API authentication,
    @@ -96,7 +96,7 @@ 
    Request Example SOAP
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -109,7 +109,7 @@ 
    Request Example SOAP
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
    @@ -122,7 +122,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -143,4 +143,4 @@ 
    Response Example SOA
    - + diff --git a/guides/m1x/api/soap/directory/directory.html b/guides/m1x/api/soap/directory/directory.html index 5dbbc72322..9bad380715 100644 --- a/guides/m1x/api/soap/directory/directory.html +++ b/guides/m1x/api/soap/directory/directory.html @@ -41,4 +41,3 @@

    Region

    - \ No newline at end of file diff --git a/guides/m1x/api/soap/directory/directory_country.list.html b/guides/m1x/api/soap/directory/directory_country.list.html index ca35a6189d..8679771e0b 100644 --- a/guides/m1x/api/soap/directory/directory_country.list.html +++ b/guides/m1x/api/soap/directory/directory_country.list.html @@ -103,7 +103,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $countries = $proxy->call($sessionId, 'country.list');
    @@ -114,7 +114,7 @@ 
    Request Example SO
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -127,7 +127,7 @@ 
    Request Example SO
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -140,7 +140,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -163,4 +163,4 @@ 
    Response Example
    - + diff --git a/guides/m1x/api/soap/directory/directory_region.list.html b/guides/m1x/api/soap/directory/directory_region.list.html index bad8464764..8866dee39a 100644 --- a/guides/m1x/api/soap/directory/directory_region.list.html +++ b/guides/m1x/api/soap/directory/directory_region.list.html @@ -117,7 +117,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     $regions = $proxy->call($sessionId, 'region.list', 'US');
    @@ -129,7 +129,7 @@ 
    Request Example SOA
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     $sessionId = $proxy->login('apiUser', 'apiKey'); 
     
    @@ -143,7 +143,7 @@ 
    Request Example SOA
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -158,7 +158,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -183,4 +183,4 @@ 
    Response Example S
    - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.add.html b/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.add.html index 167226ac75..95537ff1d4 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.add.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.add.html @@ -95,7 +95,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -117,7 +117,7 @@ 
    Request Example SOAP V1
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -133,7 +133,7 @@ 
    Request Example SOAP V2
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -144,4 +144,4 @@ 
    - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.list.html b/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.list.html index 4a29ea9e91..f74f4ca3dc 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.list.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.list.html @@ -115,7 +115,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -136,7 +136,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -150,7 +150,7 @@ 
    Request Example SOAP V
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -169,7 +169,7 @@ 
    Response Example SOAP V1
    -
    +
    array
       0 =>
         array
    @@ -187,4 +187,4 @@ 
    Response Example SOAP
    - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.remove.html b/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.remove.html index 84002a9575..936ec0c049 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.remove.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/cartGiftCard/cart_giftcard.remove.html @@ -95,7 +95,7 @@

    Examples

    Request Example SOAP V1
    -
    +
    $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
     $sessionId = $proxy->login('apiUser', 'apiKey');
     
    @@ -116,7 +116,7 @@ 
    Request Example SOAP
    Request Example SOAP V2
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
     $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
     
    @@ -130,7 +130,7 @@ 
    Request Example SOAP
    Request Example SOAP V2 (WS-I Compliance Mode)
    -
    +
    $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
     
     $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
    @@ -142,4 +142,4 @@ 
    <
    - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/enterprise_giftCard.html b/guides/m1x/api/soap/enterpriseGiftCard/enterprise_giftCard.html index 6649a594ba..eb221a1f1e 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/enterprise_giftCard.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/enterprise_giftCard.html @@ -11,7 +11,7 @@

    Customer Gift Card

    Resource Name: giftcard_customer

    -
    Methods:
    +
    Methods:
    • giftcard_customer.info - Receive information about the gift card for a selected customer
    • @@ -26,7 +26,7 @@

      Shopping Cart Gift Ca

      Resource Name: cart_giftcard

      -

      Methods:
      +
      Methods:
      • cart_giftcard.list - Retrieve the list of gift cards used in the shopping cart (quote).
      • @@ -43,7 +43,7 @@

        Gift Card Account

        Resource Name: giftcard_account

        -
        Methods:
        +
        Methods:
        • giftcard_account.create - Create a new gift card
        • @@ -55,5 +55,5 @@
          Methods:
          - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.create.html b/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.create.html index fdd3546c48..9db02683ca 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.create.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.create.html @@ -149,7 +149,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -175,7 +175,7 @@ 
          Request Example S
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login('apiUser', 'apiKey'); 
          @@ -202,7 +202,7 @@ 
          Request Example S
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -224,4 +224,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -193,7 +193,7 @@ 
          Request Example SOA
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -207,7 +207,7 @@ 
          Request Example SOA
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -222,7 +222,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             'giftcard_id' => string '1' (length=1)
             'code' => string '02DQ9T1K0Y0V' (length=12)
          @@ -246,4 +246,4 @@ 
          Response Example S
          - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.list.html b/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.list.html index 52416fbed3..130fbea58f 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.list.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.list.html @@ -126,7 +126,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -140,7 +140,7 @@ 
          Request Example SOA
          Request Example SOAP V2 (List of All Gift Card Accounts)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -152,7 +152,7 @@ 
          Request Example SOAP V2 (Complex Filter)
          -
          +
          $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           
           // If some stuff requires API authentication,
          @@ -177,7 +177,7 @@ 
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -194,7 +194,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             0 =>
               array
          @@ -219,4 +219,4 @@ 
          Response Example S
          - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.remove.html b/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.remove.html index 16635bd975..1cba60225b 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.remove.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/giftCardAccount/giftcard_account.remove.html @@ -78,7 +78,7 @@
          Request Example S
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -97,7 +97,7 @@ 
          Request Example S
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -111,7 +111,7 @@ 
          Request Example S
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -122,4 +122,4 @@ 
          Request Example S
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -140,7 +140,7 @@ 
          Request Example S
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login('apiUser', 'apiKey'); 
          @@ -161,7 +161,7 @@ 
          Request Example S
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -177,4 +177,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -119,7 +119,7 @@ 
          Request Example SO
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -133,7 +133,7 @@ 
          Request Example SO
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
          @@ -147,11 +147,11 @@ 
          Response Example SOAP V1
          -
          +
          array
             'balance' => string '500.0000' (length=8)
             'expire_date' => string '2012-04-25' (length=10)
          - + diff --git a/guides/m1x/api/soap/enterpriseGiftCard/giftCardCustomer/giftcard_customer.redeem.html b/guides/m1x/api/soap/enterpriseGiftCard/giftCardCustomer/giftcard_customer.redeem.html index 842c134dcf..fd9fbca248 100644 --- a/guides/m1x/api/soap/enterpriseGiftCard/giftCardCustomer/giftcard_customer.redeem.html +++ b/guides/m1x/api/soap/enterpriseGiftCard/giftCardCustomer/giftcard_customer.redeem.html @@ -95,7 +95,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -118,7 +118,7 @@ 
          Request Example
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -132,7 +132,7 @@ 
          Request Example
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -143,4 +143,4 @@ 
          Faults:
          Example:
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          diff --git a/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuote.html b/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuote.html
          index b4c71a54b0..09b696a125 100644
          --- a/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuote.html
          +++ b/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuote.html
          @@ -122,7 +122,7 @@ 

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -137,7 +137,7 @@ 
          Request Example S
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login('apiUser', 'apiKey'); 
          @@ -157,7 +157,7 @@ 
          Request Example S
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -175,7 +175,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             'entityId' => string '15' (length=2)
             'result' => boolean true
          @@ -183,4 +183,4 @@ 
          Response Example
          - + diff --git a/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteItem.html b/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteItem.html index 864d851a1e..342b147c0c 100644 --- a/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteItem.html +++ b/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteItem.html @@ -122,7 +122,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -139,7 +139,7 @@ 
          Request Examp
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login('apiUser', 'apiKey'); 
          @@ -158,7 +158,7 @@ 
          Request Examp
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -176,7 +176,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             'entityId' => string '1' (length=1)
             'result' => boolean true
          @@ -184,4 +184,4 @@ 
          Response Exa
          - + diff --git a/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteProduct.html b/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteProduct.html index 646d3a3373..8269b4b916 100644 --- a/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteProduct.html +++ b/guides/m1x/api/soap/enterpriseGiftMessage/giftmessage.setForQuoteProduct.html @@ -190,7 +190,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
            
          @@ -217,7 +217,7 @@ 
          Request Ex
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login('apiUser', 'apiKey'); 
          @@ -246,7 +246,7 @@ 
          Request Ex
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -269,4 +269,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $customerId = 4;
          @@ -98,7 +98,7 @@ 
          Request Example SOAP
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -111,7 +111,7 @@ 
          Request Example SOAP
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -122,4 +122,4 @@ 
          - + diff --git a/guides/m1x/api/soap/enterprise_customerbalance/customerBalance/storecredit.history.html b/guides/m1x/api/soap/enterprise_customerbalance/customerBalance/storecredit.history.html index fd1594803d..266084e7e6 100644 --- a/guides/m1x/api/soap/enterprise_customerbalance/customerBalance/storecredit.history.html +++ b/guides/m1x/api/soap/enterprise_customerbalance/customerBalance/storecredit.history.html @@ -152,7 +152,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $customerId = 4;
          @@ -164,7 +164,7 @@ 
          Request Example SOAP
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -177,7 +177,7 @@ 
          Request Example SOAP
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -192,7 +192,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             0 =>
               array
          @@ -224,4 +224,4 @@ 
          Response Example SOA
          - + diff --git a/guides/m1x/api/soap/enterprise_customerbalance/enterprise_customerbalance.html b/guides/m1x/api/soap/enterprise_customerbalance/enterprise_customerbalance.html index 318daac885..b8c19ef858 100644 --- a/guides/m1x/api/soap/enterprise_customerbalance/enterprise_customerbalance.html +++ b/guides/m1x/api/soap/enterprise_customerbalance/enterprise_customerbalance.html @@ -13,7 +13,7 @@

          Aliases: storecredit

          -

          Methods:
          +
          Methods:
          • storecredit.balance - Retrieve the customer store credit balance information
          • @@ -21,7 +21,7 @@
            Methods:
          -
          Faults:
          +
          Faults:
          @@ -48,7 +48,7 @@

          Aliases: storecredit_quote

          -
          Methods:
          +

          Methods:
          -
          Faults:
          +
          Faults:
          @@ -85,7 +85,7 @@
          Faults:
          Example:
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          diff --git a/guides/m1x/api/soap/enterprise_customerbalance/shoppingCartCustomerBalance/storecredit_quote.removeAmount.html b/guides/m1x/api/soap/enterprise_customerbalance/shoppingCartCustomerBalance/storecredit_quote.removeAmount.html
          index 43c639b431..42631e35d0 100644
          --- a/guides/m1x/api/soap/enterprise_customerbalance/shoppingCartCustomerBalance/storecredit_quote.removeAmount.html
          +++ b/guides/m1x/api/soap/enterprise_customerbalance/shoppingCartCustomerBalance/storecredit_quote.removeAmount.html
          @@ -92,7 +92,7 @@ 

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $quoteId = 15;
          @@ -104,7 +104,7 @@ 
          Request Ex
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -119,7 +119,7 @@ 
          Request Ex
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -130,4 +130,4 @@ 
          Request Examp
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $quoteId = 2;
          @@ -106,7 +106,7 @@ 
          Request Examp
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -121,7 +121,7 @@ 
          Request Examp
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -131,4 +131,4 @@ 
          SOAP

          To connect to Magento SOAP web services, load the WSDL into your SOAP client from either of these URLs:

          -
          +
          http://magentohost/api/?wsdl
          -
          +
          http://magentohost/api/soap/?wsdl
          @@ -46,7 +46,7 @@

          SOAP

          As of v1.3, you may also use the following URL to access the Magento API v2, which has been added to improve compatibility with Java and .NET:

          -
          +
          http://magentohost/api/v2_soap?wsdl=1
          @@ -54,7 +54,7 @@

          SOAP

          The following PHP example shows how to make SOAP calls to the Magento API v1:

          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -81,7 +81,7 @@ 

          XML-RPC

          To use XML-RPC, load the following URL into your XML-RPC client:

          -
          +
          http://magentohost/api/xmlrpc/
          @@ -91,7 +91,7 @@

          XML-RPC

          The following PHP example shows how to make XML-RPC calls:

          -
          +
          $client = new Zend_XmlRpc_Client('http://magentohost/api/xmlrpc/');
           
           // If somestuff requires API authentication,
          @@ -214,7 +214,7 @@ 

          SOAP API Version v2

          For example, consider the following PHP code using SOAP v1.

          -
          +
          $params = array(array(
               'status'=>array('eq'=>'pending'),
               'customer_is_guest'=>array('eq'=>'1'))
          @@ -225,7 +225,7 @@ 

          SOAP API Version v2

          With SOAP v2, the following code would be equivalent.

          -
          +
          $params = array('filter' => array(
               array('key' => 'status', 'value' => 'pending'),
               array('key' => 'customer_is_guest', 'value' => '1')
          @@ -243,4 +243,4 @@ 

          SOAP API Version v2

          Using the WS-I compliant SOAP v2 API WSDL, it is easy to automatically generate client classes for Java, .NET, and other languages using standard libraries.

          - + diff --git a/guides/m1x/api/soap/miscellaneous/magento.info.html b/guides/m1x/api/soap/miscellaneous/magento.info.html index 2b1224e500..c5585033ea 100644 --- a/guides/m1x/api/soap/miscellaneous/magento.info.html +++ b/guides/m1x/api/soap/miscellaneous/magento.info.html @@ -68,7 +68,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $magentoInfo = $proxy->call(
          @@ -81,7 +81,7 @@ 
          Request Example SOAP V1
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -94,7 +94,7 @@ 
          Request Example SOAP V2
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -108,11 +108,11 @@ 
          Reque
          Response Example SOAP V1
          -
          +
          array
             'magento_edition' => string 'Community' (length=9)
             'magento_version' => string '1.4.2.0-rc1' (length=11)
          - + diff --git a/guides/m1x/api/soap/miscellaneous/store.info.html b/guides/m1x/api/soap/miscellaneous/store.info.html index 9a3cd8d1e0..8fea1fb417 100644 --- a/guides/m1x/api/soap/miscellaneous/store.info.html +++ b/guides/m1x/api/soap/miscellaneous/store.info.html @@ -122,7 +122,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -137,7 +137,7 @@ 
          Request Example SOAP V1
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -148,10 +148,10 @@ 
          Request Example SOAP V2
          -
          Request Example SOAP V2 (WS-I Compliance Mode)
          +
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -167,7 +167,7 @@ 
          Request Example SOAP V2 (WS-I
          Response Example SOAP V1
          -
          +
          array
             'store_id' => string '2' (length=1)
             'code' => string 'english' (length=7)
          @@ -179,4 +179,4 @@ 
          Response Example SOAP V1
          - + diff --git a/guides/m1x/api/soap/miscellaneous/store.list.html b/guides/m1x/api/soap/miscellaneous/store.list.html index 580f8f0556..dace494d7d 100644 --- a/guides/m1x/api/soap/miscellaneous/store.list.html +++ b/guides/m1x/api/soap/miscellaneous/store.list.html @@ -104,7 +104,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -119,7 +119,7 @@ 
          Request Example SOAP V1
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -133,7 +133,7 @@ 
          Request Example SOAP V2
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -148,7 +148,7 @@ 
          Request
          Response Example SOAP V1
          -
          +
          array
             0 =>
               array
          @@ -171,4 +171,4 @@ 
          Response Example SOAP V1
          - + diff --git a/guides/m1x/api/soap/sales/salesOrder/salesOrder.html b/guides/m1x/api/soap/sales/salesOrder/salesOrder.html index 7ad9013242..8750fa90b8 100644 --- a/guides/m1x/api/soap/sales/salesOrder/salesOrder.html +++ b/guides/m1x/api/soap/sales/salesOrder/salesOrder.html @@ -61,7 +61,7 @@

          Examples

          Example 1. Work with orders
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -91,5 +91,5 @@ 
          Example 1. Work with orders
          - + diff --git a/guides/m1x/api/soap/sales/salesOrder/sales_order.addComment.html b/guides/m1x/api/soap/sales/salesOrder/sales_order.addComment.html index 49aa701510..fd5fbae5e2 100644 --- a/guides/m1x/api/soap/sales/salesOrder/sales_order.addComment.html +++ b/guides/m1x/api/soap/sales/salesOrder/sales_order.addComment.html @@ -87,7 +87,7 @@
          Request Example SO
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -106,7 +106,7 @@ 
          Request Example SO
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -120,7 +120,7 @@ 
          -
          + - + diff --git a/guides/m1x/api/soap/sales/salesOrder/sales_order.cancel.html b/guides/m1x/api/soap/sales/salesOrder/sales_order.cancel.html index 3c21cec055..e02ffc865a 100644 --- a/guides/m1x/api/soap/sales/salesOrder/sales_order.cancel.html +++ b/guides/m1x/api/soap/sales/salesOrder/sales_order.cancel.html @@ -72,7 +72,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -90,7 +90,7 @@ 
          Request Example SOAP V
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -103,7 +103,7 @@ 
          Request Example SOAP V
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -113,4 +113,4 @@ 
          - + diff --git a/guides/m1x/api/soap/sales/salesOrder/sales_order.hold.html b/guides/m1x/api/soap/sales/salesOrder/sales_order.hold.html index ab4a15f99b..701ef966fb 100644 --- a/guides/m1x/api/soap/sales/salesOrder/sales_order.hold.html +++ b/guides/m1x/api/soap/sales/salesOrder/sales_order.hold.html @@ -72,7 +72,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -90,7 +90,7 @@ 
          Request Example SOAP V1<
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -104,7 +104,7 @@ 
          Request Example SOAP V2<
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -115,4 +115,4 @@ 
          R
          - + diff --git a/guides/m1x/api/soap/sales/salesOrder/sales_order.info.html b/guides/m1x/api/soap/sales/salesOrder/sales_order.info.html index 2848c80056..f6e970c619 100644 --- a/guides/m1x/api/soap/sales/salesOrder/sales_order.info.html +++ b/guides/m1x/api/soap/sales/salesOrder/sales_order.info.html @@ -1004,7 +1004,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -1022,7 +1022,7 @@ 
          Request Example SOAP V1<
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -1035,7 +1035,7 @@ 
          Request Example SOAP V2<
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -1049,7 +1049,7 @@ 
          R
          Response Example SOAP V1
          -
          +
          array
             'state' => string 'new' (length=3)
             'status' => string 'pending' (length=7)
          @@ -1185,4 +1185,4 @@ 
          Response Example SOAP V
          - + diff --git a/guides/m1x/api/soap/sales/salesOrder/sales_order.list.html b/guides/m1x/api/soap/sales/salesOrder/sales_order.list.html index 6d069ac0a3..a3a2e1841e 100644 --- a/guides/m1x/api/soap/sales/salesOrder/sales_order.list.html +++ b/guides/m1x/api/soap/sales/salesOrder/sales_order.list.html @@ -421,7 +421,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -436,7 +436,7 @@ 
          Request Example SOAP V1<
          Request Example SOAP V2
          -
          +
          $params = array(array(
                       'filter' => array(
                           array(
          @@ -474,7 +474,7 @@ 
          Request Example SOAP V2<
          Request Example SOAP V2 (Simple Filter)
          -
          +
          $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           
           // If some stuff requires API authentication,
          @@ -490,7 +490,7 @@ 
          Reques
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -504,7 +504,7 @@ 
          R
          XML SOAP V2 Example
          SOAP "v2" XML Request
          -
          +
          <?xml version="1.0" encoding="UTF-8"?>
           <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="urn:Magento"
                              xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          @@ -547,4 +547,4 @@ 
          XML SOAP V2 Example
          - + diff --git a/guides/m1x/api/soap/sales/salesOrder/sales_order.unhold.html b/guides/m1x/api/soap/sales/salesOrder/sales_order.unhold.html index a971333258..0f5f57eb3b 100644 --- a/guides/m1x/api/soap/sales/salesOrder/sales_order.unhold.html +++ b/guides/m1x/api/soap/sales/salesOrder/sales_order.unhold.html @@ -71,7 +71,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -86,7 +86,7 @@ 
          Request Example SOAP V
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           $sessionId = $proxy->login('apiUser', 'apiKey'); 
           
          @@ -99,7 +99,7 @@ 
          Request Example SOAP V
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -109,4 +109,4 @@ 
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderCreditMemo/salesOrderCreditMemo.html b/guides/m1x/api/soap/sales/salesOrderCreditMemo/salesOrderCreditMemo.html index e59902a13e..4c7bb17f08 100644 --- a/guides/m1x/api/soap/sales/salesOrderCreditMemo/salesOrderCreditMemo.html +++ b/guides/m1x/api/soap/sales/salesOrderCreditMemo/salesOrderCreditMemo.html @@ -65,7 +65,7 @@
          Faults:
          Example:
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -111,5 +111,5 @@ 
          Example:
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.addComment.html b/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.addComment.html index 47f21c9189..1a3e70f7eb 100644 --- a/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.addComment.html +++ b/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.addComment.html @@ -93,7 +93,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $creditmemoIncrementId = '200000001'; //increment id of existing credit memo
          @@ -106,7 +106,7 @@ 
          Request Examp
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -118,7 +118,7 @@ 
          Request Examp
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -128,4 +128,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $creditmemoIncrementId = '100000637'; //increment id of existing credit memo
          diff --git a/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.create.html b/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.create.html
          index ac62c03f95..c45d8dec4c 100644
          --- a/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.create.html
          +++ b/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.create.html
          @@ -165,7 +165,7 @@ 

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -180,7 +180,7 @@ 
          Request Example S
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -194,7 +194,7 @@ 
          Request Example S
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -216,4 +216,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -682,7 +682,7 @@ 
          Request Example SOA
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -695,7 +695,7 @@ 
          Request Example SOA
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -708,7 +708,7 @@ 
          Response Example SOAP V1
          -
          +
          array(
               'store_id' => '1',
               'adjustment_positive' => NULL,
          @@ -882,4 +882,4 @@ 
          Response Example S
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.list.html b/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.list.html index 47dcc25ae6..799ede91f3 100644 --- a/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.list.html +++ b/guides/m1x/api/soap/sales/salesOrderCreditMemo/sales_order_creditmemo.list.html @@ -665,7 +665,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           $filter = array(
          @@ -701,7 +701,7 @@ 
          Request Example SOA
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -714,7 +714,7 @@ 
          Request Example SOA
          Request Example SOAP V2 (Complex Filter)
          -
          +
          $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           
           // If some stuff requires API authentication,
          @@ -739,7 +739,7 @@ 
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -753,7 +753,7 @@ 
          Response Example SOAP V1
          -
          +
          array(
               0 => array(
                   'store_id' => '1',
          @@ -837,4 +837,4 @@ 
          Response Example S
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderInvoice/salesOrderInvoice.html b/guides/m1x/api/soap/sales/salesOrderInvoice/salesOrderInvoice.html index b20404e594..1a653227fa 100644 --- a/guides/m1x/api/soap/sales/salesOrderInvoice/salesOrderInvoice.html +++ b/guides/m1x/api/soap/sales/salesOrderInvoice/salesOrderInvoice.html @@ -65,7 +65,7 @@

          Examples

          Example 1. Basic working with invoices.
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          diff --git a/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.addComment.html b/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.addComment.html
          index ac393b89a5..a25fe38b55 100644
          --- a/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.addComment.html
          +++ b/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.addComment.html
          @@ -85,7 +85,7 @@ 

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -103,7 +103,7 @@ 
          Request Ex
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -117,7 +117,7 @@ 
          Request Ex
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -127,4 +127,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          diff --git a/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.capture.html b/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.capture.html
          index b8fc0b71a8..6c47268572 100644
          --- a/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.capture.html
          +++ b/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.capture.html
          @@ -86,7 +86,7 @@ 

          Examples

          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -114,7 +114,7 @@ 
          Request Examp
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           $sessionID = $proxy->login('apiUser', 'apiKey');
           
          @@ -141,7 +141,7 @@ 
          Request Examp
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -153,4 +153,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -135,7 +135,7 @@ 
          Request Exampl
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -159,7 +159,7 @@ 
          Request Exampl
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey'));
          @@ -172,4 +172,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -469,7 +469,7 @@ 
          Request Example
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -482,7 +482,7 @@ 
          Request Example
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -495,7 +495,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             'store_id' => string '2' (length=1)
             'base_grand_total' => string '384.9800' (length=8)
          @@ -586,4 +586,4 @@ 
          Response Exampl
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.list.html b/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.list.html index dd6dc0527f..bfa7d88a9c 100644 --- a/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.list.html +++ b/guides/m1x/api/soap/sales/salesOrderInvoice/sales_order_invoice.list.html @@ -120,7 +120,7 @@

          Examples

          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -138,7 +138,7 @@ 
          Request Example
          Request Example SOAP V2 (List of All Invoices)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -150,7 +150,7 @@ 
          Request Example SOAP V2 (Complex Filter)
          -
          +
          $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           
           // If some stuff requires API authentication,
          @@ -175,7 +175,7 @@ 
          <
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -188,7 +188,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             0 =>
               array
          @@ -211,4 +211,4 @@ 
          Response Exampl
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderShipment/salesOrderShipment.html b/guides/m1x/api/soap/sales/salesOrderShipment/salesOrderShipment.html index 8581b01ca7..77a10f2da1 100644 --- a/guides/m1x/api/soap/sales/salesOrderShipment/salesOrderShipment.html +++ b/guides/m1x/api/soap/sales/salesOrderShipment/salesOrderShipment.html @@ -70,7 +70,7 @@

          Examples

          Example 1. Basic working with shipments
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          diff --git a/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.addComment.html b/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.addComment.html
          index 750f3314dc..aa76ee09f5 100644
          --- a/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.addComment.html
          +++ b/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.addComment.html
          @@ -87,7 +87,7 @@ 
          Request E
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -105,7 +105,7 @@ 
          Request E
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -118,7 +118,7 @@ 
          Request E
          Request Example SOAP V2 (WS- I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -128,4 +128,4 @@ 
          Request Exa
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -107,7 +107,7 @@ 
          Request Exa
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -122,7 +122,7 @@ 
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -133,4 +133,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $proxy = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           $session = $proxy->login('apiUser', 'apiKey');
          @@ -147,7 +147,7 @@ 
          Request Examp
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           $sessionId = $proxy->login('apiUser', 'apiKey');
           
          @@ -171,7 +171,7 @@ 
          Request Examp
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -198,4 +198,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -92,7 +92,7 @@ 
          Request
          Request Example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -105,7 +105,7 @@ 
          Request
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -119,7 +119,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             'custom' => string 'Custom Value' (length=12)
             'dhl' => string 'DHL (Deprecated)' (length=16)
          @@ -130,4 +130,4 @@ 
          Respons
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.info.html b/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.info.html index d2a450d605..11f7d25be7 100644 --- a/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.info.html +++ b/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.info.html @@ -283,7 +283,7 @@

          Examples

          Request example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           $session = $client->login('apiUser', 'apiKey');
           $result = $client->call($session, 'sales_order_shipment.info', '200000003');
          @@ -294,7 +294,7 @@ 
          Request example
          Request example SOAP V2
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -308,7 +308,7 @@ 
          Request example
          Request example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -318,4 +318,4 @@ 
          Examples
          Request Example SOAP V1
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -123,7 +123,7 @@ 
          Request Example
          Request Example SOAP V2 (List of All Shipments)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -135,7 +135,7 @@ 
          Request Example SOAP V2 (Complex Filter)
          -
          +
          $client = new SoapClient('http://magentohost/api/v2_soap/?wsdl');
           
           // If some stuff requires API authentication,
          @@ -159,7 +159,7 @@ 
          Request Example SOAP V2 (WS-I Compliance Mode)
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -172,7 +172,7 @@ 
          Response Example SOAP V1
          -
          +
          array
             0 =>
               array
          @@ -190,4 +190,4 @@ 
          Response Examp
          - + diff --git a/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.removeTrack.html b/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.removeTrack.html index 8d15a6923c..d400c96a68 100644 --- a/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.removeTrack.html +++ b/guides/m1x/api/soap/sales/salesOrderShipment/sales_order_shipment.removeTrack.html @@ -78,7 +78,7 @@
          Request
          -
          +
          $client = new SoapClient('http://magentohost/api/soap/?wsdl');
           
           // If somestuff requires API authentication,
          @@ -97,7 +97,7 @@ 
          Request
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); // TODO : change url
           $sessionId = $proxy->login('apiUser', 'apiKey'); // TODO : change login and pwd if necessary
           
          @@ -112,7 +112,7 @@ 
          -
          +
          $proxy = new SoapClient('http://magentohost/api/v2_soap/?wsdl'); 
           
           $sessionId = $proxy->login((object)array('username' => 'apiUser', 'apiKey' => 'apiKey')); 
          @@ -123,4 +123,4 @@ 
          + @@ -18,9 +18,9 @@

          WS-I Compliance Mode

          WSDL file with disabled WS-I compliance mode:
          -

          +

          WSDL file with enabled WS-I compliance mode:
          -

          +

          \ No newline at end of file diff --git a/guides/m1x/ce18-ee113-home.html b/guides/m1x/ce18-ee113-home.html index d4cff319d3..89b56eadb0 100644 --- a/guides/m1x/ce18-ee113-home.html +++ b/guides/m1x/ce18-ee113-home.html @@ -15,8 +15,8 @@ -
          -header + +header {% include m1x/eol_message.html %}

          Welcome

          Welcome to the documentation home page for the Magento Enterprise Edition (EE) 1.13 and Community Edition (CE) 1.8 releases! Let's start out by telling you a little bit about them.

          @@ -62,10 +62,9 @@

          Welcome

        • Improved cache adapter for single-host systems
        • Additional option of using Redis NoSQL for cache and session storage in multi-host deployments (recommended for new deployments)
        • -
        • EE customers also get detailed performance and tuning guidelines geared toward enterprise installations
        • +
        • EE customers also get detailed performance and tuning guidelines geared toward enterprise installations
          -
        • Sales, Value Added, and Fixed Product Tax calculations (Magento CE and EE):
          • Major improvements in the way sales tax is calculated.
          diff --git a/guides/m1x/ce18-ee113/EE113-benchmark.html b/guides/m1x/ce18-ee113/EE113-benchmark.html index d36c1af9cb..1744f9016c 100644 --- a/guides/m1x/ce18-ee113/EE113-benchmark.html +++ b/guides/m1x/ce18-ee113/EE113-benchmark.html @@ -13,9 +13,9 @@ - -header + +header {% include m1x/eol_message.html %}

          Magento Enterprise Edition (EE) 1.13 Benchmarking Guide

          @@ -97,7 +97,7 @@

          Scenarios

          @@ -133,7 +133,7 @@

          Catalog

          @@ -150,7 +150,7 @@

          Target Merchant @@ -194,7 +194,7 @@

          Full Re-indexing @@ -206,7 +206,7 @@

          Registered @@ -264,7 +264,7 @@

          Page Views and @@ -278,7 +278,7 @@

          - - - -

          Magento Community Edition (CE) Release Notes (1.8 and later)

          - - -
          noteNote: We'd like to make you aware that a security patch for older versions of Magento Community Edition has been posted (in the Magento Community Edition Patches section). This patch resolves a remote code execution vulnerability that enables an attacker with Magento administrator privileges to delete files and directories on a Magento installation. This vulnerability was discovered through our quarterly penetration testing process and has not been reported by merchants.

          -This issue was fixed in Magento Community Edition 1.8.0.0; no patch is necessary for versions 1.8.0.0 and later. Patches are available for Magento Community Edition 1.4.0.0 through 1.7.0.2. We encourage all affected merchants to apply the patch in their next regularly scheduled maintenance cycle.

          -Magento takes security very seriously and will continue to focus on identifying potential issues and hardening our defenses.
          - - - -

          Patches for Multiple Magento CE Versions

          -

          Magento has the following patches available for multiple Magento CE 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 CE 1.8.x as well.
          - -

          General Magento Connect Patches

          -

          Patch name: SUPEE-3941

          -
          • 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: SUPEE-3762. 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.

          - - + + + +

          Magento Community Edition (CE) Release Notes (1.8 and later)

          + + +
          noteNote: We'd like to make you aware that a security patch for older versions of Magento Community Edition has been posted (in + the Magento Community Edition Patches section). This patch resolves a remote code execution vulnerability that + enables an attacker with Magento administrator privileges to delete files and directories on a Magento + installation. This vulnerability was discovered through our quarterly penetration testing process and has not been + reported by merchants.

          + This issue was fixed in Magento Community Edition 1.8.0.0; no patch is necessary for versions 1.8.0.0 and later. + Patches are available for Magento Community Edition 1.4.0.0 through 1.7.0.2. We encourage all affected merchants + to apply the patch in their next regularly scheduled maintenance cycle.

          + Magento takes security very seriously and will continue to focus on identifying potential issues and hardening our + defenses.
          + +
          +

          Table of Contents

          +

          These Release Notes contain the following information:

          +
          + +

          Patches for Multiple Magento CE Versions

          +

          Magento has the following patches available for multiple Magento CE 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 CE 1.8.x as well.
          + +

          General Magento Connect Patches

          +

          Patch name: SUPEE-3941

          +
            +
          • + 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: SUPEE-3762. + 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.

          + + + -

          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 Magento CE versions 1.4.2.0–1.8.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.

          -
          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 CE versions 1.6.0.0–1.8.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 CE

          -

          This section discusses how to get patches referenced in these Release Notes.

          -

          To get patches for Magento CE:

          -
          1. Log in to www.magentocommerce.com/download.
          2. -
          3. In the left pane, click Downloads.
          4. -
          5. Scroll down to the Magento Community Edition Patches section.
          6. -
          7. Follow the prompts on your screen to download a patch for your version of CE.
          8. -
          9. Apply the patch as discussed in How to Apply and Revert Magento Patches.
          - -

          Magento Community Edition (CE) 1.8.1.0 Release Notes

          -

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

          - - -

          Highlights

          -

          Magento CE 1.8.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

          -

          CE 1.8.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

          -

          CE 1.8.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

          -

          CE 1.8.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.
          • -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 + 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 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.
          • -
          • Fixed the security settings for the frontend cookie to protect user sessions.
          • - -
          - -

          Issue After Upgrading to CE 1.8.1

          -

          There is a known Issue After Upgrading to CE 1.8.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. -
          3. 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
          4. -
          5. 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:

          -
            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.
          • +
          • + Fixed the security + settings for the frontend cookie to protect user sessions. + +
          • + +
          + +

          Issue After Upgrading to CE 1.8.1

          +

          + There is a known Issue After Upgrading to CE 1.8.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. +
          3. 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
            +
          4. +
          5. 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.
          6. +
          + +

          Changes in This Release

          +

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

          +
            + -
          • 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 CE 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. -
            3. Click System > Configuration > SALES > Shipping Methods.
            4. -
            5. In the right pane, expand DHL (Deprecated).
            6. -
            7. Change the value of the Gateway URL field to the following:
              -
              http://xmlapi.dhl-usa.com/ApiLanding.asp
            8. -
            9. In the upper right corner, click Save Config.
            -
          • - -
          - -

          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:

          -
          • 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 CE 1.8.1.0

          -

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

          - - -

          Shopping Cart and Checkout Fixes

          -
          • -
          • 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.
          • -
          • -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.
          • -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 CE 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. +
            3. Click System > Configuration > SALES > Shipping + Methods.
            4. +
            5. In the right pane, expand DHL (Deprecated).
            6. +
            7. Change the value of the Gateway URL field to the following:
              +
              http://xmlapi.dhl-usa.com/ApiLanding.asp
              +
            8. +
            9. In the upper right corner, click Save Config.
            10. +
            +
          • + +
          + +

          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:

          +
            +
          • + 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 CE 1.8.1.0

          +

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

          + + +

          Shopping Cart and Checkout Fixes

          +
            +
          • + +
          • +
          • + 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.
          • +
          • + + 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.

            -
          - -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. +
          • +
          + + - + - -

          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'
          • -
          • -
          • Widgets display properly on the CMS.
          • -
          • -
          • 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.
          • -
          • -
          • Back-in-stock e-mails contain the correct content.
          • -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' +
          • + +
          • +
          • + Widgets display + properly on the CMS.
          • +
          • + +
          • +
          • + 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.
          • +
          • + +
          • +
          • + 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.
          • -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 Community Edition (CE) 1.8.0.0 Release Notes

          -

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

          - - -

          Highlights

          -
          • Major overhaul of tax calculation formulas, correction of rounding errors, and additional assistance with configuration.
          • -
          • Optimized cache adapters for single-server systems
          • -
          • Upgraded Redis cache adapters for multi-server systems.
            -To set up and use Redis with Magento, see Using Redis with Magento Community Edition (CE) and Enterprise Edition (EE).
          • -
          • Eliminated many types of database deadlocks.
          • -
          - -

          Security Enhancements

          -
          • Errors are not displayed in a new Magento installation.
          • -
          • Fixed a session fixation vulnerability in the new user registration process. Attackers can no longer abuse this flaw to take over new user accounts during registration.
          • -
          • 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.)
          • -
          • Prevent attacks that use OAuth to leak sensitive information to an attacker that knows the consumer key and user token.
          • -
          • Resolved an issue that enabled attackers to gain access to billing information.
            -We thank Darryl Adia (from Ampersand Commerce) for contributing to this fix.
          • -
          • Resolved issues with the security of OAuth tokens and keys.
          • -
          • A remote code execution vulnerability was fixed.
            -We thank Bastian Ike for contributing to this fix. -
          • 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.
          • -
          • The cryptographic methods used to store passwords were improved to enhance security.
          • -
          - -

          United States Postal Service (USPS) Update

          -

          The USPS changed the names of their Priority and Express shipping options in their API in July 2013. To enable you to continue utilizing USPS Priority and Express mail methods, CE 1.8 includes a patch that addresses the issue.

          -
          importantImportant: The USPS API patch has an impact on upgrading to CE 1.8 from earlier versions. If you're doing a new CE 1.8 installation, however, you don't need to do anything.
          - -

          Following are details about the upgrade impact:

          -
          • Print all USPS shipping labels before upgrading; after upgrading, you will not be able to print them.
          • -
          • Any shopping cart price rules that use the USPS shipping method that created before you upgrade must be re created after you upgrade. Pre-existing USPS shipping methods do not work with shopping cart price rules after the upgrade.
          - -

          Performance Improvements

          -
          • Limited the way Magento performs large database lookups. -
          • Checkout performance improvements achieved by: -
            • 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.
          • -
          - -

          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:

          -
          • 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.)
          • -
          • 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

          -
          • 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.
          • -
          • 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.
          • -
          • 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.
          • -
          • 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.
          • -
          • 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.
          • -
          • When a customer selects a product on your web store, the assigned category is selected in the navigation menu.
          • -
          - -

          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.
          • -
          • 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.
          • -
          - -

          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: - -
          • -
          • 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 fix that affects UK merchants only: 3-D Secure for UK merchants implementing Direct Payment works properly. -
          • -
          • 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

          -
          • Issues related to the DHL shipping method for picking up and pricing orders on holidays have been resolved as follows: -
            • If the current date is a weekend, Magento chooses next Monday as the pick-up date.
            • -
            • If the current date is a holiday, Magento requests from DHL information about the next five consecutive days to find a workday on which to pick up the order.
            • -
            • If there is no workday in the five consecutive days following a holiday, the DHL shipping method is unavailable.
            -
          • -
          • The .htaccess.sample provided with Magento now includes php_value memory_limit 512M to be consistent with the Magento system requirements.
          • -
          • You can now install or upgrade to CE 1.8.0.0 if your Magento database had a table prefix (for example, all tables start with mage_ because you specified a tables prefix during installation).
          • -
          • MySQL database deadlock issues were resolved.
          • -
          • CE 1.8 is now World Wide Web Consortium (W3C) compliant.
          • -
          • 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.
          • -
          • You can now save a category with the option Available Product Listing Sort By: Best value or Price enabled.
          • -
          - -

          Thanks

          -

          Magento acknowledges and thanks everyone in the Magento Community who contributed to this release, including Colin Mollenhour for Redis modules.

          -

          -

          \ No newline at end of file +

        • + 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 Community Edition (CE) 1.8.0.0 Release Notes

          +

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

          + + +

          Highlights

          +
            +
          • Major overhaul of tax calculation formulas, correction of rounding errors, and additional assistance with + configuration.
          • +
          • Optimized cache adapters for single-server systems
          • +
          • + Upgraded Redis cache + adapters for multi-server systems.
            + To set up and use Redis with Magento, see Using Redis with Magento Community Edition (CE) and Enterprise Edition (EE).
          • +
          • Eliminated many types of database deadlocks.
          • +
          + +

          Security Enhancements

          +
            +
          • + Errors are not + displayed in a new Magento installation.
          • +
          • + Fixed a session + fixation vulnerability in the new user registration process. Attackers can no longer abuse this flaw to take over + new user accounts during registration.
          • +
          • + 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.)
          • +
          • + Prevent attacks that + use OAuth to leak sensitive information to an attacker that knows the consumer key and user token.
          • +
          • + Resolved an issue + that enabled attackers to gain access to billing information.
            + We thank Darryl Adia (from Ampersand Commerce) for contributing to this fix.
          • +
          • + Resolved + issues with the security of OAuth tokens and keys.
          • +
          • A remote code execution vulnerability was fixed.
            + We thank Bastian Ike for contributing to this fix. + +
          • 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.
          • +
          • The cryptographic methods used to store passwords were improved to enhance security.
          • +
          + +

          United States Postal Service (USPS) Update

          +

          The USPS changed the names of their Priority and Express shipping options in their API in July 2013. To enable you + to continue utilizing USPS Priority and Express mail methods, CE 1.8 includes a patch that addresses the + issue.

          +
          importantImportant: The USPS API patch has an impact on upgrading to CE 1.8 + from earlier versions. If you're doing a new CE 1.8 installation, however, you don't need to do anything. +
          + +

          Following are details about the upgrade impact:

          +
            +
          • Print all USPS shipping labels before upgrading; after upgrading, you will not be able to print them.
          • +
          • Any shopping cart price rules that use the USPS shipping method that created before you upgrade must be re + created after you upgrade. Pre-existing USPS shipping methods do not work with shopping cart price rules after the + upgrade.
          • +
          + +

          Performance Improvements

          +
            +
          • Limited the way Magento performs large database lookups. + +
          • Checkout performance improvements achieved by: +
              +
            • 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. + +
          • +
          + +

          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:

          +
            +
          • 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.)
          • +
          • 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

          +
            +
          • 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. + +
          • +
          • 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. + +
          • +
          • 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. + +
          • +
          • 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. + +
          • +
          • 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. + +
          • +
          • + When a customer selects a product on your web store, the assigned category is selected in the + navigation menu. + +
          • +
          + +

          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. + +
          • +
          • 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. + +
          • +
          + +

          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 fix that affects UK merchants only: 3-D Secure for UK merchants implementing Direct Payment + works 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

            +
              +
            • + Issues related to + the DHL shipping method for picking up and pricing orders on holidays have been resolved as follows: +
                +
              • If the current date is a weekend, Magento chooses next Monday as the pick-up date.
              • +
              • If the current date is a holiday, Magento requests from DHL information about the next five consecutive days + to find a workday on which to pick up the order.
              • +
              • If there is no workday in the five consecutive days following a holiday, the DHL shipping method is + unavailable.
              • +
              +
            • +
            • + The + .htaccess.sample provided with Magento now includes php_value memory_limit 512M to be + consistent with the Magento system + requirements.
            • +
            • + You can now install + or upgrade to CE 1.8.0.0 if your Magento database had a table prefix (for example, all tables start with + mage_ because you specified a tables prefix during installation).
            • +
            • MySQL database deadlock issues were resolved. + +
            • +
            • CE 1.8 is now World Wide Web Consortium (W3C) + compliant. + +
            • +
            • 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. + +
            • +
            • You can now save a category with the option Available Product Listing Sort By: Best value or + Price enabled. + +
            • +
            + +

            Thanks

            +

            Magento acknowledges and thanks everyone in the Magento Community who contributed to this release, including Colin + Mollenhour for Redis modules.

            +

            +
            + + \ No newline at end of file diff --git a/guides/m1x/ce18-ee113/ee1.13_release-notes.html b/guides/m1x/ce18-ee113/ee1.13_release-notes.html index 73921767b3..0f8fe0e922 100644 --- a/guides/m1x/ce18-ee113/ee1.13_release-notes.html +++ b/guides/m1x/ce18-ee113/ee1.13_release-notes.html @@ -1,15 +1,16 @@ --- --- - + + - + - - - - - Magento Enterprise Edition (EE) Release Notes (1.13 and later) + + + + + Magento Enterprise Edition (EE) Release Notes (1.13 and later) @@ -17,431 +18,826 @@ - - -header -{% include m1x/eol_message.html %} - - - -

            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.

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

            -
            • 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. -
            3. Click System > Configuration.
            4. -
            5. In the left navigation bar, from the ADVANCED group, click Index Management.
            6. -
            7. Expand Indexing Options.
            8. -
            9. From each list, click Update when scheduled.
            10. -
            11. 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.

            -
            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 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. -
            3. In the left pane, click Downloads.
            4. -
            5. In the right pane, click Magento Enterprise Edition.
            6. -
            7. Follow the prompts on your screen to download a patch for your version of EE.
            8. -
            9. 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
            • - + +

              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

              +
                +
              • + 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. +
              3. Click System > Configuration.
              4. +
              5. In the left navigation bar, from the ADVANCED group, click Index Management.
              6. +
              7. Expand Indexing Options.
              8. +
              9. From each list, click Update when scheduled.
              10. +
              11. Click Save Config in the upper right corner of the page.
              12. +
              + + + + + + +

              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.

              +
              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 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. +
              3. In the left pane, click Downloads.
              4. +
              5. In the right pane, click Magento Enterprise Edition.
              6. +
              7. Follow the prompts on your screen to download a patch for your version of EE.
              8. +
              9. Apply the patch as discussed in How + to Apply and Revert Magento Patches.
              10. +
              + + +

              Magento EE 1.13.1.0 Release Notes

              +

              +

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

              + - -

              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.
              • -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. -
              3. 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
              4. -
              5. 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. -
                3. Click System > Configuration > SALES > Shipping Methods.
                4. -
                5. In the right pane, expand DHL (Deprecated).
                6. -
                7. Change the value of the Gateway URL field to the following:
                  -
                  http://xmlapi.dhl-usa.com/ApiLanding.asp
                  .
                8. -
                9. In the upper right corner, click Save Config.
                -
              • - -
              - -

              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:

              -
              • 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
            • -
            • Import and Export Fixes
            • -
            • Shipping Fixes
            • -
            • Payment Fixes
            • -
            • Other Fixes
            • -
            - -

            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.
            • -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. +
            3. 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
              +
            4. +
            5. 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.
            6. +
            + +

            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. +
              3. Click System > Configuration > SALES > Shipping + Methods.
              4. +
              5. In the right pane, expand DHL (Deprecated).
              6. +
              7. Change the value of the Gateway URL field to the following:
                +
                http://xmlapi.dhl-usa.com/ApiLanding.asp
                .
              8. +
              9. In the upper right corner, click Save Config.
              10. +
              +
            • + +
            + +

            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:

            +
              +
            • + 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
          • +
          • Import and Export Fixes
          • +
          • Shipping Fixes
          • +
          • Payment Fixes
          • +
          • Other Fixes
          • + +

            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.
            • -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.
            • -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:

            - - -

            Important:

            - -

            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

            -

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

            - -

            -

            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.

            -
            -

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

          + + +

          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

          +

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

          + + +

          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:

          -
          - - - - - - - - - - - - - - - - - -
          Entity typeUniqueness rule
          Product, including custom URL redirectsAll product URL keys must be globally unique.
          Category

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

          - website
          -    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.

          CMSCMS 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 examplesReason allowed
          http://example.com/mens/shoes
          - http://example.com/womens/shoes
          Different category hierarchies.
          http://example1.com/shoes
          - http://example2.com/shoes
          Different domains.
          http://example.com/shoes (store view 1)
          - http://example.com/shoes (store view 2)
          Different store views.
          -

          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.

          - - - - - - - - - - - - - - - - - - - - - - - - - - - -
          Entity typeEntity nameURL keySample URL
          Categoryshoesshoeshttp://www.example.com/shoes.html
          Productshoesshoeshttp://www.example.com/shoes.html
          Custom URL redirectsshoesshoeshttp://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 settingResult
          Default setting: -
          1. Redirect
          2. -
          3. Category
          4. -
          5. Product
          Custom URL redirect
          1. Category
          2. -
          3. Redirect
          4. -
          5. Product
          Shoes category
          -

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

          -
          noteNote: CMS URL keys are always prioritized last.
          - - -

          For More Information about SEO

          -

          For more information about SEO, see:

          - - -

          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.

          -
          noteNote: 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.
              -
              noteNote: 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.
              • -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.

                +
                noteNote: 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.
                    +
                    noteNote: 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

                  -
                  • 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.)
                  -
                  noteNote: 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:

                  - - - -

                  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

                -

                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

                -
                • 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: - -
                • -
                • 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.
                  -
                  noteNote: 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.

              +For example, if you already have a category named Apparel > Women's > Shoes and you add another category named Apparel > Men's > Shoes, Magento creates a unique URL key for the second category. The URL key is the category name separated from its ID by a dash character (for example, shoes-42). https://jira.corp.x.com/browse/MPERF-1744
            • --> +
            +
          • +
          • 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

          +
            +
          • 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.)
          • +
          +
          noteNote: 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:

          + + + +

          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

        +

        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

        +
          +
        • 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.
            +
            noteNote: 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.

          - \ No newline at end of file + + diff --git a/guides/m1x/ce18-ee113/ht_magento-ce-sample.data.html b/guides/m1x/ce18-ee113/ht_magento-ce-sample.data.html index ebcbc366c4..c6e67a7bb5 100644 --- a/guides/m1x/ce18-ee113/ht_magento-ce-sample.data.html +++ b/guides/m1x/ce18-ee113/ht_magento-ce-sample.data.html @@ -11,7 +11,7 @@

          Overview

        • Magento Community Edition (CE) 1.9.1.0–1.9.2.0
        -
        importantImportant: Magento CE 1.9 and later use different sample data from the other versions in +
        importantImportant: Magento CE 1.9 and later use different sample data from the other versions in the preceding list. Make sure you use the correct version of sample data with your version of Magento CE.
        @@ -42,4 +42,4 @@

        Getting the Sample Data

      Installing the Sample Data

      -

      Detailed instructions for installing sample data for Magento CE 1.6–1.9 can be found on the Magento Knowledge Base.

      +

      Detailed instructions for installing sample data for Magento CE 1.6–1.9 can be found on the Magento Knowledge Base.

      diff --git a/guides/m1x/ce18-ee113/using_redis.html b/guides/m1x/ce18-ee113/using_redis.html index 8714210d9c..eaa3cd07b3 100644 --- a/guides/m1x/ce18-ee113/using_redis.html +++ b/guides/m1x/ce18-ee113/using_redis.html @@ -14,8 +14,8 @@ - -header + +header {% include m1x/eol_message.html %} diff --git a/guides/m1x/ce19-ee114-home.html b/guides/m1x/ce19-ee114-home.html index 1241c85fc7..ac045b6a96 100644 --- a/guides/m1x/ce19-ee114-home.html +++ b/guides/m1x/ce19-ee114-home.html @@ -3,10 +3,11 @@ + - + @@ -15,49 +16,76 @@ - -header -{% include m1x/eol_message.html %} - -
      -

      Magento Community Edition (CE) 1.9 and Enterprise Edition (EE) 1.14 Documentation Home

      - -

      Table of Contents

      -
      + \ No newline at end of file diff --git a/guides/m1x/ce19-ee114/RWD_dev-guide.html b/guides/m1x/ce19-ee114/RWD_dev-guide.html index 23a07b5de9..bf8ecd2afb 100644 --- a/guides/m1x/ce19-ee114/RWD_dev-guide.html +++ b/guides/m1x/ce19-ee114/RWD_dev-guide.html @@ -16,21 +16,21 @@ - -header + +header {% include m1x/eol_message.html %} - +

      Magento Community Edition (CE) 1.9 and Magento Enterprise Edition (EE) 1.14 Responsive Web Design Developer's Guide

      -

      by Erik Hansen

      -

      Edit this page on +

      by Erik Hansen

      +

      Edit this page on GitHub

      @@ -140,7 +140,7 @@

      Exceptions to Responsive Web Design

    • Multiple wishlists (EE only)
    • Place order by SKU (EE only)
    -
    notenoteNote: Magento still supports other non-responsive themes as well. You don't need to use this guide to customize those themes. For more information, see the Designer's Guide to Magento. @@ -259,10 +259,10 @@

    Disabling the Magento Cache

  • Click Submit.
    The following figure shows an example.
    -
  • +
  • Click Submit.

    The following figures shows all cache types disabled.
    - +

  • @@ -284,7 +284,7 @@

    Step 1: Creating a Directory Structure for Your Respons directories.

    The rwd/default theme falls back directly to the base/default theme, so themes in the default package will never be included as a part of the fallback chain.

    -
    notenoteNote: Magento EE only. The enterprise/default theme is completely replaced by rwd/enterprise and therefore, enterprise/default is not included as a part of the fallback chain.
    @@ -336,7 +336,7 @@

    Step 1: Creating a Directory Structure for Your Respons

    -
    importantImportant: It's very important you have a theme.xml in the app/design/frontend/custompackage/customtheme/etc directory with exactly the contents shown. Failure to configure theme.xml correctly prevents Magento from loading your theme.
    @@ -356,7 +356,7 @@

    Step 2: Copying Files For Your Theme

    Structure.

    The following figure shows how your custom theme directory structure looks after copying these files and directories.

    - +

    Step 3: Configuring a Compass Watcher

    You can configure Compass to watch your skin directories for changes to CSS and JavaScript and to compile them @@ -427,7 +427,7 @@

    Step 4: Configuring Magento to Load Your Theme

  • In the right pane, expand Themes.
  • In the Default field, enter customtheme
    The following figure shows an example.
    - +
  • In the top right corner of the page, click Save Config.
    If an error displays when you attempt to save the configuration, see Troubleshooting @@ -451,7 +451,7 @@

    Step 5: Verifying Your Custom Theme

    begin building your new theme.
  • -
    notenoteNote: If your theme fails to load properly, see the next section.
    @@ -513,7 +513,7 @@
    Wrong formatting in the web store

    Directory and File Reference

    The following figure shows the directory structure in a properly configured system, as well as the location of theme.xml, the custom theme configuration file.

    - +

    Responsive Theme Reference

    This section discusses information you need to customize the responsive theme you started in Copying @@ -534,7 +534,7 @@

    Basic Recommendations for Development

  • Edit [your Magento install dir]/skin/frontend/custompackage/customtheme/scss/config.rb to change environment = :production to environment = :development.
    For more information about this setting, see
    Compass + href="http://compass-style.org/help/documentation/configuration-reference/" target="_blank">Compass Configuration Reference.
  • Disable the Magento cache as discussed in Disabling Magento's Cache.
  • @@ -547,11 +547,9 @@

    Understanding the Sass Structure

    When Compass compiles the Sass partials, the output is a set of CSS files that are loaded by the browser: styles-ie8.css is for Internet Explorer 8 and earlier, and styles.css is for all other browsers.

    Following is the directory structure of the skin/frontend/custompackage/customtheme directory.

    -
    notenoteNote: This structure does not include the sample data assets that you will remove later in this guide.
    - -

     ├── css
     │   ├── scaffold-forms.css
    @@ -633,7 +631,6 @@ 

    Understanding the Sass Structure

    └── vendor └── _normalize.scss
    -

    This is an explanation of the files in the preceding list:

      @@ -799,9 +796,9 @@

      Working With Sprites

      The responsive theme uses two sprites: one for general icons and the other for social icons.

      Both sprite images output at 1x and 2x resolutions (for high-resolution screens). Because sprite files are very difficult to edit without the source files, you should use these Photoshop files to change these sprites: RWD_icon_sprite.psd and RWD_social_icons.psd -

      Compass provides support for generating sprites from individual image files, but it was not used to generate + href="{{ site.baseurl }}/guides/m1x/images/RWD_icon_sprite.psd">RWD_icon_sprite.psd and RWD_social_icons.psd +

      Compass provides support for generating sprites from individual image files, but it was not used to generate sprites for the responsive theme. However, you might want to take advantage of that feature for your custom theme. Using this method requires knowledge of Compass.

      @@ -902,10 +899,9 @@

      Advanced Topics

      Getting Your Theme Ready for Production

      To prepare your responsive theme for production, you should update config.rb in your theme directory to - use these values: + use these values:

      output_style = :compressed
       environment = :production
      -

      After you do this, you should recompile all of your Sass files—you can do this on the command line by running these commands inside your theme directory: compass clean and then compass compile. @@ -994,7 +990,7 @@

      High-Definition Images

      href="https://speakerdeck.com/brendanfalkowski/responsive-ecommerce-part-two#114" target="_blank">slides starting at 114 of Brendan Falkowski's Imagine 2013 talk for implementation suggestions. For a 2x solution, PictureFill (or similar polyfill) could be used, although it would need to be integrated with ElevateZoom.

      -
      notenoteNote: Category banners and product detail pages use a 1.5x image solution.
      diff --git a/guides/m1x/ce19-ee114/RWD_responsive_emails.html b/guides/m1x/ce19-ee114/RWD_responsive_emails.html index 1f339845b7..0eb4f438a8 100644 --- a/guides/m1x/ce19-ee114/RWD_responsive_emails.html +++ b/guides/m1x/ce19-ee114/RWD_responsive_emails.html @@ -10,7 +10,7 @@ - + @@ -19,334 +19,449 @@ - - -header -{% include m1x/eol_message.html %} - -
      - -

      Responsive Email Developer's Guide for Magento EE 1.14.1 and Magento CE 1.9.1

      -

      by Erik Hansen

      -

      Edit this page on GitHub

      - -

      Table of Contents

      + + + header + {% include m1x/eol_message.html %} + +
      + +

      Responsive Email Developer's Guide for Magento EE 1.14.1 and Magento CE 1.9.1

      +

      by Erik Hansen

      +

      Edit this page on + GitHub

      + + + +

      Introduction

      +

      We improved transactional emails and newsletter templates in Magento Enterprise 1.14.1 and Magento Community + 1.9.1 in a number of ways, including:

      -
      - -

      Introduction

      -

      We improved transactional emails and newsletter templates in Magento Enterprise 1.14.1 and Magento Community 1.9.1 in a number of ways, including:

      -
        -
      • Emails are now optimized for any screen size, including mobile and tablet devices
      • -
      • Header and footer content for transactional emails are now contained in their own files
      • -
      • CSS is now contained in separate CSS files
      • -
      • We provide you with a responsive sample newsletter template
      • -
      -
      noteNote: This article focuses on responsive emails but the same techniques can be used for newsletter templates as well. For more information about newsletter templates, see Using Updated Newsletter Templates.
      - - -

      Using cron to Send Emails

      -

      Starting in Magento EE 1.14.1 and CE 1.9.1, your Magento cron job sends all emails, including transactional emails. You must configure cron for emails to work.

      -

      For more information, see Setting Up Cron Jobs.

      - -

      Supported Email Clients and Devices

      -

      We tested responsive emails using a combination of real devices and Litmus. Due to the greatly varied level of support among email clients for modern web technologies, not all email clients rendered the emails perfectly. However, all of the following clients should render the emails in a manner that allows them to be easily read without obvious issues. Refer to the following sections for more information.

      - -

      Supported Desktop Clients

      - - - - - - - - - - - - - - - - - - - - -
      Operating systemClients supported
      OS X 10.8Apple Mail 6
      OS X 10.7Outlook 2011
      -
        -
      • Windows 8
      • -
      • Windows 7
      • -
      -
      -
        -
      • Outlook 2013
      • -
      • Outlook 2010
      • -
      • Outlook 2007
      • -
      • Outlook 2003
      • -
      -
      - -

      Supported Mobile Clients

      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      Operating systemClients supported
      Android 4.2 ("Jelly Bean")Native email app
      Android 2.3 ("Gingerbread")Native email app
      Gmail App (Android 4.2)Native email app
      Blackberry 5 OSNative email app
      iOS 8 -
        -
      • iPhone 6
      • -
      • iPhone 6 Plus
      • -
      -
      iOS 7 -
        -
      • iPad (Retina)
      • -
      • iPad Mini
      • -
      • iPhone 5s
      • -
      -
      iOS 6 - Mail on these devices: -
        -
      • iPhone 5
      • -
      • iPhone 4s
      • -
      -
      - -

      Supported Web Clients

      - - - - - - - - - - - - - - - - - - - - - - - - - -
      Email applicationBrowsers supported*
      AOL Mail
      • Chrome
      • -
      • Internet Explorer
      • -
      • Firefox
      Gmail
      • Chrome
      • -
      • Internet Explorer
      • -
      • Firefox
      Yahoo! Mail
      • Chrome
      • -
      • Internet Explorer
      • -
      • Firefox
      Outlook.com
      • Chrome
      • -
      • Internet Explorer
      -

      *The latest version of each browser was used for testing.

      - -

      Important Information about Upgrading

      -

      This section applies to anyone who used transactional emails in a version earlier than EE 1.14.1 or CE 1.9.1.

      -

      After upgrading from an earlier Magento version, you should preview your transactional emails, looking for changes in the logo, fonts, and styles. Because of changes introduced in this release, you might notice some differences.

      -

      Also, in CE 1.9.1 and EE 1.14.1 for the first time, you must specify a height and width for your logo image; the dimensions must be set to the area in which the logo displays. For more information, see Using a High-Resolution Logo.

      - -

      Customizing the Header or Footer in Transactional Emails

      -

      In earlier Magento CE and EE versions, each transactional email template contained a copy of the HTML for the header and footer. To make it easier to customize transactional emails, the header and footer HTML is now centralized in the following template files:

      -
        -
      • [your Magento install dir]/app/locale/en_US/template/email/html/header.html
      • -
      • [your Magento install dir]/app/locale/en_US/template/email/html/footer.html
      • -
      -

      - The header and footer template files get included in the transactional emails using a new template directive. For an example of how this works, open app/locale/en_US/template/email/account_new.html. It contains two directives that include header.html and footer.html: - -

      {{template config_path="design/email/header"}}
      -
      {{template config_path="design/email/footer"}}
      - You can customize the header and footer as discussed in the following sections:

      - - -

      Customizing Header and Footer Templates Using Files

      -

      If you can access the Magento server file system, you can customize the header and footer by editing the following files:

      -
        -
      • [your Magento install dir]/app/locale/en_US/template/email/html/header.html
      • -
      • [your Magento install dir]/app/locale/en_US/template/email/html/footer.html
      • -
      -
      noteNote: To make changes to the templates at the website or store view configuration scopes, see the next section.
      - - -

      Customizing Header and Footer Templates Using the Magento Admin Panel

      -

      You must use the Magento Admin Panel to customize header and footer templates if any of the following are true:

      -
      • You cannot access the Magento server file system
      • -
      • To customize the templates for a unique website, store, or store view
      -

      The example discussed in the following sections shows how to customize the header template. You can use the same procedure to customize the footer as well.

      -

      Using custom templates is a two-step process: first, define the template, and second, specify the website or store view on which it's used. See one of the following sections for more information:

      - - -

      Customizing the Template in the Admin Panel

      -
        -
      1. Log in to the Magento Admin Panel as an administrator.
      2. -
      3. Click System > Transactional Emails.
      4. -
      5. On the Transactional Emails page, click Add New Template.
      6. -
      7. From the Template list, click Email - Header.
      8. -
      9. From the Locale list, click the template's locale.
      10. -
      11. Click Load Template.
      12. -
      13. Enter the following information: - - +
        noteNote: This article focuses on responsive emails but the + same techniques can be used for newsletter templates as well. For more information about newsletter + templates, see Using Updated Newsletter Templates.
        + + +

        Using cron to Send Emails

        +

        Starting in Magento EE 1.14.1 and CE 1.9.1, your Magento cron job sends all emails, including + transactional emails. You must configure cron for emails to work.

        +

        For more information, see Setting Up Cron Jobs.

        + +

        Supported Email Clients and Devices

        +

        We tested responsive emails using a combination of real devices and Litmus. Due to the greatly varied level of support among email clients for modern + web technologies, not all email clients rendered the emails perfectly. However, all of the following clients + should render the emails in a manner that allows them to be easily read without obvious issues. Refer to the + following sections for more information.

        + +

        Supported Desktop Clients

        + +
        + + + + + + + - - + + - - + + - - + + + +
        Operating systemClients supported
        ItemDescriptionOS X 10.8Apple Mail 6
        Template Name fieldEnter a name for the new template, such as My HeaderOS X 10.7Outlook 2011
        Template Subject fieldIgnore; this field isn't used. +
          +
        • Windows 8
        • +
        • Windows 7
        • +
        +
        +
          +
        • Outlook 2013
        • +
        • Outlook 2010
        • +
        • Outlook 2007
        • +
        • Outlook 2003
        • +
        + +

        Supported Mobile Clients

        + + + + - - + + - - + + - - + + -
        Insert Variable ButtonClick to see a list of variables to insert. For more information about variables, see the Magento User Guide.Operating systemClients supported
        Template Content fieldEnter the contents of your email template.Android 4.2 ("Jelly Bean")Native email app
        Template Styles fieldIgnore; this field is not supported when customizing the header and footer templates.Android 2.3 ("Gingerbread")Native email app

        - The following figure shows an example:
        -
      14. -
      15. Click Preview Template to look at the HTML code in a separate browser tab page or window, or click Save Template to save it.
      - -

      Using the Template in a Website or Store View

      -

      This section discusses how to use the email template you just created in the global configuration, a website, or a store view.

      -

      To use this template:

      -
        -
      1. In the Admin Panel, click System > Configuration > GENERAL > Design.
      2. -
      3. From the Current Configuration Scope in the upper left corner, click the scope.
        - Initially, the template is associated with Default Config, which means it applies to all websites and store views. You can optionally associate it with a specific website or store view by selecting it from the list.
        - The following example shows how to associate a template with the Madison Island English store view.
        -
      4. -
      5. In the right pane, click Transactional Emails to expand it.
      6. -
      7. From the Email Header Template list, click the header template you created earlier.
        - The following figure shows an example:
        -
      8. -
      9. Click Save Config in the upper right corner of the page.
      -

      Now transactional emails use the header or footer template you created.

      - -

      Customizing CSS Styles for Emails

      -

      CSS styles for transactional emails are "inlined" on each HTML tag because many email clients require it.

      -

      CE 1.9.1 and EE 1.14.1 simplifies the way you customize email templates by locating all CSS styles in separate CSS files. When transactional emails are sent, the CSS styles are loaded from the separate CSS files and are "inlined" in the HTML before being sent.

      -

      Inlining is done using the Emogrifier library, which takes the HTML and CSS and adds all of the CSS styles to <style> attributes on the HTML tags.

      -

      The CSS for the emails is contained in the following Sass files:

      -
        -
      • [your Magento install dir]/skin/frontend/rwd/default/scss/email-inline.scss
      • -
      • [your Magento install dir]/skin/frontend/rwd/default/scss/email-non-inline.scss
      • -
      -

      As you might expect, these two files compile to skin/frontend/rwd/default/css/email-inline.css and skin/frontend/rwd/default/css/email-non-inline.css, respectively. If you're not familiar with how to work with Sass files, refer to the RWD theme documentation.

      - -

      Using Inline Styles to Customize Email CSS

      -

      - The email-inline.css file contains all of the styles that the Emogrifier class applies to the HTML before an email is sent. Magento applies only these styles to an email template if it contains this new directive: -

      {{inlinecss file="email-inline.css"}}
      - Notice that the templates in app/locale/en_US/template/email/ include this directive in each email template. The directive enables you to specify CSS that loads from the current storefront's theme and is inlined on that template.

      -

      The directive supports the standard Magento fallback hierarchy, which means that if the email-inline.css can't be found in the store's theme, Magento looks in each of the parent themes until a match is found. (A sample theme directory is skin/frontend/custompackage/customtheme/css/email-inline.css)

      -

      Refer to the Emogrifier README to see what CSS selectors are supported.

      -
      noteNote: The {{inlinecss file=""}} directive can be used a single time and cannot be used in templates that get included by other templates (for example, app/locale/en_US/template/email/html/header.html and app/locale/en_US/template/email/html/footer.html).
      - - -

      Using Non-Inline Styles to Customize Email CSS

      -

      There are certain CSS styles that can't be applied inline, such as media queries styles. These styles must be in a <style type="text/css"></style> tag.

      -

      To understand how non-inline styles are included, see line 7 in app/locale/en_US/template/email/html/header.html: -

      The variable {{var non_inline_styles}} loads CSS from several sources:

      -
        -
      • The contents of email-non-inline.css.
        - The file loads from the current storefront's theme and supports the same fallback structure as the email-inline.css file. For Magento to load additional files, go to System > Configuration > GENERAL > Design, click the Transactional Emails section and change the value of the Non-inline CSS File(s) field.
      • -
      • Each of the transactional emails has a comment at the top of the template in this format:
        -
        <!--@styles
        +                
        +                    Gmail App (Android 4.2)
        +                    Native email app
        +                
        +                
        +                    Blackberry 5 OS
        +                    Native email app
        +                
        +                
        +                    iOS 8
        +                    
        +                        
          +
        • iPhone 6
        • +
        • iPhone 6 Plus
        • +
        + + + + iOS 7 + +
          +
        • iPad (Retina)
        • +
        • iPad Mini
        • +
        • iPhone 5s
        • +
        + + + + iOS 6 + + Mail on these devices: +
          +
        • iPhone 5
        • +
        • iPhone 4s
        • +
        + + + + + +

        Supported Web Clients

        + + + + + + + + + + + + + + + + + + + + + + + + + + +
        Email applicationBrowsers supported*
        AOL Mail +
          +
        • Chrome
        • +
        • Internet Explorer
        • +
        • Firefox
        • +
        +
        Gmail +
          +
        • Chrome
        • +
        • Internet Explorer
        • +
        • Firefox
        • +
        +
        Yahoo! Mail +
          +
        • Chrome
        • +
        • Internet Explorer
        • +
        • Firefox
        • +
        +
        Outlook.com +
          +
        • Chrome
        • +
        • Internet Explorer
        • +
        +
        +

        *The latest version of each browser was used for testing.

        + +

        Important Information about Upgrading

        +

        This section applies to anyone who used transactional emails in a version earlier than EE 1.14.1 or CE 1.9.1. +

        +

        After upgrading from an earlier Magento version, you should preview your transactional emails, looking for + changes in the logo, fonts, and styles. Because of changes introduced in this release, you might notice some + differences.

        +

        Also, in CE 1.9.1 and EE 1.14.1 for the first time, you must specify a height and width for your logo image; + the dimensions must be set to the area in which the logo displays. For more information, see Using a High-Resolution Logo.

        + +

        Customizing the Header or Footer in Transactional Emails

        +

        In earlier Magento CE and EE versions, each transactional email template contained a copy of the HTML for the + header and footer. To make it easier to customize transactional emails, the header and footer HTML is now + centralized in the following template files:

        +
          +
        • [your Magento install dir]/app/locale/en_US/template/email/html/header.html
        • +
        • [your Magento install dir]/app/locale/en_US/template/email/html/footer.html
        • +
        +

        + The header and footer template files get included in the transactional emails using a new + template directive. For an example of how this works, open + app/locale/en_US/template/email/account_new.html. It contains two directives that include + header.html and footer.html:

        + +
        {{template config_path="design/email/header"}}
        +
        {{template config_path="design/email/footer"}}
        +

        You can customize the header and footer as discussed in the following sections:

        + + +

        Customizing Header and Footer Templates Using Files

        +

        If you can access the Magento server file system, you can customize the header and footer by editing the + following files:

        +
          +
        • [your Magento install dir]/app/locale/en_US/template/email/html/header.html
        • +
        • [your Magento install dir]/app/locale/en_US/template/email/html/footer.html
        • +
        +
        noteNote: To make changes to the templates at the website or + store view configuration scopes, see the next section.
        + + +

        Customizing Header and Footer Templates Using the Magento Admin Panel

        +

        You must use the Magento Admin Panel to customize header and footer templates if any of the following are + true:

        +
          +
        • You cannot access the Magento server file system
        • +
        • To customize the templates for a unique website, store, or store view
        • +
        +

        The example discussed in the following sections shows how to customize the header template. You can use the + same procedure to customize the footer as well.

        +

        Using custom templates is a two-step process: first, define the template, and second, specify the website or + store view on which it's used. See one of the following sections for more information:

        + + +

        Customizing the Template in the Admin Panel

        +
          +
        1. Log in to the Magento Admin Panel as an administrator.
        2. +
        3. Click System > Transactional Emails.
        4. +
        5. On the Transactional Emails page, click Add New Template.
        6. +
        7. From the Template list, click Email - Header.
        8. +
        9. From the Locale list, click the template's locale.
        10. +
        11. Click Load Template.
        12. +
        13. Enter the following information: + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          ItemDescription
          Template Name fieldEnter a name for the new template, such as My Header
          Template Subject fieldIgnore; this field isn't used.
          Insert Variable ButtonClick to see a list of variables to insert. For more information about variables, see + the Magento User Guide.
          Template Content fieldEnter the contents of your email template.
          Template Styles fieldIgnore; this field is not supported when customizing the header and footer templates. +

          + The following figure shows an example:
          +
        14. +
        15. Click Preview Template to look at the HTML code in a separate browser tab page or + window, or click Save Template to save it.
        16. +
        + +

        Using the Template in a Website or Store View

        +

        This section discusses how to use the email template you just created in the global configuration, a website, + or a store view.

        +

        To use this template:

        +
          +
        1. In the Admin Panel, click System > Configuration > GENERAL > + Design.
        2. +
        3. From the Current Configuration Scope in the upper left corner, click the scope.
          + Initially, the template is associated with Default Config, which means it applies to + all websites and store views. You can optionally associate it with a specific website or store view by + selecting it from the list.
          + The following example shows how to associate a template with the Madison Island English store view.
          +
        4. +
        5. In the right pane, click Transactional Emails to expand it.
        6. +
        7. From the Email Header Template list, click the header template you created earlier.
          + The following figure shows an example:
          +
        8. +
        9. Click Save Config in the upper right corner of the page.
        10. +
        +

        Now transactional emails use the header or footer template you created.

        + +

        Customizing CSS Styles for Emails

        +

        CSS styles for transactional emails are "inlined" on each HTML tag because many email clients require it.

        +

        CE 1.9.1 and EE 1.14.1 simplifies the way you customize email templates by locating all CSS styles in + separate CSS files. When transactional emails are sent, the CSS styles are loaded from the separate CSS + files and are "inlined" in the HTML before being sent.

        +

        Inlining is done using the Emogrifier + library, which takes the HTML and CSS and adds all of the CSS styles to <style> + attributes on the HTML tags.

        +

        The CSS for the emails is contained in the following Sass files:

        +
          +
        • [your Magento install dir]/skin/frontend/rwd/default/scss/email-inline.scss
        • +
        • [your Magento install dir]/skin/frontend/rwd/default/scss/email-non-inline.scss
        • +
        +

        As you might expect, these two files compile to skin/frontend/rwd/default/css/email-inline.css + and skin/frontend/rwd/default/css/email-non-inline.css, respectively. If you're not familiar + with how to work with Sass files, refer to the RWD theme documentation.

        + +

        Using Inline Styles to Customize Email CSS

        +

        + The email-inline.css file contains all of the styles that the Emogrifier class applies to the + HTML before an email is sent. Magento applies only these styles to an email template if it contains this new + directive:

        +
        {{inlinecss file="email-inline.css"}}
        +

        Notice that the templates in app/locale/en_US/template/email/ include this directive in each + email template. The directive enables you to specify CSS that loads from the current storefront's theme and + is inlined on that template.

        +

        The directive supports the standard Magento fallback hierarchy, which means that if the + email-inline.css can't be found in the store's theme, Magento looks in each of the parent + themes until a match is found. (A sample theme directory is + skin/frontend/custompackage/customtheme/css/email-inline.css)

        +

        Refer to the Emogrifier README + to see what CSS selectors are supported.

        +
        noteNote: The {{inlinecss file=""}} + directive can be used a single time and cannot be used in templates that get included by other templates + (for example, app/locale/en_US/template/email/html/header.html and + app/locale/en_US/template/email/html/footer.html).
        + + +

        Using Non-Inline Styles to Customize Email CSS

        +

        There are certain CSS styles that can't be applied inline, such as media queries styles. These styles must be + in a <style type="text/css"></style> tag.

        +

        To understand how non-inline styles are included, see line 7 in + app/locale/en_US/template/email/html/header.html: +

        The variable {{var non_inline_styles}} loads CSS from several sources:

        +
          +
        • The contents of email-non-inline.css.
          + The file loads from the current storefront's theme and supports the same fallback structure as the + email-inline.css file. For Magento to load additional files, go to + System > Configuration > GENERAL > + Design, click the Transactional Emails section and change the + value of the Non-inline CSS File(s) field.
        • +
        • Each of the transactional emails has a comment at the top of the template in this format:
          +
          <!--@styles
           @-->
          - If you modify a template and add CSS styles inside that comment, they are included in the non_inline_styles variable. -
        • -
        • If you customize transactional emails using the Magento Admin Panel, you can add CSS styles to the Template Styles field to include those styles in the non_inline_styles variable. For more information, see Customizing Header and Footer Templates Using the Magento Admin Panel.
        • -
        -

        After the CSS is loaded, it's wrapped in a <style type="text/css"></style> tag and is assigned to the non_inline_styles variable.

        -
        noteNote: When you are writing "non-inline" CSS, you must add the !important declaration after each property so the style has a high enough specificity to get applied. This is the best way to get your custom styles to override styles defined in the email-inline.css file.
        - - - -

        For the logo in your email to look optimal on high-resolution devices such as retina displays, you must use a logo that is at least two times larger than the area in which you want it to display. For example, let's say your email has a 200px × 100px area for the logo. The logo image must be at least 400px × 200px.

        -

        If you don't have access to a high-resolution version of your logo, you can upload a normal-resolution image. For example, if your logo image is 200px × 100px, specify 200 for the width and 100 for the height.

        - -

        Upgrade Considerations

        -

        This section applies to you if you upgraded to CE 1.9.1 or EE 1.14.1 from an earlier version.

        -

        In CE 1.19.1 and EE 1.14.1 for the first time, transactional email templates specify the width and height of the area in which the logo displays. Therefore, if you use transactional emails, you must configure your templates with a logo height and width as discussed in the next section.

        -

        For example, suppose the area in which the logo displays is 200px × 100px. Specify 200 for height and 100 for width even if the physical dimensions of the logo are larger.

        - -

        Adding a High-Resolution Logo

        -

        You can add your logo to transactional emails in either of the following ways:

        - - -

        Updating a High-Resolution Logo Using the File System

        -

        If you can access the Magento server file system, follow these steps:

        -
          -
        1. Locate the skin directory for your store (for example, skin/frontend/custompackage/customtheme/).
        2. -
        3. Save the logo image as logo_email.gif in the skin directory (for example, skin/frontend/custompackage/customtheme/images/logo_email.gif).
        4. -
        5. Open app/locale/en_US/template/email/html/header.html in a text editor.
        6. -
        7. Update the width and height attributes to reflect the area in which you want your logo to display (for example, 200px × 100px).
          - A snippet follows:
          -
          <img
          +                    If you modify a template and add CSS styles inside that comment, they are included in the
          +                    non_inline_styles variable.
          +                
        8. +
        9. If you customize transactional emails using the Magento Admin Panel, you can add CSS styles to the + Template Styles field to include those styles in the non_inline_styles + variable. For more information, see Customizing Header and Footer + Templates Using the Magento Admin Panel.
        10. +
      +

      After the CSS is loaded, it's wrapped in a <style + type="text/css"></style> tag and is assigned to the + non_inline_styles variable.

      +
      noteNote: When you are writing "non-inline" CSS, you must + add the !important declaration after each property so the style has a high enough + specificity to get applied. This is the best way to get your custom styles to override styles + defined in the email-inline.css file.
      + + + +

      For the logo in your email to look optimal on high-resolution devices such as retina displays, you must + use a logo that is at least two times larger than the area in which you want it to display. For example, + let's say your email has a 200px × 100px area for the logo. The logo image must be at least 400px + × 200px.

      +

      If you don't have access to a high-resolution version of your logo, you can upload a normal-resolution + image. For example, if your logo image is 200px × 100px, specify 200 for the width + and 100 for the height.

      + +

      Upgrade Considerations

      +

      This section applies to you if you upgraded to CE 1.9.1 or EE 1.14.1 from an earlier version.

      +

      In CE 1.19.1 and EE 1.14.1 for the first time, transactional email templates specify the width and height + of the area in which the logo displays. Therefore, if you use transactional emails, you must configure + your templates with a logo height and width as discussed in the next section.

      +

      For example, suppose the area in which the logo displays is 200px × 100px. Specify 200 + for height and 100 for width even if the physical dimensions of the logo are larger.

      + +

      Adding a High-Resolution Logo

      +

      You can add your logo to transactional emails in either of the following ways:

      + + +

      Updating a High-Resolution Logo Using the File System

      +

      If you can access the Magento server file system, follow these steps:

      +
        +
      1. Locate the skin directory for your store (for example, + skin/frontend/custompackage/customtheme/).
      2. +
      3. Save the logo image as logo_email.gif in the skin directory (for example, + skin/frontend/custompackage/customtheme/images/logo_email.gif).
      4. +
      5. Open app/locale/en_US/template/email/html/header.html in a text editor.
      6. +
      7. Update the width and height attributes to reflect the area in + which you want your logo to display (for example, 200px × 100px).
        + A snippet follows:
        +
        <img
             {{if logo_width}}
             width="{{var logo_width}}"
             {{else}}
        @@ -361,98 +476,132 @@ 

        Updating a High-Resolution Logo Using the File System< src="{{var logo_url}}" alt="{{var logo_alt}}" - border="0"/>

      8. -
      -
      noteNote: To use a file type other than GIF or if you need to upload unique logos for different websites, stores, or store views, see the next section.
      - - -

      Updating a High-Resolution Logo Using the Admin Panel

      -

      You can update your high-resolution logo using the Admin Panel if any of the following are true:

      -
      • The file format is not GIF
      • -
      • You don't have access to the Magento server file system
      • -
      • The logo is specific to a website, store, or store view
      -

      To upload a high-resolution logo using the Admin Panel:

      -
        -
      1. Log in to the Magento Admin Panel as an administrator.
      2. -
      3. Click System > Configuration > GENERAL > Design.
      4. -
      5. From the Current Configuration Scope in the upper left corner, click the scope to display the logo.
        - Initially, the logo is associated with Default Config, which means it applies to all websites and store views. You can optionally associate it with a specific website or store view by selecting it from the list.
        - The following example shows how to associate a logo with the Madison Island English store view.
        -
      6. -
      7. In the right pane, click Transactional Emails to expand it.
      8. -
      9. Enter the following information: - - - - - - - - - - - - - - - - - - - - - - - - - - -
        ItemDescription
        Logo ImageClick Browse and browse to locate the logo image.
        Delete Image checkboxSelect the checkbox to delete the current logo image. Ignore the other fields.
        Logo Image Alt fieldEnter alternate text to display if the image is not available. For a logo, it's typically the name of your company.
        Logo Width fieldEnter the numeric width, in pixels, of the area in which to display the image (not the dimensions of the logo image).
        Logo Height fieldEnter the numeric height, in pixels, of the area in which to display the image (not the dimensions of the logo image).

        - The following figure shows an example.
        -
      10. -
      11. Click Save Config in the upper right corner of the page.
      12. -
      - -

      Using Contact Information in Transaction Emails

      -

      Transactional emails can output your store email address, store phone number, and store hours of operation if those values are configured in the Admin Panel. To set those values:

      -
        -
      1. Log in to the Magento Admin Panel as an administrator.
      2. -
      3. To set the phone number and hours of operation: -
          -
        1. Click System > Configuration > GENERAL > General.
        2. -
        3. In the right pane, click Store Information to expand it.
        4. -
        5. If you want to include a phone number, input the phone number in the Store Contact Telephone field.
        6. -
        7. If you want to include your hours of operation, input them in the Store Hours of Operation field.
        8. + border="0"/>
    + - -
  • To set the store email address: +
    noteNote: To use a file type other than GIF or if you + need to upload unique logos for different websites, stores, or store views, see the next section. +
    + + +

    Updating a High-Resolution Logo Using the Admin Panel

    +

    You can update your high-resolution logo using the Admin Panel if any of the following are true:

    +
      +
    • The file format is not GIF
    • +
    • You don't have access to the Magento server file system
    • +
    • The logo is specific to a website, store, or store view
    • +
    +

    To upload a high-resolution logo using the Admin Panel:

      -
    1. Click System > Configuration > GENERAL > Store Email Addresses.
    2. -
    3. In the right pane, click General Contact or Sales Representative to expand it.
    4. -
    5. In the Sender Name field, input the name that you want the email to be sent from, such as your company name.
    6. -
    7. In the Sender Email field, input the email address.
    8. +
    9. Log in to the Magento Admin Panel as an administrator.
    10. +
    11. Click System > Configuration > GENERAL > + Design.
    12. +
    13. From the Current Configuration Scope in the upper left corner, click the scope to + display the logo.
      + Initially, the logo is associated with Default Config, which means it applies to + all websites and store views. You can optionally associate it with a specific website or store view + by selecting it from the list.
      + The following example shows how to associate a logo with the Madison Island English store view.
      +
    14. +
    15. In the right pane, click Transactional Emails to expand it.
    16. +
    17. Enter the following information: + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      ItemDescription
      Logo ImageClick Browse and browse to locate the logo image.
      Delete Image checkboxSelect the checkbox to delete the current logo image. Ignore the other fields.
      Logo Image Alt fieldEnter alternate text to display if the image is not available. For a logo, it's + typically the name of your company.
      Logo Width fieldEnter the numeric width, in pixels, of the area in which to display the image + (not the dimensions of the logo image).
      Logo Height fieldEnter the numeric height, in pixels, of the area in which to display the image + (not the dimensions of the logo image).

      + The following figure shows an example.
      + +
    18. +
    19. Click Save Config in the upper right corner of the page.
    -
  • -
  • When you're finished, click Save Config in the upper right corner of the page.
  • - - - -

    Localizing Transactional Emails

    -

    Only the en_US templates were updated to the new responsive email structure. To use the responsive emails for other locales, copy the en_US/template/email/ directory into the respective app/locale/[LOCALE CODE] directory and update the text strings to that locale.

    -

    Using Updated Newsletter Templates

    -

    The focus of this article is on transactional emails but the same techniques can be used with newsletter templates as well, including:

    - -

    In the Magento Admin Panel, go to Newsletter > Newsletter Templates and look at the template named Example Newsletter Template. We added this template as a reference for how to build a responsive newsletter.

    +

    Using Contact Information in Transaction Emails

    +

    Transactional emails can output your store email address, store phone number, and store hours of + operation if those values are configured in the Admin Panel. To set those values:

    +
      +
    1. Log in to the Magento Admin Panel as an administrator.
    2. +
    3. To set the phone number and hours of operation: +
        +
      1. Click System > Configuration > GENERAL > + General.
      2. +
      3. In the right pane, click Store Information to expand it.
      4. +
      5. If you want to include a phone number, input the phone number in the Store Contact + Telephone field.
      6. +
      7. If you want to include your hours of operation, input them in the Store Hours of + Operation field.
      8. +
      +
    4. +
    5. To set the store email address: +
        +
      1. Click System > Configuration > GENERAL > + Store Email Addresses.
      2. +
      3. In the right pane, click General Contact or Sales + Representative to expand it.
      4. +
      5. In the Sender Name field, input the name that you want the email to be sent + from, such as your company name.
      6. +
      7. In the Sender Email field, input the email address.
      8. +
      +
    6. +
    7. When you're finished, click Save Config in the upper right corner of the page.
    8. +
    -

    Getting Help

    -

    If you encounter issues customizing email templates, contact Magento Support. Another option is to post your question on the community magento.stackexchange.com site and tag it with rwd-email and rwd-theme.

    +

    Localizing Transactional Emails

    +

    Only the en_US templates were updated to the new responsive email structure. To use the responsive emails + for other locales, copy the en_US/template/email/ directory into the respective + app/locale/[LOCALE CODE] directory and update the text strings to that locale.

    + +

    Using Updated Newsletter Templates

    +

    The focus of this article is on transactional emails but the same techniques can be used with newsletter + templates as well, including:

    + +

    In the Magento Admin Panel, go to Newsletter > Newsletter Templates + and look at the template named Example Newsletter Template. We added this template as a + reference for how to build a responsive newsletter.

    + + +

    Getting Help

    +

    If you encounter issues customizing email templates, contact Magento Support. Another option is to post + your question on the community magento.stackexchange.com site and tag it with rwd-email and + rwd-theme.

    -
    +
    + \ No newline at end of file diff --git a/guides/m1x/ce19-ee114/ce1.9_release-notes.html b/guides/m1x/ce19-ee114/ce1.9_release-notes.html index 9913b8d5d1..228dd1edf9 100644 --- a/guides/m1x/ce19-ee114/ce1.9_release-notes.html +++ b/guides/m1x/ce19-ee114/ce1.9_release-notes.html @@ -14,9 +14,9 @@ - -header + +header {% include m1x/eol_message.html %} @@ -32,6 +32,11 @@

    Magento Open Source Release Notes (1.9 and later)

    Important Upgrade Information

    -
    importantImportant: Use Magento Open Source 1.9.3.0 or later for all new Magento Open Source installations and upgrades to get the latest fixes, features, and security updates.
    +
    importantImportant: Use Magento Open Source 1.9.3.0 or later for all new Magento Open Source installations and upgrades to get the latest fixes, features, and security updates.
    + + +

    Magento Open Source 1.9.4.5 Release Notes

    + +

    This version (or patch SUPEE-11314, which applies to older versions of Magento) provides resolution of multiple critical security issues. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento | APSB20-22 for a comprehensive discussion of these issues.

    + + +

    Magento Open Source 1.9.4.4 Release Notes

    + +

    This version (or patch SUPEE-11295, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento | APSB20-02 for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • The Disable button present when you run the compiler from Admin > System > Tools > Compiler is now enabled as expected. Previously, when you clicked the Disable button, it did not change state.
    • +
    + + +

    Magento Open Source 1.9.4.3 Release Notes

    + +

    This version (or patch SUPEE-11219, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • WebserviceX has been removed from the Magento 1.x code base.
    • +
    • This release adds two new currency services for currency rate import: CurrencyConverterAPI and FixerIO
    • +
    + +

    Known issue

    +

    This release includes a fix for a security vulnerability that potentially allowed changes to protected store settings. As a result, extensions or customizations that depend on saving configuration fields that are not defined in system.xml files may no longer work correctly.

    + + + +

    Magento Open Source 1.9.4.2 Release Notes

    +

    This version (or patch SUPEE-11155, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    Note: We are aware of the incompatibilities between patch SUPEE-11155 and the PHP 7.2 support patch and are currently working on a new version of SUPEE-11155 that resolves these incompatibilities. See Security Patch SUPEE-11555 - Possible issues? for a community-driven discussion on issues and solutions related to this SUPEE. Check these release notes and the Magento Security Center for updates on the availability on the new patch.

    + + + +

    We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • The Magento logging feature now works as expected after the SUPEE-11086 patch is installed. Previously, after application of this patch, Magento could only write only to a file that already existed on the server, and did not create new log files.
    • + + +
    • Magento 1.14.4.0 and the PHP7.2 support patch now include the same files as expected. The previous version of the patch did not include the following three files, which were included in Magento 1.14.4.0. + Magento 1.14.4.0: lib/phpseclib/PHP/Compat/Function/array_fill.php, lib/phpseclib/PHP/Compat/Function/bcpowmod.php, and lib/phpseclib/PHP/Compat/Function/str_split.php.
    • +
    + +

    Known issues

    + +

    The extensive security enhancements we’ve included to this release have resulted in the following changes to Magento behavior:

    +
      +
    • You can no longer upload files with the extension .swf to the WYSIWYG editor.
    • + +
    • Third-party checkout extensions and closed security cases will either not work securely or will not work at all. +
    • + +
    • The Authorize.net Direct Post module  has been enhanced to support the replacement of Authorize.net’s MD5-based hash with a (SHA-512) signature key. Authorize.net will no longer support implementations using the MD5-based hash as of June 28, 2019. You will need to update your signature key after upgrading to this version of Magento. For information about updating your signature key, see the Get a New Signature Key discussion in the Update Authorize.Net Direct Post from MD5 to SHA-512 help article. Note that although this help article describes how to install the earlier patch, merchants upgrading to this release of Magento are not applying the patch and should consult only the Get a New Signature Key discussion. If you’ve applied the patch to your Magento installation while running an earlier version of Magento, uninstall the Update Authorize.Net Direct Post from MD5 to SHA-512 patch before upgrading to this release. +
    • + +
    • You can no longer preview JavaScript in a newsletter template in the Admin.
    • + +
    • Sitemap names cannot exceed 32 characters.
    • + +
    + + + +

    Magento Open Source 1.9.4.1 Release Notes

    + +

    This version (or patch SUPEE-11086, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Note: Magento’s implementation of the Authorize.Net Direct Post payment method currently uses MD5-based hash for all M1 and M2 installations. As of June 28, 2019, Authorize.Net will stop supporting MD5-based hash usage.

    + +

    This will result in Magento merchants not being able to use Authorize.Net Direct Post to process payments. To avoid disruption and to continue processing payments, merchants must apply a patch provided by Magento and add a Signature Key (SHA-512) in the Magento Admin configuration settings. Magento released this patch in late February to address this issue on pre-2.3.1 installations of Magento. See Update Authorize.Net Direct Post from MD5 to SHA-512.

    + +

    Information about the deprecation of Authorize.Net Direct Post can be found in Authorize.net Direct Post (Deprecated).

    + +

    Fixed issues and enhancements

    +
      + +
    • Google Image Charts has been deprecated and replaced by Image-Charts for dashboard charts.
    • + +
    • Layered navigation now works as expected when full page cache and block caching are enabled. Previously, you could not clear layered navigation filters when these features were enabled.
    • + +
    • Errors caused by problematic PHP error logging have been resolved. Previously, Magento displayed excessive and unnecessary 404 errors.
    • + +
    • Magento now displays the following message when an invalid character is used, Attribute code is invalid. Please use only letters (a-z), numbers (0-9) or underscore(_) in this field, first character should be a letter. Do not use "event" for an attribute code. Previously, Magento did not flag invalid attribute codes.
    • + +
    • You can now add to the cart products with custom options for which the custom option checkbox has not been checked. Previously, Magento did not add the product to the cart, and displayed this message, Cannot add the item to shopping cart.
    • + +
    • URL redirects for products now work as expected. Previously, when you selected a product from the Category page and Add URL Redirect has been enabled, Magento redirected users to URL Redirect Information and threw this error, exception 'Mage_Core_Exception' with message 'Invalid block type: Mage_Adminhtml_Block_Empty_Edit_Form' in app/Mage.php:580
    • + +
    • Magento now displays payment information during the confirmation step of check out and successfully processes an order when inline translation is enabled. Previously, Magento did not display this payment information during check out, and the order was not completed.
    • + +
    • You can now create a staging website when development mode is enabled. Previously, Magento threw an error after you added a website from System > Content Staging > Staging Websites. +
    • + + +
    • You can now successfully delete a website by clicking Delete Website as expected. Previously, when you clicked this button, Magento threw a fatal error.
    • + +
    • You can now add a banner by clicking Add Banner from the Admin. Previously, Magento threw an error when you clicked this button.
    • + +
    • Magento no longer throws an Undefined index: is_recurring error when when you try to save a product when deploying Magento with development mode enabled.
    • + +
    + +

    Known issue

    +
      +
    • If there were any custom widgets created by usage of helper methods in layout updates, they will no longer work.
    • +
    + + @@ -105,9 +233,7 @@

    Magento Open Source 1.9.3.10 Release Notes

    Known issue

    -

    You cannot re-send the password for new customers who created their account during checkout.

    - - +

    You cannot re-send the password for new customers who created their account during checkout.

    Magento Open Source 1.9.3.9 Release Notes

    This version (or patch SUPEE-10752, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    @@ -155,12 +281,12 @@

    Magento Open Source 1.9.3.7 Release Notes

    Fixed issues

      -
    • Magento no longer displays the “Invalid Secret Key. Please refresh the page.†message when a user loads the Admin.
    • +
    • Magento no longer displays the “Invalid Secret Key. Please refresh the page." message when a user loads the Admin.
    • The one-page checkout page now displays the following message when a customer checks out an order for which no amount is due: No payment information required. Magento versions prior to 1.14.3.3 included this message, but it was missing from v1.14.3.3.
    • -
    • We’ve fixed a typo in the patch header information. (autocomplete="new-pawwsord†is now autocomplete="new-passwordâ€.) +
    • We’ve fixed a typo in the patch header information. (autocomplete="new-pawwsord" is now autocomplete="new-password".)
    @@ -197,7 +323,7 @@

    Magento Open Source 1.9.3.5 Release Notes

    Magento Open Source 1.9.3.4 Release Notes

    -

    This patch addresses both security and functional issues discovered when using the SUPEE-9767 patch. We recommend upgrading your Magento store to this latest version. +

    This patch addresses both security and functional issues discovered when using the SUPEE-9767 patch. We recommend upgrading your Magento store to this latest version.

    Here are your upgrade options: @@ -224,14 +350,7 @@

    Magento Open Source 1.9.3.4 Release Notes

    - - - - - - - -See Magento Security Center for a comprehensive discussion of these security issues.

    +

    See Magento Security Center for a comprehensive discussion of these security issues.

    This release also provides support for the following functional issues:

    @@ -251,7 +370,7 @@

    Installation

    -This patch is available from Magento Tech Resources.

    +This patch is available from Magento Tech Resources. @@ -298,13 +417,13 @@

    Magento Open Source 1.9.3.1 Release Notes

  • Auto-generated passwords are sent to new customers as expected.
  • The method Mage_Api_Model_Server_Handler_Abstract::processingMethodResult() accepts scalar and array values.
  • The default MySQL Full-Text search works as expected; it no longer returns all products.
  • -
  • Prevented a potential Cross-Site Request Forgery (CSRF) vulnerability by changing the form key when a customer signs out of the storefront.
  • +
  • Prevented a potential Cross-Site Request Forgery (CSRF) vulnerability by changing the form key when a customer signs out of the storefront.
  • Catalog price rules return the correct price.
  • Indexers now update all products instead of skipping the last product updated.
  • -
    noteNote: You currently cannot upgrade to this version using Magento Connect Manager. We expect to resolve this issue soon.
    +
    noteNote: You currently cannot upgrade to this version using Magento Connect Manager. We expect to resolve this issue soon.

    Magento Open Source 1.9.3.0 Release Notes

    See the following sections for information about this release:

    @@ -313,7 +432,6 @@

    Magento Open Source 1.9.3.0 Release Notes

  • Security Enhancements
  • Check for .swf Files After Upgrade
  • Backward-Incompatible Changes
  • -
  • Changes
  • Fixes
  • Highlights

    @@ -325,7 +443,7 @@

    Security Enhancements

  • Password enhancements
  • -

    General security enhancements

    +

    General security enhancements

    For more information about these security enhancements, see our Security Center article.

    Patches for major security issues in earlier versions of the Magento software are available on the Magento download page (look for SUPEE-8788.)

    See How to Apply the SUPEE-8788 Patch

    . @@ -343,7 +461,7 @@

    General security enhancements

  • Resolved a potential man-in-the-middle vulnerability.
  • Resolved a potential PHP security vulnerability.
  • An administrative user is no longer able to create a potential security vulnerability that used the block cache.
  • -
  • Resolved a potential cross-site request forgery (CSRF) vulnerability involving the wishlist.
  • +
  • Resolved a potential cross-site request forgery (CSRF) vulnerability involving the wishlist.
  • Resolved a potential remote code execution exploit.
  • It is no longer possible to log in to a store as an existing customer using only an e-mail address.
  • @@ -368,14 +486,6 @@

    Password enhancements

    - - - - - - - -

    Check for .swf Files After Upgrade

    @@ -561,7 +671,7 @@

    Recent Patches

  • How to Get Patches For Magento EE
  • -
    noteNote: Some of the patches discussed in this section have EE_1.14.0.1 in the name. These patches were all tested against Open Source 1.9.x as well.
    +
    noteNote: Some of the patches discussed in this section have EE_1.14.0.1 in the name. These patches were all tested against Open Source 1.9.x as well.

    General Magento Connect Patches

    @@ -570,7 +680,7 @@

    General Magento Connect Patches

  • 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.
  • +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: SUPEE-3762. 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.

    @@ -580,9 +690,9 @@

    How to Get Patches For Magento Open Source

    To get patches for Magento Open Source:

    1. Log in to www.magentocommerce.com/download.
    2. In the left pane, click Downloads.
    3. -li>Scroll down to the Magento Open Source Patches section. +
    4. Scroll down to the Magento Open Source Patches section.
    5. Follow the prompts on your screen to download a patch for your version of Magento Open Source.
    6. -
    7. Apply the patch as discussed in How to Apply and Revert Magento Patches.
    +
  • Apply the patch as discussed in How to Apply and Revert Magento Patches.
  • Magento Open Source 1.9.0.0 Release Notes

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

    @@ -613,7 +723,6 @@

    Highlights

    (Conversion means helping customers stay interested and complete their purchases.)

    -

    Security Enhancements

    • Addressed a potential cross-site scripting (XSS) vulnerability while creating configurable product variants.
    • @@ -632,7 +741,7 @@

      Changes

    • Two new options to prevent "clickjacking" if you run Magento in a frame or iframe:
      • Enable frames only in the same domain.
      • Enable frames.
      • -
        importantImportant: For security reasons, Magento strongly recommends against running the Magento software in a frame.
        +
        importantImportant: For security reasons, Magento strongly recommends against running the Magento software in a frame.

        The options are available in the Admin Panel at System > Configuration > ADVANCED > Admin > Security and are named Allow Magento Backend to run in frame and Allow Magento Frontend to run in frame.

        Enabling the option causes the X-Frame-Options request header to be sent.

      @@ -644,8 +753,8 @@

      Changes

    • -
    • Open Source 1.9 includes a fix 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.

      -
      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.
    • +
    • Open Source 1.9 includes a fix 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. +
      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.
    • The default values for two configuration options changed. Both options can be found in the Admin Panel under System > Configuration > CATALOG > Catalog > Frontend. The new default values follow:
      • Products per Page on Grid Allowed Values is now 12, 24, 36.
      • Products per Page on Grid Default Value is now 12.
      @@ -673,9 +782,6 @@

      Changes

      The user can select the Use as preferred shipping address checkbox to instruct PayPal to change their shipping address.
    - - -

    Tax Calculation Fixes

      This release provides support for PHP 7.2. -
    • We’ve removed the CC module. As a result, third-party modules that depend upon either the ccsave method or the xmlconnect method will not work as expected. Third-party themes that implement ccsave will not work as expected, either.
    • -
    • The Magento logo has been updated throughout the code base.
    • -
    • The Continue button now works as expected on the Payments step of checkout when paying with the PayPal payment method.
    • -
    • Google Tag Manager now logs sales information in Google Analytics as expected.
    • -
    • The product export CSV file now contains columns for super attributes.
    • -
    • Magento no longer throws an error when a customer accesses their shopping cart after items in their cart have been removed due to a timeout. Previously, Magento displayed this error, `Notice: Undefined variable: freePackageValue in /var/www/dev/htdocs/app/code/core/Mage/Shipping/Model/Carrier/Tablerate.php on line 130`.
    • -
    • Clicking on a configurable product’s swatch on the product list page now updates product price as expected.
    • -
    • Customers can now successfully add a grouped product to their shopping cart when category permissions are enabled. Previously, Magento did not add the product to the cart, but instead displayed a descriptive error message.
    • -
    • Magento no longer displays incorrect prices on the storefront after a failure of the enterprise refresh index.
    • -
    • We’ve resolved issues in the indexing locking mechanism that previously resulted in Magento throwing an exception after indexing completed.
    • -
    • Magento no longer throws a fatal error when a merchant uses an already reserved word to name a product attribute.
    • -
    • Magento now adds the correct sales tax to orders being shipped to U.S. addresses that use zip codes with the optional four-digit suffix (for example, 73365-1234). Previously, the Tax rule triggered a failure if the U.S. zip code that had this optional four-digit suffix.
    • -
    • Magento now displays all products on a production website that were edited by a role-restricted user on the associated staging website.
    • -
    • We’ve resolved an issue that caused Target Rules to throw an exception when a customer opened a product view page.
    • -
    - - -

    Magento Commerce 1.14.3.10 Release Notes

    - -

    This version (or patch SUPEE-10888, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote cross-site scripting and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    - -

    Note: With this release, Magento is announcing the following support policy: Magento will provide software support through June 2020 for Magento Commerce 1.x. Depending on your Magento Commerce 1 version, software support may include both quality fixes and security patches. Please review our Magento Software Lifecycle Policy Magento Software Lifecycle Policy to see how your version of Magento Commerce 1 is supported.

    - - -

    Known issue

    - -

    You cannot re-send the password for new customers who created their account during checkout.

    -

    - - - - - -

    Magento Commerce 1.14.3.9 Release Notes

    -

    This version (or patch SUPEE-10752, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    - -

    Fixed issues and enhancements

    -
      -
    • Magento no longer performs unnecessary write operations on the core_url_rewrite table.
    • -
    • Customers can now successfully register during checkout without being unexpectedly logged out.
    • -
    • Incorrect escaping in the cron.sh file no longer prevents cron jobs from running in parallel as expected.
    • -
    • Magento now cleans session data as expected after a customer logs out.
    • -
    - - - -

    Known issue

    -

    If your custom code or extension is using Zend/Filter/PregReplace.php with the modifier e, it will now return an error due to possible RCE issues. See APPSEC-2029 in Magento Security Center for more information.

    - - - - -

    Magento Commerce 1.14.3.8 Release Notes

    -

    This version (or patch SUPEE-10570, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    - -

    Fixed issues and enhancements

    -
      -
    • Changed Magento Admin to support recent USPS shipping changes. On February 23, 2018, USPS removed APIs that support the creation of shipping labels without postage. In response, we’ve removed this functionality from the Magento Admin. Consequently, you cannot create and print shipping labels that do not have postage applied. 

    • - -
    • Updated copyright to 2018.
    • -
    - -

    Known issues

    - -

    These two known issues are associated with the use of HTML tags within a product’s SKU attribute:

    - -
      -
    • If you try to import products that contain HTML tags in the SKU attribute, Magento displays this error at the data validation stage (that is, when you click Check data):
 Invalid value in SKU column. HTML tags are not allowed.
    • - - -
    • If you try to create or edit a product in the Admin panel and the product’s SKU attribute value contains HTML tags, Magento throws this error when you try to save the product: HTML tags are not allowed in SKU attribute.
    • -
    - - -

    Magento Commerce 1.14.3.7 Release Notes

    -

    This patch (SUPEE-10415) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    - -

    Fixed issues

    - -
      - - -
    • Magento no longer displays the “Invalid Secret Key. Please refresh the page.†message when a user loads the Admin.
    • - - -
    • The one-page checkout page now displays the following message when a customer checks out an order for which no amount is due: No payment information required. Magento versions prior to 1.14.3.3 included this message, but it was missing from v1.14.3.3.
    • - - -
    • We’ve fixed a typo in the patch header information. (autocomplete="new-pawwsord†is now autocomplete="new-passwordâ€.) -
    • -
    - -

    Known issue

    -

    Issue: Magento displays a "404: Page Not Found" error from the errors/ directory after upgrading to SUPEE-10415. This issue occurs only in Magento installations that run certain third-party extensions.

    - -

    Description: Magento is not properly logging PHP warnings that occur early during page initialization. Instead, of logging the error and continuing operation, Magento generates a 404 page. (Previously, Magento logged these warnings in the system.log file, and execution would continue as usual.)

    - -

    Workaround: Confirm that there are no PHP warnings generated by any of the extensions or customizations.

    - - - - -

    Notes

    - -
    • We no longer support custom file extensions for Mage::log(). Supported file extensions include .log, .txt, .html, .csv. For more information, navigate to Developers > Log Settings from the Admin. Magento displays this comment: Logging from Mage::log(). File is located in {{ base_dir }}/var/log. Allowed file extensions: log, txt, html, csv.
    • - -
    • Passwords for new users are now limited to 256 characters. If a new user enters a password that exceeds 256 characters, Magento displays this message: Please enter a password with at most 256 characters.
    • -
    - - - -

    Magento Commerce 1.14.3.6 Release Notes

    -

    This patch (SUPEE-10266) provides resolution of multiple critical security issues and several functional fixes. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    - - - - -

    SUPEE-10266 includes a fix for MPERF-9685. This fix is not included in release 1.14.3.6. However, in some cases, SUPEE-10266 can cause issues in the checkout process. Specifically, if a customer enables the Add gift options checkbox during checkout, the checkout process will not progress beyond the payments step.

    - -

    Note: We’ve released patch SUPEE-10348 to address issues with checkout that some users experienced after applying SUPEE-10266. SUPEE-10348 must be applied on top of SUPEE-10266. Note that if you are experiencing issues in checkout when using gift options, SUPEE-10348 should resolve these issues.

    - - - -

    If you are currently affected by this issue, you can workaround this issue by restore these two files to the pre-patch versions:

    -  -

    app/design/frontend/enterprise/default/template/giftcardaccount/onepage/payment/scripts.phtml

    - -

    app/design/frontend/rwd/enterprise/template/giftcardaccount/onepage/payment/scripts.phtml

    - - -We’ve also fixed an issue where uploaded images were twice their original size after you applied SUPEE-9767 v2. - - -

    Magento Commerce 1.14.3.5 Release Notes

    -We have skipped release 1.14.3.5. - -

    Magento Commerce 1.14.3.4 Release Notes

    -

    This patch (SUPEE-9767 version 2) addresses both security and functional issues discovered when using the SUPEE-9767 patch. We recommend upgrading your Magento store to this latest version. - - Here are your upgrade options: - - -

    • Upgrade to Magento Commerce 1.14.3.4. You don’t need to revert any patches or install SUPEE-9767 version 2 as version 2 is already included in the 1.14.3.4 release.
    • - -
    • If you’ve already installed SUPEE-9767 version 1, you can either: - -
        -
      • Upgrade to Magento Commerce 1.14.3.4, or
      • - -
      • revert SUPEE-9767 version 1, then install SUPEE-9767 version 2.
      • -
      -
    • - - - -
    • If you haven’t installed SUPEE-9767 version 1, you can either: - -
      • Upgrade to Magento Commerce 1.14.3.4, or
      • - -
      • install SUPEE-9767 version 2. -
      - -
    - - - - - - - -See Magento Security Center for a comprehensive discussion of these security issues.

    - -

    This release also provides support for the following functional issues:

    - -

    General fixes

    -
    • We’ve added a missing form_key to the enterprise shipping template (app/design/frontend/enterprise/default/template/checkout/onepage/shipping.phtml).
    • - -
    • We’ve restored missing strip_tags functionality in the checkout JavaScript.
    • -
    • We’ve changed how Magento validates form keys during the generic five-step checkout process. Previously, customer registration failed during standard checkout processing if form key authentication was enabled.
    • -
    • You can now successfully add a product to the shopping cart when FPC (Full Page Cache) is enabled. Previously, when FPC was enabled, adding a product to the cart resulted in an empty cart.
    • -
    • Magento now displays the Allow_symlinks message in the Admin message area as expected.
    • -
    • Magento now preserves the background transparency of uploaded images as expected. Previously, transparency was lost after the image was uploaded, resulting in an unusable image.
    • -
    • You can now use Checkout with Multiple Addresses when checkout form validation is enabled.
    • - -
    - -

    Installation

    -
      -
    • The Allow symlinks option is now disabled during installation or upgrade processes. Previously, when you changed the Allow symlinks setting to true in the database before upgrading and then installing the patch, this option remained enabled, but you could no longer access it from the Admin panel.
    • -
    - -This patch is available from Magento Tech Resources.

    - - - - - - - - - -

    Magento Commerce 1.14.3.3 Release Notes

    -

    This patch provides resolution of multiple critical security issues. These critical issues include remote code execution for authenticated Admin users, access control bypass, and cross-site request forgery issues. See Magento Security Center for a comprehensive discussion of these issues.

    - -

    This release also provides support for the following issue:

    - -

    Support for PayPal's update to its Instant Payment Notification (IPN) server URL. PayPal provides more information about this feature in IPN Verification Postback to HTTPS Microsite. This update is essential for retaining uninterrupted service after June 30.

    - -

    SUPEE-8167, an older patch that also contains this fix, was added on May 8, 2017, and is available from Magento Tech Resources.

    - -

    Known Issues

    -

    This patch/release has known issues. Please see SUPEE-9767 for updates.

    - -

    Note: Before applying this patch or updating to this release, disable the Symlinks setting in System > Configuration > Advanced > Developer > Enable Symlinks. If the Symlinks setting is enabled, it will override your configuration file settings. If that override occurs, you will need to directly modify the database to change those settings.

    - -

    Magento Commerce 1.14.3.2 Release Notes

    -

    This patch addresses the following issues:

    -
    • Removal of vulnerability with the Zend framework Zend_Mail library. For more information, see Magento Security Center.
    • -
    • Updated the copyright year to 2017.
    - - -

    Magento Commerce 1.14.3.1 Release Notes

    -

    This patch addresses the following issues:

    -
      -
    • We restored the old tax calculation algorithm for shipping charges. The patch to apply new calculation will be available on request.
    • -
    • Resolved an issue with setting the session lifetime to 0.
    • -
    • The monthly cron job that cleans up the table that contains IP addresses and passwords runs properly.
    • -
    • All configurable product images are imported.
    • -
    • You no longer get an exception due to an undefined addCrumbs() method call.
    • -
    • Resolved the error Notice: Undefined index: session_expire_timestamp when accessing the storefront.
    • -
    • Values for drop-down label values are saved correctly.
    • -
    • The "Price as configured" for bundle products displays correctly in the shopping cart.
    • -
    • Auto-generated passwords are sent to new customers as expected.
    • -
    • The method Mage_Api_Model_Server_Handler_Abstract::processingMethodResult() accepts scalar and array values.
    • -
    • The default MySQL Full-Text search works as expected; it no longer returns all products.
    • -
    • Prevented a potential Cross-Site Request Forgery (CSRF) vulnerability by changing the form key when a customer signs out of the storefront.
    • -
    • Prevented a potential Cross-Site Scripting (XSS) vulnerability when adding a category.
    • -
    • Catalog price rules return the correct price.
    • -
    • Indexers now update all products instead of skipping the last product updated.
    • - -
    - -
    noteNote: You currently cannot upgrade to this version using Magento Connect Manager. We expect to resolve this issue soon.
    - - -

    Magento Commerce 1.14.3.0 Release Notes

    -

    See the following sections for information about this release:

    - -
    • Highlights
    • -
    • Security Enhancements
    • -
    • Check for .swf File After Upgrade
    • -
    • Backward-Incompatible Changes
    • -
    • Changes
    • -
    • Fixes
    • - -

      Highlights

      -

      Magento Commerce 1.14.3 delivers more than 120 quality improvements, as well as support for PHP 5.6 in addition to PHP 5.4 and 5.5.

      - -

      Security Enhancements

      -

      We addressed the following security issues in this release:

      - - -

      General security enhancements

      -

      For more information about these security enhancements, see our Security Center article.

      -

      Patches for major security issues in earlier versions of the Magento software are available in the Magento Commerce customer portal.

      - -

      Details about security fixes:

      -
      • Resolved a potential SQL injection (Zend Framework issue)
      • -
      • Resolved a cache poisoning issue
      • -
      • We now provide better protection against path exploits.
      • -
      • Resolved a potential cross-site scripting (XSS) vulnerability when adding a category.
      • -
      • Resolved a potential XSS vulnerability that affected the Magento server's request URI.
      • -
      • Resolved a potential XSS vulnerability in invitations.
      • -
      • You can no longer cause out-of-memory errors on the Magento server by flooding it with images that have incorrect dimensions.
      • -
      • The Magento Admin Panel login page now renders in HTTPS if you configured the Magento server for HTTPS.
      • -
      • We added the nosniff header to our .htaccess files.
      • -
      • Magento no longer uses Adobe Flash for uploads.
      • -
      • Fixed several potential issues indicated by static code scans.
      • -
      • Resolved a potential man-in-the-middle vulnerability.
      • -
      • Resolved a potential PHP security vulnerability.
      • -
      • An administrative user is no longer able to create a potential security vulnerability that used the block cache.
      • -
      • Resolved a potential cross-site request forgery (CSRF) vulnerability involving the wishlist.
      • -
      • Resolved a potential remote code execution exploit.
      • -
      • It is no longer possible to log in to a store as an existing customer using only an e-mail address.
      • - - - - -
      - - -

      Password enhancements

      -
      • A user can reset a password only after receiving an e-mail. In addition, we introduced the following configuration settings: -
        • Limit the number of forgotten password requests from one IP address to five times per hour.
        • -
        • Limit the number of forgotten password requests from one e-mail address to five times per 24 hours.
        • -
        • Limit the number of forgotten password requests to no more than once ever 10 minutes per e-mail address.
        -
      • -
      • The forgot password link expires after the first use or two hours (by default).
      • -
      • When a user changes their e-mail address, they are required to provide their password and to acknowledge the change from the previous address.
      • -
      • We now ignore leading and trailing spaces in a user's password.
      • -
      • The new customer e-mail now includes the customer's password.
      • -
      • Resetting a password using a password recovery e-mail succeeds.
      • - - -
      - - - - -
    - - - - - - -

    Check for .swf Files After Upgrade

    -

    If you upgraded to Magento Commerce 1.14.3 after applying the SUPEE-8788 patch, make sure the following files have been deleted:

    - -
    skin/adminhtml/default/default/media/flex.swf
    -skin/adminhtml/default/default/media/uploader.swf
    -skin/adminhtml/default/default/media/uploaderSingle.swf
    - -

    If the files are present, delete them to avoid a potential security exploit. As of Magento Commerce 1.14.0.0, we no longer distribute .swf files with the Magento software.

    - -

    Backward-Incompatible Changes

    -

    The following backward-incompatible changes were made in this release:

    -

    Mage_Adminhtml_Block_Cms_Wysiwyg_Images_Content_Uploader: Parent class was removed.

    -

    Mage_Uploader_Model_Config_Abstract: Overrides the magic method __call and its behavior can be inconsistent. For example:

    - -
    ->setData('underscore_key', 1)
    -->getUnderscoreKey() //null
    - - -

    Fixes

    -

    The following sections discuss other fixes in this release:

    - - - -

    Tax Calculation Fixes

    -
    • The subtotal including tax on an invoice is calculated correctly.
    • - - -
    - -

    Shopping cart and checkout fixes

    -
    • One product displays one time in a cart even if the product was added once as a guest and another time as a logged-in user.
    • -
    • Bundled products now display properly in the mini cart as well as the shopping cart.
    • -
    • Moving a configurable product to a shopping cart in the Admin Panel functions normally.
    • -
    • Shipping discount coupons are now based correctly on a customer's shipping address.
    • -
    • First Class Mail letter now displays as a shipping option in the shopping cart.
    • -
    • You can now pay for a product using both store credit and reward points.
    • -
    • An exception no longer displays when a customer uses a gift card in an invalid transaction (such as an incorrect payment card number).
    • -
    • We added validation so a special price must be less than the actual price.
    • -
    • Exceptions no longer display when a customer checks out.
    • -
    • Fixed a programming issue that prevented serializing and unserializing values in the shopping cart.
    • -
    • Magento recovers from payment processor unavailability properly; the customer is charged and the item is shipped.
    • -
    • You can no longer order an empty product; that is, a product with no options.
    • - - - - -
    - -

    Catalog fixes

    -
    • A configurable product with decimal quantity less 1 now displays the proper quantity in the catalog.
    • -
    • Configurable products are now sorted by attribute, not by product ID.
    • -
    • Errors no longer display when you use Mage_Catalog_Block_Product_List on a product detail page.
    • -
    • Removed the undefined variable where from app/code/core/Mage/CatalogSearch/Model/Resource/Fulltext.php.
    • - - - - -
    - -

    Price rule fixes

    -
    • A catalog price rule that targets a bundled product by percentage calculates the price properly.
    • -
    • A shopping cart price rule that includes tax now calculates properly.
    • -
    • With the flat product catalog enabled, a catalog price rule with multi-select attributes works properly.
    • -
    • Errors no longer display when two users add a product at the same time. Magento thanks Babenko eCommerce for contributing this fix.
    • -
    • You can now add configurable products to the shopping cart after configuring a shopping cart rule.
    • - - -
    -

    Visual Merchandiser fixes

    -
    • We bundled the following fixes in a patch: - -
      • The value of Attribute in the Smart Category section displays the entire category name.
      • -
      • We reduced the frequency of rebuilding the Visual Merchandiser index to improve efficiency and performance.
      • -
      • Duplicate products no longer display when you choose to hide not-visible products.
      • -
      • Reapplied patches for various functions like indexing.
      • - -
      -
    • -
    • Improved the display of the out of items message.
    • - - -
    - -

    Configurable swatches fixes

    -
    • Fixed a memory leak in the configurable swatches module.
    • -
    • Configurable swatches for out-of-stock products now display consistently in layered navigation, the category view page, and the product view page.
    • -
    • Configurable swatches work properly even if there is no image (before the fix, a JavaScript error was thrown).
    • -
    • Resolved performance issues.
    • -
    • Swatch images for configurable products display properly.
    • - - - - -
    - - -

    Import/export fixes

    -
    • We bundled the following fixes in a patch: -
      • Exporting a large number of products no longer results in an out-of-memory error.
      • -
      • You can import into multiple stores if some stores are set to be replaced.
      • -
      • Re-importing customers that have a multi-select attribute preserves the attribute.
      • -
      • File uploads are processed properly.
      • -
      • Fixed broken help links in the Magento Admin Panel.
      • - -
      -
    • - - -
    • Importing products no longer consumes an excessive amount of memory.
    • - - - -
    • Coupon reports exported as .csv now display the correct totals.
    • - - - -
    - -

    Indexer fixes

    -
    • With flat category tables enabled, reindexing no longer removes the category class tag.
    • -
    • Resolved errors with the Product Flat Index not completely indexing a large number of changes.
    • -
    • All indexes now reindex when set to update when scheduled.
    • -
    • Improved performance of the category indexers. Magento thanks Vaimo for contributing this fix.
    • -
    • Categories saved with a / character as the suffix display properly.
    • - - -
    - -

    Other fixes

    -
      -
    • Applied United States Postal Service API changes for January 17, 2016.
    • -
    • Default variable values now save normally.
    • -
    • The WYSIWYG editor handles XHTML tags like cellpadding and cellspacing properly.
    • -
    • The configuration setting Allow HTML Tags on Frontend is honored.
    • -
    • Orders created using the Magento Admin now display on the Orders and Returns page on the storefront.
    • -
    • The option to merge Cascading Stylesheets (CSS) and JavaScript now works properly with a responsive web design (RWD) theme.
    • -
    • On a mobile device when the Magento storefront uses an RWD theme, the Filter bar displays one time only.
    • -
    • The Magento Connect Manager downloader's .htaccess file is no longer overwritten when the downloader component is updated.
    • -
    • The configuration cache is no longer corrupted under heavy load.
    • -
    • Order update e-mails are sent only once.
    • -
    • A SOAP API call to /api/soap/?wsdl returns normally.
    • -
    • A value that contains special characters is handled without errors by the SOAP API.
    • - -
    • Fixed the untranslatable base/default/template/sales/guest/form.phtml template.
    • -
    • Magento now stores two-digit birth years properly (for example, 80 is stored as 1980).
    • -
    • HTTP 200 (OK) status codes are returned for pages after a session expires.
    • -
    • You can view a disabled product without errors if compilation is enabled.
    • -
    • A Value Added Tax (VAT) ID now validates properly. If the customer specifies an invalid ID, the customer is notified they will be charged VAT tax.
    • -
    • Listing shipments no longer displays an exception.
    • -
    • You can filter associated products for a group product without errors.
    • -
    • When you manage product attributes, selecting an action from Actions works properly.
    • -
    • You can now add a configurable product by SKU to an order using the Admin Panel.
    • -
    • You can now save a product's weight attribute.
    • -
    • You can now save changes to a CMS page hierarchy when hierarchy metadata is disabled.
    • -
    • You can now save a banner after upgrading.
    • -
    • Using a Portable Network Graphics (.png) image on a CMS page no longer results in a HEADERS_ALREADY_SENT message to be logged.
    • -
    • Fixed an exception related to an unknown database table.
    • -
    • Fixed an issue with JavaScript merging.
    • -
    • You can now print 10 or more shipping labels without issues.
    • -
    • A PHP notice no longer occurs when you log the Magento Admin Panel IP address in the event log.
    • -
    • A SQL error no longer displays when you create a new floating point product attribute programmatically.
    • -
    • Added a missing image to the codebase.
    • -
    • The expression Mage::getModel('core/variable')->addValuesToResult() returning a collection with column plain_value and html_value now returns a collection with columns plain_value and html_value.
    • -
    • Payment no longer results in the exception ERR (3): Notice: Undefined offset: 1 in app/code/core/Mage/Sales/Model/Order.php on line 1258.
    • -
    • The correct telephone number displays in transactional e-mails. We changed the variable phone to store_phone. Magento thanks Classy Llama Studios for contributing this fix.
    • -
    • The Google sitemap now lists store URLs properly.
    • -
    • Implemented search query caching, which speeds up search results.
    • -
    • After a customer submits an order, the following error should not display: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'ECO0000148' for key 'UNQ_SALES_FLAT_ORDER_INCREMENT_ID'.
    • -
    • With flat category enabled, you no longer see errors due to an undefined method call.
    • -
    • Case-sensitive variations of URL rewrites work as expected.
    • -
    • Resolved a JavaScript syntax error in bundle.js.
    • -
    • The cron-related error Warning: shell_exec() has been disabled for security reasons... has been resolved. Magento thanks Stefan Hagspiel for reporting this issue.
    • -
    • cron no longer runs multiple times unnecessarily.
    • -
    • Cached static blocks now display properly.
    • - -
    - -

    Magento Commerce 1.14.2.0 Release Notes

    -

    Magento Commerce 1.14.2.0 Release Notes are in the User Guide.

    - -

    Magento Commerce 1.14.1.0 Release Notes

    -

    Magento Commerce 1.14.1.0 Release Notes are in the User Guide.

    - -

    Magento Commerce 1.14.0.1 Release Notes

    -

    Magento Commerce 1.14.0.1 resolves the following issues:

    -
    • Customers can no longer apply a coupon from an inactive shopping cart price rule to a purchase.
    • -
    • Customers using a smartphone or other small viewport can expand subcategories in the web store that uses the new responsive theme.
    - -

    Recent Patches

    -
    noteNote: The patches discussed in this section are built in to Commerce 1.14.1; you need to get them only if you're running an earlier Commerce version.
    - -

    We'd like to draw your attention to several new patches that were recently posted to the Partner Portal and Support Center. These patches deliver important improvements, such as enabling several concurrent administrators to work with the product catalog, and to make it easier to install community-created translation packages.

    -

    Details about the patches follow. To install these patches, see How to Get Patches For Magento Commerce.

    - - -

    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. -
    3. Click System > Configuration.
    4. -
    5. In the left navigation bar, from the ADVANCED group, click Index Management.
    6. -
    7. Expand Indexing Options.
    8. -
    9. From each list, click Update when scheduled.
    10. -
    11. Click Save Config in the upper right corner of the page.
    - - - - - -

    How to Get Patches For Magento Commerce

    -

    This section discusses how to get patches referenced in these Release Notes. Magento has other patches available from the Commerce 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 Commerce:

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

    Magento Commerce 1.14.0.0 Release Notes

    -

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

    - - -

    Highlights

    -

    This section lists the key new features in Magento Commerce 1.14. For more information about these new features, see the Magento User Guide.

    -
    • The default theme in Magento Commerce 1.14 uses Responsive Web Design principles to provide a better experience for users of mobile devices in particular. Benefits include: -
      • You can get a tablet and smart phone friendly responsive site in about half the time as before, speeding time to market and freeing up resources for other projects.
      • -
      • Your responsive site makes you better able to participate in the fast growing mobile commerce space, gives you the ability to more easily adapt to new opportunities, and is less expensive to maintain. A responsive site also offers potential search engine optimization (SEO) benefits because it uses Google's preferred approach to mobile-optimizing sites.
      -
    • -
    • Magento Commerce 1.14 now supports Solr versions up to 3.6.2 natively (that is, without a patch). Catalog indexing happens efficiently and automatically in the background, with no manual intervention required, resulting in better administrative performance.
      -For more information about using Solr with Magento Commerce, see the Magento User Guide.
      -Note: If you're using the Solr search engine with Commerce versions 1.13.1 or earlier, you must perform an additional step during upgrade due to the fact that the Solr schema changes in Commerce 1.14. You must copy two files to your Solr server—schema.xml and solrconfig.xml. For details, see the section on upgrading Solr in the Magento upgrade guide.
    • -
    • Cross-border trade: (Also referred to as pricing consistency.) We support European Union (EU) merchants operating across regions and geographies who want to show their customers a single price. Pricing is clean and uncluttered regardless of tax structures and rates that vary from country to country.
      -To enable cross-border trade in the Admin Panel, click System > Configuration > SALES > Tax > Calculation Settings, option Enable Cross Border Trade.
    • -
    • Supports PHP 5.4. For more information, see the PHP changelog.
    • -
    • The Zend Framework has been upgraded to version 1.12.3
    • -
    • Checkout improvements: -
      • You can capture up to 18% more sales by providing customers access to financing using the Bill Me Later service at no additional cost to you.
      • -
      • You can offer your customers a smoother, more streamlined PayPal Express Checkout experience, which tries alternative payment options when a customer's credit card is rejected
      • -
      • Improve the PayPal Express checkout experience by eliminating the following steps in the checkout process: -
        • The order review page can be enabled or disabled
        • -
        • Eliminate the necessity of clicking Update Order before Place Order
        -
      • - -
      -

      (Conversion means helping customers stay interested and complete their purchases.)

      -
    - -

    Security Enhancements

    -
    • Addressed a potential cross-site scripting (XSS) vulnerability while creating configurable product variants.
    • -
    • Addressed a potential security issue that could result in displaying information about a different order to a customer.
    • -
    • Users can no longer change the currency if the payment method PayPal Website Payments Standard is used.
    • -
    • Removed an .swf file from the Magento distribution because of security issues.
    • -
    • Improved file system security.
    • -
    • Enhanced the security of action URLs, such as billing agreements.
    • -
    • Addressed a potential session fixation vulnerability during checkout.
    • -
    • Improved the security of the Magento randomness function.
    • -
    - -

    Changes

    -
    • A default setting for configurable and bundled products has changed. When you create a configurable or bundled product in the Admin Panel, click Manage > Products. Create a new configurable or bundled product and click the Design tab. The default option for Display Product Options In has changed to Product Info Column.
    • -
    • The Google Websites Optimizer has been disabled because it has been deprecated by Google. (In earlier Commerce versions, this option was available in the Admin Panel at System > Configuration > SALES > Google API > Google Website Optimizer).
    • -
    • Two new options to prevent "clickjacking" if you run Magento in a frame or iframe: -
      • Enable frames only in the same domain.
      • -
      • Enable frames.
      • -
        noteNote: For security reasons, Magento strongly recommends against running the Magento software in a frame.
        - -

        The options are available in the Admin Panel at System > Configuration > ADVANCED > Admin > Security and are named Allow Magento Backend to run in frame and Allow Magento Frontend to run in frame.

        -

        Enabling the option causes the X-Frame-Options request header to be sent.

      -
    • -
    • FedEx changed their endpoints for sandbox and production to the following: -
      • Production: https://ws.fedex.com/web-services
      • -
      • Sandbox: https://wsbeta.fedex.com/web-services
      -

      Because of these changes, Magento cannot retrieve shipping rate information or print shipping labels for FedEx unless this fix is applied.

      -
    • - -
    • Magento Commerce 1.14 includes a fix 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.

      -
      noteNote: 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.
    • -
    • If you use the Solr search engine, you no longer need to manually reindex the Catalog Search Index (except after you upgrade to EE 1.14 from an earlier version).
    • -
    • The default values for two configuration options changed. Both options can be found in the Admin Panel under System > Configuration > CATALOG > Catalog > Frontend. The new default values follow: -
      • Products per Page on Grid Allowed Values is now 12, 24, 36.
      • -
      • Products per Page on Grid Default Value is now 12.
      -
    • On the New Rule page for shopping cart price rules (Rule Information tab page), explanatory text Usage limit enforced for logged in customers only was added to the Uses per customer field. This is to avoid confusion encountered by some Magento merchants.
    • -
    • Changes to PayPal Express checkout: -
      • Changes to both Proceed to Checkout and to Pay With PayPal: -
        • Customers cannot edit their billing address on the PayPal site—in fact, the billing address does not display on the PayPal site.
        • -
        • Magento Commerce uses the customer's PayPal address information, not the address information stored in Magento Commerce. The customer does not need to enter Magento Open Source or Commerce address information.
        • -
        • When the customer is redirected to the PayPal site, they can click Change next to their payment method to change it.
        • -

          The Magento administrator can set billing address information in the Admin Panel as follows: System > Configuration > SALES > Payment Methods. For any payment method that includes Express Checkout, in Basic Settings, set the value of the Require Customer's Billing Address list.

          -
        -
      • -
      -
      • Changes to Pay With PayPal only: -
        • If the Magento administrator does not require the customer's billing address, the customer's billing address is set to the customer's PayPal shipping address.
        • -
        • If the Magento requires the customer's billing address, the customer's billing address is set to the customer's PayPal billing address.
        • -
        • On the PayPal site, the customer can click Change next to their shipping address to change it. The customer can choose any shipping address configured with PayPal.
        • -
        • Because the customer's configured address in Magento is not used, the customer's shipping address stored in PayPal is never changed.
        -
      -
      • Changes to Proceed to Checkout only: -
        • No Change link displays next to a customer's shipping address on the PayPal site.
        • -
        • In the event of a shipping address mismatch between Magento and PayPal, the following message displays when the customer attempts to pay using PayPal:
          -
          The address you entered on store-name is different than your PayPal preferred shipping address. 
          -Return to store-name if you'd like to change the shipping address
          -The user can select the Use as preferred shipping address checkbox to instruct PayPal to change their shipping address.
        • -
        -
      -
    • - -
    - -

    Tax Calculation Fixes

    -
      -
    • Fixed price and dynamic price bundled products where the price is configured to include tax display prices correctly regardless of tax settings. (For example, customer's default tax rate is different from the origin tax rate.)
    • -
    • Resolved a one-cent rounding issue when Fixed Product Tax (FPT) is enabled and the option Apply Discount to FPT is set to Yes. (These options are available in the Admin Panel by going to System > Configuration > SALES > Tax > Fixed Product Taxes.)
    • -
    • Resolved issues with calculating the credit memo amount when FPT is discounted and the customer purchases more than one item.
    • -
    - -

    Fixes

    - -

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

    - - -

    Web Store and Shopping Cart Fixes

    -
    • With full page caching enabled: -
      • Customers can no longer see each other's wish list or previously viewed products.
      • -
      • Related products set to not rotate display on the web store. (In other words, an administrator set System > Configuration > CATALOG > Catalog > Rule-Based Product Relations, option Rotation Mode for Products in Related Product List set to Do not rotate.)
      • -
      • The product ratings block refreshes on the storefront after a new rating has been approved.
      • -
      • Tier pricing is calculated properly.
      • -
      -
    • -
    • Resolved a 404 (Not Found) error navigating from a product in one category to an upsell product in a different category.
    • - -
    • A customer can update quantities of items in their mini shopping cart from their My Account page.
    • -
    • The Minimum Advertised Price pop-up works properly in the web store. When the customer clicks Click for price, the price displays as expected.
    • -
    • The "customer since" date is correct.
    • -
    • Switching stores when viewing a product with store-scoped URL keys works as expected.
    • -
    • Setting System > Configuration > CATALOG > Inventory, option Display Out of Stock Products to Yes no longer causes all products to appear as out of stock.
    • -
    • Entering accented characters in the zip code field during checkout results in a validation error instead of an exception message.
    • -
    • Gift card codes are sent only after an item is purchased.
    • -
    • A customer who attempts to log in as another customer with incorrect credentials is denied.
    • -
    • Resolved issues with applying a 100% discount to an order.
    • -
    • Customers are no longer redirected to the home page when they have permission to view a category.
    • -
    • Discount amount displays correctly for products with custom options.
    • -
    • Issues with placing PayPal Payments Advanced or PayPal Payflow Link orders using Internet Explorer 9 have been resolved.
    • -
    - -

    Promotional Price Rule Fixes

    -

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

    -
    • Shopping cart price rules apply properly to grouped products.
    • -
    • Two catalog price rules applied to the same product work properly.
    • -
    • The setting Stop Further Rules Processing is honored.
    • -
    • A user with read-only privileges in the Admin Panel cannot save changes to a price rule.
    • -
    • Applying a shopping cart price rule does not display an exception.
    • -
    • Coupon codes apply only to products eligible for the price rule.
    • - -
    - -

    Administrative Ordering, Invoicing, Credit Memo Fixes

    -
    • An administrative user with access to only one website from which a product was deleted no longer sees a stack trace when attempting to create an RMA for that product. In other words, after a customer placed an order for a product on Website1, an administrator with privileges to all websites removes the product. Later, when an administrator with access to only Website1 attempts to create an RMA for the deleted product, that administrator no longer sees an error message; instead, they see an expected Access Denied message.
    • -
    • Resolved an issue with incorrectly calculating the amount of an invoice when some items were discounted by a shopping cart price rule.
    • -
    • Credit memo amount is calculated correctly when processing a partial invoice with a discount.
    • -
    • Making comments in a credit memo no longer returns items to stock. (Prerequisite: an administrator set System > Configuration > CATALOG > Inventory > Product Stock Options, option Automatically Return Credit Memo Item to Stock set to Yes.)
    • - -
    - -

    Import Fixes

    -
    • A product with a custom attribute set imports successfully.
    • -
    • A fatal error caused by Mage_ImportExport_Model_Scheduled_Operation was fixed.
      -Magento thanks Tim Bezhashvyly for contributing to this fix.
    • -
    - -

    Payment Method Fixes

    -
    • If guest checkout is disabled, a customer must log in to check out with PayPal Express.
    • -
    • Eliminated errors in the logs when an administrator clicks System > Configuration > SALES > Payment Methods.
    • -
    • You can now use New Zealand dollars as the base currency with the eWAY Direct payment bridge.
    • -
    • Store credit is applied correctly when using Website Payments Pro Hosted Solution.
    • -
    • If the merchant country is Germany (DE), disabled guest checkout for the express checkout method and PayPal Website Payments Standard.
    • -
    - -

    Solr Search Engine Fixes

    -
    • Eliminated a spurious error from the logs when Solr is enabled as the search engine.
    • -
    • Solr sorts search results by score.
    • -
    • A quick search by SKU works with the Solr search engine if the SKU contains hyphen characters.
    • -
    • Solr search works properly if you set allow_url_fopen = Off in php.ini.
    • -
    • Using layered navigation filtering no longer returns the wrong results. (For example, filtering by brand works properly.)
    • -
    • Resolved an issue where search results don't display correctly after a Magento upgrade.
    • -
    • Catalog navigation works properly.
    • -
    • Products display as expected in categories if the products have a Date attribute with the option Used for Sorting in Product Listing set to Yes. There are no exceptions in Magento logs after reindexing.
    • -
    • Corrected the sort order of products searched by SKU.
    • -
    • Search results of products with names and/or SKUs that contains numbers, letters, and a hyphen character (-) are as expected.
    • -
    • Resolved issues with search results for products in a locale other than en_US with numeric SKUs.
    • -
    • Resolved issues with Solr not returning product search results.
    • -
    • Search results no longer include products that are either Disabled or Out of Stock.
    • - - -
    - -

    Other Fixes

    -
    • Restored images on a customer's Reward Points page.
    • -
    • Categories on the storefront now display with spaces between category names for cached and non-cached pages.
    • -
    • A customer can now initiate a return from the storefront.
    • -
    • An administrative user can subscribe to low stock RSS feeds without errors.
    • -
    • Category URLs work as expected, regardless of the setting of Create Custom Redirect for old URL for the category's URL key.
    • -
    • Setting allow_url_fopen = Off in php.ini has no effect on the CMS WYSIWYG editor.
    • -
    • No fatal error displays when a role-restricted user previews a newsletter in the Admin Panel.
    • -
    • Google Sitemap files now include the .html suffix for category and product URLs.
    • -
    • Customers can use advanced search on your storefront if Magento EE is configured to use the default MySQL Fulltext search engine and the server uses MySQL 5.6.
    • -
    • A role-restricted user can preview a newsletter in the Admin Panel to which the user has privileges.
    • -
    • After synchronizing media files with the database, media/customer/.htaccess is present with the correct data. (Prerequisite: an administrator set System > Configuration > ADVANCED > System > Storage Configuration for Media set to Database).
    • -
    • cron now restarts indexers if they previously failed to run.
    • -
    • You can save changes to a category that has more than 1,000 products.
    • -
    • Deactivating one of several banners no longer causes exceptions in system.log.
    • -
    • Resolved issues with the WSDL cache.
    • -
    • Improved the efficiency of product searches.
    • -
    • Resolved issues with the full page cache crawler.
    • -
    • Resolved issues with the DHL International shipping method.
    • -
    • Resolved 404 (Not Found) errors in layered navigation.
    • -
    • Resolved a SQL error when attempting to assign a bundled product to another website.
    • -
    • Rules-based product relations perform as expected after being saved.
    • -
    • Resolved an issue with sending duplicate Content-Type headers when using mod_fastcgi with the Apache web server.
    • - - - -
    - - -

    Open Source Software Licensing Agreements

    -

    Some versions of Magento Commerce use open source software licensing. Following are license agreements for that software.

    -

    Touch punch: This code is dual licensed under the MIT or GPL Version 2 licenses and is therefore free to use, modify and/or distribute, but if you include Touch Punch in other software packages or plugins, please include an attribution to the original software and a link to this Touch Punch website.

    +--- +--- + + + + + + + + + + Magento Commerce Release Notes (1.14 and later) + + + + + + +header +{% include m1x/eol_message.html %} + + +

    Magento Commerce Release Notes (1.14 and later)

    + + + + + + +

    Important Upgrade Information

    +
    importantImportant: Use Magento Commerce 1.14.3.0 or later for all new Magento Commerce installations and upgrades to get the latest fixes, features, and security updates.
    + +

    Magento Commerce 1.14.4.5 Release Notes

    + +

    This version (or patch SUPEE-11314, which applies to older versions of Magento) provides resolution of multiple critical security issues. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    +

    We recommend upgrading your Magento store to this latest version. See Magento | APSB20-22 for a comprehensive discussion of these issues.

    + + + +

    Magento Commerce 1.14.4.4 Release Notes

    + +

    This version (or patch SUPEE-11295, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento | APSB20-02 for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • The Disable button present when you run the compiler from Admin > System > Tools > Compiler is now enabled as expected. Previously, when you clicked the Disable button, it did not change state.
    • +
    + + + +

    Magento Commerce 1.14.4.3 Release Notes

    + +

    This version (or patch SUPEE-11219, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • WebserviceX has been removed from the Magento 1.x code base.
    • +
    • This release adds two new currency services for currency rate import: CurrencyConverterAPI and FixerIO
    • +
    + +

    Known issue

    +

    This release includes a fix for a security vulnerability that potentially allowed changes to protected store settings. As a result, extensions or customizations that depend on saving configuration fields that are not defined in system.xml files may no longer work correctly.

    + + + + +

    Magento Commerce 1.14.4.2 Release Notes

    + +

    This version (or patch SUPEE-11155, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    Note: We are aware of the incompatibilities between patch SUPEE-11155 and the PHP 7.2 support patch and are currently working on a new version of SUPEE-11155 that resolves these incompatibilities. See Security Patch SUPEE-11555 - Possible issues? for a community-driven discussion on issues and solutions related to this SUPEE. Check these release notes and the Magento Security Center for updates on the availability on the new patch.

    + + +

    We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • The Magento logging feature now works as expected after the SUPEE-11086 patch is installed. Previously, after application of this patch, Magento could only write only to a file that already existed on the server, and did not create new log files.
    • + + +
    • Magento 1.14.4.0 and the PHP7.2 support patch now include the same files as expected. The previous version of the patch did not include the following three files, which were included in Magento 1.14.4.0. + Magento 1.14.4.0: lib/phpseclib/PHP/Compat/Function/array_fill.php, lib/phpseclib/PHP/Compat/Function/bcpowmod.php, and lib/phpseclib/PHP/Compat/Function/str_split.php.
    • +
    + +

    Known issues

    + +

    The extensive security enhancements we’ve included to this release have resulted in the following changes to Magento behavior:

    +
      +
    • You can no longer upload files with the extension .swf to the WYSIWYG editor.
    • + +
    • Third-party checkout extensions and closed security cases will either not work securely or will not work at all. +
    • + +
    • The Authorize.net Direct Post module  has been enhanced to support the replacement of Authorize.net’s MD5-based hash with a (SHA-512) signature key. Authorize.net will no longer support implementations using the MD5-based hash as of June 28, 2019. You will need to update your signature key after upgrading to this version of Magento. For information about updating your signature key, see the Get a New Signature Key discussion in the Update Authorize.Net Direct Post from MD5 to SHA-512 help article. Note that although this help article describes how to install the earlier patch, merchants upgrading to this release of Magento are not applying the patch and should consult only the Get a New Signature Key discussion. If you’ve applied the patch to your Magento installation while running an earlier version of Magento, uninstall the Update Authorize.Net Direct Post from MD5 to SHA-512 patch before upgrading to this release. +
    • + +
    • You can no longer preview JavaScript in a newsletter template in the Admin.
    • + +
    • Sitemap names cannot exceed 32 characters.
    • + +
    + + + + + +

    Magento Commerce 1.14.4.1 Release Notes

    + +

    This version (or patch SUPEE-11086, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These security enhancements help close cross-site scripting, arbitrary code execution, and sensitive data disclosure vulnerabilities as well as other security issues.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + + +

    Note: Magento’s implementation of the Authorize.Net Direct Post payment method currently uses MD5-based hash for all M1 and M2 installations. As of June 28, 2019, Authorize.Net will stop supporting MD5-based hash usage.

    + +

    This will result in Magento merchants not being able to use Authorize.Net Direct Post to process payments. To avoid disruption and to continue processing payments, merchants must apply a patch provided by Magento and add a Signature Key (SHA-512) in the Magento Admin configuration settings. Magento released this patch in late February to address this issue on pre-2.3.1 installations of Magento. See Update Authorize.Net Direct Post from MD5 to SHA-512 .

    + +

    Information about the deprecation of Authorize.Net Direct Post can be found in Authorize.net Direct Post (Deprecated).

    + +

    Fixed issues and enhancements

    +
      +
    • Google Image Charts has been deprecated and replaced by Image-Charts for dashboard charts.
    • + + +
    • Layered navigation now works as expected when full page cache and block caching are enabled. Previously, you could not clear layered navigation filters when these features were enabled.
    • + +
    • Errors caused by problematic PHP error logging have been resolved. Previously, Magento displayed excessive and unnecessary 404 errors.
    • + +
    • Magento now displays the following message when an invalid character is used, Attribute code is invalid. Please use only letters (a-z), numbers (0-9) or underscore(_) in this field, first character should be a letter. Do not use "event" for an attribute code. Previously, Magento did not flag invalid attribute codes.
    • + +
    • You can now add to the cart products with custom options for which the custom option checkbox has not been checked. Previously, Magento did not add the product to the cart, and displayed this message, Cannot add the item to shopping cart.
    • + +
    • URL redirects for products now work as expected. Previously, when you selected a product from the Category page and Add URL Redirect has been enabled, Magento redirected users to URL Redirect Information and threw this error, exception 'Mage_Core_Exception' with message 'Invalid block type: Mage_Adminhtml_Block_Empty_Edit_Form' in app/Mage.php:580
    • + +
    • Magento now displays payment information during the confirmation step of check out and successfully processes an order when inline translation is enabled. Previously, Magento did not display this payment information during check out, and the order was not completed.
    • + +
    • You can now create a staging website when development mode is enabled. Previously, Magento threw an error after you added a website from System > Content Staging > Staging Websites. +
    • + + +
    • You can now successfully delete a website by clicking Delete Website as expected. Previously, when you clicked this button, Magento threw a fatal error.
    • + +
    • You can now add a banner by clicking Add Banner from the Admin. Previously, Magento threw an error when you clicked this button.
    • + +
    • Magento no longer throws an Undefined index: is_recurring error when when you try to save a product when deploying Magento with development mode enabled.
    • + +
    + +

    Known issue

    +
      +
    • If there were any custom widgets created by usage of helper methods in layout updates, they will no longer work.
    • +
    + + + + +

    Magento Commerce 1.14.4.0 Release Notes

    + +

    This version (or patch SUPEE-10975, which applies to older versions of Magento) provides resolution of multiple critical security issues and functional fixes. These critical security issues include remote code execution (RCE), cross-site scripting (XSS), and cross-site request forgery (CSRF) issues. This release also provides support for PHP 7.2.

    + +

    We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Note that after updating to this release, third-party modules that depend upon Magento core backup functionality will no longer work. Alternatively, you can use one of these two methods to enable database backups:

    + +
      +
    • Change false to true in the config > modules > Mage_Backup > active setting of app/etc/modules/Mage_All.xml.
    • +
    • From the Admin, change the System > Configuration > Advanced > Disable  Modules Output > Mage_Backup from disabled to enabled.
    • +
    + +

    Fixed issues and enhancements

    +
      +
    • This release provides support for PHP 7.2.
    • +
    • We’ve removed the CC module. As a result, third-party modules that depend upon either the ccsave method or the xmlconnect method will not work as expected. Third-party themes that implement ccsave will not work as expected, either.
    • +
    • The Magento logo has been updated throughout the code base.
    • +
    • The Continue button now works as expected on the Payments step of checkout when paying with the PayPal payment method.
    • +
    • Google Tag Manager now logs sales information in Google Analytics as expected.
    • +
    • The product export CSV file now contains columns for super attributes.
    • +
    • Magento no longer throws an error when a customer accesses their shopping cart after items in their cart have been removed due to a timeout. Previously, Magento displayed this error, `Notice: Undefined variable: freePackageValue in /var/www/dev/htdocs/app/code/core/Mage/Shipping/Model/Carrier/Tablerate.php on line 130`.
    • +
    • Clicking on a configurable product’s swatch on the product list page now updates product price as expected.
    • +
    • Customers can now successfully add a grouped product to their shopping cart when category permissions are enabled. Previously, Magento did not add the product to the cart, but instead displayed a descriptive error message.
    • +
    • Magento no longer displays incorrect prices on the storefront after a failure of the enterprise refresh index.
    • +
    • We’ve resolved issues in the indexing locking mechanism that previously resulted in Magento throwing an exception after indexing completed.
    • +
    • Magento no longer throws a fatal error when a merchant uses an already reserved word to name a product attribute.
    • +
    • Magento now adds the correct sales tax to orders being shipped to U.S. addresses that use zip codes with the optional four-digit suffix (for example, 73365-1234). Previously, the Tax rule triggered a failure if the U.S. zip code that had this optional four-digit suffix.
    • +
    • Magento now displays all products on a production website that were edited by a role-restricted user on the associated staging website.
    • +
    • We’ve resolved an issue that caused Target Rules to throw an exception when a customer opened a product view page.
    • +
    + + +

    Magento Commerce 1.14.3.10 Release Notes

    + +

    This version (or patch SUPEE-10888, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote cross-site scripting and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Note: With this release, Magento is announcing the following support policy: Magento will provide software support through June 2020 for Magento Commerce 1.x. Depending on your Magento Commerce 1 version, software support may include both quality fixes and security patches. Please review our Magento Software Lifecycle Policy Magento Software Lifecycle Policy to see how your version of Magento Commerce 1 is supported.

    + + +

    Known issue

    + +

    You cannot re-send the password for new customers who created their account during checkout.

    + +

    Magento Commerce 1.14.3.9 Release Notes

    +

    This version (or patch SUPEE-10752, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • Magento no longer performs unnecessary write operations on the core_url_rewrite table.
    • +
    • Customers can now successfully register during checkout without being unexpectedly logged out.
    • +
    • Incorrect escaping in the cron.sh file no longer prevents cron jobs from running in parallel as expected.
    • +
    • Magento now cleans session data as expected after a customer logs out.
    • +
    + + + +

    Known issue

    +

    If your custom code or extension is using Zend/Filter/PregReplace.php with the modifier e, it will now return an error due to possible RCE issues. See APPSEC-2029 in Magento Security Center for more information.

    + + + + +

    Magento Commerce 1.14.3.8 Release Notes

    +

    This version (or patch SUPEE-10570, which applies to older versions of Magento) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Fixed issues and enhancements

    +
      +
    • Changed Magento Admin to support recent USPS shipping changes. On February 23, 2018, USPS removed APIs that support the creation of shipping labels without postage. In response, we’ve removed this functionality from the Magento Admin. Consequently, you cannot create and print shipping labels that do not have postage applied. 

    • + +
    • Updated copyright to 2018.
    • +
    + +

    Known issues

    + +

    These two known issues are associated with the use of HTML tags within a product’s SKU attribute:

    + +
      +
    • If you try to import products that contain HTML tags in the SKU attribute, Magento displays this error at the data validation stage (that is, when you click Check data):
 Invalid value in SKU column. HTML tags are not allowed.
    • + + +
    • If you try to create or edit a product in the Admin panel and the product’s SKU attribute value contains HTML tags, Magento throws this error when you try to save the product: HTML tags are not allowed in SKU attribute.
    • +
    + + +

    Magento Commerce 1.14.3.7 Release Notes

    +

    This patch (SUPEE-10415) provides resolution of multiple critical security issues. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    Fixed issues

    + +
      + + +
    • Magento no longer displays the “Invalid Secret Key. Please refresh the page." message when a user loads the Admin.
    • + + +
    • The one-page checkout page now displays the following message when a customer checks out an order for which no amount is due: No payment information required. Magento versions prior to 1.14.3.3 included this message, but it was missing from v1.14.3.3.
    • + + +
    • We’ve fixed a typo in the patch header information. (autocomplete="new-pawwsord" is now autocomplete="new-password".) +
    • +
    + +

    Known issue

    +

    Issue: Magento displays a "404: Page Not Found" error from the errors/ directory after upgrading to SUPEE-10415. This issue occurs only in Magento installations that run certain third-party extensions.

    + +

    Description: Magento is not properly logging PHP warnings that occur early during page initialization. Instead, of logging the error and continuing operation, Magento generates a 404 page. (Previously, Magento logged these warnings in the system.log file, and execution would continue as usual.)

    + +

    Workaround: Confirm that there are no PHP warnings generated by any of the extensions or customizations.

    + + + + +

    Notes

    + +
    • We no longer support custom file extensions for Mage::log(). Supported file extensions include .log, .txt, .html, .csv. For more information, navigate to Developers > Log Settings from the Admin. Magento displays this comment: Logging from Mage::log(). File is located in {{ base_dir }}/var/log. Allowed file extensions: log, txt, html, csv.
    • + +
    • Passwords for new users are now limited to 256 characters. If a new user enters a password that exceeds 256 characters, Magento displays this message: Please enter a password with at most 256 characters.
    • +
    + + + +

    Magento Commerce 1.14.3.6 Release Notes

    +

    This patch (SUPEE-10266) provides resolution of multiple critical security issues and several functional fixes. These critical security issues include remote code execution, cross-site scripting, and cross-site request forgery issues. We recommend upgrading your Magento store to this latest version. See Magento Security Center for a comprehensive discussion of these issues.

    + + + + +

    SUPEE-10266 includes a fix for MPERF-9685. This fix is not included in release 1.14.3.6. However, in some cases, SUPEE-10266 can cause issues in the checkout process. Specifically, if a customer enables the Add gift options checkbox during checkout, the checkout process will not progress beyond the payments step.

    + +

    Note: We’ve released patch SUPEE-10348 to address issues with checkout that some users experienced after applying SUPEE-10266. SUPEE-10348 must be applied on top of SUPEE-10266. Note that if you are experiencing issues in checkout when using gift options, SUPEE-10348 should resolve these issues.

    + + + +

    If you are currently affected by this issue, you can workaround this issue by restore these two files to the pre-patch versions:

    +  +

    app/design/frontend/enterprise/default/template/giftcardaccount/onepage/payment/scripts.phtml

    + +

    app/design/frontend/rwd/enterprise/template/giftcardaccount/onepage/payment/scripts.phtml

    + + +We’ve also fixed an issue where uploaded images were twice their original size after you applied SUPEE-9767 v2. + + +

    Magento Commerce 1.14.3.5 Release Notes

    +We have skipped release 1.14.3.5. + +

    Magento Commerce 1.14.3.4 Release Notes

    +

    This patch (SUPEE-9767 version 2) addresses both security and functional issues discovered when using the SUPEE-9767 patch. We recommend upgrading your Magento store to this latest version.

    + + Here are your upgrade options: + + +
    • Upgrade to Magento Commerce 1.14.3.4. You don’t need to revert any patches or install SUPEE-9767 version 2 as version 2 is already included in the 1.14.3.4 release.
    • + +
    • If you’ve already installed SUPEE-9767 version 1, you can either: + +
        +
      • Upgrade to Magento Commerce 1.14.3.4, or
      • + +
      • revert SUPEE-9767 version 1, then install SUPEE-9767 version 2.
      • +
      +
    • + + + +
    • If you haven’t installed SUPEE-9767 version 1, you can either: + +
      • Upgrade to Magento Commerce 1.14.3.4, or
      • + +
      • install SUPEE-9767 version 2. +
      + +
    + +

    See Magento Security Center for a comprehensive discussion of these security issues.

    + +

    This release also provides support for the following functional issues:

    + +

    General fixes

    +
    • We’ve added a missing form_key to the enterprise shipping template (app/design/frontend/enterprise/default/template/checkout/onepage/shipping.phtml).
    • + +
    • We’ve restored missing strip_tags functionality in the checkout JavaScript.
    • +
    • We’ve changed how Magento validates form keys during the generic five-step checkout process. Previously, customer registration failed during standard checkout processing if form key authentication was enabled.
    • +
    • You can now successfully add a product to the shopping cart when FPC (Full Page Cache) is enabled. Previously, when FPC was enabled, adding a product to the cart resulted in an empty cart.
    • +
    • Magento now displays the Allow_symlinks message in the Admin message area as expected.
    • +
    • Magento now preserves the background transparency of uploaded images as expected. Previously, transparency was lost after the image was uploaded, resulting in an unusable image.
    • +
    • You can now use Checkout with Multiple Addresses when checkout form validation is enabled.
    • + +
    + +

    Installation

    +
      +
    • The Allow symlinks option is now disabled during installation or upgrade processes. Previously, when you changed the Allow symlinks setting to true in the database before upgrading and then installing the patch, this option remained enabled, but you could no longer access it from the Admin panel.
    • +
    + +This patch is available from Magento Tech Resources. + + + + + + + + + +

    Magento Commerce 1.14.3.3 Release Notes

    +

    This patch provides resolution of multiple critical security issues. These critical issues include remote code execution for authenticated Admin users, access control bypass, and cross-site request forgery issues. See Magento Security Center for a comprehensive discussion of these issues.

    + +

    This release also provides support for the following issue:

    + +

    Support for PayPal's update to its Instant Payment Notification (IPN) server URL. PayPal provides more information about this feature in IPN Verification Postback to HTTPS Microsite. This update is essential for retaining uninterrupted service after June 30.

    + +

    SUPEE-8167, an older patch that also contains this fix, was added on May 8, 2017, and is available from Magento Tech Resources.

    + +

    Known Issues

    +

    This patch/release has known issues. Please see SUPEE-9767 for updates.

    + +

    Note: Before applying this patch or updating to this release, disable the Symlinks setting in System > Configuration > Advanced > Developer > Enable Symlinks. If the Symlinks setting is enabled, it will override your configuration file settings. If that override occurs, you will need to directly modify the database to change those settings.

    + +

    Magento Commerce 1.14.3.2 Release Notes

    +

    This patch addresses the following issues:

    +
    • Removal of vulnerability with the Zend framework Zend_Mail library. For more information, see Magento Security Center.
    • +
    • Updated the copyright year to 2017.
    + + +

    Magento Commerce 1.14.3.1 Release Notes

    +

    This patch addresses the following issues:

    +
      +
    • We restored the old tax calculation algorithm for shipping charges. The patch to apply new calculation will be available on request.
    • +
    • Resolved an issue with setting the session lifetime to 0.
    • +
    • The monthly cron job that cleans up the table that contains IP addresses and passwords runs properly.
    • +
    • All configurable product images are imported.
    • +
    • You no longer get an exception due to an undefined addCrumbs() method call.
    • +
    • Resolved the error Notice: Undefined index: session_expire_timestamp when accessing the storefront.
    • +
    • Values for drop-down label values are saved correctly.
    • +
    • The "Price as configured" for bundle products displays correctly in the shopping cart.
    • +
    • Auto-generated passwords are sent to new customers as expected.
    • +
    • The method Mage_Api_Model_Server_Handler_Abstract::processingMethodResult() accepts scalar and array values.
    • +
    • The default MySQL Full-Text search works as expected; it no longer returns all products.
    • +
    • Prevented a potential Cross-Site Request Forgery (CSRF) vulnerability by changing the form key when a customer signs out of the storefront.
    • +
    • Prevented a potential Cross-Site Scripting (XSS) vulnerability when adding a category.
    • +
    • Catalog price rules return the correct price.
    • +
    • Indexers now update all products instead of skipping the last product updated.
    • + +
    + +
    noteNote: You currently cannot upgrade to this version using Magento Connect Manager. We expect to resolve this issue soon.
    + + +

    Magento Commerce 1.14.3.0 Release Notes

    +

    See the following sections for information about this release:

    + +
    • Highlights
    • +
    • Security Enhancements
    • +
    • Check for .swf File After Upgrade
    • +
    • Backward-Incompatible Changes
    • +
    • Fixes
    • + +

      Highlights

      +

      Magento Commerce 1.14.3 delivers more than 120 quality improvements, as well as support for PHP 5.6 in addition to PHP 5.4 and 5.5.

      + +

      Security Enhancements

      +

      We addressed the following security issues in this release:

      + + +

      General security enhancements

      +

      For more information about these security enhancements, see our Security Center article.

      +

      Patches for major security issues in earlier versions of the Magento software are available in the Magento Commerce customer portal.

      + +

      Details about security fixes:

      +
      • Resolved a potential SQL injection (Zend Framework issue)
      • +
      • Resolved a cache poisoning issue
      • +
      • We now provide better protection against path exploits.
      • +
      • Resolved a potential cross-site scripting (XSS) vulnerability when adding a category.
      • +
      • Resolved a potential XSS vulnerability that affected the Magento server's request URI.
      • +
      • Resolved a potential XSS vulnerability in invitations.
      • +
      • You can no longer cause out-of-memory errors on the Magento server by flooding it with images that have incorrect dimensions.
      • +
      • The Magento Admin Panel login page now renders in HTTPS if you configured the Magento server for HTTPS.
      • +
      • We added the nosniff header to our .htaccess files.
      • +
      • Magento no longer uses Adobe Flash for uploads.
      • +
      • Fixed several potential issues indicated by static code scans.
      • +
      • Resolved a potential man-in-the-middle vulnerability.
      • +
      • Resolved a potential PHP security vulnerability.
      • +
      • An administrative user is no longer able to create a potential security vulnerability that used the block cache.
      • +
      • Resolved a potential cross-site request forgery (CSRF) vulnerability involving the wishlist.
      • +
      • Resolved a potential remote code execution exploit.
      • +
      • It is no longer possible to log in to a store as an existing customer using only an e-mail address.
      • + + + + +
      + + +

      Password enhancements

      +
      • A user can reset a password only after receiving an e-mail. In addition, we introduced the following configuration settings: +
        • Limit the number of forgotten password requests from one IP address to five times per hour.
        • +
        • Limit the number of forgotten password requests from one e-mail address to five times per 24 hours.
        • +
        • Limit the number of forgotten password requests to no more than once ever 10 minutes per e-mail address.
        +
      • +
      • The forgot password link expires after the first use or two hours (by default).
      • +
      • When a user changes their e-mail address, they are required to provide their password and to acknowledge the change from the previous address.
      • +
      • We now ignore leading and trailing spaces in a user's password.
      • +
      • The new customer e-mail now includes the customer's password.
      • +
      • Resetting a password using a password recovery e-mail succeeds.
      • +
      +
    + +

    Check for .swf Files After Upgrade

    +

    If you upgraded to Magento Commerce 1.14.3 after applying the SUPEE-8788 patch, make sure the following files have been deleted:

    + +
    skin/adminhtml/default/default/media/flex.swf
    +skin/adminhtml/default/default/media/uploader.swf
    +skin/adminhtml/default/default/media/uploaderSingle.swf
    + +

    If the files are present, delete them to avoid a potential security exploit. As of Magento Commerce 1.14.0.0, we no longer distribute .swf files with the Magento software.

    + +

    Backward-Incompatible Changes

    +

    The following backward-incompatible changes were made in this release:

    +

    Mage_Adminhtml_Block_Cms_Wysiwyg_Images_Content_Uploader: Parent class was removed.

    +

    Mage_Uploader_Model_Config_Abstract: Overrides the magic method __call and its behavior can be inconsistent. For example:

    + +
    ->setData('underscore_key', 1)
    +->getUnderscoreKey() //null
    + + +

    Fixes

    +

    The following sections discuss other fixes in this release:

    + + + +

    Tax Calculation Fixes

    +
    • The subtotal including tax on an invoice is calculated correctly.
    • + + +
    + +

    Shopping cart and checkout fixes

    +
    • One product displays one time in a cart even if the product was added once as a guest and another time as a logged-in user.
    • +
    • Bundled products now display properly in the mini cart as well as the shopping cart.
    • +
    • Moving a configurable product to a shopping cart in the Admin Panel functions normally.
    • +
    • Shipping discount coupons are now based correctly on a customer's shipping address.
    • +
    • First Class Mail letter now displays as a shipping option in the shopping cart.
    • +
    • You can now pay for a product using both store credit and reward points.
    • +
    • An exception no longer displays when a customer uses a gift card in an invalid transaction (such as an incorrect payment card number).
    • +
    • We added validation so a special price must be less than the actual price.
    • +
    • Exceptions no longer display when a customer checks out.
    • +
    • Fixed a programming issue that prevented serializing and unserializing values in the shopping cart.
    • +
    • Magento recovers from payment processor unavailability properly; the customer is charged and the item is shipped.
    • +
    • You can no longer order an empty product; that is, a product with no options.
    • + + + + +
    + +

    Catalog fixes

    +
    • A configurable product with decimal quantity less 1 now displays the proper quantity in the catalog.
    • +
    • Configurable products are now sorted by attribute, not by product ID.
    • +
    • Errors no longer display when you use Mage_Catalog_Block_Product_List on a product detail page.
    • +
    • Removed the undefined variable where from app/code/core/Mage/CatalogSearch/Model/Resource/Fulltext.php.
    • + + + + +
    + +

    Price rule fixes

    +
    • A catalog price rule that targets a bundled product by percentage calculates the price properly.
    • +
    • A shopping cart price rule that includes tax now calculates properly.
    • +
    • With the flat product catalog enabled, a catalog price rule with multi-select attributes works properly.
    • +
    • Errors no longer display when two users add a product at the same time. Magento thanks Babenko eCommerce for contributing this fix.
    • +
    • You can now add configurable products to the shopping cart after configuring a shopping cart rule.
    • + + +
    +

    Visual Merchandiser fixes

    +
    • We bundled the following fixes in a patch: + +
      • The value of Attribute in the Smart Category section displays the entire category name.
      • +
      • We reduced the frequency of rebuilding the Visual Merchandiser index to improve efficiency and performance.
      • +
      • Duplicate products no longer display when you choose to hide not-visible products.
      • +
      • Reapplied patches for various functions like indexing.
      • + +
      +
    • +
    • Improved the display of the out of items message.
    • + + +
    + +

    Configurable swatches fixes

    +
    • Fixed a memory leak in the configurable swatches module.
    • +
    • Configurable swatches for out-of-stock products now display consistently in layered navigation, the category view page, and the product view page.
    • +
    • Configurable swatches work properly even if there is no image (before the fix, a JavaScript error was thrown).
    • +
    • Resolved performance issues.
    • +
    • Swatch images for configurable products display properly.
    • + + + + +
    + + +

    Import/export fixes

    +
    • We bundled the following fixes in a patch: +
      • Exporting a large number of products no longer results in an out-of-memory error.
      • +
      • You can import into multiple stores if some stores are set to be replaced.
      • +
      • Re-importing customers that have a multi-select attribute preserves the attribute.
      • +
      • File uploads are processed properly.
      • +
      • Fixed broken help links in the Magento Admin Panel.
      • + +
      +
    • + + +
    • Importing products no longer consumes an excessive amount of memory.
    • + + + +
    • Coupon reports exported as .csv now display the correct totals.
    • + + + +
    + +

    Indexer fixes

    +
    • With flat category tables enabled, reindexing no longer removes the category class tag.
    • +
    • Resolved errors with the Product Flat Index not completely indexing a large number of changes.
    • +
    • All indexes now reindex when set to update when scheduled.
    • +
    • Improved performance of the category indexers. Magento thanks Vaimo for contributing this fix.
    • +
    • Categories saved with a / character as the suffix display properly.
    • + + +
    + +

    Other fixes

    +
      +
    • Applied United States Postal Service API changes for January 17, 2016.
    • +
    • Default variable values now save normally.
    • +
    • The WYSIWYG editor handles XHTML tags like cellpadding and cellspacing properly.
    • +
    • The configuration setting Allow HTML Tags on Frontend is honored.
    • +
    • Orders created using the Magento Admin now display on the Orders and Returns page on the storefront.
    • +
    • The option to merge Cascading Stylesheets (CSS) and JavaScript now works properly with a responsive web design (RWD) theme.
    • +
    • On a mobile device when the Magento storefront uses an RWD theme, the Filter bar displays one time only.
    • +
    • The Magento Connect Manager downloader's .htaccess file is no longer overwritten when the downloader component is updated.
    • +
    • The configuration cache is no longer corrupted under heavy load.
    • +
    • Order update e-mails are sent only once.
    • +
    • A SOAP API call to /api/soap/?wsdl returns normally.
    • +
    • A value that contains special characters is handled without errors by the SOAP API.
    • + +
    • Fixed the untranslatable base/default/template/sales/guest/form.phtml template.
    • +
    • Magento now stores two-digit birth years properly (for example, 80 is stored as 1980).
    • +
    • HTTP 200 (OK) status codes are returned for pages after a session expires.
    • +
    • You can view a disabled product without errors if compilation is enabled.
    • +
    • A Value Added Tax (VAT) ID now validates properly. If the customer specifies an invalid ID, the customer is notified they will be charged VAT tax.
    • +
    • Listing shipments no longer displays an exception.
    • +
    • You can filter associated products for a group product without errors.
    • +
    • When you manage product attributes, selecting an action from Actions works properly.
    • +
    • You can now add a configurable product by SKU to an order using the Admin Panel.
    • +
    • You can now save a product's weight attribute.
    • +
    • You can now save changes to a CMS page hierarchy when hierarchy metadata is disabled.
    • +
    • You can now save a banner after upgrading.
    • +
    • Using a Portable Network Graphics (.png) image on a CMS page no longer results in a HEADERS_ALREADY_SENT message to be logged.
    • +
    • Fixed an exception related to an unknown database table.
    • +
    • Fixed an issue with JavaScript merging.
    • +
    • You can now print 10 or more shipping labels without issues.
    • +
    • A PHP notice no longer occurs when you log the Magento Admin Panel IP address in the event log.
    • +
    • A SQL error no longer displays when you create a new floating point product attribute programmatically.
    • +
    • Added a missing image to the codebase.
    • +
    • The expression Mage::getModel('core/variable')->addValuesToResult() returning a collection with column plain_value and html_value now returns a collection with columns plain_value and html_value.
    • +
    • Payment no longer results in the exception ERR (3): Notice: Undefined offset: 1 in app/code/core/Mage/Sales/Model/Order.php on line 1258.
    • +
    • The correct telephone number displays in transactional e-mails. We changed the variable phone to store_phone. Magento thanks Classy Llama Studios for contributing this fix.
    • +
    • The Google sitemap now lists store URLs properly.
    • +
    • Implemented search query caching, which speeds up search results.
    • +
    • After a customer submits an order, the following error should not display: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'ECO0000148' for key 'UNQ_SALES_FLAT_ORDER_INCREMENT_ID'.
    • +
    • With flat category enabled, you no longer see errors due to an undefined method call.
    • +
    • Case-sensitive variations of URL rewrites work as expected.
    • +
    • Resolved a JavaScript syntax error in bundle.js.
    • +
    • The cron-related error Warning: shell_exec() has been disabled for security reasons... has been resolved. Magento thanks Stefan Hagspiel for reporting this issue.
    • +
    • cron no longer runs multiple times unnecessarily.
    • +
    • Cached static blocks now display properly.
    • + +
    + +

    Magento Commerce 1.14.2.0 Release Notes

    +

    Magento Commerce 1.14.2.0 Release Notes are in the User Guide.

    + +

    Magento Commerce 1.14.1.0 Release Notes

    +

    Magento Commerce 1.14.1.0 Release Notes are in the User Guide.

    + +

    Magento Commerce 1.14.0.1 Release Notes

    +

    Magento Commerce 1.14.0.1 resolves the following issues:

    +
    • Customers can no longer apply a coupon from an inactive shopping cart price rule to a purchase.
    • +
    • Customers using a smartphone or other small viewport can expand subcategories in the web store that uses the new responsive theme.
    + +

    Recent Patches

    +
    noteNote: The patches discussed in this section are built in to Commerce 1.14.1; you need to get them only if you're running an earlier Commerce version.
    + +

    We'd like to draw your attention to several new patches that were recently posted to the Partner Portal and Support Center. These patches deliver important improvements, such as enabling several concurrent administrators to work with the product catalog, and to make it easier to install community-created translation packages.

    +

    Details about the patches follow. To install these patches, see How to Get Patches For Magento Commerce.

    + + +

    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. +
    3. Click System > Configuration.
    4. +
    5. In the left navigation bar, from the ADVANCED group, click Index Management.
    6. +
    7. Expand Indexing Options.
    8. +
    9. From each list, click Update when scheduled.
    10. +
    11. Click Save Config in the upper right corner of the page.
    + + + + + +

    How to Get Patches For Magento Commerce

    +

    This section discusses how to get patches referenced in these Release Notes. Magento has other patches available from the Commerce 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 Commerce:

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

    Magento Commerce 1.14.0.0 Release Notes

    +

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

    + + +

    Highlights

    +

    This section lists the key new features in Magento Commerce 1.14. For more information about these new features, see the Magento User Guide.

    +

    Overview

    @@ -46,14 +46,14 @@

    Overview

    These releases include a number of improvements:

    -
    importantImportant: Use CE 1.9.1 or EE 1.14.1 or later for all new EE installations and upgrades to get the latest fixes, features, and security updates.
    +
  • Magento CE and EE documentation home page, which also has information about new features
  • +
    importantImportant: Use CE 1.9.1 or EE 1.14.1 or later for all new EE installations and upgrades to get the latest fixes, features, and security updates.

    The sections that follow get you started on your installation or upgrade. Detailed, step-by-step procedures are discussed in the following articles:

    - + -

    Getting Help With Your Installation or Upgrade

    +

    Getting Help With Your Installation or Upgrade

    In the event you have a large, distributed system or you need additional help, consult the following resources.

    @@ -79,7 +79,7 @@

    Getting Help With Your Installation or Upgrade

    -

    Getting Magento CE or EE

    +

    Getting Magento CE or EE

    The following table discusses where to get the upgrade image and optional sample data.

    @@ -106,8 +106,11 @@

    Getting Magento CE or EE

    Installing Magento CE or EE

    -

    See Installing Magento CE or EE.

    +

    See Installing Magento CE or EE.

    Upgrading to Magento CE or EE

    -

    See Upgrading to Magento CE or EE.

    +

    See Upgrading to Magento CE or EE.

    +
    + + \ No newline at end of file diff --git a/guides/m1x/install/installing_install.html b/guides/m1x/install/installing_install.html index e713702bb5..e91fc3dcb8 100644 --- a/guides/m1x/install/installing_install.html +++ b/guides/m1x/install/installing_install.html @@ -16,9 +16,9 @@ - -header + +header {% include m1x/eol_message.html %}
    @@ -28,7 +28,7 @@

    Installing and Verifying Magento Community Edition (CE) and Enterprise Edition (EE)

    -

    Edit this page on GitHub

    +

    Edit this page on GitHub

    Contents

    @@ -48,20 +48,20 @@

    Overview

    • Magento Community Edition (CE) 1.8.x or 1.9.x
    • Magento Enterprise Edition (EE) 1.13.x or 1.14.x

    To install Magento CE or Magento EE, use the following high-level guidelines:

    -
    1. Set up a system that meets the Magento system requirements.
    2. +
      1. Set up a system that meets the Magento system requirements.
      2. Install prerequisite software (web server, PHP, and required PHP extensions).
      3. Set up a MySQL Magento database instance.
      4. Run the Magento installer to complete the installation.
      5. Verify that Magento installed correctly.
      -
      importantImportant: Perform all installations to Magento the latest version of CE 1.9 or Magento EE 1.14 to get the latest fixes, features, and security updates.
      +
      importantImportant: Perform all installations to Magento the latest version of CE 1.9 or Magento EE 1.14 to get the latest fixes, features, and security updates.

      Prerequisites

      Before starting your installation:

      -

      Installing Optional Software

      This section discusses how to create or install the following:

      @@ -171,7 +171,7 @@

      Creating phpinfo.php

      // Show all information, defaults to INFO_ALL phpinfo();

    For more information, see the phpinfo manual page.

    -

    To view the results, enter the following URL in your browser's location or address field: +

    To view the results, enter the following URL in your browser's location or address field:

    http://web-server-ip-or-host/phpinfo.php

    If a 404 (Not Found) error displays, check the following:

    • Start the web server if necessary.
    • @@ -218,7 +218,7 @@

      Installing phpmyadmin

      Creating a Magento Database Instance

      This section discusses how to create a new database instance for Magento. Although a new database instance is recommended, you can optionally install Magento into an existing database instance. If you choose to do that, skip this section and continue with Installing Optional Sample Data.

      -
      noteNote: Before you continue, review the information about MySQL discussed in Prerequisites.
      +
      noteNote: Before you continue, review the information about MySQL discussed in Prerequisites.

      To create a new database instance:

      1. Log in to your database server as any user.
      2. @@ -265,11 +265,11 @@

        Extracting the Magento Installation Archive

        Installing Optional Sample Data

    Magento provides sample data you can optionally install to give you an idea of what products look like in the Admin Panel and in your web store. You can use this sample data to learn how Magento works and to experiment with custom themes.

    You must install sample data on the file system and in the database before you install Magento.

    -
    noteNote: Only if your database is shared between more than one Magento installation. Database table names used by the sample data are not configurable. To use sample data with a new Magento installation, you must manually add a prefix to all sample data tables and use the same prefix when you install Magento.
    +
    noteNote: Only if your database is shared between more than one Magento installation. Database table names used by the sample data are not configurable. To use sample data with a new Magento installation, you must manually add a prefix to all sample data tables and use the same prefix when you install Magento.

    To skip sample data installation, continue with Setting File and Directory Ownership and Privileges.

    To install Magento sample data:

    -
    1. Download the sample data from one of the locations discussed in Getting Magento CE or EE.
    2. +
      1. Download the sample data from one of the locations discussed in Getting Magento CE or EE.
      2. If necessary, transfer the sample data to your Magento server.
      3. On your Magento server, extract the sample data archive to a directory other than your Magento installation directory.
      4. Make note of the path to the sample data's media subdirectory.
      5. @@ -342,7 +342,7 @@

        Setting File and Directory Ownership and Privileges

        Installing Magento CE or EE

        This section discusses how to run the Magento installer, using Magento EE as an example. The Magento CE installer has exactly the same options; only the appearance is different.

        -
        importantImportant: The procedure that follows assumes that your web server and database server are on the same host. If they are installed on different hosts, additional tasks are required. Get help before you continue your installation.
        +
        importantImportant: The procedure that follows assumes that your web server and database server are on the same host. If they are installed on different hosts, additional tasks are required. Get help before you continue your installation.

        To install Magento CE or EE:

        1. Complete all of the tasks discussed earlier in this article.
        2. @@ -351,7 +351,7 @@

          Installing Magento CE or EE

          For example, if your web server is http://www.example.com, listens on port 80, and Magento is installed in the web server docroot's magento subdirectory, enter
          http://www.example.com/magento
          The following page displays.
          - +
        3. Select the checkbox that indicates you agree to the terms and conditions, and click Continue.
        4. On the Localization page, enter the following information.
          @@ -375,7 +375,7 @@

          Installing Magento CE or EE


          The following figure shows an example of configuring Magento for US English in the US Central time zone and using the US Dollar as the default currency.
          -
        5. +
        6. Click Continue.
          The Configuration page displays. Each of its three sections is discussed in the following step.
        7. In the Configuration page, enter the following information: @@ -415,7 +415,7 @@

          Installing Magento CE or EE


          A sample follows.
          -
        8. +
        9. In the Web Access Options section, enter the following information.
          @@ -451,7 +451,7 @@

          Installing Magento CE or EE


          A sample follows.
          -
        10. +
        11. In the Session Storage Options section, click one of the following options:
          • File to store user session data on the file system in the [your Magento install dir]/var/session directory.
            File-based session storage is appropriate unless the Magento file system access is slow or you have a clustered database.
          • @@ -461,7 +461,7 @@

            Installing Magento CE or EE

          • Click Continue.
            -
            importantImportant: If errors display, you must resolve them before continuing.
          • +
            importantImportant: If errors display, you must resolve them before continuing.
          • In the Create Admin Account page, enter the following information. @@ -501,11 +501,11 @@

            Installing Magento CE or EE


            A sample follows.
            -
          • +
          • Click Continue.
            The following page displays to indicate a successful installation.
            -
          • -
      + +

    Verifying that Magento CE or Magento EE Installed Successfully

    To make sure Magento installed properly, you should log in to the Admin Panel to verify the Magento version.

    @@ -516,7 +516,7 @@

    Verifying that Magento CE or Magento EE Installed SuccessfullyLog in to the Admin Panel as an administrator.
  • Scroll to the bottom of the page; the version should display as 1.14 (Magento EE) or 1.9.0.0 (Magento CE).
    The following figure shows an example.
    -
  • + - You never advance past the installer's Configuration page. - Try selecting the Skip Base URL Validation Before the Next Step checkbox. If problems persist, get help. + Try selecting the Skip Base URL Validation Before the Next Step checkbox. If problems persist, get help. +

    + + \ No newline at end of file diff --git a/guides/m1x/install/installing_req-prereq_centos.html b/guides/m1x/install/installing_req-prereq_centos.html index 953dbc6251..2232695159 100644 --- a/guides/m1x/install/installing_req-prereq_centos.html +++ b/guides/m1x/install/installing_req-prereq_centos.html @@ -18,13 +18,13 @@ - -header + +header {% include m1x/eol_message.html %}

    CentOS: Installing Required Prerequisite Software for Magento CE 1.8 Magento EE 1.13 (or Later)

    -

    Edit this page on GitHub

    +

    Edit this page on GitHub

    @@ -34,7 +34,7 @@

    CentOS: Installing Required Prerequisite Software for Magento CE 1.8 Magento
  • Overview
  • Updating System Software
  • Apache
  • -
  • nginx
  • +
  • nginx
  • PHP
  • MySQL
  • Next Steps
  • @@ -44,8 +44,8 @@

    CentOS: Installing Required Prerequisite Software for Magento CE 1.8 Magento

    Overview

    This article discusses how to install required prerequisite software for CentOS. You must complete these tasks before you install Magento CE 1.8 or later or Magento EE 1.13 or later.

    -

    Before you continue, make sure you familiarize yourself with the installation process discussed in Prerequisites.

    -
    noteNote: You must install system software on CentOS as a user with root privileges.
    +

    Before you continue, make sure you familiarize yourself with the installation process discussed in Prerequisites.

    +
    noteNote: You must install system software on CentOS as a user with root privileges.

    Updating System Software

    @@ -75,7 +75,7 @@

    Enabling Apache Rewrites

    PHP

    Magento CE and EE support the following PHP versions:

    -
    • Magento CE 1.6.0.0–1.8.1.0 and Magento EE 1.11.0.0–1.13.1.0 support PHP 5.3 natively. They can be used with PHP 5.4 if you apply the PHP 5.4 patch.
    • +
      • Magento CE 1.6.0.0–1.8.1.0 and Magento EE 1.11.0.0–1.13.1.0 support PHP 5.3 natively. They can be used with PHP 5.4 if you apply the PHP 5.4 patch.
      • Magento CE 1.9.0.x and EE 1.14.0.x support PHP 5.4 natively. They are backward-compatible with PHP 5.3
      • Magento CE 1.9.1 and EE 1.14.1 support PHP 5.5 natively. They are backward-compatible with PHP 5.4

      We recommend you use the most recent PHP version supported by your version of Magento. For example, you should use PHP 5.5 with CE 1.9.1 or EE 1.14.1.

      @@ -83,7 +83,7 @@

      PHP

      Check with a system administrator or reference for your version of CentOS to see what PHP versions are available.

      -

      If you're installing Magento CE 1.9.1 or Magento EE 1.14.1, you can use PHP 5.5; otherwise, we recommend PHP 5.4. For certain versions of CE and EE, a patch is required to use PHP 5.4.

      +

      If you're installing Magento CE 1.9.1 or Magento EE 1.14.1, you can use PHP 5.5; otherwise, we recommend PHP 5.4. For certain versions of CE and EE, a patch is required to use PHP 5.4.

      Enter the following command to see what version of PHP is currently running:

      php -v

      See one of the following sections for more information:

      @@ -100,7 +100,7 @@

      Upgrading PHP

      If PHP is not installed, install PHP 5.3 using the following command:

      yum -y install php php-xml

      Continue with one of the following sections.

      -
      importantImportant: The following sections discuss suggested PHP upgrade paths. Because you're choosing a non-CentOS repository to upgrade PHP, make your choice carefully. Not all repositories work equally well. We don't recommend any particular repository. Consult a system administrator or CentOS reference for more information.
      +
      importantImportant: The following sections discuss suggested PHP upgrade paths. Because you're choosing a non-CentOS repository to upgrade PHP, make your choice carefully. Not all repositories work equally well. We don't recommend any particular repository. Consult a system administrator or CentOS reference for more information.

      Upgrading to PHP 5.5

      @@ -139,7 +139,7 @@

      Increasing the PHP Memory Limit

      MySQL

      This section discusses how to install and configure MySQL 5.6. CentOS 6.x repositories have MySQL 5.1; to install a different version of MySQL, see the MySQL documentation.

      -
      noteNote: Use the tasks that follow only on a new MySQL database. Some of the tasks require you to delete users and should not be performed on a database that has already been set up.
      +
      noteNote: Use the tasks that follow only on a new MySQL database. Some of the tasks require you to delete users and should not be performed on a database that has already been set up.

      The following procedure is based on Install MySQL Server 5.6 in CentOS 6.x and Red Hat 6.x Linux.

      1. Install the MySQL database: @@ -155,7 +155,7 @@

        MySQL

      Next Steps

      -

      After installing the required prerequisite software, continue your installation with Preparing Your Server for Magento CE or EE.

      +

      After installing the required prerequisite software, continue your installation with Preparing Your Server for Magento CE or EE.

    \ No newline at end of file diff --git a/guides/m1x/install/installing_req-prereq_ubuntu.html b/guides/m1x/install/installing_req-prereq_ubuntu.html index 75e77a8c87..daaaae4de0 100644 --- a/guides/m1x/install/installing_req-prereq_ubuntu.html +++ b/guides/m1x/install/installing_req-prereq_ubuntu.html @@ -18,13 +18,13 @@ - -header + +header {% include m1x/eol_message.html %}

    Ubuntu: Installing Required Prerequisite Software for Magento CE 1.8 Magento EE 1.13 (or Later)

    -

    Edit this page on GitHub

    +

    Edit this page on GitHub

    @@ -34,7 +34,7 @@

    Ubuntu: Installing Required Prerequisite Software for Magento CE 1.8 Magento
  • Overview
  • Updating System Software
  • Apache
  • -
  • nginx
  • +
  • nginx
  • PHP
  • MySQL
  • Next Steps
  • @@ -43,8 +43,8 @@

    Ubuntu: Installing Required Prerequisite Software for Magento CE 1.8 Magento

    Overview

    This article discusses how to install required prerequisite software for Ubuntu. You must complete these tasks before you install Magento CE 1.8 or later or Magento EE 1.13 or later.

    -

    Before you continue, make sure you familiarize yourself with the installation process discussed in Prerequisites.

    -
    noteNote: You must install system software on Ubuntu as a user with root privileges.
    +

    Before you continue, make sure you familiarize yourself with the installation process discussed in Prerequisites.

    +
    noteNote: You must install system software on Ubuntu as a user with root privileges.

    Updating System Software

    @@ -56,7 +56,7 @@

    Updating System Software

    apt-get upgrade

    Apache

    -

    This section discusses how to install Apache. For more details, you can consult a reference like the Ubuntu site. +

    This section discusses how to install Apache. For more details, you can consult a reference like the Ubuntu site.

    Magento requires Apache use server rewrites. You must also specify the type of directives that can be used in .htaccess, which Magento uses to specify rewrite rules.

    Installing and configuring Apache is basically a three-step process: install the software, enable rewrites, and specify .htaccess directives.

    @@ -76,18 +76,18 @@

    Enabling Apache Rewrites for Apache 2.2

    1. Open the following file for editing.
      vim /etc/apache2/sites-available/default
    2. Locate the following block. -
      <Directory /var/www/>
      -    Options Indexes FollowSymLinks MultiViews
      -    AllowOverride None
      -    Order allow,deny
      -    allow from all
      +
      <Directory /var/www/>
      +    Options Indexes FollowSymLinks MultiViews
      +    AllowOverride None
      +    Order allow,deny
      +    allow from all
       </Directory>
    3. Change the value of AllowOverride to [value from Apache site]. -
      <Directory /var/www/>
      -    Options Indexes FollowSymLinks MultiViews
      -    AllowOverride All
      -    Order allow,deny
      -    allow from all
      +
      <Directory /var/www/>
      +    Options Indexes FollowSymLinks MultiViews
      +    AllowOverride All
      +    Order allow,deny
      +    allow from all
       </Directory>
    4. Save the file and exit the text editor.
    5. Configure Apache to use the mod_rewrite module.
      @@ -107,14 +107,14 @@

      Enabling Apache Rewrites for Apache 2.4

      <Directory "/var/www">
       AllowOverride [value from Apache site]
       </Directory>
      -Note: You must change the value of AllowOverride in the directive for the directory to which you expect to install the Magento software. For example, to install in the web server docroot, edit the directive in <Directory /var/www>.
    6. - +Note: You must change the value of AllowOverride in the directive for the directory to which you expect to install the Magento software. For example, to install in the web server docroot, edit the directive in <Directory /var/www>. +
    7. Restart Apache:
      service apache2 restart

    PHP

    Magento CE and EE support the following PHP versions:

    -
    • Magento CE 1.6.0.0–1.8.1.0 and Magento EE 1.11.0.0–1.13.1.0 support PHP 5.3 natively. They can be used with PHP 5.4 if you apply the PHP 5.4 patch.
    • +
      • Magento CE 1.6.0.0–1.8.1.0 and Magento EE 1.11.0.0–1.13.1.0 support PHP 5.3 natively. They can be used with PHP 5.4 if you apply the PHP 5.4 patch.
      • Magento CE 1.9.0.x and EE 1.14.0.x support PHP 5.4 natively. They are backward-compatible with PHP 5.3
      • Magento CE 1.9.1 and EE 1.14.1 support PHP 5.5 natively. They are backward-compatible with PHP 5.4

      We recommend you use the most recent PHP version supported by your version of Magento. For example, you should use PHP 5.5 with CE 1.9.1 or EE 1.14.1.

      @@ -122,7 +122,7 @@

      PHP

      Check with a system administrator or reference for your version of Ubuntu to see what PHP versions are available.

      -

      If you're installing Magento CE 1.9.1 or Magento EE 1.14.1, you can use PHP 5.5; otherwise, we recommend PHP 5.4. For certain versions of CE and EE, a patch is required to use PHP 5.4.

      +

      If you're installing Magento CE 1.9.1 or Magento EE 1.14.1, you can use PHP 5.5; otherwise, we recommend PHP 5.4. For certain versions of CE and EE, a patch is required to use PHP 5.4.

      Enter the following command to see what version of PHP is currently running:

      php -v

      See one of the following sections for more information:

      @@ -133,7 +133,7 @@

      PHP

    Upgrading PHP

    -
    importantImportant: The following sections discuss suggested PHP upgrade paths. Because you're choosing a non-Ubuntu repository to upgrade PHP, make your choice carefully. Not all repositories work equally well. We don't recommend any particular repository. Consult a system administrator or Ubuntu reference for more information.
    +
    importantImportant: The following sections discuss suggested PHP upgrade paths. Because you're choosing a non-Ubuntu repository to upgrade PHP, make your choice carefully. Not all repositories work equally well. We don't recommend any particular repository. Consult a system administrator or Ubuntu reference for more information.

    To upgrade your version of PHP, see one of the following:

    • Upgrade to PHP 5.5: PHP site and dev-metal.
    • @@ -163,7 +163,7 @@

      Installing PHP 5.5 on Ubuntu 14

      apt-get -y install php5

      Installing Required PHP Extensions

      -

      Enter the following command to install PHP extensions required by Magento: +

      Enter the following command to install PHP extensions required by Magento:

      apt-get -y install php5 php5-mhash php5-mcrypt php5-curl php5-cli php5-mysql php5-gd libapache2-mod-php5

      Increasing the PHP memory Limit

      @@ -229,5 +229,8 @@

      Installing MySQL 5.6 on Ubuntu 14

      Next Steps

      -

      After installing the required prerequisite software, continue your installation with Preparing Your Server for Magento CE or EE.

      +

      After installing the required prerequisite software, continue your installation with Preparing Your Server for Magento CE or EE.

      +
    + + \ No newline at end of file diff --git a/guides/m1x/install/installing_upgrade_ce18_upgrade-roadmap.html b/guides/m1x/install/installing_upgrade_ce18_upgrade-roadmap.html index 96184b3a7f..638d152999 100644 --- a/guides/m1x/install/installing_upgrade_ce18_upgrade-roadmap.html +++ b/guides/m1x/install/installing_upgrade_ce18_upgrade-roadmap.html @@ -18,8 +18,8 @@ - -header + +header {% include m1x/eol_message.html %}

    Upgrade Roadmap for Magento Community Edition (CE) 1.8 or 1.9

    @@ -30,7 +30,7 @@

    Upgrade Roadmap for Magento Community Edition (CE) 1.8 or 1.9

    Magento recommends you upgrade your installation using the following guidelines in a development or test environment, separate from your existing production environment:

    1. Install Magento in a different directory:
      • Recommended. Set up a new system (that is, another host) on which to install Magento.
        -The system should be identical to, if not better than, your current system. The new system must meet the Magento system requirements.
      • +The system should be identical to, if not better than, your current system. The new system must meet the Magento system requirements.
      • Install Magento in a new, empty root installation directory on the same server.
    2. In your current production environment: @@ -51,5 +51,7 @@

      Upgrade Roadmap for Magento Community Edition (CE) 1.8 or 1.9

    3. Test the development system thoroughly, including:
      • Verify all extensions, themes, and customizations work.
      • Place orders using all webstores and all payment methods.
    - -

    When you're ready to start your upgrade, see Upgrading to and Verifying Magento Community Edition 1.8 and Enterprise Edition 1.13 - Part 2.

    +

    When you're ready to start your upgrade, see Upgrading to and Verifying Magento Community Edition 1.8 and Enterprise Edition 1.13 - Part 2.

    +
    + + \ No newline at end of file diff --git a/guides/m1x/install/installing_upgrade_details.html b/guides/m1x/install/installing_upgrade_details.html index 28823d7840..de638f85e3 100644 --- a/guides/m1x/install/installing_upgrade_details.html +++ b/guides/m1x/install/installing_upgrade_details.html @@ -15,12 +15,12 @@ - -header + +header {% include m1x/eol_message.html %}

    Upgrading to and Verifying Magento Community Edition and Enterprise Edition—Part 2

    -

    Edit this page on GitHub

    +

    Edit this page on GitHub

    Table of Contents

    @@ -41,29 +41,29 @@

    Overview

    This article discusses how you upgrade to:

    • Magento Community Edition (CE) 1.8 or 1.9.x
    • Magento Enterprise Edition (EE) 1.13.0.2, 1.13.1, or 1.14.x
    -
    importantImportant: Magento recommends CE 1.9.1.0 or later or EE 1.14.1.0 or later for all CE and EE installations and upgrades to get the latest fixes, features, and security updates.
    +
    importantImportant: Magento recommends CE 1.9.1.0 or later or EE 1.14.1.0 or later for all CE and EE installations and upgrades to get the latest fixes, features, and security updates.

    Because of changes to URL rewrites, the following upgrades are more complex than other upgrades.

    • Upgrading from EE 1.12 or earlier to EE 1.14.x
    • Upgrading from EE 1.13.0.0 or EE 1.13.0.1 to EE 1.14.x
    -
    noteNote: If you're upgrading from EE 1.13.0.2 to EE 1.13.1.0 or later, your upgrade doesn't involve changes to URL rewrites and you can skip many of the steps discussed in the other upgrades. Continue with Getting Ready For Your Upgrade.
    +
    noteNote: If you're upgrading from EE 1.13.0.2 to EE 1.13.1.0 or later, your upgrade doesn't involve changes to URL rewrites and you can skip many of the steps discussed in the other upgrades. Continue with Getting Ready For Your Upgrade.

    Upgrade Roadmaps

    -

    Getting Ready For Your Upgrade

    This section discusses how to get ready for your upgrade by backing up the database and customizations on the file system. The steps that follow do not affect your current production system. You can continue serving customers with no downtime.

    To get ready for your upgrade:

    -
    1. Get the Magento installation archive as discussed in Getting Magento CE or EE.
    2. +
      1. Get the Magento installation archive as discussed in Getting Magento CE or EE.
      2. Install Magento in a different directory:
        • Recommended. Set up a new system (that is, another host) on which to install Magento.
          -The system should be identical to, if not better than, your current system. The new system must meet the Magento system requirements.
        • +The system should be identical to, if not better than, your current system. The new system must meet the Magento system requirements.
        • Install Magento in a new, empty root installation directory on the same server.
        • -
          importantImportant: Do not upgrade Magento in the same directory on the same server because post-upgrade errors are likely to occur.
        -
      3. +
        importantImportant: Do not upgrade Magento in the same directory on the same server because post-upgrade errors are likely to occur.
        +
      4. Magento strongly recommends you observe the following guidelines when you set up the Magento database in your development environment:
        • Magento for the first time uses MySQL database triggers to improve database access during reindexing. Magento does not support any custom triggers in the Magento database because custom triggers can introduce incompatibilities with future Magento versions.
        • @@ -96,7 +96,7 @@

          Enabling Exception Logging

          This enables you to enable exception logging so you'll see exceptions in the development environment after the upgrade.
        • In the right pane, click Log Settings to expand it.
          The following figure shows an example.
          -
        • +
        • From the Enabled list, click Yes.
        • Optionally change the names of the log files.
        • Click Save Config.
      @@ -117,10 +117,10 @@

      Disabling cron Jobs

      The Index Mode list displays.
    3. From the Index Mode list, click Manual Update.
      The following figure shows an example.
      -
    4. +
    5. At the top right corner, click Submit.
    6. Make sure all indexers are now set for Manual Update as the following figure shows.
      -
    --> + -->

    Setting All Indexers for Update on Save

    This section applies to upgrading Magento EE only. Skip this section if you're using Magento CE.

    @@ -132,10 +132,10 @@

    Setting All Indexers for Update on Save

    Running the URL Redirect Script (EE 1.13.0.0 and 1.13.0.1 only)

    -

    If you're upgrading to EE 1.14 from EE 1.13.0.0 or 1.13.0.1, see EE 1.13.1.0 Upgrade: Running the EE 1.13.0.0 or EE 1.13.0.1 URL Redirect Script now. When you're done, return here to continue your upgrade.

    +

    If you're upgrading to EE 1.14 from EE 1.13.0.0 or 1.13.0.1, see EE 1.13.1.0 Upgrade: Running the EE 1.13.0.0 or EE 1.13.0.1 URL Redirect Script now. When you're done, return here to continue your upgrade.

    Completing the Magento Upgrade

    To complete the upgrade, go to your Magento base URL in a web browser. The first time you go to your Magento base URL, server-side scripts run to update the database. Depending on the amount of data in your database, this process can take a long time.

    -
    importantImportant: Completing the upgrade requires downtime on your production system. If you continue to take orders on your production system, there is no way to reconcile all of the new orders in the replacement development system. You can reduce the amount of downtime to a minimum by thoroughly testing your development system before shutting down production.
    +
    importantImportant: Completing the upgrade requires downtime on your production system. If you continue to take orders on your production system, there is no way to reconcile all of the new orders in the replacement development system. You can reduce the amount of downtime to a minimum by thoroughly testing your development system before shutting down production.
    -

    If you're upgrading from a version earlier than CE 1.4 or EE 1.7, Magento strongly recommends the two-step upgrade approach discussed in Upgrade Path. In addition, you should expect the upgrade and testing process to take a long time and to expect more downtime for your production system.

    +

    If you're upgrading from a version earlier than CE 1.4 or EE 1.7, Magento strongly recommends the two-step upgrade approach discussed in Upgrade Path. In addition, you should expect the upgrade and testing process to take a long time and to expect more downtime for your production system.

    Complete the following tasks in the order shown:

    1. Running the Upgrade Scripts and Fixing Exceptions
    2. Running the URL Redirect Script (EE 1.12.x and earlier only)
    3. @@ -439,10 +438,10 @@

      Completing the Magento Upgrade

      Running the Upgrade Scripts and Fixing Exceptions

      The first step in your upgrade is to run server-side upgrade scripts. Depending on the nature of your customizations and extensions, and how many customers and products are in your database, these scripts can take a long time to run and can result in exceptions. You must resolve all exceptions before continuing to the next step in the process.

      This step in the upgrade process is iterative; that is, you'll probably run through it more than once.

      -
      noteNote: Your production system remains up during this step in the upgrade process. You can continue taking and shipping orders and also making changes in the Admin Panel.
      +
      noteNote: Your production system remains up during this step in the upgrade process. You can continue taking and shipping orders and also making changes in the Admin Panel.

      To run the upgrade scripts:

      1. In a web browser address or location field, enter your Magento installation's base URL.
        -
        noteNote: If you upgraded Magento on the same server, you might need to update your Apache web server's virtual host configuration to reference the new Magento installation directory. For more information about configuring virtual hosts, see the Apache Virtual Host documentation.
        +
        noteNote: If you upgraded Magento on the same server, you might need to update your Apache web server's virtual host configuration to reference the new Magento installation directory. For more information about configuring virtual hosts, see the Apache Virtual Host documentation.
        (You updated the Magento database with the development system base URL as discussed in Updating the Magento Database.)
      2. Wait while upgrade scripts run on the server.
      3. @@ -455,7 +454,7 @@

        Running the Upgrade Scripts and Fixing Exception
      4. Use the following command to delete the contents of the Magento var/ subdirectories:
        rm -rf [your Magento install dir]/var/cache [your Magento install dir]/var/full_page_cache \
         	[your Magento install dir]/var/locks [your Magento install dir]/var/session
        -
        noteNote: Some of these directories might be empty; this is normal.
      5. +
        noteNote: Some of these directories might be empty; this is normal.
      6. Clean up the file system as discussed in Finishing the File System.
      7. Repeat step 1 in this section.
      8. Repeat the tasks discussed in this section until no more fatal errors display in the browser.
      @@ -471,7 +470,7 @@

      Post-Upgrade Tasks (EE 1.13.0.1 Only)

      Continue with Setting Up Magento Cron Jobs.

      Running the URL Redirect Script (EE 1.12.x and Earlier Only)

      -

      If you're upgrading to EE 1.14 from EE 1.12 or earlier, see EE 1.14 Upgrade: Running the EE 1.12 and Earlier URL Redirect Script now. When you're done, return here to continue your upgrade.

      +

      If you're upgrading to EE 1.14 from EE 1.12 or earlier, see EE 1.14 Upgrade: Running the EE 1.12 and Earlier URL Redirect Script now. When you're done, return here to continue your upgrade.

      Setting Up the Magento Cron Job

      -

      You should now set up your Magento cron job as discussed here.

      +

      You should now set up your Magento cron job as discussed here.

      Clearing Magento var/ Subdirectories

      Run the following command to clean the Magento var/ subdirectories:

      rm -rf [your Magento install dir]/var/cache [your Magento install dir]/var/full_page_cache [your Magento install dir]/var/locks
      -
      noteNote: Some of these directories might be empty; this is normal.
      +
      noteNote: Some of these directories might be empty; this is normal.

      Verifying the Status of Indexers

      After the cron job runs, all indexers should be in a Ready status. Before testing your upgrade, verify all indexers are Ready; otherwise, your testing will be inconclusive.

      @@ -494,7 +493,7 @@

      Verifying the Status of Indexers

      1. Log in to the Admin Panel as an administrator.
      2. Click System > Index Management.
        Verify that all indexers have a status of Ready, as the following figure shows.
        -
      3. +
      4. If indexers are not Ready, use the following guidelines: @@ -518,13 +517,13 @@

        Testing the Magento Upgrade

        1. Test all extensions and customizations thoroughly.
          Make sure the UIs perform as expected, make sure the extensions behave properly, and so on.
        2. Run some orders, making sure prices are calculated correctly and that orders go through the configured payment mechanisms.
        3. -
        4. If you encounter issues, get help.
        5. +
        6. If you encounter issues, get help.
        7. Before making the development system live, back up everything in your production and development environments again.
          The way you make your development system live is up to you; a simple way is to update your DNS server to point to the development IP address.

        Taking Your Old Production System Offline

        The last step in upgrading is to take your production system offline and switching to your development system—which then becomes the production system from that point on.

        -
        importantImportant: Before continuing, make sure all errors have been resolved and that you have thoroughly tested the upgrade as discussed in the preceding section.
        +
        importantImportant: Before continuing, make sure all errors have been resolved and that you have thoroughly tested the upgrade as discussed in the preceding section.

        To switch from your production to development system:

        1. Put your production system in maintenance mode so it cannot accept orders or other changes.
          To do so, create an empty file named [your Magento install dir]/maintenance.flag.
        2. @@ -538,10 +537,10 @@

          Taking Your Old Production System Offline

          The way you do this is up to you; typically, you can configure your DNS server to send requests for your web store domain to the development system's IP address. Be aware that propagating the change to other DNS servers can take some time.
        3. Verify your former development system is functioning as your new Magento web store in production.
        4. Shut down the old production system.
        -

        Congratulations! You successfully upgraded! Review our welcome page to see the improvements you're getting.

        +

        Congratulations! You successfully upgraded! Review our welcome page to see the improvements you're getting.

        Setting Magento File System Permissions and Ownership After Upgrade

        -

        To secure your Magento installation after the upgrade, see After You Install Magento: Recommended File System Ownership and Privileges.

        +

        To secure your Magento installation after the upgrade, see After You Install Magento: Recommended File System Ownership and Privileges.

        Troubleshooting

        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.

        @@ -554,6 +553,7 @@

        Troubleshooting

        [your Magento install dir]/app/code/core/Mage/GoogleCheckout/etc
      5. When you log back in to the Admin Panel, everything works as expected.
      6. -

        In the event of any other issue during the upgrade, see Getting Help With Your Installation or Upgrade.

        +

        In the event of any other issue during the upgrade, see Getting Help With Your Installation or Upgrade.

        -

        + + \ No newline at end of file diff --git a/guides/m1x/install/installing_upgrade_from-ee112.html b/guides/m1x/install/installing_upgrade_from-ee112.html index a7f78c9ce2..a61036a278 100644 --- a/guides/m1x/install/installing_upgrade_from-ee112.html +++ b/guides/m1x/install/installing_upgrade_from-ee112.html @@ -18,8 +18,8 @@ - -header + +header {% include m1x/eol_message.html %}
        @@ -31,9 +31,9 @@

        EE 1.14 Upgrade: Running the EE 1.12 and Earlier URL Redirect Script

        • From EE 1.12.x or earlier to EE 1.13.0.2
        • From EE 1.12.x or earlier to EE 1.13.1.0
        • From EE 1.12.x or earlier to EE 1.14.0.0
        -

        If your upgrade is not in the preceding list, go back to Upgrading to and Verifying Magento Community Edition (CE) 1.8 and Enterprise Edition (EE) 1.13.

        +

        If your upgrade is not in the preceding list, go back to Upgrading to and Verifying Magento Community Edition (CE) 1.8 and Enterprise Edition (EE) 1.13.

        This article discusses how to run the URL redirect script that creates HTTP 301 (Moved Permanently) redirects for any duplicate product URL keys. This enables Previous links in your web store to work, for example.

        - +

        To create redirects for your URLs, perform the following tasks in the order shown:

        1. Verifying that cron is Disabled
        2. Changing Indexer Settings to Update When Scheduled
        3. @@ -57,9 +57,9 @@

          Changing Indexer Settings to
        4. In the right pane, expand Index Options.
        5. Click Update when scheduled from the list for every indexer.
          The following figure shows an example.
          -
        6. +
        7. In the upper right corner, click Save Config.
          -
          noteNote: Ignore any messages requesting you to reindex or flush the cache; you'll do that later.
        8. +
          noteNote: Ignore any messages requesting you to reindex or flush the cache; you'll do that later.
        9. Log out of the Admin Panel.
        10. If the script ran without errors, continue with Running the URL Redirect Script.
        @@ -76,7 +76,7 @@

        Reindexing

        Running the URL Redirect Script

        This section discusses how to run the URL redirect script to create permanent redirects for any URLs that changed in EE 1.13.1.0.

        -
        noteNote: The time the script takes to run and the amount of memory it uses is directly proportional to the size of your database. If your database has 100,000 SKUs or more, Magento strongly recommends you monitor thread execution as discussed in this section. For large databases, the script can require several hours to complete.
        +
        noteNote: The time the script takes to run and the amount of memory it uses is directly proportional to the size of your database. If your database has 100,000 SKUs or more, Magento strongly recommends you monitor thread execution as discussed in this section. For large databases, the script can require several hours to complete.

        To run the script:

        1. Change to your Magento installation directory.
        2. @@ -85,7 +85,7 @@

          Running the URL Redirect Script thread_count is the number of threads to use. Magento recommends setting this to the number of CPU cores in your system minus 1 to a maximum of 15. For example, if your system has 8 CPU cores, enter
          php -f shell/url_migration_to_1_13.php 7
          -
          noteNote: Each thread can use up to 512MB of RAM.
          +
          noteNote: Each thread can use up to 512MB of RAM.
        3. Wait while the script runs.
          Messages like the following display to indicate progress:
          [INFO]: Initialization...
          @@ -113,16 +113,16 @@ 

          Running the URL Redirect Script

          This error can be caused by either a product or category url_key attribute being set for Global scope. To determine which type of url_key attribute is causing the error:

          1. Log in as an administrator to the Admin Panel of the production system (in other words, the system you're upgrading from).
          2. Click Catalog > Attributes > Manage Attributes.
          3. -
          4. Click the url_key row.
          5. +
          6. Click the url_key row.
          7. Examine the value of the Scope list. A sample follows.
            -
          8. +
          9. If the value in the Scope list is Global:
            1. Select another value from the list. You can select any value other than Global.
            2. Click Save Attribute.
            3. Log out of the Admin Panel.
            4. -
            5. Re-export the database as discussed in Backing Up the Database.
            6. -
            7. In the development system, drop and re-create the database as discussed in Pre-Upgrade Tasks for Your Development Environment.
            8. -
            9. Import the database you just exported as discussed in Updating the Magento Database.
            10. +
            11. Re-export the database as discussed in Backing Up the Database.
            12. +
            13. In the development system, drop and re-create the database as discussed in Pre-Upgrade Tasks for Your Development Environment.
            14. +
            15. Import the database you just exported as discussed in Updating the Magento Database.
            16. Try running the upgrade script again.
          10. If the value of the Scope list is not Global, the issue is likely that the category url_key attribute is set to global. To confirm this: @@ -157,13 +157,17 @@

            Viewing the List of Redir All redirects created by the URL redirect script display the following description:
            1.12.0.2-1.13.x migration redirect
            The following figure shows an example.
            -

          +

        Verifying That URLs Work Properly

        Assuming all your post-upgrade issues are fixed, go to your web store and navigate the category tree. Click some products and make sure they display properly. Verify that all Previous and Back links work properly.

        Completing Your Upgrade

        Complete your upgrade:

        -
        1. Setting Up the Magento Cron Job
        2. -
        3. Clearing Magento var/ Subdirectories
        4. -
        5. Complete the remainder of the tasks on that page in the order shown
        \ No newline at end of file +
        1. Setting Up the Magento Cron Job
        2. +
        3. Clearing Magento var/ Subdirectories
        4. +
        5. Complete the remainder of the tasks on that page in the order shown
        + +
        + + \ No newline at end of file diff --git a/guides/m1x/install/installing_upgrade_from-ee11300-or-01.html b/guides/m1x/install/installing_upgrade_from-ee11300-or-01.html index 47bf5cb5e1..def267e339 100644 --- a/guides/m1x/install/installing_upgrade_from-ee11300-or-01.html +++ b/guides/m1x/install/installing_upgrade_from-ee11300-or-01.html @@ -16,12 +16,12 @@ - -header + +header {% include m1x/eol_message.html %}

        EE 1.14 Upgrade: Running the EE 1.13.0.0 or EE 1.13.0.1 URL Redirect Script

        -

        Edit this page on GitHub

        +

        Edit this page on GitHub

        @@ -31,7 +31,7 @@

        EE 1.14 Upgrade: Running the EE 1.13.0.0 or EE 1.13.0.1 URL Redirect Script<
        • From EE 1.13.0.1 to EE 1.13.0.2
        • From EE 1.13.0.1 to EE 1.13.1.0
        • From EE 1.13.0.1 to EE 1.14.0.0
        -

        If your upgrade is not in the preceding list, skip this article and continue with Completing the Magento Upgrade.

        +

        If your upgrade is not in the preceding list, skip this article and continue with Completing the Magento Upgrade.

        This article discusses how to run the URL redirect script that creates HTTP 301 (Moved Permanently) redirects for any duplicate product URL keys. This enables Previous links in your web store to work, for example.

        For more information about URL changes, see the EE 1.13.0.2 Release Notes. (Release Notes for the latest release are here.)

        To create redirects for your URLs, perform the following tasks in the order shown:

        @@ -57,13 +57,13 @@

        Running the Script

        [INFO]: Start root category "Default Category" processing ... [INFO]: Start root category "test" processing ... [INFO]: Executed in time -
      7. If the script succeeded, continue with Completing the Magento Upgrade.
      8. +
      9. If the script succeeded, continue with Completing the Magento Upgrade.
      10. Troubleshooting

        If errors display, check [your Magento install dir]/shell/migration.log for exceptions. Following are errors that might display when you run the migration script:

        • Application is not installed yet, please complete install wizard first
        • PHP Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[28000] [1045] Access denied for user 'name'@'hostname' (using password: YES)' in /var/www/magento/lib/Zend/Db/Adapter/Pdo/Abstract.php

        If one of these displays, make sure you copied [your Magento install dir]/app/etc/local.xml from your development system to the production system. Edit it if necessary to reference the production database instance. After you copy and edit local.xml, run the URL redirect script again.

        -

        Continue your upgrade with Completing the Magento Upgrade.

        +

        Continue your upgrade with Completing the Magento Upgrade.

        \ No newline at end of file diff --git a/guides/m1x/install/installing_upgrade_landing.html b/guides/m1x/install/installing_upgrade_landing.html index 4b2ce47f84..55d1585020 100644 --- a/guides/m1x/install/installing_upgrade_landing.html +++ b/guides/m1x/install/installing_upgrade_landing.html @@ -18,12 +18,12 @@ - -header + +header {% include m1x/eol_message.html %}

        Upgrading to and Verifying Magento Community Edition (CE) and Enterprise Edition (EE), Part 1

        -

        Edit this page on GitHub

        +

        Edit this page on GitHub

        @@ -39,7 +39,7 @@

        Overview

      11. Magento Enterprise Edition (EE) 1.13 or 1.14
      12. Upgrade Path

        -
        importantImportant: Magento recommends CE 1.9.1.0 or later or EE 1.14.1.0 or later for all CE and EE installations and upgrades to get the latest fixes, features, and security updates.
        +
        importantImportant: Magento recommends CE 1.9.1.0 or later or EE 1.14.1.0 or later for all CE and EE installations and upgrades to get the latest fixes, features, and security updates.

        The following table provides basic information about how you perform your upgrade. More detailed information is discussed later in this article.

        @@ -73,11 +73,11 @@

        Magento EE Upgrade Path

        • Upgrading from EE 1.12 or earlier to EE 1.13.0.2 or later (including to EE 1.14)
        • Upgrading from EE 1.13.0.1 to EE 1.13.0.2 or later (including to EE 1.14)

        For more information about these upgrades, see Understanding the Upgrade to EE 1.13.0.2 or EE 1.14.

        -
        noteNote: If you're upgrading from EE 1.13.0.2 to EE 1.13.1.0 or later, your upgrade doesn't involve changes to URL rewrites and you can skip some of the steps discussed in the other upgrades. Continue with Upgrading to and Verifying Magento Community Edition (CE) and Enterprise Edition (EE)—Part 2.
        +
        noteNote: If you're upgrading from EE 1.13.0.2 to EE 1.13.1.0 or later, your upgrade doesn't involve changes to URL rewrites and you can skip some of the steps discussed in the other upgrades. Continue with Upgrading to and Verifying Magento Community Edition (CE) and Enterprise Edition (EE)—Part 2.

        Upgrading to Magento CE 1.9

        -

        Unless you're upgrading from an older CE version, skip the remainder of this article and continue with Upgrade Roadmap for Community Edition (CE).

        +

        Unless you're upgrading from an older CE version, skip the remainder of this article and continue with Upgrade Roadmap for Community Edition (CE).

        - - -header +header {% include m1x/eol_message.html %} - - - - +

        Magento for Developers: Part 1—Introduction to Magento

        @@ -38,14 +33,14 @@

        Magento for Developers: Part 1—Introduction to Magento

        -->

        Other articles in this series:

        What is Magento? It's the most powerful online eCommerce platform in the universe and is changing the face of eCommerce forever. :-)

        @@ -67,34 +62,34 @@

        In this article...

      13. Wrap Up -

        Or for the more visually oriented Magento_MVC.pdf. +

        Or for the more visually oriented Magento_MVC.pdf.


        Code Organized in Modules

        -

        Magento organizes its code into individual Modules. In a typical PHP Model-View-Controller (MVC) application, all the Controllers will be in one folder, all the Models in another, etc. In Magento, files are grouped together based on functionality, which are called modules in Magento. +

        Magento organizes its code into individual Modules. In a typical PHP Model-View-Controller (MVC) application, all the Controllers will be in one folder, all the Models in another, etc. In Magento, files are grouped together based on functionality, which are called modules in Magento.

        Magento's Code

        -

        For example, you'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's checkout functionality in +

        For example, you'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's checkout functionality in

        app/code/core/Mage/Checkout
        -

        You'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's Google Checkout functionality in +

        You'll find Controllers, Models, Helpers, Blocks, etc. related to Magento's Google Checkout functionality in

        app/code/core/Mage/GoogleCheckout

        Your Code

        -

        When you want to customize or extend Magento, rather than editing core files directly, or even placing your new Controllers, Models, Helpers, Blocks, etc. next to Magento code, you'll create your own Modules in +

        When you want to customize or extend Magento, rather than editing core files directly, or even placing your new Controllers, Models, Helpers, Blocks, etc. next to Magento code, you'll create your own Modules in

        app/code/local/Package/Modulename

        Package (also often referred to as a Namespace) is a unique name that identifies your company or organization. The intent is that each member of the world-wide Magento community will use their own Package name when creating modules in order to avoid colliding with another user's code.

        -

        When you create a new Module, you need to tell Magento about it. This is done by adding an XML file to the folder: +

        When you create a new Module, you need to tell Magento about it. This is done by adding an XML file to the folder:

        app/etc/modules
        -

        There are two kinds of files in this folder, the first enables an individual Module, and is named in the form: +

        There are two kinds of files in this folder, the first enables an individual Module, and is named in the form:

        Packagename_Modulename.xml -

        The second is a file that will enable multiple Modules from a Package/Namespace, and is named in the form: +

        The second is a file that will enable multiple Modules from a Package/Namespace, and is named in the form:

        Packagename_All.xml. Note it is only used by the core team with the file Mage_All.xml. It is not recommended to activate several modules in a single file, as this breaks the modularity of your modules. @@ -102,7 +97,7 @@

        Configuration-Based MVC

        Magento is a configuration-based MVC system. The alternative to this would a convention-based MVC system.

        -

        In a convention-based MVC system, if you wanted to add, say, a new Controller or maybe a new Model, you'd just create the file/class, and the system would pick it up automatically. +

        In a convention-based MVC system, if you wanted to add, say, a new Controller or maybe a new Model, you'd just create the file/class, and the system would pick it up automatically.

        In a configuration-based system, like Magento, in addition to adding the new file/class to the codebase, you often need to explicitly tell the system about the new class, or new group of classes. In Magento, each Module has a file named config.xml. This file contains all the relevant configuration for a Magento Module. At runtime, all these files are loaded into one large configuration tree.

        @@ -120,30 +115,30 @@

        Configuration-Based MVC

        Controllers

        -

        In any PHP system, the main PHP entry point remains a PHP file. Magento is no different, and that file is index.php. +

        In any PHP system, the main PHP entry point remains a PHP file. Magento is no different, and that file is index.php.

        -

        However, you never CODE in index.php. In an MVC system, index.php will contain code/calls to code that does the following: +

        However, you never CODE in index.php. In an MVC system, index.php will contain code/calls to code that does the following:

        1. Examines the URL

        2. Based on some set of rules, turns this URL into a Controller class and an Action method (called Routing)

        3. Instantiates the Controller class and calls the Action method (called dispatching)

        -

        This means the practical entry point in Magento (or any MVC-based system) is a method in a Controller file. Consider the following URL: +

        This means the practical entry point in Magento (or any MVC-based system) is a method in a Controller file. Consider the following URL:

        http://example.com/catalog/category/view/id/25
        -

        Each portion of the path after the server name is parsed as follows. +

        Each portion of the path after the server name is parsed as follows.

        Front Name - catalog

        -

        The first portion of the URL is called the front name. This, more or less, tells magento which Module it can find a Controller in. In the above example, the front name is catalog, which corresponds to the Module located at: +

        The first portion of the URL is called the front name. This, more or less, tells magento which Module it can find a Controller in. In the above example, the front name is catalog, which corresponds to the Module located at:

        app/code/core/Mage/Catalog

        Controller Name - category

        -

        The second portion of the URL tells Magento which Controller it should use. Each Module with Controllers has a special folder named 'controllers' which contains all the Controllers for a module. In the above example, the URL portion category is translated into the Controller file +

        The second portion of the URL tells Magento which Controller it should use. Each Module with Controllers has a special folder named 'controllers' which contains all the Controllers for a module. In the above example, the URL portion category is translated into the Controller file

        app/code/core/Mage/Catalog/controllers/CategoryController.php
        -

        Which looks like +

        Which looks like

         class Mage_Catalog_CategoryController extends Mage_Core_Controller_Front_Action
         {
        @@ -180,7 +175,7 @@ 

        Parameter/Value - id/25

        <catalog> <use>standard</use> <args> - <module>Mage_Catalog</module> + <module>Mage_Catalog</module> <frontName>catalog</frontName> </args> </catalog> @@ -188,7 +183,7 @@

        Parameter/Value - id/25

        </frontend>
        -

        Don't worry too much about the specifics right now, but notice the +

        Don't worry too much about the specifics right now, but notice the

        <frontName>catalog</frontName> @@ -198,7 +193,7 @@

        Parameter/Value - id/25

        Multiple Routers

        -

        The routing described above is for the Magento cart application (often called the frontend). If Magento doesn't find a valid Controller/Action for a URL, it tries again, this time using a second set of Routing rules for the Admin application. If Magento doesn't find a valid Admin Controller/Action, it uses a special Controller named Mage_Cms_IndexController. +

        The routing described above is for the Magento cart application (often called the frontend). If Magento doesn't find a valid Controller/Action for a URL, it tries again, this time using a second set of Routing rules for the Admin application. If Magento doesn't find a valid Admin Controller/Action, it uses a special Controller named Mage_Cms_IndexController.

        The CMS Controller checks Magento's content Management system to see if there's any content that should be loaded. If it finds some, it loads it, otherwise the user will be presented with a 404 page.

        @@ -207,18 +202,18 @@

        Multiple Routers

        Context-Based URI Model Loading

        -

        Now that we're in our Action method entry point, we'll want to start instantiating classes that do things. Magento offers a special way to instantiate Models, Helpers and Blocks using static factory methods on the global Mage class. For example: +

        Now that we're in our Action method entry point, we'll want to start instantiating classes that do things. Magento offers a special way to instantiate Models, Helpers and Blocks using static factory methods on the global Mage class. For example:

         Mage::getModel('catalog/product');
         Mage::helper('catalog/product');
         
        -

        The string 'catalog/product' is called a Grouped Class Name. It's also often called a URI. The first portion of any Grouped Class Name (in this case, catalog), is used to lookup which Module the class resides in. The second portion ('product' above) is used to determine which class should be loaded. +

        The string 'catalog/product' is called a Grouped Class Name. It's also often called a URI. The first portion of any Grouped Class Name (in this case, catalog), is used to lookup which Module the class resides in. The second portion ('product' above) is used to determine which class should be loaded.

        -

        So, in both of the examples above, 'catalog' resolves to the Module app/code/core/Mage/Catalog. +

        So, in both of the examples above, 'catalog' resolves to the Module app/code/core/Mage/Catalog.

        -

        Meaning our class name will start with Mage_Catalog. +

        Meaning our class name will start with Mage_Catalog.

        Then, product is added to get the final class name

        @@ -230,7 +225,7 @@

        Context-Based URI Model Loading

        Mage_Catalog_Helper_Product -

        These rules are bound by what's been setup in each Module's config file. When you create your own custom Module, you'll have your own grouped classnames (also calles classgroups) to work with Mage::getModel('myspecialprefix/modelname');. +

        These rules are bound by what's been setup in each Module's config file. When you create your own custom Module, you'll have your own grouped classnames (also calles classgroups) to work with Mage::getModel('myspecialprefix/modelname');.

        You don't have to use Grouped Class Names to instantiate your classes. However, as we'll learn later, there are certain advantages to doing so.

        @@ -238,7 +233,7 @@

        Context-Based URI Model Loading

        Magento Models

        -

        Magento, like most frameworks these days, offers an Object Relational Mapping (ORM) system. ORMs get you out of the business of writing SQL and allow you to manipulate a datastore purely through PHP code. For example: +

        Magento, like most frameworks these days, offers an Object Relational Mapping (ORM) system. ORMs get you out of the business of writing SQL and allow you to manipulate a datastore purely through PHP code. For example:

         $model = Mage::getModel('catalog/product')->load(27);
        @@ -248,15 +243,15 @@ 

        Magento Models

        $model->save();
        -

        In the above example we're calling the methods "getPrice" and "setPrice" on our Product. However, the Mage_Catalog_Model_Product class has no methods with these names. That's because Magento's ORM uses PHP's magic __call method to implement getters and setters. +

        In the above example we're calling the methods "getPrice" and "setPrice" on our Product. However, the Mage_Catalog_Model_Product class has no methods with these names. That's because Magento's ORM uses PHP's magic __call method to implement getters and setters.

        -

        Calling the method $product->getPrice(); will "get" the Model attribute "price". +

        Calling the method $product->getPrice(); will "get" the Model attribute "price".

        -

        Calling $product->setPrice(); will "set" the Model attribute "price". All of this assumes the Model class doesn't already have methods named getPrice or setPrice. If it does, the magic methods will be bypassed. If you're interested in the implementation of this, checkout the Varien_Object class, which all Models inherit from. +

        Calling $product->setPrice(); will "set" the Model attribute "price". All of this assumes the Model class doesn't already have methods named getPrice or setPrice. If it does, the magic methods will be bypassed. If you're interested in the implementation of this, checkout the Varien_Object class, which all Models inherit from.

        -

        If you wanted to get all the available data on a Model, call $product->getData(); to get an array of all the attributes. +

        If you wanted to get all the available data on a Model, call $product->getData(); to get an array of all the attributes.

        -

        You'll also notice it's possible to chain together several calls to the set method:
        +

        You'll also notice it's possible to chain together several calls to the set method:

        $model->setPrice($price)->setSku('SK83293432');

        That's because each set method returns an instance of the Model. This is a pattern you'll see used in much of the Magento codebase.

        @@ -286,13 +281,13 @@

        Magento Models

        Helpers

        -

        Magento's Helper classes contain utility methods that will allow you to perform common tasks on objects and variables. For example:
        +

        Magento's Helper classes contain utility methods that will allow you to perform common tasks on objects and variables. For example:

        > $helper = Mage::helper('catalog'); -

        You'll notice we've left off the second part of the grouped class name. Each Module has a default Data Helper class. The following is equivalent to the above:
        +

        You'll notice we've left off the second part of the grouped class name. Each Module has a default Data Helper class. The following is equivalent to the above:

        $helper = Mage::helper('catalog/data'); -

        Most Helpers inherit form Mage_Core_Helper_Abstract, which gives you several useful methods by default. +

        Most Helpers inherit form Mage_Core_Helper_Abstract, which gives you several useful methods by default.

         $translated_output =  $helper->__('Magento is Great'); //gettext style translations
         if($helper->isModuleOutputEnabled()): //is output for this module on or off?
        @@ -331,20 +326,20 @@ 

        Layouts

        }
        -

        Instead, the Controller action ends with two calls +

        Instead, the Controller action ends with two calls

         $this->loadLayout();
         $this->renderLayout();
         
        -

        So, the "V" in Magento's MVC already differs from what you're probably used to, in that you need to explicitly kick off rendering the layout. +

        So, the "V" in Magento's MVC already differs from what you're probably used to, in that you need to explicitly kick off rendering the layout.

        The layout itself also differs. A Magento Layout is an object that contains a nested/tree collection of "Block" objects. Each Block object will render a specific bit of HTML. Block objects do this through a combination of PHP code, and including PHP .phtml template files.

        Blocks objects are meant to interact with the Magento system to retrieve data from Models, while the phtml template files will produce the HTML needed for a page.

        -

        For example, the page header Block app/code/core/Mage/Page/Block/Html/Head.php uses the head.phtml file page/html/head.phtml. +

        For example, the page header Block app/code/core/Mage/Page/Block/Html/Head.php uses the head.phtml file page/html/head.phtml.

        Another way of thinking about it is the Block classes are almost like little mini-controllers, and the .phtml files are the view.

        @@ -355,7 +350,7 @@

        Layouts

        $this->renderLayout(); -

        Magento will load up a Layout with a skeleton site structure. There will be Structure Blocks to give you your html, head, and body, as well as HTML to setup single or multiple columns of Layout. Additionally, there will be a few Content Blocks for the navigation, default welcome message, etc. +

        Magento will load up a Layout with a skeleton site structure. There will be Structure Blocks to give you your html, head, and body, as well as HTML to setup single or multiple columns of Layout. Additionally, there will be a few Content Blocks for the navigation, default welcome message, etc.

        "Structure" and "Content" are arbitrary designations in the Layout system. A Block doesn't programmatically know if it's Structure or Content, but it's useful to think of a Block as one or the other.

        @@ -393,10 +388,10 @@

        Layouts

        It's saying in the catalog Module, in the category Controller, and the default Action, insert the catalog/navigation Block into the "left" structure Block, using the catalog/navigation/left.phtml template.

        -

        One last important thing about Blocks. You'll often see code in templates that looks like this:
        +

        One last important thing about Blocks. You'll often see code in templates that looks like this:

        $this->getChildHtml('order_items') -

        This is how a Block renders a nested Block. However, a Block can only render a child Block if the child Block is included as a nested Block in the Layout XML file. In the example above our catalog/navigation Block has no nested Blocks. This means any call to $this->getChildHtml() in left.phtml will render as blank. +

        This is how a Block renders a nested Block. However, a Block can only render a child Block if the child Block is included as a nested Block in the Layout XML file. In the example above our catalog/navigation Block has no nested Blocks. This means any call to $this->getChildHtml() in left.phtml will render as blank.

        If, however, we had something like:

        @@ -409,7 +404,7 @@ 

        Layouts

        </catalog_category_default>
        -

        From the catalog/navigation Block, we'd be able to call
        +

        From the catalog/navigation Block, we'd be able to call

        $this->getChildHtml('foobar');
        @@ -434,7 +429,7 @@

        Observers

        </events> -

        and then write some code that would run whenever a user logged in: +

        and then write some code that would run whenever a user logged in:

         class Packagename_Mymodule_Model_Observer
        @@ -453,7 +448,7 @@ 

        Class Overrides

        Finally, the Magento System offers you the ability to replace Model, Helper and Block classes from the core modules with your own. This is a feature that's similar to "Duck Typing" or "Monkey Patching" in a language like Ruby or Python.

        -

        Here's an example to help you understand. The Model class for a product is Mage_Catalog_Model_Product. +

        Here's an example to help you understand. The Model class for a product is Mage_Catalog_Model_Product.

        Whenever the following code is called, a Mage_Catalog_Model_Product object is created

        @@ -507,3 +502,6 @@

        Class Overrides

        Wrap Up

        We hope you've enjoyed this whirlwind tour of some of the features the Magento eCommerce system offers to developers. It can be a little overwhelming at first, especially if this is your first experience with a modern, object-oriented PHP system. If you start to get frustrated, take a deep breath, remind yourself that this is new, and new things are hard, but at the end of the day it's just a different way of coding. Once you get over the learning curve you'll find yourself loath to return to other, less powerful systems.

        + +
      14. + \ No newline at end of file diff --git a/guides/m1x/magefordev/mage-for-dev-2.html b/guides/m1x/magefordev/mage-for-dev-2.html index b3f750efa5..3c94eee744 100644 --- a/guides/m1x/magefordev/mage-for-dev-2.html +++ b/guides/m1x/magefordev/mage-for-dev-2.html @@ -13,17 +13,10 @@ Magento for Developers: Part 2—The Magento Config - - -header +header {% include m1x/eol_message.html %} - - - - -

        Magento for Developers: Part 2—The Magento Config

        by Alan Storm, updated for Magento 1.12

        @@ -38,14 +31,14 @@

        Magento for Developers: Part 2—The Magento Config

        The config is the beating heart of the Magento System. It describes, in whole, almost any module, model, class, template, etc. than you'll need to access. It's a level of abstraction that most PHP developers aren't used to working with, and while it adds development time in the form of confusion and head scratching, it also allows you an unprecedented amount of flexibility as far as overriding default system behaviors go.

        diff --git a/guides/m1x/magefordev/mage-for-dev-3.html b/guides/m1x/magefordev/mage-for-dev-3.html index 66911fe3d0..5e09a7e138 100644 --- a/guides/m1x/magefordev/mage-for-dev-3.html +++ b/guides/m1x/magefordev/mage-for-dev-3.html @@ -12,42 +12,27 @@ Magento for Developers: Part 3—Magento Controller Dispatch - - -header +header {% include m1x/eol_message.html %} - - - - +

        The Model-View-Controller (MVC) architecture traces its origins back to the Smalltalk Programming language and Xerox Parc. Since then, there have been many systems that describe their architecture as MVC. Each system is slightly different, but all have the goal of separating data access, business logic, and user-interface code from one another.

        @@ -162,7 +147,7 @@

        Configuring Routes

        <helloworld> <use>standard</use> <args> - <module>Magentotutorial_Helloworld</module> + <module>Magentotutorial_Helloworld</module> <frontName>helloworld</frontName> </args> </helloworld> @@ -246,12 +231,12 @@

        How should Action Controllers be named?

        Remember the <module> tag back in config.xml?

        -<module>Magentotutorial_Helloworld
        +<module>Magentotutorial_Helloworld</module>
         

        An Action Controller's name will

          -
        1. Start with this string specified in config.xml (Magentotutorial_Helloworld)
        2. +
        3. Start with this <module> string specified in config.xml (Magentotutorial_Helloworld)
        4. Be followed by an underscore (Magentotutorial_Helloworld_)
        5. Which will be followed by the Action Controller's name (Magentotutorial_Helloworld_Index)
        6. And finally, the word "Controller" (Magentotutorial_Helloworld_IndexController)
        7. @@ -275,10 +260,10 @@

          What's that index/index nonsense?

          http://example.com/helloworld -

          If we had a URL that looked like this +

          If we had a URL that looked like this

          http://example.com/checkout/cart/add
          -

          Magento would +

          Magento would

          1. Consult the global config to find the module to use for the frontName checkout (Mage_Checkout)
          2. Look for the cart Action Controller (Mage_Checkout_CartController)
          3. @@ -287,7 +272,7 @@

            What's that index/index nonsense?

            Other Action Controller Tricks

            -

            Let's try adding a non-default method to our Action Controller. Add the following code to IndexController.php +

            Let's try adding a non-default method to our Action Controller. Add the following code to IndexController.php

             public function goodbyeAction() {
            @@ -302,16 +287,16 @@ 

            Other Action Controller Tricks

             public function paramsAction() {
            -    echo '
            '; + echo '<dl>'; foreach($this->getRequest()->getParams() as $key=>$value) { - echo '
            Param: '.$key.'
            '; - echo '
            Value: '.$value.'
            '; + echo '<dt><strong>Param:</strong>'.$key.'</dt>'; + echo '<dt><strong>Value: </strong>'.$value.'</dt>'; } - echo '
            '; + echo '</dl>'; }
            -

            and visit the following URL +

            and visit the following URL

            http://example.com/helloworld/index/params?foo=bar&baz=eof

            You should see each parameter and value printed out.

            diff --git a/guides/m1x/magefordev/mage-for-dev-4.html b/guides/m1x/magefordev/mage-for-dev-4.html index aa74c29c85..ec76055920 100644 --- a/guides/m1x/magefordev/mage-for-dev-4.html +++ b/guides/m1x/magefordev/mage-for-dev-4.html @@ -13,16 +13,11 @@ Magento for Developers: Part 4—Magento Layouts, Blocks and Templates - - -header +header {% include m1x/eol_message.html %} - - - - +

            Developers new to Magento are often confused by the Layout and View system. This article will take a look at Magento's Layout/Block approach, and show you how it fits into Magento MVC worldview.

            diff --git a/guides/m1x/magefordev/mage-for-dev-5.html b/guides/m1x/magefordev/mage-for-dev-5.html index e434bbbace..d47c4189ec 100644 --- a/guides/m1x/magefordev/mage-for-dev-5.html +++ b/guides/m1x/magefordev/mage-for-dev-5.html @@ -13,17 +13,10 @@ Magento for Developers: Part 5—Magento Models and ORM Basics - - -header +header {% include m1x/eol_message.html %} - - - - - @@ -77,9 +70,9 @@

            Anatomy of a Magento Model

            Enable developer mode

            Something you should do in development—but never in production—is to enable Magento's developer mode which, among other things, displays exceptions in your browser. It's useful for debugging your code.

            Enable developer mode in any of the following ways:

            -
            • developer mode -
            • Edit the .htaccess in the Magento root directory file to add SetEnv MAGE_IS_DEVELOPER_MODE "true"

              - +
              • developer mode
              • +
              • Edit the .htaccess in the Magento root directory file to add SetEnv MAGE_IS_DEVELOPER_MODE "true"
              • +

              Creating a Basic Model

              To begin, we're going to create a basic Magento Model. PHP MVC tradition insists we model a weblog post. The steps we'll need to take are

              @@ -108,7 +101,7 @@

              Create a Weblog Module

              <weblog> <use>standard</use> <args> - <module>Magentotutorial_Weblog</module> + <module>Magentotutorial_Weblog</module> <frontName>weblog</frontName> </args> </weblog> @@ -178,7 +171,7 @@

              The Global Config and Creating The Model

              need to create our own resource, can't just use core_resource --> - <resourceModel>weblog_resource</resourceModel> + <resourceModel>weblog_resource</resourceModel> </weblog> </models> <!-- ... --> @@ -229,7 +222,7 @@

              The Global Config and Resources

              So, we've setup our Model. Next, we need to setup our Model Resource. Model Resources contain the code that actually talks to our database. In the last section, we included the following in our config.

              -<resourceModel>weblog_resource
              +<resourceModel>weblog_resource</resourceModel>
               

              The value in <resourceModel /> will be used to instantiate a Model Resource class. Although you'll never need to call it yourself, when any Model in the weblog group needs to talk to the database, Magento will make the following method call to get the Model resource

              @@ -461,3 +454,5 @@

              Model Collections

              Wrapup

              Congratulations, you've created and configured your first Magento Model. In a later article we'll take a look at Magento's Entity Attribute Value Models (EAV), which expand on what we've learned here.

              + + \ No newline at end of file diff --git a/guides/m1x/magefordev/mage-for-dev-6.html b/guides/m1x/magefordev/mage-for-dev-6.html index 229f9b6cdd..bb1fbea0bb 100644 --- a/guides/m1x/magefordev/mage-for-dev-6.html +++ b/guides/m1x/magefordev/mage-for-dev-6.html @@ -13,17 +13,10 @@ Magento for Developers: Part 6—Magento Setup Resources - - -header +header {% include m1x/eol_message.html %} - - - - -

              Magento for Developers: Part 6—Magento Setup Resources

              by Alan Storm, updated for Magento 1.12

              @@ -41,20 +34,20 @@

              Magento for Developers: Part 6—Magento Setup Resources

              Other articles in this series:

              On any fast paced software development project, the task of keeping the development and production databases in sync become a sticky wicket. Magento offers a system to create versioned resource migration scripts that can help your team deal with this often contentious part of the development process.

              -

              In the ORM article we created a model for a weblog post. At the time, we ran our CREATE TABLE statements directly against the database. This time, we'll create a Setup Resource for our module that will create the table for us. We'll also create an upgrade script for our module that will update an already installed module. The steps we'll need to take are

              +

              In the ORM article we created a model for a weblog post. At the time, we ran our CREATE TABLE statements directly against the database. This time, we'll create a Setup Resource for our module that will create the table for us. We'll also create an upgrade script for our module that will update an already installed module. The steps we'll need to take are

              1. Add the Setup Resource to our config
              2. @@ -65,7 +58,7 @@
                Other articles in this series:

                Adding the Setup Resource

                -

                So, let's continue with the weblog module we created last time. In our <global /> section, add the following +

                So, let's continue with the weblog module we created last time. In our <global /> section, add the following

                 <global>
                @@ -73,7 +66,7 @@ 

                Adding the Setup Resource

                <resources> <weblog_setup> <setup> - <module>Magentotutorial_Weblog</module> + <module>Magentotutorial_Weblog</module> <class>Magentotutorial_Weblog_Model_Resource_Setup</class> </setup> </weblog_setup> @@ -213,7 +206,7 @@

                Resource Versions

                DELETE from core_resource where code = 'weblog_setup';
                -

                We'll also want to drop the table we manually created in the ORM article.

                +

                We'll also want to drop the table we manually created in the ORM article.

                DROP TABLE blog_posts;
                @@ -410,3 +403,6 @@

                Module Upgrades

                Wrap-up

                You should now know the basics of how to use Magento Setup Resources to create versioned database migration scripts, as well as understand the scripts provided in the core modules. Beyond having a standard way for developers to write migration scripts, Setup Resources become much more important when creating and modifying Entity Attribute Value models.

                + +
              + diff --git a/guides/m1x/magefordev/mage-for-dev-7.html b/guides/m1x/magefordev/mage-for-dev-7.html index c8631954ce..0445954489 100644 --- a/guides/m1x/magefordev/mage-for-dev-7.html +++ b/guides/m1x/magefordev/mage-for-dev-7.html @@ -13,17 +13,10 @@ Magento for Developers: Part 7—Advanced ORM: Entity Attribute Value - - -header +header {% include m1x/eol_message.html %} - - - - - -

              In the first ORM article we told you there were two kinds of Models in Magento. Regular, or "simple" Models, and Entity Attribute Value (or EAV) Models. We also told you this was a bit of a fib. Here's where we come clean.

              +

              In the first ORM article we told you there were two kinds of Models in Magento. Regular, or "simple" Models, and Entity Attribute Value (or EAV) Models. We also told you this was a bit of a fib. Here's where we come clean.

              ALL Magento Models interacting with the database inherit from the Mage_Core_Model_Abstract / Varien_Object chain. What makes something either a simple Model or an EAV Model is its Model Resource. While all resources extend the base Mage_Core_Model_Resource_Abstract class, simple Models have a resource that inherits from Mage_Core_Model_Resource_Db_Abstract, and EAV Models have a resource that inherits from Mage_Eav_Model_Entity_Abstract

              @@ -110,9 +103,9 @@

              Weblog, EAV Style

              http://example.com/complexworld
              -

              If you're unsure how to do this, be sure you've mastered the concepts in the previous tutorials.

              +

              If you're unsure how to do this, be sure you've mastered the concepts in the previous tutorials.

              -

              Next, we'll create a new Model named Weblogeav. Remember, it's the Resource that's considered EAV. We design and configure our Model the exact same way, so let's configure a Model similar to one we created in the first ORM article.

              +

              Next, we'll create a new Model named Weblogeav. Remember, it's the Resource that's considered EAV. We design and configure our Model the exact same way, so let's configure a Model similar to one we created in the first ORM article.

               <global>
              @@ -121,7 +114,7 @@ 

              Weblog, EAV Style

              <!-- ... --> <complexworld> <class>Magentotutorial_Complexworld_Model</class> - <resourceModel>complexworld_resource</resourceModel> + <resourceModel>complexworld_resource</resourceModel> </complexworld> <!-- ... --> </models> @@ -277,7 +270,7 @@

              Systems and Applications

              Creating a Setup Resource

              -

              So, it's theoretically possible to manually insert the rows you'll need into the Magento database to get your Model working, but it's not recommended. Fortunately, Magento provides a specialized Setup Resource that provides a number of helper method that will automatically create the needed records to get the system up and running.

              +

              So, it's theoretically possible to manually insert the rows you'll need into the Magento database to get your Model working, but it's not recommended. Fortunately, Magento provides a specialized Setup Resource that provides a number of helper method that will automatically create the needed records to get the system up and running.

              So, for starters, configure the Setup Resource like you would any other.

              @@ -287,7 +280,7 @@

              Creating a Setup Resource

              <resources> <complexworld_setup> <setup> - <module>Magentotutorial_Complexworld</module> + <module>Magentotutorial_Complexworld</module> <class>Magentotutorial_Complexworld_Model_Resource_Setup</class> </setup> </complexworld_setup> @@ -306,7 +299,7 @@

              Creating a Setup Resource

              Take note that we're extending from Mage_Eav_Model_Entity_Setup rather than Mage_Core_Model_Resource_Setup.

              -

              Finally, we'll set up our installer script. If you're not familiar with the naming conventions here, you'll want to review the setup resource tutorial on Setup Resources.

              +

              Finally, we'll set up our installer script. If you're not familiar with the naming conventions here, you'll want to review the setup resource tutorial on Setup Resources.

              File: app/code/local/Magentotutorial/Complexworld/sql/complexworld_setup/install-0.1.0.php:

              @@ -317,7 +310,7 @@ 

              Creating a Setup Resource

              Clear your Magento Cache, reload you page, and the above exception should be thrown, meaning you've correctly configured your Setup Resource.

              -

              NOTE: We'll be building up our install script piece by piece. If you've read the previous tutorial, you'll know you need to remove the setup's row from the core_resource table and clear your cache to make an installer script re-run. For the remainder of this tutorial, please remember that anytime we add or remove an item from our installer and re-run it, you'll need to remove this row from the database and clear your Magento cache. Normally you would create this file and run it once, a tutorial is something of an edge case.

              +

              NOTE: We'll be building up our install script piece by piece. If you've read the previous tutorial, you'll know you need to remove the setup's row from the core_resource table and clear your cache to make an installer script re-run. For the remainder of this tutorial, please remember that anytime we add or remove an item from our installer and re-run it, you'll need to remove this row from the database and clear your Magento cache. Normally you would create this file and run it once, a tutorial is something of an edge case.

              Adding the Entity Type

              @@ -331,7 +324,7 @@

              Adding the Entity Type

              'entity_model' => 'complexworld/eavblogpost', //table refers to the resource URI complexworld/eavblogpost - //...
        eavblog_posts
        + //<complexworld_resource>...<eavblogpost><table>eavblog_posts</table> 'table' =>'complexworld/eavblogpost', )); $installer->endSetup(); diff --git a/guides/m1x/magefordev/mage-for-dev-8.html b/guides/m1x/magefordev/mage-for-dev-8.html index dbeef7cb7a..130f445977 100644 --- a/guides/m1x/magefordev/mage-for-dev-8.html +++ b/guides/m1x/magefordev/mage-for-dev-8.html @@ -13,17 +13,10 @@ Magento for Developers: Part 8—Varien Data Collections - - -header +header {% include m1x/eol_message.html %} - - - - - @@ -414,7 +407,7 @@

        Other Comparison Operators

        WHERE (e.sku > 'n2610') array("lt"=>'n2610') -WHERE (e.sku < 'n2610') +WHERE (e.sku < 'n2610') array("gteq"=>'n2610') WHERE (e.sku >= 'n2610') @@ -423,13 +416,13 @@

        Other Comparison Operators

        WHERE (e.sku >= 'n2610') array("lteq"=>'n2610') -WHERE (e.sku <= 'n2610') +WHERE (e.sku <= 'n2610') array("finset"=>array('n2610')) WHERE (find_in_set('n2610',e.sku)) array('from'=>'10','to'=>'20') -WHERE e.sku >= '10' and e.sku <= '20' +WHERE e.sku >= '10' and e.sku <= '20'

    Most of these are self explanatory, but a few deserve a special callout

    @@ -469,7 +462,7 @@

    from - to filter

    The above yields

    -
    WHERE (_table_price.value >= '10' and _table_price.value <= '20')'
    +
    WHERE (_table_price.value >= '10' and _table_price.value <= '20')'

    AND or OR, or is that OR and AND?

    diff --git a/guides/m1x/other/appsec-900_addhandler.html b/guides/m1x/other/appsec-900_addhandler.html index 8ab02f3ceb..a8e52fb04d 100644 --- a/guides/m1x/other/appsec-900_addhandler.html +++ b/guides/m1x/other/appsec-900_addhandler.html @@ -1,7 +1,7 @@ --- --- - + @@ -16,10 +16,10 @@ -header +header {% include m1x/eol_message.html %} - + @@ -37,7 +37,7 @@

    Overview

  • Create files with a .csv extension, create writable directories, and change the permission of existing files to world-writable (777).
  • -
    noteNote: The preceding exploits require the attacker to have administrative access to your Magento Admin Panel Dashboard. You can resolve these issues with the patch discussed in this article.
    +
    noteNote: The preceding exploits require the attacker to have administrative access to your Magento Admin Panel Dashboard. You can resolve these issues with the patch discussed in this article.

    Creating files with a .csv extension can lead to executing files like php.csv (only under circumstances discussed in this article). The ability to run code with a .csv extension is dangerous itself and could be combined with other attacks; for example, targeting other software installed on the server.

    You can resolve this issue by changing your server's configuration as discussed in Resolving the File System Vulnerability.

    @@ -83,8 +83,8 @@

    Getting the Patch

    SUPEE-1533_EE_1.9.x_v1.patch -

    To get and apply your patch, see How to Apply and Revert Magento Patches.

    -
    importantImportant: After applying your patch, Magento strongly recommends you evaluate your vulnerability and configure PHP as discussed in Resolving the Vulnerability
    +

    To get and apply your patch, see How to Apply and Revert Magento Patches.

    +
    importantImportant: After applying your patch, Magento strongly recommends you evaluate your vulnerability and configure PHP as discussed in Resolving the Vulnerability

    Determining Your Vulnerability to the File System Attack

    @@ -98,10 +98,10 @@

    Determining Your Vulnerability to the File System Attack

    In a web browser, display that page. (For example, http://www.example.com/path/test.php.csv
  • If your browser saves the file or prompts you to save the file instead of displaying it, your server is not vulnerable. You can ignore the rest of this article.
  • If a page similar to the following displays, your server is vulnerable. Continue with the next section.
    -
  • +

    Resolving the File System Vulnerability

    -
    importantImportant: Magento strongly recommends you perform all tasks discussed in this section in a development or testing environment and not in a production environment.
    +
    importantImportant: Magento strongly recommends you perform all tasks discussed in this section in a development or testing environment and not in a production environment.

    To resolve this vulnerability, you must log in to the Magento server as a user with root privileges or as a user with permissions to change the web server configuration.

    To resolve the vulnerability:

    1. Comment out the directive in httpd.conf by preceding it with a pound sign (#) as follows:
      @@ -114,7 +114,7 @@

      Resolving the File System Vulnerability

      <FilesMatch \.php$>
           SetHandler php5-script
       </FilesMatch>
      - The regular expression in this setting matches .php only to the final extension in the file name, applying the handler only to PHP files and preventing PHP from executing.

      + The regular expression in this setting matches .php only to the final extension in the file name, applying the handler only to PHP files and preventing PHP from executing.
    diff --git a/guides/m1x/other/discover-card-validation.html b/guides/m1x/other/discover-card-validation.html index 4bcf9582ff..b3f276aac2 100644 --- a/guides/m1x/other/discover-card-validation.html +++ b/guides/m1x/other/discover-card-validation.html @@ -1,7 +1,7 @@ --- --- - + @@ -16,10 +16,10 @@ - header + header {% include m1x/eol_message.html %} - + @@ -33,7 +33,7 @@

    Discover credit card validation issue: Magento EE 1.9.1.1—1.13.1.0 and -
    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.
    +
    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.
    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.
  • +To set file system permissions appropriately, see After You Install Magento: Recommended File System Ownership and Privileges.

    How to Get This Patch

    To get this patch:

    @@ -45,11 +45,12 @@

    How to Get This Patch

  • In the left pane, click Downloads.
  • In the right pane, click Magento Enterprise Edition.
  • Follow the prompts on your screen to download a patch for your version of EE.
  • -
  • Apply the patch as discussed in How to Apply and Revert Magento Patches.
  • +
  • Apply the patch as discussed in How to Apply and Revert Magento Patches.
  • Solr Search Results and Indexing

    Patch name: PATCH_SUPEE-3630_EE_1.12.x_v1.sh for EE 1.12.x. After applying this patch, your search engine returns search results to users on the web store while reindexing is underway. We recommend you install this patch if you're using the Solr search engine. This patch can result in slower performance if you're using the default MySQL Full Text search engine.

    To get this patch, contact Magento Support.

    - - +
    + + diff --git a/guides/m1x/other/ht_extend_magento_rest_api.html b/guides/m1x/other/ht_extend_magento_rest_api.html index d520e08be7..4ac541c6f8 100644 --- a/guides/m1x/other/ht_extend_magento_rest_api.html +++ b/guides/m1x/other/ht_extend_magento_rest_api.html @@ -1,6 +1,6 @@ --- --- - + @@ -19,8 +19,8 @@ - -header + +header {% include m1x/eol_message.html %} @@ -67,7 +67,7 @@

    System Requirements

    Magento CE 1.7 and later support the OAuth 1.0a specification.
  • Optional. phpmyadmin, which makes it easier to view and manipulate the Magento database. You can use phpmyadmin for convenience to get the OAuth key and shared secret later in this guide.
  • -
    noteNote: Although Magento supports other Linux operating systems, Ubuntu is the only one discussed in this guide. Consult an appropriate reference for equivalent commands on other Linux operating systems.
    +
    noteNote: Although Magento supports other Linux operating systems, Ubuntu is the only one discussed in this guide. Consult an appropriate reference for equivalent commands on other Linux operating systems.

    Installing OAuth

    @@ -76,7 +76,7 @@

    Installing OAuth

    -
    noteNote: You must perform the tasks discussed in this section as a user with root privileges.
    +
    noteNote: You must perform the tasks discussed in this section as a user with root privileges.

    Creating a phpinfo File

    Before you begin, create a phpinfo.php file, if you have not already done so, to determine if you already have OAuth running.

    @@ -92,7 +92,7 @@

    Creating a phpinfo File

    http://www.example.com/phpinfo.php
  • Search the resulting output for OAuth.
    The following figure shows an example of OAuth being properly set up.
    -
    +
    If the preceding does not display, OAuth is not set up so continue with the next section.
    If OAuth is already installed, continue with Defining a Magento Coupon Code Generation Rule.
  • @@ -103,10 +103,10 @@

    Installing the OAuth Packages

    apt-get install php-pear
     apt-get install libpcre3-dev
     pecl install oauth

    -
    noteNote: Remember that you must perform the tasks discussed in this section as a user with root privileges.
    +
    noteNote: Remember that you must perform the tasks discussed in this section as a user with root privileges.

    Wait while each package is installed. The message Build process completed successfully displays to indicate OAuth installed successfully.
    -

    noteNote: If Error: `make' failed displays after you enter pecl install oauth, see OAuth Package Installation Error: `make' failed.
    +
    noteNote: If Error: `make' failed displays after you enter pecl install oauth, see OAuth Package Installation Error: `make' failed.
    If the following displays, you must edit your php.ini file to find the OAuth library:
    configuration option "php_ini" is not set to php.ini location
     You should add "extension=oauth.so" to php.ini
    @@ -123,8 +123,8 @@

    Installing the OAuth Packages

    Confirming that OAuth Installed Successfully

    If your phpinfo.php page is still open in a web browser, press Control+R to force a refresh; otherwise, enter the URL shown in Creating a phpinfo File to view it.

    The following figure shows an example of a properly set up OAuth extension.

    - -
    noteNote: Do not continue until you know that OAuth installed successfully.
    + +
    noteNote: Do not continue until you know that OAuth installed successfully.

    Defining a Magento Coupon Code Generation Rule

    To define a Magento coupon code generation rule:

    @@ -132,7 +132,7 @@

    Defining a Magento Coupon Code Generation Rule

  • Click Promotions > Shopping Cart Price Rules.
  • On the Shopping Cart Price Rules page, click Add New Rule (in the upper-right corner of the page).
    The General Information page displays as follows.
    -
  • +
  • Enter the following information.
    @@ -141,7 +141,6 @@

    Defining a Magento Coupon Code Generation Rule

    - @@ -205,7 +204,7 @@

    Defining a Magento Coupon Code Generation Rule

    The message The rule has been saved displays at the top of the page to indicate that Magento successfully saved the rule you just created.
  • In the left navigation bar, click Actions.
    The Actions page displays as follows.
    -
  • +
  • Enter the following information.
  • Item Description
    Rule Name
    @@ -250,7 +249,7 @@

    Defining a Magento Coupon Code Generation Rule

  • Click Save (in the upper-right corner of the page).
    The message The rule has been saved displays to indicate that Magento saved the rule action options you just entered. Notice that this page now has a row for the Generate Coupons rule you just defined.
    A sample follows.
    -
  • +
  • Write down the rule ID (circled in red in the preceding figure). You will use this value later in this guide.
  • Generating Coupon Codes

    @@ -286,13 +285,13 @@

    Generating Coupon Codes

    - +
    Dash Every X CharactersEnter 0.Enter 0.
  • Click Generate.
    Magento displays the three coupon codes you created in the Coupon Code section as the following figure shows.
    -
  • +
  • Click Save.
  • Extending Magento's REST API to Include Coupon Auto-Generation

    @@ -308,7 +307,7 @@

    Disabling the Magento Cache

    To disable the cache:

    1. In the Magento Admin Panel, click System > Cache Management.
      The Cache Storage Management page displays as follows.
      -
    2. +
    3. Click Select All (on the upper-left of the page).
      A check mark displays next to each Magento cache in the list.
    4. From the Actions list, click Disable.
    5. @@ -321,7 +320,7 @@

      Creating Configuration Files

      This section discusses how to create a module (also referred to as an extension). The module consists of configuration files that create a web service that extends the Magento REST API to take input from an external program. This program uses HTTP POST and OAuth calls to auto-generate coupon codes.

      In this guide, the external program is a PHP script; however, it could be any application that uses OAuth and REST calls.

      For more information about Magento module development, see developer documentation on Magento Connect.

      -
      noteNote: It is up to you to determine ownership and permissions. This guide assumes you create files and directories as root and change the permissions appropriately later. Consult an IT administrator if you're not sure how to proceed.
      +
      noteNote: It is up to you to determine ownership and permissions. This guide assumes you create files and directories as root and change the permissions appropriately later. Consult an IT administrator if you're not sure how to proceed.
      1. Log in to your Magento server and create the following directories:
        @@ -339,12 +338,11 @@ 

        Creating Configuration Files

        /var/www/magento/app/code/community/CouponDemo/AutoGen/etc /var/www/magento/app/code/community/CouponDemo/AutoGen/Model/Api2/Coupon/Rest/Admin

        The following figure shows an example.

        -
        -
        importantImportant:
        • You must create the files and directories exactly as shown; directory names are case-sensitive.
        • +
          +
          importantImportant:
          • You must create the files and directories exactly as shown; directory names are case-sensitive.
          • Do not change any values in the configuration files discussed in this section.
          • When you create your configuration files, leave no white space at the beginning of the files. Leading white space might cause errors when Magento reads the files and might prevent the coupon demonstration module from working.
          -

          - +

          Overview

          -

          Magento Enterprise Edition (EE) versions 1.8.0.0 and later enable you to configure either of the following as a catalog search engine:

          - +

          Magento Enterprise Edition (EE) versions 1.8.0.0 and later enable you to configure either of the following as a + catalog search engine:

          +

          Solr enables you to provide your web store users with a powerful full-text search engine that includes:

          - +

          See one of the following sections for more information:

          - +

          Intended Audience and Purpose of this Guide

          -

          This guide is intended for Magento EE administrators and systems integrators who have some familiarity with search engines—ideally, who also have Solr configuration experience. No programming is required to perform the tasks discussed in this guide.

          -

          This guide discusses a simple Solr configuration that uses the example Solr configuration provided with Solr, default Solr integration options provided with Magento EE, and also explains how to configure Magento EE to use Solr. Advanced configuration tasks—such as setting up dictionaries—are beyond the scope of this guide.

          -
          noteNote: The example Solr configuration is not intended to be used in a production site. It's for testing and development only. Because it's simple to use which, it's a great way for you to learn more about Solr.
          +

          This guide is intended for Magento EE administrators and systems integrators who have some familiarity with search + engines—ideally, who also have Solr configuration experience. No programming is required to perform the tasks + discussed in this guide.

          +

          This guide discusses a simple Solr configuration that uses the example Solr configuration provided with Solr, default + Solr integration options provided with Magento EE, and also explains how to configure Magento EE to use Solr. Advanced + configuration tasks—such as setting up dictionaries—are beyond the scope of this guide.

          +
          noteNote: The example Solr configuration is not intended to be used in a + production site. It's for testing and development only. Because it's simple to use which, it's a great way for you + to learn more about Solr.

          Comparing the Search Options

          -

          The following table provides a quick comparison between Magento with the default MySQL full text search and Magento with Solr search.

          +

          The following table provides a quick comparison between Magento with the default MySQL full text search and Magento + with Solr search.

          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + --> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          FeatureMagento with MySQL full-text searchMagento with Solr search
          Full text search

          Yes and also supports two additional search modes:

          -
          • Like
          • -
          • Combined (like and full text)
          -
          Yes†
          Search recommendationsYesYes
          Faceted search (used in layered navigation)YesYes
          Range (such as price range)YesYes
          Sort-by options (for example, sort by relevance)YesYes
          Zero results tips or results correctionNoYes
          SuggestionsNoYes
          ClusteringNoYes
          Attribute weight based on attribute settingsNoYes
          Search localized charactersNoYes
          Word delimiter (for example, searching for spider man or spiderman return spider-man)NoYes
          FeatureMagento with MySQL full-text searchMagento with Solr search
          Full text search +

          Yes and also supports two additional search modes:

          +
            +
          • Like
          • +
          • Combined (like and full text)
          • +
          +
          Yes†
          Search recommendationsYesYes
          Faceted search (used in layered navigation)YesYes
          Range (such as price range)YesYes
          Sort-by options (for example, sort by relevance)YesYes
          Zero results tips or results correctionNoYes
          SuggestionsNoYes
          ClusteringNoYes
          Attribute weight based on attribute settingsNoYes
          Search localized charactersNoYes
          Word delimiter (for example, searching for spider man or spiderman + return spider-man)NoYes
          -†—"Like" searching is supported by MySQL full text search but not by Solr. Defined by the Mage_CatalogSearch_Model_Resource_Fulltext::prepareResult() class, like searching joins each term in your search using LIKE statements combined by OR. Like searching is best used in stores that have simple products where users search for specific terms.

          +†—"Like" searching is supported by MySQL full text search but not by Solr. Defined by the +Mage_CatalogSearch_Model_Resource_Fulltext::prepareResult() class, like searching joins each term in your +search using LIKE statements combined by OR. Like searching is best used in stores that have simple products where users +search for specific terms.

          Support Matrix for Solr and Magento EE

          The following table summarizes what versions of Magento EE work with what versions of Solr.

          - - - - - - - - - - - - - - - - - - - - - - - - - - - + --> + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          Magento EE versionCompatible Solr version(s)Comment
          EE 1.14.x.xAny version up to 3.6.2.No patch is required to use EE 1.14.x.x with Solr 3.6.2. Click here to browse the list of all available Solr versions.

          EE 1.13.x.xAny version up to 3.6.2.Click here to browse the list of all available Solr versions.

          EE 1.12.0.xAny version up to 3.5.0

          If you use a later version, such as 3.6.x, see Information About Enterprise Edition (EE) Patches for Apache Solr to get a patch.

          -

          Click here to browse the list of all available Solr versions.

          EE 1.8.0.0 to 1.11.0.2Any version up to 3.4.0. -

          To use a Solr version later than 1.4.x, see Information About Enterprise Edition (EE) Patches for Apache Solr to get a patch.

          - Click here to browse the list of all available Solr versions.
          Magento EE versionCompatible Solr version(s)Comment
          EE 1.14.x.xAny version + up to 3.6.2.No patch is required to use EE 1.14.x.x with Solr 3.6.2. Click here to browse the list of all + available Solr versions.
          EE 1.13.x.xAny version + up to 3.6.2.Click here to + browse the list of all available Solr versions.
          EE 1.12.0.xAny version + up to 3.5.0 +

          If you use a later version, such as 3.6.x, see Information About + Enterprise Edition (EE) Patches for Apache Solr to get a patch.

          +

          Click here to browse the list of + all available Solr versions.

          +
          EE 1.8.0.0 to 1.11.0.2Any version + up to 3.4.0. + +

          To use a Solr version later than 1.4.x, see Information About + Enterprise Edition (EE) Patches for Apache Solr to get a patch.

          + Click here to browse the list of all + available Solr versions. +
          -
          noteNote: Magento EE does not support Solr 4.x.
          +
          noteNote: Magento EE does not support Solr 4.x.

          More Information About the Solr Solution

          -

          Solr runs as a standalone full-text search server in a servlet container such as Jetty (which is used by the Solr example configuration) and Tomcat.

          -

          Solr uses the Lucene Java search library for full-text indexing and search. Your applications interact with Solr using HTTP POST (in JSON, XML, CSV, or binary formats) to index documents and using HTTP GET to retrieve search results back as JSON, XML, or a variety of other formats (Python, Ruby, PHP, CSV, binary, and so on). If you're a programmer, try the Solr tutorial. Whether you're a programmer or not, read the Solr FAQ.

          +

          Solr runs as a standalone full-text search server in a servlet container such as Jetty (which is used by the Solr + example configuration) and Tomcat.

          +

          Solr uses the Lucene Java search library for full-text indexing and search. Your applications interact with Solr + using HTTP POST (in JSON, + XML, CSV, or binary formats) to index + documents and using HTTP + GET to retrieve search results back as JSON, XML, or a + variety of other formats (Python, Ruby, PHP, CSV, binary, and so on). If you're a programmer, try the Solr tutorial. Whether + you're a programmer or not, read the Solr FAQ.

          No programming is required to implement Solr as discussed in this guide.

          -

          Solr's powerful external configuration allows it to be tailored to almost any type of application without Java coding, and it has an extensive plug-in architecture when more advanced customization is required. Solr is highly scalable, providing distributed search and index replication.

          -
          importantImportant: Customize the Solr search engine at your own risk. Magento supports only the options displayed in the Admin Panel. Customizing the Solr engine itself, while potentially useful, can cause issues with Magento. If you encounter problems with your customizations, do not contact Magento Support; instead, consult the resources available from the Apache Solr Wiki.
          -

          In this guide, you'll use the example configuration provided with Solr and Magento's provided Solr configuration to implement a simple, quick integration with Solr.

          +

          Solr's powerful external configuration allows it to be tailored to almost any type of application without Java + coding, and it has an extensive plug-in architecture when more advanced customization is required. Solr is highly + scalable, providing distributed search and index replication.

          +
          importantImportant: Customize the Solr search engine at your own risk. Magento + supports only the options displayed in the Admin Panel. Customizing the Solr engine itself, while potentially + useful, can cause issues with Magento. If you encounter problems with your customizations, do not contact Magento + Support; instead, consult the resources available from the Apache Solr Wiki.
          +

          In this guide, you'll use the example configuration provided with Solr and Magento's provided Solr configuration to + implement a simple, quick integration with Solr.

          Some reasons to use Solr with Magento include:

            -
          • Magento ships with a sample Solr configuration that enables you to provide users with a powerful search engine without your needing to customize any code.
          • -
          • You get better performance of search, catalog views, and layered navigation.
          • -
          • When the system is under load, Solr avoids frequent updates of the MySQL catalogsearch_fulltext table and alleviates issues with database table locks.
          +
        • Magento ships with a sample Solr configuration that enables you to provide users with a powerful search engine + without your needing to customize any code.
        • +
        • You get better performance of search, catalog views, and layered navigation.
        • +
        • When the system is under load, Solr avoids frequent updates of the MySQL catalogsearch_fulltext table and + alleviates issues with database table locks.
        • +

        Simple Comparison of Solr and MySQL Search Engines

        -

        Following is a simple comparison of the default MySQL full-text search and Solr search using Magento EE 1.14.0.0 and Solr 3.6.2. Magento EE catalog content is provided by sample data you can download from Magento.

        -

        Among the many options Solr gives you is the option to suggest names of products in the event the user enters an incomplete or incorrect search term in your Magento store's Search field.

        +

        Following is a simple comparison of the default MySQL full-text search and Solr search using Magento EE 1.14.0.0 and + Solr 3.6.2. Magento EE catalog content is provided by sample data you can download from Magento.

        +

        Among the many options Solr gives you is the option to suggest names of products in the event the user + enters an incomplete or incorrect search term in your Magento store's Search field.

        Default MySQL Full-Text Search Using an Incorrect Search Term

        -

        Using the default MySQL full-text search, if a user enters an incorrect search term (such as shirrt instead of shirt, no results display as the following figure shows.

        - +

        Using the default MySQL full-text search, if a user enters an incorrect search term (such as shirrt instead + of shirt, no results display as the following figure shows.

        +

        Solr Search Using an Incorrect Search Term

        Using Solr, if a user enters an incorrect search term, suggestions display as the following figure shows.

        - -

        In addition, if a user enters an incomplete search term, Magento provides dictionary-based suggestions as the following figure shows.

        - + +

        In addition, if a user enters an incomplete search term, Magento provides dictionary-based suggestions as the + following figure shows.

        +

        Prerequisites

        The tasks discussed in this guide require the following:

        -
        • Magento EE and Solr versions discussed in Support Matrix for Solr and Magento EE.
        • -
        • Java version 1.6 or later.
          -To determine if Java is already installed, enter the following command:

          -
          java -version
          -If the message java: command not found displays, you must install the Java SDK as discussed in the next section. If Java is installed, make sure it's version 1.6 or later.
        • -
        • Tomcat or Jetty servlet container. This guide discusses using Jetty, which comes with Solr. Consult another resource, such as the Solr Wiki, to use Tomcat with Solr.
          -To see if you're currently running Jetty and to check the version, see How to find out the version of Jetty.
        • -
        +
          +
        • Magento EE and Solr versions discussed in Support Matrix for Solr and Magento EE. +
        • +
        • Java version 1.6 or later.
          + To determine if Java is already installed, enter the following command:

          +
          java -version
          + If the message java: command not found displays, you must install the Java SDK as discussed in the next + section. If Java is installed, make sure it's version 1.6 or later.
        • +
        • Tomcat or Jetty servlet container. This guide discusses using Jetty, which comes with Solr. Consult another + resource, such as the Solr Wiki, to use Tomcat + with Solr.
          + To see if you're currently running Jetty and to check the version, see How + to find out the version of Jetty.
        • +

        Installing Prerequisite Software

        The following sections discuss how to install the prerequisite software:

        - +

        Installing the Java 6 SDK

        To install the Java 6 SDK, enter the following command as a user with root privileges:

        apt-get install openjdk-6-jdk

        To install Java 7, enter the following command as a user with root privileges:

        apt-get install openjdk-7-jdk
        -
        noteNote: Java version 7 might not be available for all operating systems. For example, you can search the list of available packages for Ubuntu here.
        +
        noteNote: Java version 7 might not be available for all operating systems. For + example, you can search the list of available packages for Ubuntu here.

        Installing Solr 3.6.2 and Jetty

        -

        The Apache Solr package installs both Solr and Jetty. If Jetty is already installed, see the Solr with Jetty Wiki for more information.

        -
        noteNote: Tomcat is also a supported servlet container for Solr but discussing how to set up Tomcat with Solr is beyond the scope of this guide. For more information, see the Solr With Tomcat Wiki.
        +

        The Apache Solr package installs both Solr and Jetty. If Jetty is already installed, see the Solr with Jetty Wiki for more information.

        +
        noteNote: Tomcat is also a supported servlet container for Solr but discussing how to + set up Tomcat with Solr is beyond the scope of this guide. For more information, see the Solr With Tomcat Wiki.

        To install Solr and Jetty:

        -
        1. Find a suitable Solr distribution. - -

          If you're not sure what version of Solr to use, see Support Matrix for Solr and Magento EE.

          -
        2. -
        3. As a user with root privileges, use wget or a similar command to download the file to an empty directory such as /etc/solr. An example follows.

          -
          cd empty-directory
          +
            +
          1. Find a suitable Solr distribution. + +

            If you're not sure what version of Solr to use, see Support Matrix for Solr and + Magento EE.

            +
          2. +
          3. As a user with root privileges, use wget or a similar command to download the file to an empty + directory such as /etc/solr. An example follows.

            +
            cd empty-directory
             wget http://archive.apache.org/dist/lucene/solr/3.6.2/apache-solr-3.6.2.tgz

            -Messages similar to the following display to confirm a successful download.
            -
            wget http://archive.apache.org/dist/lucene/solr/3.6.2/apache-solr-3.6.2.tgz
            +    Messages similar to the following display to confirm a successful download.
            +
            wget http://archive.apache.org/dist/lucene/solr/3.6.2/apache-solr-3.6.2.tgz
             --2012-11-01 16:20:16--  http://archive.apache.org/dist/lucene/solr/3.6.2/apache-solr-3.6.2.tgz
             Resolving archive.apache.org... 140.211.11.131
             Connecting to archive.apache.org|140.211.11.131|:80... connected.
            @@ -232,233 +331,348 @@ 

            Installing Solr 3.6.2 and Jetty

            100%[======================================>] 78,673,382 1.41M/s in 36s -2012-11-01 16:20:52 (2.08 MB/s) - `apache-solr-3.6.2.tgz' saved [78673382/78673382]
          4. -
          5. Unpack the Solr installation; an example follows.

            -
            tar -xvf apache-solr-3.6.2.tgz
          6. -
          7. Continue with the next section.
          +2012-11-01 16:20:52 (2.08 MB/s) - `apache-solr-3.6.2.tgz' saved [78673382/78673382]
          +
        4. +
        5. Unpack the Solr installation; an example follows.

          +
          tar -xvf apache-solr-3.6.2.tgz
          +
        6. +
        7. Continue with the next section.
        8. +

        Configuring Solr to Work With Magento

        The following topics discuss how to configure Solr to work with Magento EE:

        - +

        Copying the Magento Solr Configuration and Starting Solr

        -

        Magento comes packaged with a sample Solr configuration you can use and customize. To get started, you'll copy the Magento configuration to Solr, replacing any existing files. After that you can start Solr and begin configuring Magento to work with it.

        -
        noteNote: The example Solr configuration is not intended to be used in a production site. It's for testing and development only. It's simple to use which makes it a great way for you to learn more about Solr.
      2. +

        Magento comes packaged with a sample Solr configuration you can use and customize. To get started, you'll copy the + Magento configuration to Solr, replacing any existing files. After that you can start Solr and begin configuring + Magento to work with it.

        +
        noteNote: The example Solr configuration is not intended to be used in a + production site. It's for testing and development only. It's simple to use which makes it a great way for you to + learn more about Solr.
        +

        To copy the Magento Solr configuration:

        -
        1. As a user with root privileges, enter the following commands in the order shown to copy over the Solr configuration with the one packaged with Magento EE:

          -
          cd [your Solr install dir]/example/solr/conf
          +
            +
          1. As a user with root privileges, enter the following commands in the order shown to copy over the Solr + configuration with the one packaged with Magento EE:

            +
            cd [your Solr install dir]/example/solr/conf
             cp -R [your Magento install dir]/lib/Apache/Solr/conf/* .

            -For example, if Solr is installed in /etc/solr/apache-solr-3.6.2 and Magento is installed in /var/www/magento, enter:

            -
            cd /etc/solr/apache-solr-3.6.2/example/solr/conf
            +    For example, if Solr is installed in /etc/solr/apache-solr-3.6.2 and Magento is installed in
            +    /var/www/magento, enter:

            +
            cd /etc/solr/apache-solr-3.6.2/example/solr/conf
             cp -R /var/www/magento/lib/Apache/Solr/conf/* .

            -
            noteNote: If you're prompted to overwrite files, try the command \cp -R [your Magento install dir]/lib/Apache/Solr/conf/* .
            -
          2. -
          3. CentOS with Tomcat 6 only. If you're using Tomcat 6 on CentOS, you must modify [your Solr install dir]/example/solr/conf/solrconfig.xml
            -Locate the following line:
            -
            <dataDir>${solr.data.dir:./solr/data}</dataDir>
            -Change it to:
            -
            <dataDir>${solr.data.dir:}</dataDir>
          4. +
            noteNote: If you're prompted to overwrite files, try the command \cp -R [your + Magento install dir]/lib/Apache/Solr/conf/* .
            + +
          5. CentOS with Tomcat 6 only. If you're using Tomcat 6 on CentOS, you must modify [your Solr install + dir]/example/solr/conf/solrconfig.xml
            + Locate the following line:
            +
            <dataDir>${solr.data.dir:./solr/data}</dataDir>
            + Change it to:
            +
            <dataDir>${solr.data.dir:}</dataDir>
            +
          6. -
          7. As a user with root privileges, enter the following command to start Solr:

            -
            java -jar [your Solr install dir]/example/start.jar

            -
            noteNote: This method for starting Solr is for convenience and testing purposes only. In a production environment, you should start and stop Solr using a script as discussed in Scripting Solr Startup and Shutdown.
            +
          8. As a user with root privileges, enter the following command to start Solr:

            +
            java -jar [your Solr install dir]/example/start.jar

            +
            noteNote: This method for starting Solr is for convenience and testing purposes + only. In a production environment, you should start and stop Solr using a script as discussed in Scripting Solr Startup and Shutdown.
            -

            Configuring Magento to Work With Solr

            -

            This section discusses how to configure Magento EE to use the Solr search engine.

            -

            To configure Magento to work with Solr:

            -
            1. Log in to the Magento Admin Panel as an administrator.
            2. -
            3. Click System > Configuration > CATALOG > Catalog.
            4. -
            5. In the right pane, expand Catalog Search.
            6. -
            7. The following table shows the minimum amount of information to enter to test the connection to your Solr search engine. Leave all other values at their defaults.
              - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
              OptionDescription
              Search EngineClick Solr
              Solr Server HostnameEnter the fully qualified hostname or IP address of the machine running Solr. (If Solr is running on the same host as Magento, you can optionally use 127.0.0.1.)
              Solr Server PortEnter Solr's listen port. (The example Jetty servlet container uses 8983. The default for Tomcat is usually 8080.)
              Solr Server UsernameOptional. Enter a username for Solr authentication, if desired.
              Solr Server PasswordOptional. Enter the user's password, if desired.
              Solr Server TimeoutEnter a connection timeout value, in seconds.
              Solr Server Path -

              Specifies the path and name of the Solr web application. The path used by the example Solr configuration is solr.

              -

              If you customized Solr, the value you enter in this field must exactly match the value of webapp_name=value in [your Solr install dir]/example/solr/conf/scripts.conf.

              Indexation Mode

              Specifies how Solr processes indexed content.

              -

              From the Indexation Mode list, click one of the following:

              -
              • Final commit (Default, recommended): After you reindex the content search index, Solr starts processing content. Users see results from content that was searchable before indexing started and the Magento store remains available for other requests.

                -

                Final commit has much better performance then partial commit, and does not require any additional Solr configuration as does engine autocommit.

                -

                Indexing begins after all unneeded data is removed and new data is added. At that point, users see results from newly indexed data immediately.

              • -
              • Partial commit: All content is removed from Solr after you reindex the content search index and users at that time see no search results. As content is gradually reindexed, users see only the results of content that has been indexed.
              • -
              • Engine autocommit: Content is put in the index queue but is not committed. You must configure Solr to commit at regular intervals (for example, every 5 minutes) or when a certain number of uncommitted items is reached.

                -

                For more information, see the discussion of the <autoCommit> XML element in the solrconfig.xml section of the Solr Wiki.

                -
              -

              -The following figure shows an example.
              -
            8. -
            9. Click Test Connection.
              -The button changes as follows.
              - --- - - - - - - - - - - - - - -
              Button stateMeaning
              The test connection succeeded. Click Save Config and continue with the next section.
              The test connection failed. Try the following: -
              • Examine the command window in which you started Solr for stack traces and exceptions. You must resolve those before you continue.
                - In particular, make sure you started Solr as a user with root privileges.
              • -
              • Verify that allow_url_fopen = On is present in your server's php.ini.
                - If you are not sure where php.ini is located, you can create a phpinfo.php page to locate it.
              • -
              • Verify the value of the Solr Server Hostname field. Make sure the server is available. You can try the server's IP address instead.
              • -
              • Use the command netstat -an | grep listen-port command to verify that the port specified in the Solr Server Port field is not being used by another process.
                - For example, to see if Solr is running on its default port, use the following command: -
                netstat -an | grep 8983
                - If Solr is running on port 8983, it displays similar to the following:
                - tcp 0 0 :::8983 :::* LISTEN
              • -
              • If Solr is installed on a remote machine, use the ping command to verify that machine is reachable from your Magento instance.
              • -
              • If SELinux is enabled, make sure the Solr servlet container's listen port is available; otherwise, Magento cannot communicate with the servlet container. For example, you can consult the SELinux Centos wiki.
              -
            10. -
            11. Only after the test connection succeeds, click Save Config and continue with the next section.
            12. -
            + --> + + + + Option + Description + + + Search Engine + Click Solr + + + Solr Server Hostname + Enter the fully qualified hostname or IP address of the machine running Solr. (If + Solr is running on the same host as Magento, you can optionally use 127.0.0.1.) + + + Solr Server Port + Enter Solr's listen port. (The example Jetty servlet container uses 8983. The + default for Tomcat is usually 8080.) + + + Solr Server Username + Optional. Enter a username for Solr authentication, if desired. + + + + Solr Server Password + Optional. Enter the user's password, if desired. + + + Solr Server Timeout + Enter a connection timeout value, in seconds. + + + Solr Server Path + + +

            Specifies the path and name of the Solr web application. The path used by the example Solr + configuration is solr.

            +

            If you customized Solr, the value you enter in this field must exactly match the value of + webapp_name=value in [your Solr install + dir]/example/solr/conf/scripts.conf.

            + + + + Indexation Mode + +

            Specifies how Solr processes indexed content.

            +

            From the Indexation Mode list, click one of the following:

            +
              +
            • +

              Final commit (Default, recommended): After you reindex the content + search index, Solr starts processing content. Users see results from content that was searchable + before indexing started and the Magento store remains available for other requests.

              +

              Final commit has much better performance then partial commit, and does not require any additional + Solr configuration as does engine autocommit.

              +

              Indexing begins after all unneeded data is removed and new data is added. At that point, users + see results from newly indexed data immediately.

              +
            • +
            • Partial commit: All content is removed from Solr after you reindex the content + search index and users at that time see no search results. As content is gradually reindexed, users + see only the results of content that has been indexed.
            • +
            • +

              Engine autocommit: Content is put in the index queue but is not committed. You + must configure Solr to commit at regular intervals (for example, every 5 minutes) or when a + certain number of uncommitted items is reached.

              +

              For more information, see the discussion of the <autoCommit> XML element in the solrconfig.xml section + of the Solr Wiki.

              +
            • +
            + + + +
            + The following figure shows an example.
            + +
          9. +
          10. Click Test Connection.
            + The button changes as follows.
            + + + + + + + + + + + + + + + + + +
            Button stateMeaning
            The test connection succeeded. Click Save Config and continue + with the next section.
            The test connection failed. Try the following: +
              +
            • Examine the command window in which you started Solr for stack traces and exceptions. You must + resolve those before you continue.
              + In particular, make sure you started Solr as a user with root privileges.
            • +
            • Verify that allow_url_fopen = On is present in your server's + php.ini.
              + If you are not sure where php.ini is located, you can create a phpinfo.php page to locate it.
            • +
            • Verify the value of the Solr Server Hostname field. Make sure the server is + available. You can try the server's IP address instead.
            • +
            • Use the command netstat -an | grep listen-port command to verify that the port + specified in the Solr Server Port field is not being used by another process.
              + For example, to see if Solr is running on its default port, use the following command: +
              netstat -an | grep 8983
              + If Solr is running on port 8983, it displays similar to the following:
              + tcp 0 0 :::8983 :::* LISTEN
            • +
            • If Solr is installed on a remote machine, use the ping command to verify that machine is + reachable from your Magento instance.
            • +
            • If SELinux is enabled, make sure the Solr servlet container's listen port is available; otherwise, + Magento cannot communicate with the servlet container. For example, you can consult the SELinux Centos wiki. +
            +
            +
          11. +
          12. Only after the test connection succeeds, click Save Config and continue with the next + section.
          13. +
          -

          Basic Solr Configuration

          -

          This section discusses how to configure Magento to work with Solr using options in the Admin Panel. Although additional Solr customization is possible, it is beyond the scope of this guide.

          -
          importantImportant: Customize the Solr search engine at your own risk. Magento supports only the options displayed in the Admin Panel. Customizing the Solr engine itself, while potentially useful, can cause issues with Magento. If you encounter problems with your customizations, do not contact Magento Support; instead, consult the resources available from the Apache Solr Wiki.
          -

          To configure Magento to work with Solr:

          -
          1. Start the Magento Admin Panel and log in as an administrator.
          2. -
          3. Click System > Configuration.
          4. -
          5. In the left navigation bar, under the CATALOG group, click Catalog > Catalog Search.
          6. -
          7. The following table shows the minimum amount of information to enter to test the connection to your Solr search engine. Leave all other values at their defaults.
            - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            OptionDescription
            Minimal Query LengthEnter the minimum number of characters permitted for a catalog search. -
            Maximum Query LengthEnter the maximum number of characters permitted for a catalog search.
            Search Engine
            - Solr Server Hostname
            - Solr Server Port
            - Solr Server Username
            - Solr Server Password
            - Solr Server Timeout
            - Solr Server Path
            - Indexation Mode -
            Discussed in Configuring Solr to Work With Magento.
            Enable Search Suggestions

            Suggestions are the native Solr mechanism of advising users in the event they enter incomplete or incorrect user input. Suggestions, when enabled, are automatically provided as part of any search request.

            -

            Solr completes incomplete or incorrect input using a dictionary that is based on the main index (and can be customized using configuration files to use any other arbitrary dictionary). Suggestions display with default text "Did you mean:" in the search results page if needed.

            -

            Notes: -

            • Search suggestions are not the same as AJAX hints.
            • -
            • Enabling suggestions negatively affects performance because they result in more complex queries to Solr.

            Search Suggestions CountEnter the maximum number of suggestions to return.
            Show Results Count for Each Suggestion

            The default option, No, displays only the suggestion and not the number of results for each suggestion.

            -

            Click Yes to display the number of results for each suggestion.

            Enable Search Recommendations

            Recommendations display terms related to a requested word or phrase on the search results page.

            -

            This functionality is not based on third party engine functionality, but is implemented as part of the Enterprise_Search module and can be shown with the Solr search suggestions block.

            -

            By default, Magento uses the Enterprise_Search_Model_Adapter_HttpStream module for recommendations. If you install the Apache Solr PHP extension, Magento automatically uses the Enterprise_Search_Model_Adapter_PhpExtension adapter instead. Both adapters function in the same way with no difference in performance. However, the PhpExtension adapter is not tested by Magento so you must thoroughly test any modifications you make to it before deploying it in a production environment.

            -
            noteNote: Enabling recommendations negatively affects performance because they result in more complex queries to Solr and more database calls.
            -
            Search Recommendations CountEnter the maximum number of recommendations to return.
            Show Results Count for Each Recommendation

            The default option, No, displays only the recommendation and not the number of results for each recommendation.

            -

            Click Yes to display the number of results for each recommendation.

            Enable Solr Engine for Catalog Navigation

            Click Yes (the default) to use Solr to enable layered navigation in the category view.

            -

            Click No to use the database for layered navigation in the category view.

          +

          Basic Solr Configuration

          +

          This section discusses how to configure Magento to work with Solr using options in the Admin Panel. Although + additional Solr customization is possible, it is beyond the scope of this guide.

          +
          importantImportant: Customize the Solr search engine at your own risk. + Magento supports only the options displayed in the Admin Panel. Customizing the Solr engine itself, while + potentially useful, can cause issues with Magento. If you encounter problems with your customizations, do not + contact Magento Support; instead, consult the resources available from the Apache Solr Wiki.
          +

          To configure Magento to work with Solr:

          +
            +
          1. Start the Magento Admin Panel and log in as an administrator.
          2. +
          3. Click System > Configuration.
          4. +
          5. In the left navigation bar, under the CATALOG group, click Catalog > Catalog + Search.
          6. +
          7. The following table shows the minimum amount of information to enter to test the connection to your Solr + search engine. Leave all other values at their defaults.
            + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
            OptionDescription
            Minimal Query LengthEnter the minimum number of characters permitted for a catalog search.
            Maximum Query LengthEnter the maximum number of characters permitted for a catalog search.
            Search Engine
            + Solr Server Hostname
            + Solr Server Port
            + Solr Server Username
            + Solr Server Password
            + Solr Server Timeout
            + Solr Server Path
            + Indexation Mode +
            Discussed in Configuring Solr to Work With Magento. +
            Enable Search Suggestions +

            Suggestions are the native Solr mechanism of advising users in the event they enter + incomplete or incorrect user input. Suggestions, when enabled, are automatically provided as part of + any search request.

            +

            Solr completes incomplete or incorrect input using a dictionary that is based on the main index (and + can be customized using configuration files to use any other arbitrary dictionary). Suggestions + display with default text "Did you mean:" in the search results page if needed.

            +

            Notes:

            +
              +
            • Search suggestions are not the same as AJAX hints.
            • +
            • Enabling suggestions negatively affects performance because they result in more complex queries + to Solr.
            • +
            +
            Search Suggestions CountEnter the maximum number of suggestions to return.
            Show Results Count for Each Suggestion +

            The default option, No, displays only the suggestion and not the number of results + for each suggestion.

            +

            Click Yes to display the number of results for each suggestion.

            +
            Enable Search Recommendations +

            Recommendations display terms related to a requested word or phrase on the search results + page.

            +

            This functionality is not based on third party engine functionality, but is implemented as part of + the Enterprise_Search module and can be shown with the Solr search suggestions block.

            +

            By default, Magento uses the Enterprise_Search_Model_Adapter_HttpStream module for + recommendations. If you install the Apache + Solr PHP extension, Magento automatically uses the + Enterprise_Search_Model_Adapter_PhpExtension adapter instead. Both adapters function in the + same way with no difference in performance. However, the PhpExtension adapter is not tested + by Magento so you must thoroughly test any modifications you make to it before deploying it in a + production environment.

            +
            noteNote: Enabling recommendations negatively affects + performance because they result in more complex queries to Solr and more database calls.
            +
            Search Recommendations CountEnter the maximum number of recommendations to return.
            Show Results Count for Each Recommendation +

            The default option, No, displays only the recommendation and not the number of + results for each recommendation.

            +

            Click Yes to display the number of results for each recommendation.

            +
            Enable Solr Engine for Catalog Navigation +

            Click Yes (the default) to use Solr to enable layered navigation in the category view.

            +

            Click No to use the database for layered navigation in the category view.

            +
            +
          8. +
          -

          Reindexing Catalog Search and Refreshing the Full Page Cache

          -

          After you change the Solr configuration, you must reindex the catalog search index and refresh the full page cache as follows:

          -
          1. In the Admin Panel, click System > Cache Management.
          2. -
          3. Select the checkbox next to Page Cache.
          4. -
          5. From the Actions list in the upper right, click Refresh.
            -The following figure shows an example.
            -
          6. -
          7. To update the catalog search index, open a command prompt window.
          8. -
          9. Change to the shell subdirectory of your Magento installation directory.
            -For example, on CentOS: -
            cd /var/www/html/magento/shell
          10. -
          11. Enter the following command: -
            php indexer.php --reindex catalogsearch_fulltext
          12. +

            Reindexing Catalog Search and Refreshing the Full Page Cache

            +

            After you change the Solr configuration, you must reindex the catalog search index and refresh the full page + cache as follows:

            +
              +
            1. In the Admin Panel, click System > Cache Management.
            2. +
            3. Select the checkbox next to Page Cache.
            4. +
            5. From the Actions list in the upper right, click Refresh.
              + The following figure shows an example.
              + +
            6. +
            7. To update the catalog search index, open a command prompt window.
            8. +
            9. Change to the shell subdirectory of your Magento installation directory.
              + For example, on CentOS: +
              cd /var/www/html/magento/shell
              +
            10. +
            11. Enter the following command: +
              php indexer.php --reindex catalogsearch_fulltext

            Scripting Solr Startup and Shutdown

            In a production environment, you should start and stop Solr using a script.

            -
            noteNote: You must perform all tasks discussed in this section as a user with root privileges.
            +
            noteNote: You must perform all tasks discussed in this section as a user with root privileges.

            Create a script named /etc/init.d/solr with options similar to the following:

            #!/bin/sh
              
            @@ -492,40 +706,47 @@ 

            Scripting Solr Startup and Shutdown

            exit 1 ;; esac
            -

            All parameters shown in the following table are required.

            - --- - - - - - - - - - - - - - - - - - - - - - -
            ValueDescription
            [your Solr install dir]The absolute file system path to your Solr installation. (For example, /etc/solr/apache-solr-3.6.2
            jetty-stop-port
            - jetty-stop-key

            Security parameters used to prevent malicious attempts to stop Jetty.

            -

            For -DSTOP.PORT=, specify any unused port.

            -

            For -DSTOP.KEY=, specify a string. If you omit a value for -DSTOP.KEY=, Jetty generates a random key you must enter to stop Jetty.

            -

            For more information, see Securing Jetty.

            path-to-solr-log-fileAbsolute file system path to the Solr log file. (For example, /var/log/solr.log)
            java_homeAbsolute file system path to your Java executable. (For example, /usr/bin/java)
            +

            All parameters shown in the following table are required.

            + + + + + + + + + + + + + + + + + + + + + + + + + +
            ValueDescription
            [your Solr install dir]The absolute file system path to your Solr installation. (For example, + /etc/solr/apache-solr-3.6.2
            jetty-stop-port
            + jetty-stop-key
            +

            Security parameters used to prevent malicious attempts to stop Jetty.

            +

            For -DSTOP.PORT=, specify any unused port.

            +

            For -DSTOP.KEY=, specify a string. If you omit a value for -DSTOP.KEY=, Jetty + generates a random key you must enter to stop Jetty.

            +

            For more information, see Securing Jetty.

            +
            path-to-solr-log-fileAbsolute file system path to the Solr log file. (For example, + /var/log/solr.log)
            java_homeAbsolute file system path to your Java executable. (For example, + /usr/bin/java)
            -

            An example follows:

            -
            #!/bin/sh
            +        

            An example follows:

            +
            #!/bin/sh
              
             #Starts, stops, and restarts Apache Solr.
             #chkconfig: 35 92 08
            @@ -557,21 +778,30 @@ 

            Scripting Solr Startup and Shutdown

            exit 1 ;; esac
            -

            To complete the script:

            -
            1. Make sure you saved the edited version of the script.
            2. -
            3. Give the script executable permissions as follows:
              -
              chmod +x /etc/init.d/solr
            4. -
            5. You can now start, stop, and restart Solr as follows: -
              • Start Solr: /etc/init.d/solr start
              • -
              • Stop Solr: /etc/init.d/solr stop
              • -
              • Restart Solr: /etc/init.d/solr restart
              -
            +

            To complete the script:

            +
              +
            1. Make sure you saved the edited version of the script.
            2. +
            3. Give the script executable permissions as follows:
              +
              chmod +x /etc/init.d/solr
              +
            4. +
            5. You can now start, stop, and restart Solr as follows: +
                +
              • Start Solr: /etc/init.d/solr start
              • +
              • Stop Solr: /etc/init.d/solr stop
              • +
              • Restart Solr: /etc/init.d/solr restart
              • +
              +
            6. +
            -

            Next Steps

            -

            For additional information about Solr, see the following:

            - +

            Next Steps

            +

            For additional information about Solr, see the following:

            + - \ No newline at end of file diff --git a/guides/m1x/other/ios-instrux.html b/guides/m1x/other/ios-instrux.html index 5b9e67cdf0..edffe09221 100644 --- a/guides/m1x/other/ios-instrux.html +++ b/guides/m1x/other/ios-instrux.html @@ -14,18 +14,12 @@ - - - -header +header {% include m1x/eol_message.html %} - - -

            Creating an iOS App for Magento MobileConnect

            @@ -79,3 +73,5 @@

            For More Information

            +
            + \ No newline at end of file diff --git a/guides/m1x/other/payflow.html b/guides/m1x/other/payflow.html index 795fcae525..db4121f67a 100644 --- a/guides/m1x/other/payflow.html +++ b/guides/m1x/other/payflow.html @@ -1,7 +1,7 @@ --- --- - + @@ -16,12 +16,12 @@ - header + header {% include m1x/eol_message.html %} - +
            - +

            Error Using Payflow with Magento Enterprise Edition (EE) 1.12.0.2

            @@ -35,4 +35,7 @@

            Problem

            Solution

            To resolve this issue, contact Magento Support and request the patch for support issue ID SUPEE-1474.

            -

            Then apply the patch as discussed in How to Apply and Revert Magento Patches.

            \ No newline at end of file +

            Then apply the patch as discussed in How to Apply and Revert Magento Patches.

            +
            + + \ No newline at end of file diff --git a/guides/m1x/other/php5.4_patch.html b/guides/m1x/other/php5.4_patch.html index fe862ca5d3..94407a0e6a 100644 --- a/guides/m1x/other/php5.4_patch.html +++ b/guides/m1x/other/php5.4_patch.html @@ -1,7 +1,7 @@ --- --- - + @@ -16,10 +16,10 @@ - header + header {% include m1x/eol_message.html %} - +

            Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community Edition (CE)

            @@ -43,7 +43,7 @@

            Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community
          13. In the left pane, click Downloads.
          14. In the right pane, click Magento Enterprise Edition.
          15. Follow the prompts on your screen to download the PHP 5.4 Compatibility patch.
          16. -
          17. Apply the patch as discussed in How to Apply and Revert Magento Patches.
          +
        2. Apply the patch as discussed in How to Apply and Revert Magento Patches.
        \ No newline at end of file diff --git a/guides/m1x/other/remote-code-exploit.html b/guides/m1x/other/remote-code-exploit.html index e2831546a1..477e881093 100644 --- a/guides/m1x/other/remote-code-exploit.html +++ b/guides/m1x/other/remote-code-exploit.html @@ -1,7 +1,7 @@ --- --- - + @@ -15,8 +15,8 @@ - -header + +header {% include m1x/eol_message.html %}
        @@ -39,7 +39,7 @@

        Overview

        existing files to world-writable (777). -
        notenoteNote: The preceding exploits require the attacker to have administrative access to your Magento Admin Panel Dashboard. You can resolve these issues with the patch discussed in this article.
        @@ -100,9 +100,9 @@

        Getting the Patch

        -

        To get and apply your patch, see How +

        To get and apply your patch, see How to Apply and Revert Magento Patches.

        -
        importantimportantImportant: After applying your patch, Magento strongly recommends you evaluate your vulnerability and configure PHP as discussed in Resolving the Vulnerability.
        @@ -125,11 +125,11 @@

        Determining Your Vulnerability to the File System Attack

      3. If a page similar to the following displays, your server is vulnerable. Continue with the next section.
        -
      4. +

      Resolving the File System Vulnerability

      -
      notenoteNote: Magento strongly recommends you perform all tasks discussed in this section in a development or testing environment and not in a production environment.
      @@ -150,7 +150,7 @@

      Resolving the File System Vulnerability

      SetHandler php5-script </FilesMatch>
    The regular expression in this setting matches .php only to the final extension in the file name, - applying the handler only to PHP files and preventing PHP from executing.

    + applying the handler only to PHP files and preventing PHP from executing.
    diff --git a/guides/m1x/other/solr-ee-patches.html b/guides/m1x/other/solr-ee-patches.html index a02006540f..3d6283ab15 100644 --- a/guides/m1x/other/solr-ee-patches.html +++ b/guides/m1x/other/solr-ee-patches.html @@ -1,7 +1,7 @@ --- --- - + @@ -16,10 +16,10 @@ - header + header {% include m1x/eol_message.html %} - +

    Information About Enterprise Edition (EE) Patches for Apache Solr

    @@ -58,7 +58,7 @@

    Issues Fixed in the Magento E
  • Search results no longer include products that are either Disabled or Out of Stock.
  • -

    Installation Instructions

    +

    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.
      @@ -248,7 +248,7 @@

      Issues Fixed in the Magento E
    3. Search results display correctly if products have attribute values set at the store view.
    4. -

      Installation Instructions

      +

      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.
        @@ -322,7 +322,7 @@

        Issues Fixed in the Magento E
      3. When the user chooses to display all search results, the correct number of results display.
      4. Search results include only products that are in stock.
      5. -

        Installation Instructions

        +

        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. @@ -377,5 +377,6 @@

          Troubleshooting

        3. Try running the patch again.
          If problems persist, contact Magento Support.
        4. - - +
    + + diff --git a/guides/m1x/system-requirements.md b/guides/m1x/system-requirements.md index 154d718249..7a03586066 100644 --- a/guides/m1x/system-requirements.md +++ b/guides/m1x/system-requirements.md @@ -4,35 +4,40 @@ title: System Requirements for Magento Enterprise Edition and Community Edition --- Magento requires a LAMP or LNMP stack. - + #### Operating System Linux x86-64 - + #### Web Server * Apache 2.x * Nginx 1.7.x - + #### Database -MySQL 5.6 (Oracle or Percona) - +* Magento EE 1.14.3 and later: + * MySQL 5.7 (Oracle or Percona) +* Earlier Magento versions: + * MySQL 5.6 (Oracle or Percona) + #### PHP - -* Magento CE 1.9.2 and later, Magento EE 1.14.2 and later: + +* Magento EE 1.14.4.0 and later: + * PHP 7.2.x +* Magento CE 1.9.2 and later, Magento EE 1.14.2 - EE 1.14.3.10: * PHP 5.6.x * PHP 5.4.x * PHP 5.5.x * Earlier Magento versions: * PHP 5.4.x * PHP 5.5.x - + #### SSL * A valid security certificate is required for HTTPS. * Self-signed SSL certificates are not supported. - + #### Magento can utilize the following technologies: * [Redis]({{ site.baseurl }}/guides/m1x/ce18-ee113/using_redis.html) @@ -44,5 +49,5 @@ MySQL 5.6 (Oracle or Percona) memcached can be used for session or cache storage * Apache Solr - - [Solr search](http://merch.docs.magento.com/ee/user_guide/search_seo/search-configuration-solr.html) can be used as a search provider for Magento Enterprise Edition (EE) only + + [Solr search](http://merch.docs.magento.com/ee/user_guide/search_seo/search-configuration-solr.html) can be used as a search provider for Magento Enterprise Edition (EE) only \ No newline at end of file From 4c394166a72d7b2dc1d0d79b3b6913739afb39a2 Mon Sep 17 00:00:00 2001 From: Splendid Internet Date: Mon, 17 Aug 2020 15:58:20 +0200 Subject: [PATCH 2/4] new colors/styles acc. to openmage website --- .../poppins-v12-latin-600.eot | Bin 0 -> 8755 bytes .../poppins-v12-latin-600.svg | 322 +++++++++++++++++ .../poppins-v12-latin-600.ttf | Bin 0 -> 16032 bytes .../poppins-v12-latin-600.woff | Bin 0 -> 10612 bytes .../poppins-v12-latin-600.woff2 | Bin 0 -> 7988 bytes .../poppins-v12-latin-regular.eot | Bin 0 -> 8633 bytes .../poppins-v12-latin-regular.svg | 323 ++++++++++++++++++ .../poppins-v12-latin-regular.ttf | Bin 0 -> 16136 bytes .../poppins-v12-latin-regular.woff | Bin 0 -> 10536 bytes .../poppins-v12-latin-regular.woff2 | Bin 0 -> 7900 bytes common/css/stylesheet-fonts.css | 93 ++--- common/css/stylesheet.css | 19 +- 12 files changed, 679 insertions(+), 78 deletions(-) create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-600.eot create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-600.svg create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-600.ttf create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-600.woff create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-600.woff2 create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-regular.eot create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-regular.svg create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-regular.ttf create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-regular.woff create mode 100644 common/css/poppins-v12-latin/poppins-v12-latin-regular.woff2 diff --git a/common/css/poppins-v12-latin/poppins-v12-latin-600.eot b/common/css/poppins-v12-latin/poppins-v12-latin-600.eot new file mode 100644 index 0000000000000000000000000000000000000000..1029a2f2e1981ea90847f15684927e02e4d127e4 GIT binary patch literal 8755 zcma)?WmFWvzy6n{8+PejmR>rgySuwVx8_;&31I>0Mn$?qX_bz@zyH1W z+_(4poHO%0pZT7dcXQ^&2tWY?-7M*IJ;|D7QK9e@|W`=49@o&djpt@?nM0FQr3?jLstIQ(lR0O( zAHe|#0=NOZ|0MV?{a^L~0Oa(Qb^iC<|8l4RZ5jZBIe@_$K$!%ZI)YElV;g=@z-|~j zIl6JCw5wX9bCZ+_^Pr)_ElF_tg*#b;t{C0nZs9-Vu%eT3ym8AOtV-&H<2398;7Cs~ zNDkR@{xUArT%2)>+o5|!Rq#kX^kNHI_Oca}4#z+#Q}&0juvF_Sa`y!f`xDwvd^5Dt z)Vzipa1B_w(_^|hPbWX2bdW&ih6NfQ1j2bmD4rM`kBh`4cgh$U9dt-4Qq_OXx8SXIm zMCFi-XcJf9TdS;a9#XQd;+_-N4l;!+vaDNK4jXd8o^}`J9k50W_jrW!lI_u?lIcM5 z@kS+{NJ9i|(nbB6T|~-_zi_*Nj_Lw0N$+Kl zN`C^OC+R1}_c5dOICj3Ky5@TNT~YgVC#Z{!t?(RAEf%YF5&1#lkLuZoH;O)~SH+aU+hN&RJU}S+yI(yv>@XB}4X9y+`N3)LUY$nVvml{lHTodjJ}ku*(K~csz4;u~ zZ2GqkNajS2q9(CZEFxT0{(I$O-gTGFTYzYYiN$OZ%-65Fp-t_-(uED4j;d)$$l2C! zXj@Fi%sn0mXSS1e8Fe_lYhUBv8ldaqMfO;O*g_ClL30x#Z)Arr0%&3QqXDAvs~=B- zd&&3JjBF*)F>=-?5_)SW3nnWZ6;OG8ET}z{?SCK#{q$Q7!r=onj&|cT1We|9Z>}Z? zL${@y!{=X_GvBnXyR-ZJNM7!Piu3IS76QIs7+JY8HkXzSo&cC{+b=^TKzIb^-H3lqiFobYA>5sXJnfTxl z!;j_FX$kjGKxs>=v+aTb{%ANTNu7T~$`^;(p$=*mCaiMGRLPKx^)2eS8d=k!=93;l zZsS?TP(Gt8jE%3eht;BWR}Ji9Ri*$X*Lxyqv9_;EbfY^cpWu5~w-dd@;gP4Abqx=2 zz)cjgdf$_8^Hj1^I?dqFjh&`QzU%H1=(7=^bu_5#FPl$SnS#H9;k2MeuHpWms}wdx zHH%wzt$$)XHm9V>q~~L{b?vro#@`gF_~6Bjje^M@Ur3vfe`J-@j#3Z`v>nxnhaj;7 z0c_qmv$^{=qGNcQIZi?5g=4~TnDiq?i8=w{nRt!}LQL5=3GeReNizpS1KC(X~nloZ|a&CJ73d?u<5pUMPX7FHpJ(bG6%P- z5%i2W7vrhD@LGVcE>7wcJt8%Dt(mr(xenh4t3mAC;^ol;8PApucC3Tph7k56gB!t@ zK8rzu8Xq^`6Fm8;ieMhlciJM`+MhVF!VEG~fNmvFij_p^1JbTjN0T!Rw?}?S6h$p! z5W}d&y@-xVdTZ*yd~*V2j3UhmPxDH_B0=?lamq_RM2tBZ!N4lUg*RMWK97~U_~yPd zc;Iz8WfuJ}V!8EC6@b=Y!(}1wUxVbGqmuq;k;i=D6yg9wAv9gu zXsC|G8CQfNm(*9bqG6jQ8#Rk$J?>iID7yKc%sK%tK(nnZ@mtpe2{SgRT57)>)PbVR z@plWtY@C-ektyd4N2+9r^bH{f6C6^a))PY1HP@tz656~K^O}LsG!@z?SYlyK#Vuw} z_=kBYj<+74X)XjKn zI5CMi=d*sF!jo>z9#AbF3+=5tB`j!6uxdxRlQ(Rr&M*~)t*1zgodU-Be;+BD1npPi zXT(#yMx_)%l|oH89Jm+$btBNy;%;KF!kqZ|vgfkGoog@45+Xzh!<%xw*4PHbrdfzM zy$Chq;B0Ee;6oXw$%>}dAuz>3gNvMHgz%bg(*7FbUgZCTm0Si?L2rx4sxJnf&C0w& z)RJn3T_s5SMEXZ#CzQTJnP~9w@(C zEy6=44|GD(9*&|90{9-qm_rfkEMY=oR5=!M+`c|=h`ZtRwlZNCgQF|*QVcwZMz%r{ zA_B7Ul~$7a=+jq0il&rCoD*#h2 zrPwF_yExS@;CK9uuK=PM4qW=SHyAz2`S-NLhtJoVs=3x6p^D9u6)oHS@Ew$%-!xk9jKKsvOo|fbh6V%8d zjI#@1ILYtWhtkVqxh$PSD(dD%=vpxh^k_HJ&-tIr`U6A9+$PGFJO4a6P)&h!fi=r0 zj;eg*iddhj2?_H4h5$D|iBoZYpkw19ypJ`4+nhPAn`C>`mRA#F_X)C*gf6${y3=rU z{;U*$P9IS#O*24k6yy%X+%zF{%8#xSsWaQ#c8g!cH${i(w;x&cwuy&bS%4xaMbUur zKi7thgG~rbf%bp9F}Rf0xSLouZWu zA#1Y&8zu^M3a7^9axzMIqS-*3WwN?vVOrB;+K%?Kf7>MK*X0KZrRt{7x!T_ID%@mR zRA`_r8e2PgW56H8WS zVzf-$4k+Ih0?^Hb*pzFV&GirYuH9rK)o6RTYDs}CDvpn=SKk8g^=H|mbt$I26R zk^;K7MU|J@e)nbG3P`9EdaCh$x!%qVN*+7-Lx(d&(sztDil;j_=j2uMg4GWR+wCD%(=!@I%CQi7N({Gzn znb^P|xae54<_~lb@&tUD7lClN*fNFj0%k|T{A?f#WT_r+A zXcSV%heJyW>K0}k@5^+#bc~1u`{PbS-b>7fqST56uNR?Kor7Hz!jT2ew_jdAQ$g`}G-@lC*m<>A*5WgQV$pJ>XE**|L$ z1%Xa?l5F%{cpWIa&^hxo8$rxf5V{3?w@@ejwGkf1Fjmny6&Z3iqV=31?2RW`IEo*g zpDL4jf@@|jwe5@~L4RNzWpICiraa-K*w>Ax!t|&Ws!ytR-oE|QT*6>mn-|N|Dxbz}6JkeWE@dMx zW@K2;4VaU`TUVx%lCv6BIwY-IqM!$ohw0g4zdT33%f;B!KGh zDKjBrYi8Gv+aTJ%!@_oJw54Loks|pfjNtH_4(>wA!yh)+!l$J00Th;biZs>nZ1Vnh zSVJ*LvaGOA)w7w^)MdI93753&{>Y-!yafPXLYw-%NAE%eDYQ^^4KLy=4sc{QRRRZt zhl4zqr0m4|ybtxEC>B41t@Il_%$??0N}&K> zCgxb!&`>z7wixei`s~^%tY?}S`Na3(AcTMzuS!95X{1C&`#75FGVHl zAzmGiqGf?Sm7Z!UHij-+&QECT@D;q~qImFAty-DSX`-TU(Q z+TwHt?`1;?eb4q?jwORAR;fx5+$#yYfs+$iFyb&)WVuB+dMq?_A}n0Es{f0EXnGhL zCdCp>4{=P>s{VX8Aala+W!wv+0 z>_<2JYFt5ypG~!&vJ(A*;aBFb8`+iwD_o?qAcy|G!=O=V^eD3no0{k7TI;)Pzy{7*w`i_P{7}r#sE%hnPu>Ng1{W;wFU`)jT4S0TB>1 zg*ZZnmqX>>4zLQ_1!E+2WI5?#t&1s@y!JU^xObGjOM8;(1<1Pq=k4`L*Ai2?`Jt-~ zowJuLo&Jngo{s)|Du&$0pe)(ta2j)_pe}?ATqNgM2u|L8-KSa1seWmppBrZRwN$gB zG}24V;fhBtg?w<*VSFneB7y{M{LL(e?A)>t1A+K0+!5D zHG#geb6k^E9e`F&RMSFiVS;&_7f$mZ4als^TGlvj3bsm@iPrj*z<7F9UJEIIp(9n% zQLBQv z4v|-Ccs1xEe6hbNf)`7nM#)!@!e6_%n$Wx*ByBOw+Q?`9H(#D0LyY>3RC8q(%u8f1 z6)OyXT0KE5@IY))jUm8952~tw9&wgN;K>)og8!y1p4_}nvkH#z{Rf^1HIP$CddpG@r>lMW7C@$V&Y@;4GdC-J0x5|J~R|VBmMDtz> z6WA0eh?!Pr+M40=SSkIfl%*3?z@J$C$SCz7Go`P}N*@ECK4XI`0#)vNvZL+zuF0N< z-k?dXzag2R9x*#$J~ePu*+7h%1r$UZiF9OTAa>W%w4V5*#)nXC5t-F}jBO6L(@M6b+@NIt z-uQ1kWEbuHNDUr2a^J0|#qhEX3ZuMF9E9q>gP{&YP`i-Ud3%@akNjsTH+OsFGzK!P z)44UKS?mVQ+N3)0V$99@i5tiaJCT8kY(dG(py7BqLOew7C6zlt22d<-vm$_?6KMVo3QZES@2 zW>*S+biJYsy9bh?jc%`S%hp3Qq=ei^E4TW$#E$83)eFUbR$oSQ=N{i9Bn-Uzu(2U1 zlS#&Dn*mei;#VjZub8$aVnb!zb!cA@_9m*bh@zqi&X)L55Va@8$j&kg_+a4QGYY>; zfv@)TJGFdgAnQ`{R~Gy!YIvVITJIHZG~3o(BT`h}Jz~c!t3u>61ILO_yOyd~BT7Ll zQw0tb79VRAS>eX%e$#e2wt)+gX?xV}Dp}49^vaI;<^BMsxVTkHPfdTtk5655ZjI$W zLs`dUsy^hLN$pCCxOt@}t=`whsoaNIZLi3UO&)L5y_CkxIJ{Dt?^q#^wBW9Vuzl#t zX+80JC3e91V|3@vqC75)7~2^RRHgr>N`MC<$0Sx)Wng;L4NF*LCcXZ$`ErP&Al^WI5ph9Q3WT;KoEQKux=kt(4YiZQRJqsOlZX8sj%xt}q@GP&I^0d(9fe&U4PO6Ue8QmcHJ)q{)tS+__KiiJt8CJ+}-D z7mFK9F2s7v?Zt1uPfVLxl*hU0izy8xqI$6n`lvTzJ4TmC(H8whhM$9{i+COTbei5XDk&m``A{a z4v4`gcpsQ8o!S&gzRy4DDz5*CbCC`d3-aL2<8b1plZ;?EcmFv0?W?=U=0F*+=W|WtrkbC2)i`Oe_wL>D_G;cMdeK?@B(5f7Vj}OfUGSdS9Lg8#I$# z1O4j}b7(bUF9bK0Y_vWMT$^#Y`^D8cOC?U+$lm`I4z6Tg~*>9yFK+EGH4;vSDZ z^oVpw|i<$>IUiiG#!1?8s){!^!c)_||pG4;FDW3Fkjcnd|8u`J|J&aT^Rl7VZ7 z!}`uMfhV?e8#ntMyOMdOHD4>1Z!T1gy@$^dleG5umkgDIo8ueG4qlrq^ z!n*PG*W1*Jqtwi45q}XTu4Xy57}|Xo^6Ov#0~c^?LzAqDk4L#hfD~6^2&{<&=BRk{ zVkfWSX}amqwF;u!-bz#cF<$V0%>H(#4G(M$o-H-TAtE4GDJL}ar=(kYZSPa)dr_++ z2M3RF05tMm3Kuh8585_v{d8?vqX4KZ&|KL$`0$a zCeTMN;}Kmn-EaU$>?{>Hr|?(o8U^QK%ed2PrTDUY@}1P;lXjliJQ&)9g98mKR+LNv z_7UCNM>giW5N=(Kn6Q+Xve$Y$QBiCH&&X>cx{+{3VI$Q09+?u3x#wnx+f93Jo_E4z zZ(Pi96xCX36l%GN+=j`_Z_L(#3Phb>YLW-bva;Q=}yBVZl|WP(d}VBF=D^ zY0lii)(FEVLCXfi0hq&iq_Pv6u;ZY>SjLQo86!oP{#c8!=>FU+NLeSU?4%t{9z#w5 zEBABQ&?k<_IjtYyHYLVHf?|9yfd22CrmW2PYYT_vJ$kU&($-zKYu>^wXM)VS*0idWD6>xGlvk~EON787Zt4_pWQeon1H;xi&t&99a zn!2=jZlAF)>cY1wRR4B0J$G`uV1(_BGp1^%IY%5GS29E_(%VV6%bv>EEY&5mW}}Nc zK`z7L-Sf}QkG{%2u823m%`xge*M<3ovpvw1GySrw9vVUBH#81+2-_~&3XXh3M*dEbwv&-<8i?5ZDQgSTy$ z>5#=Jnh<^QoziivTmB?*vk*hW2i~I`8Ah;aegEg-ZYeSGBk5%gUX0Y6+WH)Wup8tR z%QC87hDp+x1OJ11wM~c{JhN-D6w`q0vq1j@=$y)>7Wy4Kn1NSxpGa{8SnWP26{RQ3 zmbjTo#J`$KJQ3zfv?d}K{dN~-s4`Qave1nekz2?yO3UJn<@_a^gyMJ7AJlZZcM$SL zlM9td9~w$mF+w)*TE`hiilBO?#W65&m2WyKE(HT0LBo)712=ZVcYkdu%d$DWm{=kh z@iLCjC<7rD>$!NUM9kb_Dm~=cxqU(t=Lt)2e`_npI1y7(Vsz=Nf@GlAqZtv;keKAY z;;-6S`uTeQqMCzGv-~(coEOW|C^iqU(kWa*qP)r}1vUh0s;7VXRQ&HP1;E%d_8he# zCH1ubu=}c0sSds}7`;eC8K1z@7f;;_+{msIx&F*#uoTf_`iYj0SKq>)wxz**i}Zt0 zP5$-^{j!3ha$bi5bKnGdUwJwq-TR1-+|E@URC9g@?p)P!ZhP~>k|A2?$8P2D_4;1?MAff nS(rZGdAKzN7`S=r5TPP5uW=LyFLEi^Wo@Y6|L2p&f7Sm3VMpH{ literal 0 HcmV?d00001 diff --git a/common/css/poppins-v12-latin/poppins-v12-latin-600.svg b/common/css/poppins-v12-latin/poppins-v12-latin-600.svg new file mode 100644 index 0000000000..63d4ce3d6c --- /dev/null +++ b/common/css/poppins-v12-latin/poppins-v12-latin-600.svg @@ -0,0 +1,322 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/common/css/poppins-v12-latin/poppins-v12-latin-600.ttf b/common/css/poppins-v12-latin/poppins-v12-latin-600.ttf new file mode 100644 index 0000000000000000000000000000000000000000..1eeb7d5ceceb4a74840b48c7a90007afa1d56712 GIT binary patch literal 16032 zcma)j3qVv={{J~=fB{4hhG9SuW|$Xmh8bpt;SIz44GM@n1QmIRpdz5CZN4?p&GJ$H z$}%fgvv*l*+E!bx?f!c0R=e3ltF3Lzep%^OTip45&bLS?s+_>Zj7#vm49}+O*~#X4zdfWR#F2^T_JvD3 zmOb{^U%c^r2cF;T>RY||a&p6Kxc_fL%x`vgb}X8?N!L$^brsrd-DvPLvE}F=if3K- z(v_<&j_Ft8{Ue0Py88wec6_?++;0f6JVyvUv9x2=GTK7*c)lC`)%_hyI}KOzI|)e# zJoL?F1A{A%whrziB(s1JHjQ|q7onHgDeT6J_+VcFgam2=HB_UL*^M+%t}x2!Wx&7e0Aw-~`z~gGC*dRtkjpJftz2stFRR6_#buF;mr|pZTi9{UuMX%o>rUu4>GnUS z+4rb+llFvmv-U>e!U@d@`uu@)$M9KqVBP)rtUG|IiPd$K*=4~*OX5fhQ10a=S8A;W zgV7SAvL-R?$8NPKLqb$qv?(K*lAztoOBrOdrlNt_tzAXAi$>W#uY!`fx$73@whzkp z%e1q~8*_!5V+^{uC*tFbdz&*nYwLWv=9UEfE=X5X*x2t~TkE}O?yPv9(+X{MAyvdq zf6y~QFRV00YhtE93_9sumt~>sESUz}h7uh~AS7r4wb2Hvo@%LwGT34U7+Nyrg^f3& zP2W^h)Wk2gK^WOaw+a3B@JI&@LsMg8QSsbPM_L+N(a=y)+0anA59B>nQdMn?sS=je z*H`kks;cVhDoz0{An|1{lUR-)jnPXRZQx|Ki{E_Z5V_W7&_;VHgF{p*o6QcAc*#{d zyOFn8SX)KMSmjV|RYiEHxivdyUV>~Jjh+>ukBokVG3vObC|Gq=Se|pdqadxk(b|z) z*dMLQ(wZt0Of@MQt!8FeitZui!RD_qYL9fMAB(R}%p#QY54lt1ACY@F=WwRMnBW@6K`N#8?Ip{W?Cc+0+PSlf>W(}>6Wgcv2 za#R|rvf6^Ismy4#gaj#rnOxJkbg+LXhIhQ=-%Z1ByMr2frnd`!dEkifUK<#b6wq$^ zJo|_Q;z1=>$&D(lU2e1+?JA>1PJeCQupzZi)g7|LzG1y(K-Ck<9-5b&+}d>0P0j7e zi7j(??7$p#q?6UKg`hd1T5uuQ8@y*>HK#Y7#(!#j;f2u`Uf`<*xJJnb`V>Mwiz$J;!*IWJfVW3}ubm@E8Re$*K_2XKOifG2HM>$=^$*YS(qq5!8k z6hY}}Y3V^s`{IiaK6K{HLuH-0xt(PdT{$^j6?*5--UV*H?1LIDR;HL-hG3_&T5fgh^U2bK{cI zZfjm*dY*kr`SM*J+gOg>Vy~!~HEWl}lx*?X&ekopG}?0-13ZFSN;2E5D+W?B9Eq8! zgY)A}79+5i3=}SBuM=M~9Xqj7OCZ!4=&X=gl4G22hTWKn;r$PARJrY8EGLT)kqO&o-Z&l#I-*jJPzvE%Zg! z{=iI4(bDX}u@x;brn0Q;yf`gA&Z$}mtzHCtgcBn;M%?Y>G8`dpu2E@40=rQ|?@LK4 z%%h<#w!B4Yj{b`7k>ne;^{n*S@Lwg)EL%=i2CIx4SQnF+wxqmxAiL$h)lWUMqW(m7 zMn*w?T6zKYrNz>o?60sxBClzz8s;hdYZvtsj?s_U!1!)9A4X9|(p{HWDR^!sF%UB- z2HhiS9Zs}Knu!`o$3f>h2gI8SYPo%&re?ryOSESft|~7dDa^K0l3_7tWSLCaM~Vvp zQ;`GK)YfFRHred6RiQ081)VlqXF*P@>RFr3oM^Kr{xRKV&dE)&W^jz$x+W+ZSDL_uU94%K;wDLYLy+mzdtxoO3&p~R(aW!-j<4F@xGY`|C6q2#Vnwa(g8 zKCtn`QycDYaI~g9k!#DybK0#=F4v+QvkVf=bquT~*E9#w9t&OYJ+p&$fh3F`0CWK` znw)Po(RWw@mnppwI$1?y&z*bZ+__B`@IkM3@-SP^!hm5|UeU}yRX)sSTynwIRpNWc7l!&YeQ|{&x&_ingz1S4Z zLzn&PhHj5Fo{5cZmV_kBCTi;`?warv{=9tQg09MANm&W0=7g+v+qm(neqyB96)*b> zyO}shF<)y^Vnw-?7(->Z$lOfe#=Z1pS52@opqU_x_=>%Htl805mYVA`tHn~$klkO{ zp!OL`mIa6EQo{CZ9X#1{>(-94;Q1?;{ibF6xBIIzwMnu1w5XUEc5}lWi|cNg7awCx zY_2ZfP@S17e505V8d|W}vU>Bt?}pZH(YD0Y-_dpJrJKgzh%1VTOHC|^i8XPofkf7Cuk9^~b|M?wQlsxp^~tX1wqU)d}x$Nhrjax$GpF0Zka~ z#gl<&ft?&by=v*wHG+jhh*{`4;1HHg zq2#I*h9FR*eB+BRsE@FO?q#J95BzooduD~Z?`5p$gE8ob-mo(8bl*RJevF-5{`i3K z4&F+;ejmHmpx?FI)mk-5f94i)5g#l*bWU1!yUo5JuV(R#OLWw~W%sz4{7Y#q8 zp`RrrrF9n+b*I%=EEz3bTaK-F9c~`v7KrbE8`k5N9&l)IS@6xajR|j!jnR1QvxvqD ze`P0y4=Hzi`3Uj`M!+&F(EAMlJzgY2tb_c$hdcN?G!TwAyhFDE3#9K2FI=={jK&%b zF_-O>p9 z6h?T$dRc&K%Nw5xyT%3v&?LQ;W#iV5!=VjCIKU@WC}i1V&-9)eyX%7w#9f^c(kU+7 z|G>E75pi(pnDBdGB5RDE7c}e{K}|1!Z?vu-*#EE>u~#6) z_sQ(0lr)3GTu`5ty{x2ftNZ|SB*&)c?dF1p?DS=oa&ud5ygAtr6{GSGHdg0nx1{v6 z>5}7OBJ`?&;Fy}cv~~v|P(w!4*pq0T_>Qzzran1#64E;U6f0fMp>zVu5%hr;Q3Ohc zAA%&gaRzJPYh})YvYnOdtE+xh22QRiE-x>pj|jC*YqGP~G|`7KgFjYz8Z)@P5b!H| z+C`4J$iC-(CyChjTP&Wh72 zgKl8UupY7pR0c1RFUOW$9Q*R%zP;FtXylU~-9O%jxBZx*N1DMC{xQg6p*=rhikDW()~w*;HRK4}%1&{d+C{r2d*s)b zwp_aTo+C^-{skT2eU`XpvlFhraeXHG9Vf=0jM==Izwu?YhZU0jh2#)^(m!BL#f$Z9%C$pZQ(xgcWg8A4(_$wg3Gn55h$|+LitRwg*NNO z`B}w-PH92tEq$!hXmE;4Ib#_$7pFGK-2b>u2s)ZChNkwumlSU)<`QvXhguBf3vG6_lP#g)=OdY9!>%hZZn>Em~*zJuMHrHpzsAo=@ zXWY?JI}#Sbws4xjCt*(Pg?kW^RESD#=c%!=lP50!>*7T)d-E5<=fXvIZ+I|&pW?y% zeLMos;ykjyF|*sJor;ocaRV0=7?L%w1A-jR2`trH@)k#gcV#m3x@8cnhr#K#o^@jTY~j_$B|t z9f5vvV`=$@nwkyel^bgf&Y0PmnYGoKK49zm4aL&;sJ_fvU0+{aUC*_R@IAE6q-L9{ zZA8ZSkJ=`yb=J?c4Y5et#%vId%FH#puhBMK8oq}#m?t!ws2RkZ%YV`gg~P=e&CsF| zZ5c(d?@z=z4SHu>oKtUb#?hYjC5hUSpI)VNbf(e`v(04&L#f45ZZJT#iIk;luoi44 zvX@GZ9C1Gv8`JdpU~xvww`Nxg7g<~bdK+Ee(QknTFzPiv$1k}Y@HkZ5&cD@{Bird= zkBv#RXJ%JBtP7nBhrPDQQeq9UX&ISS4r*PP?~^jeqK;FCg@?}wQ0J#5RU|B&qcKK= zMa&8aP&@6W3emnJyF?eU$AK5gm*C)9xpm_?IOS*I>b$v+=I8HR3k`EQB5e3Loi@0A z`yl7+TzDZh5HH9y{MQL(!W|JPLdX-V*%{tw$y?;$?3K^r#@{Z|#oCvY(L&)h&R;Zz z&jKl8m6!!qQ?IbV!?4hVvAwSx`|o}0=}}R9DYx3PLiCyNLC{I^K??8L-`RQF;av-Q z_jE7dE6|O?Iu<9)qxTEVRP-m{M=&ME!mqf-2N_w>x$nuR4lZB3@5Ix`kJAtu{J;ak zMd5P}lc(@+)`&6OTcF%+feX?o9NoL>gFAn{o5lU~It^wK!aBMUec|KKQ|QZm5JU%7 z1rL~B`cCNm=4*P(;NWsvG${IP{VoT6Kz5KI3|4Rt*eIq3IJT9+D#<;Ta&dAoI_EFY z!_J*gW4|fI$G5ezFfQAhdZ${gsrZRh#}!t#`ue1p=sg|@`nc-0_^QU?jEFhDtvYLw zFPm0qi*EIs6CM>Y(pZ(yRvoKP@Zfu!Y|BY;39 zW;7(t2w25L6Y2vz0}hZxm5ClAtSTjKbHk^Oyb56UBz!3e`q=8WgsR4oh^X*6ey!2A z!fDL6$f|4gofDBU+*lRgRvicMmU8&itJNLiuLc1Vuh{gVV&ibz4RL22xi%D06xzR{ zQe%MT&mNw!A0E5AR`a=l1OO#=)JalVGq>wS0i_3iSlulHV5QCwA6h#CWz{Bf4a-se1|S89wR zTL9%8G*LfIMj9%xgBU@vOd&iZF^&z)4$kN;92k9Uf9<^uVQ z_5yps!qheGCVN`?OpCUChIf2@H1Lo~4$>>E(Vg++>3VoYM&#?UBG1`lQI%aK4^i@< zkNX4M6{8<$(i}NS_OyiTbVrmrJv}$h;fTw1q-hSPn6z3`vX*8irKM+wgy4OAR#qZ< zD3!VCj)a`~=ENkkIVmXxd!6v>QQ@N&rCiQ)5$d3(w1GZc0n9 zaW^re-rct1hs+e@o^fewO;t(rYpXO-AsS7Xt}!>YMrD)Q3^9|9J?52GE4FXtd2(OY zM@!h(z|?g~BHQYZSX2^^?mFE$_U?mpZseOtx3rWuHEn8XS@p2{!zD77 z{GN@_6Fk>L!JWtqkBkY~^u)JY`>v@m%>Y(CNFt4(Z?l)+7lli8!s{_DCH5pavY|St zHFBPZpQDtEJgC)DF*%c!)nT`HWR)~FmXtI!l(Z=osa5e_&K_;tO10cKP|aSlb!2C? z+wJXH*&R0Frlyk8rl!);xsR*8>&naDHbyDDy?G)GJhX~#WAAb8&U4!+fNo&#Em{Oz zgwtkvh&}J-E>2;{1E==X@#HDQ(6 zWCZoF0q%uU$gu{_!i2*>_ns2i>C>k-pQ20Gj*hM!-L`EMBO(#xJ5kq#^egxPyE_%_ zu4jq5ZSQg6!xd3c!84*f`(!nR3Aq}RgFabbQ>ly%2@27t=Bh2TbaoA93&dVZFdOvd zM0MC*$ijvu<@;(GORf#AEy|AL2vqR3rpD!RtNqfapR$uZi$?IK93EveEdLb$$H?8hN&lyL=gg+` zgs2@mobcPZcT%5VQV17iX5qEGqM|&>|51Zcc@7J>)QAyYpd^Aei-uK?jxdr7C3by-Qesop3kx7v-~=-tXpdcbv|t z#aZWC-ifd@IUMuMmU#|GlbJ?X^tzN3oi3FX)g>m@*{pR*Np)N}lM^kLM9gc3Y<@5y zn+hW@vFOF`oz0sdmo&ab{4q`lrw7pkQ%{L-`T*z9krK50On^c%C2+tjM!7|Q?-Kfr zuzm}@@nT%xvwQc(-O|+L-caRuAu?23^77I@y>RO-yt<%AP3w90tjMpxeS`La*GK;& zpSC$L|Chp+Ep&DDFR-k%QVTy@Fn-(5xz_`lg2;kJ?u|ob8DakaClCL8qo)6pt9J;) zTj)(6#xHsH*9YQnnK$o0v-v_1*v%qVZo7?Z&UjZV{hryNEs)8Ts#}uB#6(+Ux2Rwg zRg$A`2?00I)$ZW=sJqHFw~bDgxtMLjtr|DF3tc%0X0gx(UKVRYveSrzby!PIoaAG& z`xn}WuW7%1vi})!c1r)j$@a74*p&7SlkL6a^py5DCfol&J}0}ecX;x$0c7R_xGZt~ zCRSLiIDJDkN*X9*J)eC>y@aJ#3U8+?!DvfQvC1dal1|2`}OU^WNJIdt6_A@<4|hvB@4uMV2FG#&Y$3( z-}@Kahmp?(OV4b$uk#0^S{a4BF8j7IxB);W=>} zB9M$LN)sTEg+3xy&aM;{UFlx6YU#owM<%OhG-{M;#-Co>-@oSg=!0&oumdvADF{Kq zac9XBBGh7?McfS(Bj-fw^^5Jp*R=E9Nd3=n4g%JtdHDQN`&shJly<&LslAt6z%D6p zxdw4SE%#FN+#QE24mVsyFWj=bdH2rdojY50-m(VwxA6Psowstm6^iKl2l#klm@OXI z6O}&K%1E?dJ*0$uJ5f;sgw;!_Gg9u*+N^9}ToQ^ynFEPw9gE_UQ7y{sPqKH6pVU*6 zwG0jkeLyd~ZZAb0hE*qz7NcII(`5IX))b+Bq}5~!wHdV1h}uz|LwMYXf(*y0Sd$QO z2aP65@jK$4uWuhFQ`WzXN->utg)vu)S38DL1$x=xaG-i+XwSTfJ+m#XJ*y`zB_-|8Kp{zW{fpfz!|6D# zlet`qehE;ABVLkG72OMtMIM$*;e*?g5mP*=nIrXO{f-2qQen)fC|KS;f5>;MEWx1F z>&-$qd%w!6h`bFjx z=%Q-6%&~P+lD>X@QDaqAVqD?6YK^17nf?YU8dJo9M1jf3G0GR`4V-!tFx z)^E^iLJT_5+WQ%wM}v5>m3@K;jcezt?w>?lXdJ7ZyWJ|gQZAh_nINo%MdX!lm|e5J zymW0vWp-%n%Hq)EEz?!YoNM!AV)FHdTw`qpD|n!#`_?j^A6{RSXiwGUs%9FeskFJu z@$>p}o2^`r@0teegv)xp$i20ILk7Klm&m1Jep+S$)OBd*9>fboj{euT4`0(BFxmeM zx&LZ^oVc5q=PcPirTzQK_Flp(i84}3?5vpWf!^j3AkL8SoRY*&Dg-%G>kJg73GqJ*xJ6Z?qr%>a2fi~UGVYz=QWYxxu(*@jeX4R7b-SIT8me9HR_!Xa7PEIvTn7g{8)Np)}}qy(zPnMg+YUorJtReM`TooKj#Zq$MVx<_ z_Xn>@HG#2^4}3k$o`(z*))4YaQ83b=xw+I9fOYif?hsTx-- z8FBmdi~80gyMl70N3orkBeyTi>(S|#=hdt)E#Fv^+i%eJ<%^}s@-%CS*H6xvm^`B) z$5@j=y+U(%mC~A$VwH+HsU}lu!P?r$jKYGS!h}m#vG|#M52S*0$ zy~=&W+gVDzyo?>no9?HG&&PK#6dleIQe;}`-JB12HU+0MFVMS(hov{NnyYVQH9xuB zZ=$g8i`X~k9j)E+_@2HF`s`19wh4^zHx{|J9do)FkbJToyw#o&<&>}UANKu#WgS&UxoK7 zK?f=mm*aC$vWUDu*V1=*Ho_*lH=LyNI&^_AjQ-aAyH{_|M;~F_jr- zD>x+(n=`X8vK@&o{s$VT_-!d7_uOaOx<>|S;K$HL`;(snNHJ#4?n1UBL@B=BO zmm9+F);>J6>Pc;VA!CIN+9yYb9@gF+)__xeGoO2hv3H)I*`76OHZ2)h-#0td&p&i_ z-;Jw!an{E&JJjDVbhafOy9}cpG8M9Ga-I!RX!tQZg;pP^g}xR`#439j^{MHhwM^(> z&Be`aJL+55^L4^E)E|kK_uv2I6WadKM|>v}=h*p9!E^L0VJ_z^;CSMcI^%IEdJ=Mu z+>DyoO4QCMV2I>3G*FP+4~B1p`(FVx?>6!#4WoCmA9yM~ot}$5*LvRU`FqdzJpbwC=@sdf z=vC@9-|J?t$GyIg2g~c_UGi=6JLS*F-;#gfO}vA=HQr|L0`FSyHt#*&fAqfW6X(<7 zGwSo4&&R&R*WjDwTjqO%?_IusnntJDr&UecIqlfASEikxHtwhLOZ3b0+w8a7?=3%< zpKE%=^z!K&r$0aav*|zj*ZGh5zvBO6KyZLIAU8W%otCh{l zF6E%|2IY3;9_3xikCk63e+-d_C_c-zwd_FUK#&z{9&J0J)C%yi7m#M!NA$80 zGL!8hR#_JAeIb{>Cwlq`S%NEwd65Ek4}2zp1h8Uoo(D;wpAtQeIap~g(Xnijz#2&+ z+e?z!CQ{9AB!x^zv}_|uXDdh^m7{+FiDe~t_YrBwY3wF8lSF%jlVbMYSa%~S1RHDF zD;O7yE9mMo4Z(9d*4R%9>7US!zU(}H1JS=7zc@q4)}yV1SXdrWv)>XY`vdX!fd9!J zA_lgWOk=skOur^u*=6z|y+r!iZ*T}O1bYjBwYi^Ya23L;@Lvt-GgThG15&W4DWJ*3tw3Uk+TR`m{#IRKPCqH6X~Z` zG6%o4tOj}t_~*FCzU;uek)@DK4l8XVJ*Az5)IIil{*IFyumuxomLx^q48!Ll*g*8vpQzG@n;RiRF?v@i|94WDD>YJn(eb zP533GT>1qMm}v#?1`|B-nQ}`=>71f!@*E-2N@)#`0XC>6_=_ieSR6ZzA2sSu+^%vh zPhf3i;`+g8eGbnF;(I^bO(!=H7fqqF*(r90on!B*gVi(Dk?Lr*L7lEHP#@PsM+ZeK zVORKPI>z0N-gT3`73xrRgxK40O>gSD;`-S2f@`;Hx!@y^@h`_OUN~{#@e7Y#c=*Ec z3kNRjz7Ti*$q&wa@Z!(#A};iQe0h__d^aA*zY@dI6#-qR2n4v=MJHCaJ=NEhjb?Nr0}Fo~C%%t1>hT57~z%h0Ev z42sVy(9(-{3&jz6WC*|AXj>t^j}d2DiJ1pUI!@aqW9}ZY#}IORNfAtTCvwXt5Iv~#MmB^k8yn%g};`=>_fQkzzn5;xd?yrlJN^rUq6!fNd+_} z{7VH~X;YrAg(C51t8z?D-QOVg#BsO`t%I0z5chrfqJ(q z5D*t5FH=g&5dT$>N>YVg)R0thREp^@+$c!c;+wQ^*6}F!0jbuJ>Mp8lDEKfUyv`6q38wf zmw-q5z*TpH0?R=a&X=4=hsg+X(yPcQcx???N7j<3$szJ9=!P4~dU6rg>LmFqd4xO) zTmColK60~ECR3it z{aYaY=3B*IbH3A~aA?HuTD5bsCrw9OirTpZipP)o$g>vL8Ut&v|L!KgW^%2MB!#Dtq7$^G}WTlkb1V zEl@v*n>#wVxB>vQ$e-Nu^PNcL1}bZIS_RbI8bB=$UMBy+3CoAmCRBdH`dRfN6A|fN&^eWVu2{H83t)@t*?@90pca1=vwG zYqkp*HAG}az`QeJ?|*X}8$+5{kl{ik#TaLX?E(^(fGU7`&p<}QaQ<*`On6MMg3qrw zwoQ|^BCqf&(P5O zeV5FbIYfbjz!4HequIDh#wx~ZR_gBDayjb($eDdvP8`c-$4V*Oi>^p zegj%jXNIVRvWrKiB1WbTVyF=?42s-x+z^8z_wnLLhnGo7h5WO#i9Hf+{XpZwq{^%; z9c00oe%&T?eDRdn(F%Ps6kHa`VH{H9MdBF&lf*GH9Qd3zora22cL>i#PR!B3`ePW= z#bRt9sz_EXMAH)F%Fwf+jEe@xv8qSiq=EEZG_h_kc-f8vQ|ySOKxaA{%i6!3@ap)BaWPH}kGVZKh$qj$U1 zG>|aE?+Lw<5|K?N8X3M^T%yEzsA~3)eq&#@Y#?c6MzXXt1AgErRwNOGAg2b2HCq-y zwCadixi<;uOuL}Dq4USuNo<(#1c;EVvZT^ulvkl@O{%zD50~Xqy0{ST#)UiW#jd7# zVSk)wsLtUhYbx%&!bhNfI8@)L`=mIoa%cNMH@2XQ*27=!Cn9Gu0>cSq_9aAv7OG$b zVYbw2!e(Lz-3!|injIf|!MH#)uslmJm)biK!{3T#YxL>+KIR24t|$r$iNn5H`=pfC z@^ZTN!m>6|@S)Imeci!Qty_k(Q+nE}`ud8Bq#6KJN@%i30Vh2vmAvJwN*%lhze{6E zoz<@t6)%lOabTSekWah>F*UUWJ+3j;BTlP|p^Py;nys1t7SBS)eJ>@{)6HZoB-Hp# zSUF{n#9#9xQYpQmwl~A7 zvtNt--Cq3|AIX=itn8RlsBhBr6KOIHk$)_h`PE3i6_1rLEZxWVUQhkA^w@9x%44iJ zU4{Bl;&XMhZ7;#P6xMz-e;|PkA%d+ImZHh3MQ3YXjhL3acNX*YYpL)zk9+5{5es|K zSuBZ5qhG0uYpxeflf=4hX+xXs5YkL~auuT{Ixe9EGvX=^GeU71dF$S&A8cVFIg61Kf-s4d&9AM}Plawu3=0Z}RE5*o;g}S7Xyx^buZ~ta;fTV(-Zl z6W>@dDz0j1VzY*I=VbUqcPZmQSc8x)s5)x=ILFz%eq|bT+L;0ZTIpx8Qb=0_^+i4p z*TG$|6Ss*xnk+`P`}H}iXFP^YtE&)aWgfyG`2xr#MH;IISXEHgo&grA@h zNSoH60x4Os)o@14J?QHvrhU1z=(BX9)tKu3T|&x!Y_cV=i3K_mq2gLySsw33gQEsjNH{Tb>QzHmR6anpD;3v!mtaI8UL2Es-IEz z3b{)xdTAIO*RmXhpO3P>Z%2q6F9wm2Wyw|rzzrFT&+kxV4R3#yYc+|8=q4s9^~?lJ z5Bm$UD?tc2%u6_Qz07TrvOoFQrKT>XBaWnPcy;WtOcPN(o+LR~hFk~d zUd6ZB5Fl-7t?{;&3a&L@MvJI)&Y0kAVxr?p)i(<0uV3>+npf8~aM4_q(X5FC8*=kd z4>iTK+pPB_pK;q;>ZzUCAFqKgn)X?&gv#}jYk0X7S%$a{Fq~n{NKwzAdgEh~*{URi zyZ5_CHo)r_-NZV7Tu+*R989#n(Nyhim!|E6v&9~8W+LUXeoJwqg__N>LODgK#W@KW z;bU*uSi3kh>Kol+b}1N)sDUWQuk{+s9XAjN&k`VN<`?42(X}0`jAcD(TvHHM%q!TR zqOi&93P|iuvQ&k9Nb-Nn+dHVvF1uAYtCn998rdM6H=efT$y&cVM`3GWM?+@*+k_($ z;B)tCSTwtJ;qd(NF6dvNcoa-G0(&+@Cf)BE4LUgBh|%+{Jkb!#Fr4ft6cjjs zi?2cN{O#)mKJ_vG1xh=zWZPB8(-tjX=V>Cu2a45$%R8!Lb*R7ks`-T6iyh_+c>ukVrBZ|J1*L^{c5}8$whT_3kyMqQKZQ9NTXZ3;AV5%?O{LFm+`=dn)R$@ z*SB(V0ibX`5frgpD{pIZP7#QqsEC*N`F@AB@e!R02(GOsytinhCz8>FBQl#Qb7G$h)b^%De1y|jiISvX z>|H+7e@+;v;922xFREmouB&f#h`7hEvn(N4&?>6jO6;r`x3Oc8;jyqzQp0H|TB)Fr zjxPAEm|CJ3tIcpES)zrv#(yp<#(tfmp!DWJGlpSGJ^EW(Iix8rkAkX_HdQI#8UA&o zO!N84XJ$V#fo$)pL`nNZXYi1GIdK>w1V1dW zD{0v8xD}1q`&71~*0EE3?nHl9IPU;SwOi~jl^TL;>FfJogNOa9+wiKym&c7ieqV{9 zgndzAr{BqCiNK))y*iV{oea9y514WG>g=G^T?3xZ_pRy(kFEP9pPeTD>pqsQ9f!lK zP&zB4ddwk(-*;juGQYnvbQ8Y6mP)_{5xk*^?1bz>b;mS# z;WXdi^`Ia>?k>Z<<^MzF-H(y6|CK-whetv{_^RmKe=5Je6z-~K_w+J0;tQrTCOl&O zaQG<7;k~I#xZI8twG}ZwzA^nZB>D#x@A3sjMX+0|9>_&pE9sF;e88AmuDP;IiDvk8 z@#s+7ePK^Q3dTeu+fCul%f9bqo)FuQOWuz!v0s<^-Y1Lls+C0U$qNCs5-!K$Os_0f{r>d8!-ruHnbBhtL zs?POcgEEfeP|lI^Clj-%jxm*KH}n_&(VCPn?mxu1a9#T5p9$NO51Kx?9-!Xgscz_{??VC)ul1_&=O;W|w7`eSpyt+xdu&Z{V=h-v zK5mR>7jjZ+>-u7Eo8-$r$<6>NRX>t6n#c1w#hF#2&^jMKVatqMjN{V5w6SU8^7jF7 ztnayciE11p>#M}5KDj_>aDzQ!4^&;F9!k1T%Dp1=^tb(5Os1H7zX2mjQuwbp>e6F7 zCKLW>Z3;0%o0D#F3kP0eoaA1 zk)gZ{ar09A!vRaV(2c!ZODT^yp;PrIUoGWpOZd0!8x-m&CYftJ9{AjR?3sJqzMzGD zh{4o7v{}3Ej?!Yg;x_N%DiitGp$vWzo|aO29^{2K`+>7=v`YC&O*c19O}B;hYrNid zN9|i~NH_4(`au)5{?QNge^1;}C;{;UI-MR-Ed@)C7*)NV8F;bJ9=W|j$CK8uEQH%> z`$6yTs@3X6?lw(IO+)2_LRryn3O6O)yD;>Aqa(hiPUeJ)2QZW!>HWc&WoFkqb7B?*V6C!`OE;`|&!7k##az@HLgRQGa5U1p2}nQ0XbNBkA% zM}t#?AqDGH;hc(@Of)TXag))}eaJ|yW91^??ly-C22%{`1Si?Xp}RQVPVXlneIcc%CtQaoIU0Um>BaIK$~0(Snn{E~57WS6 zYO)qQ0e)?b{28hdKgi`6CV#Hc8THd0q!~{?+17#G{?e`f-Uo{>Q~gr|ooSP6ksXx+ z8Pzg|1ax-OO|%wsg)xCQFQmOky(Ws>r!YWvxsJ+W;C=8Y6zz@X%2LR&!vvx(JjB~; zf3{#8z?z5X&bDHS77N#65xQR~&(dNNaJ{|3qH*MmYkM;MVE91dw;%+w%mGY`#a$_j z8WLeYazoCxJ8#-LC4Ejvd7}pIvaWFhVnU|Hw^_j_J&Z+grT+qUeY(M@SKk{fa2~64 z!$O~X{r@g<;^|&F?_v^$Z*dvc4rc-IpWz!8`bj8!RlAWVm-9gp?1B~SHg&uNn&e$S8(kx$5Hc*tDimj2Uen8k>QE!p z#Q&^8LtE*WEDx~7V`7+={q|uWubf0YTHbe z`2%uFlHV%eFHU376=M>u&m5m5SrD5+Ng5yicGhTS?609z>tmc_#de=PCpr9Of%DA>;BW zP9jVGK>7+9(^=WLddE@Sj4a(OM8_x4E^6Cii*(L?cmXTaf82n7KGJ9|P*_wTB*dZ& zCv#Z&&1qpl7`*q2Z=9VhU$Uc5o%GJQ@C7=0$f2ey`L84Jz7OVTYB9or z-*boBw=tQwpWox+6xn50sp>%46wP3kWM(gqvfP9iWuq0@^{-{hhpgI*<~}&2HpGxV zFT6OxG6CYS_Z8-LBZwnMXZCMjFLNe+i`2PH5OhX*8$aBrl~tY87wuo$8)oA*xMHE2 z(SH`Zj|h?Z?oDj&Q!_5OQpbv|O4zj)Rg5dNbU>_%Hh>jVeOuVaT}YdLSyE=|Z3B`b z{E)2&LPcM}@u6*6Vc9$|L2ZU-utH;3^Z^H(Q36&r+kFFnmI?_J+)a-%!&g_#`7I*O zT?c!6n>H_9yiO0M4MY77KOojd3lpP`NejzptqwsQP)bj(bTvDp3TYjkO+_}>wyU%K z?a>09!?3=&R^MJ|;vs)_Sx^5xeH=!YT-mp@o;;OMytAnlG#?qYH(n4cXiTOL!9%<7E=RG4q9}N(?FF!|)gMjdm`1t@$;I(w& z*HN&BL;~vYzV_%H**{)AnhyQBL@{@>AP`(XyL0zh%B$@!WZWbUFRvUeTT4SH2?-}B zKR>4|eTxbOG`C0AwWiUz>z`(~9VPRL%fKf013rExP?O>ym7*dQRct(^axD{sPpV>) zVxI7DK$L#GM^a1TK;C*dbZBj9FiKg7$5}WqH9i(I67ADBV z&#w1_Ugii>LyO8d8ekX&kwx7T+3E#*E}$}mX&G5gHle^Phx2ws=C1)3x%$VYJ~P+%?)Q6j=Qhhx^u`o1$yGtF zkDxzXv>(M7H!(3aC5k=aZlG#+cQ-qzs*Fturrii4p;1=UA}_ksQF^s~`F?HJE1Y#>P#71| z7!q<{-i9^JwR(XRyCL4*Ir?*-uW8I!rCeb^y>fn0Z=xw9qiKP+!IkJYREN}`Ne>!3 z^`SY;XuZ~WE(e(QffJ^_kQ~-2^kP`q9L!^6s0;?`GEGz1anScj9L|JP=Tm{S{i~PB z^&2iD>$hB9PnGuCa#^!7lMNJtii@zY)x56m0McsavVziw#-Cg;j_lZUu-RZO<@NJG zu&w`_yRYUVj>eLRI?{WyF=*s)?Mv{S@fxj|Pt!<@9oUk%D_iwFVBvHVwBzo30e3Q< z*Ltb*+7*Tb?#yJt{kcgkb2x%=$~W&<{Y+7pPhjH4fX;@oYk!FS=Nb{*=Q5j*@=Sko z?HjLiXk*tO#Ew@7jXGDQb38W9iWtV6H*JKKlnr%K8H$*PD8gS-|gWSKFPw4!7oAhVnyvXS>J>@x|!CD9sl3JtyY{oq4A z)CL_0M=b{zR`bf!lU(?i7?0yRm*#b&uC1`X0fj<=tA8BdnS!7fL(t&d)p8&$9rK z;3-mYJoHYd6-JmkLP0cSE;0uAo}mx!-Eo^GkS1dfZ}*>{5t3sj{j3^@qGS1q+yKc_ z;s8kAPl~6{21Ni{VbKTa^ek53{Fpp^r~dT%z<~RC2$Js|o*Z8147!PZfB&L{yiFq) zMuf#VNM)-8QV}Hr&;9ciw9?e$NAgmr_~eTnNbQ6xwDnd61tW z0(+(QJ3a1Oh_JIv7Q$e`21HJ^OC)zCl;Imkb zyi=yc_5O^%0Vq)%K7*6g%a7M{I6GV>bt+LzDQ5fNks@Fx+% zfF?!g@fmEwm_mch)yJ47Xyj4(%P(OoYH}zya^-^6#Gt5hWAj9&5%gi!vR>d_ax&7H zmc43yHgZ-+fZU9CqGWaZu5g(klfdWsI~mcUycKkYb@L2>%u(1lL|sgMT<6gF8#77g zQGIG8)%0Rc|;XN-hJ5g&dpdMGrPolGsoJbzlJk)GtvY9I$9v}>jtc2;dmhR7v*W*y`X$O2f_)8t`Vt!P z_;tx%{c_WBdg$vYL0G1AJD3T*Gal9Zw^-5KF~=3=rombHxJ<~-J$&R-Y zfURgL7*Ax-9?TC<*e!VHDJkthRJAgPY^_(Sd8nB?5tZX7z+&yZnl`V=+>*Cxee<+hm8(6YoFbE& zE#gWh(Oz3iiBCYeM`%sXl#Ln=?NJ>EwnC6ENXRW?P^~oF$F1|YYBo|8rb${zl5@e1Ew(Pbp057(CAt&$T=TjN=U;;Hk4 zdEZp^4N`;NX>r-_dm0ipaT-fi?|Jdi+aN!S-`D%I_;Y@Re&+4k(Dh5$n@bgBE-nVz zJ=y|vjZRQZs~XJh*^&NL{y5k1qyg;`G$*0V{JamL*wEhO-9HDqX0sbG)k_rE-J_h4 z{hr9|Y`hhL5PD5da;>=^tBAd|TdEO@D{EQmWEaIBYo(V(&L7u(lk=DtgD_k!L^z%e z>Y)CLsOvExTfMXU{b*?^YrVsE{#xuK{pPOMNMNUbd>W;ZnfiJZ>bzA-LR|#BY~S9w zesS5n+P3Lm%kUEE*r&bzxV=oI+X|O>lLum=c|jOUBsXMWlD^c_Unx?nrLWr3S8Fb5 z%Qx!3$3Z9=WzYJ{d!NL?)s(P!(6GqI%SoN5MK=i>vT8KJcJe^IJd`;=)WYxtqnNR( zUmE1231zUY0fH_xBEh)Fqg-lXgL`G042aVjaS-;r2K;sDtV!*cLypcR4_pzHzmn2 zC5o1FEV&4?XraIy*k>E8&%{L4f;*K-C(jb>qX9dp9!5SN<&ZH_nh05cnxt$e3)$6;*{x$zwec11mH!4SJ^#BXMPpbpd(PV%|A=*gdGi&#Hxh9^la|#@ z-!G_i^n%uFSzzcwydt^D#@Vnpf)rL1o(RS<%>E*UJL8Qq#3p>^zCiF*q05Y+R-Ja; zOtccsPM;NmH>|^e!;D?%p@&fx|sdC7nvNk#*A9Ol*DzMh`-v zvM*vTw7+@>Cl(%a_G2O!EmVs?#g#?qBj1O+t|M+B&boElfXtMVZ-HVAXok5XIlBZ- zd#&dBU7mt`x=&CB=chQR+?7Ev*u#ZRhl$CtCxoQgzbd{n%*%N5b@&%Q5Ba6{QC)!> z8f(kIQa_*VmbwG_?a=%k|802e>!C!}+tKhuHZe!{RpvvdcSvj&DTj~6gfH`#)|kN@ zOc*ahvoA12w1>!(GL>KPub0Imb%3#hz(t|f@avr7)%A_$_L?w3gYkfPONr*491r0a zXb<0K@L2H&n8?bFcQnh!k05JK-yYsaT)0~!LhNr8mi2u<(-00njY zpO0guxP0)xejS&4@_qNc7GVln;*-JwApcYUug@d#wdE&yn9KC%k0mDFX^3wsy-a|z z2Dpk(--BHuR28u*_O~ZKj_u~j-)qf3)|)T#n|};6UHst=SsR+_XaiF-EU(EM_8a83 zCAwQN3nc)NrK*%9#EK}_yJY$?%toMGX$npw5!(&8$c0;OK}3J1JK${a4N5;C z?yXPu_^L~?-U#`GKktHr=$~HaAb;rH51oiQlJUCcky`V_s&*AaWwIG)3b!xpZqT4c zc`srDD9)qr_Wz%`zD0s z?+Qb2tLG36nlR@|NPJ(U+q0!RUVBQuWRNy!V=-sI7_CP08ic&g!9>nskUv|!m$Wg9 z*F#fuoAu&7VK7HjzrWnm`*jw4hntQJ>mL(>i;2CitN$G#k|-0}_VO4fxD6e22mz44P#KY%!+yR&{6GB zyfg|X#ZpSndd2wX5rhcPIsgDTtI0wC)eciHlrb3_I-sW^BX;Y*!uWr8a}EYHxzj?h zxF)d7Q8k8|8+$#n=<{UH`X=aE2}J#(MpPcEVQ|WFkybOBrY}=N&640SI(?uVRUxUK zMCX=E{IAevRYrusj`J@m>(GJj@#ZSG-ha@SAVtA zO>|W3e9IS-?KDO8FaB;g_9V>_uJvu>_a$0w$MT@S;rn%6UXSvw$Nk%jJgD;{nM^A| zkQRp%Weuh%M7OtY$NxAytiOEsR_4<_){9e;@gOd&3$a;nM@>3V{7&ke{wE*iY@#jRt@MKzgo) z#Se->i($hcc}x*Kg}1l2%L9(v-by8CB}HYhFIgY+lsuqfq00*@nh{#V@btflK8BW; z=CtGK_d`Chv_49d#vN5W;^`~rSM0;IaHw((($mdpj9`*W{_2>-2*1Y3Dc|6Y&sDSL zkaboTti)Vw_qJhFcMM;wSN6yI7!_d30?r7SEra#ygb-BKEyLabKdwtUqsm?SF z%;vpRC=b6!TQ$Cdph}VQ|8F1b4GH>h)9XQUSZ@aVth;lE+hwGc!?a;RpK4-EF2F-W zk&^?N^qQ=f3)Iu?g}fh5c#LNffM2Cz33z~WDb^eolNl|>vq|O*TGhHO!1=Tv0`3>9 z9%OqniKaA4IeZ?wbE&pG_M3m7c4m_;SqwY9o_6Qc9Yp-!U+{3S(i2jW(h^gXwN*6K zv=BnSK=<}*k^Q$E-7Alp$#cVI0rU0d$#kzNmb@%gI>TUKm=fh!N~um~g=KB=8XnDb zwE)4ip*;7=N-QP{$%cVcDOT6qTJbwB3QSf&i* zZYH(2-|zcb%>Cca;sZXAu*qcpaFF+fBI41B=Q+<74*Yc69SbD>v6k0acQ%rXn&W++ zIajjYNEs^?L+Jge)%Ls7^1$o{>EQ2R0o6$8}2c)BG@HaL2kp+hzphC&G}C5PA#=ziGL>c$+Cu6pq2T_u-*0={SH!YdHHrF2*_OFQ zvX(|_HuO5zDTQNres2EM!X!X5^iWO*o zKz-dt@}kri)+@gc2gd*Nd-+eN=KjRs6`k6D1VvNj30a!r*7LO6gq z0oBP>L@RTnUM=%d!KMN>Gd%~pWt7w?5cDk^1Gufq1JtM%`>kU1pCNAElW4(fz=0jB z68@iMUux>v2f*6^J<-d6eRZ8!VDxRbl9Az6n1oZRXEFwCu(q6Ma(k)o^k#4Gi-IM< zHo@R96f7Mkh8^#O!z19)CSy%c(Vo3>PL71d!IHc=zo}+En`h=5b9C1IAO7>=yB80a zE-am0I*REu6@mjF z+QLX1S1j4XI;6qwo6j)!r-1*ITbBmE)!31@d5ZC=@31UW9fTsl_FMSGySG~kKm+Wf z+=n(Q@lGxN{FUaCbL6UItDm(NOQ)35F4}Ncs1HA21LrR@^pyY{do`d8&B^jLstpvH zRTght!nG?>Q2mM}JC_>nQaFpx_%JCj_S~6*^A|B4xIe_Iz&5?Fy4$Dg1MM?-x3=IL zDGW8bR(l-FU-f5du0!!H1WvnKSpG<5djpCueyy|4dWT?r@WFZ7?GPxGN?}NmwcQZh zlMM|P&s_bO!M(e0jtLNRkf<6_%Dk zTNx}(lT=y|bjpa*kQK9(yJLA8NAz9y7Ast|D#X$z`Tp9h`SbZaNjNMCG^X*IdApZz zZLG-T{jHKlw7{!$~Q95ZJ=vPk{~<_BRlu z&9Oz!3H&(y-C8E@Ct3C$c-CcTV>mX$N4xOEHFz3cGK*79O|ulj_wi)W=PB2{h?ol^ z!xM@7iCio3yD<^^+n-ZjNkJ27;3VdIcK2Z7kb+TS@*Wb`MkE44v@eV%8ULWkxMgdg z#NW{VpA#v*>7C>=*!I-9)o|4u9~bS4qVpX7J=SD|eC6g#EK?kNy?>`-lFM z-!Vl51Le^OA)j3W!taAc%8zk{A%=NHtJXNK!b}9yVYmwV<#|WTg9F9Z0&~5c!sS5< zPA0NQqK_C$BtBhSUR-sB|C=$lm#)oZxvK9yU3J@XJW$0az&*zZLkgjYHGnbuc?pR- zQgg05i{M9A-)G=K2A@`R_GVFWPiiSNE4xH?BXzN18%moq)*rb9#75c2cp~pXws`KK zJA*2F{ZlNZTVh*=LQG~D-4R(13SHB{CD)CrYo1q{a~Sf%M-hC^gD;hGN?Y33&mKbc z5%MLcA#PG}R)A~G4nBImB>c_w)9M>~>>y_Y4Om8!R;aFGIl`Gw+bOU{VfAD1rEiqj zzkdzOIw+xn7*v$!trXk}C*{h8mATpZH&Sq^oUrg*KskQG+}mOGVq*5)Wx+)uGE0=E z6l;aThO+m{(VT<(8DRp$GyD~74Z@ihd&D4m$3AYBpUq*LEWIizzWE~h3r03+xV8STQ>8x68VdB2+51sbcL!ebS! z>JFzm_{4EgvSocnTJ%~OF!H}%D&tdWng$*@#3g$xhNtIL^}wnYJWTOG6pF}+a$lfF z9u3;S^Odv-eP|2*&z-r|(8R|NMHsF)gFbpN9JwTEYYlG0H&1cN3qTDNy8Mih#xu{% zbo0IMpZ%McaP5TX;ekSLnd8gw^!&=q!}>bcD^DDT!h5)_K@j{jG#s(`^1n#7yf7?dA9pmD zn<-8P8Mxb81W?{*6RSq?UTl;Z!T zcGT7ff@`^2CSxvmn9@#`lYfJa9yx0C?&y*}j&$t0_e6~Hh%@oyKvB?H z$W46n?1t}M16~`@;jM3uj<%gR+4?qY-aa`hkFXE3*~7YsLKW_qVY6rcmZ<I^Drvfno{d8m9EnVVGY0^1&@K6L-+M-%amYUu za_l3@$6%91d`zx};dNyYp^E3}+}>Q@R~J&)-}gHuBSX&RW%4ty&1ZU#zXkTILWvOH z4O*KD@k~J}i&deNvfb5OmCIX5+~0h0%R+y-r!FL~bJuw(HzPwR;xc&xc6z2L1FUj~ zx`)EdhRxps#rbL`)99w_bb{nV$z(Bd-f?mZv&3S16GN%=GQ@Uq7PrW;96Ugy9-tE5 zCX=rc4!$qpFsWi*MusSh!hq5_;O?FwGLPl()#M<^dbQQ6KU5zNAJLm$a^$c_D+?6#fBW7k z#M4xIlUB*?sMbJ+=Ut7&weSsbthiLND6WjwJl@^snRmOcG`5cQ^x5R_$U-x^q4rQ- z;Y-f({@))DOlyeqa3~G?B?j5LNt%XfO9Ov&#}K;5|6SPk>7K}aYDd_f8ibjY79N|K z=Ojr93oxmJK+mRg`PsVV>4I8>#THZBU%fhvC!C>eyEF*kZxzk%G1(jEn&9Po>kJeQ z*UY9nB@o?ZW^*|PYTaIV#YwN%zQ%F9hJAJn^_Ec@m%!#(SPZ9F!gShL0$o|&dgULL zKHpkdVatfZR5n|-=q#GWn(W>a^)M&sn_uu_a2S8;Nya6E&ldAo0JrAvI~r?C?LLpo zzor9?YQx?KpT1zSepmzN1^Y;H0onpSbN^UVe{Th}Zx>Yg&cfRji*LWv6L;SUdTYQg zf9BnL{zb99x8w(?pnZjwS*If*3@<62Ei}(MoaSJSyjBaFQ7(}%TozVVmX*aE|74e2 z*;znvgl?dMqrT?D8ldu(Z(SgklsB?ivqMDMeO5aDaqFyN z|EYizJJ$<0_!ok*>)32-CZu(1q7Ei(+1$wSQpgRQM({AGfg&niKZUiCDO*v=`Mn!O zk$I?0jgZGJtRc&)dR;-qyCR23n9#H&v15}cQjg|p1#FI`hOGw4^K}byzkHz%d@_GZ zDp!caa)tEN;9P;q*Ur^ywsPgZf;n(;etG`r^8D1R*eh7Tn_YNg{y^s+{eSEOiwje} zje{Fs?n!7#06$IL@4r8D%W}71@6<1Szs%e;-!*}n`3LVj@jrR^&dellf(O2AO!wZd zVqIgGd4M>?%k@nyO%2a&;Qe#qU%C3jzjp!GThAMIwDr%y+`-}Bqk11N?#Ny@IFIg8 z_JH5d*?(}=16YNyqaKp-iYVu`gV@3BgJvpEQZE&D>d%tVG7$=m79i7PRBD<+h;F#7 zmC?WhV5V@T19`%ByR)V^JY;Y7?T;!h|vg=XO0G76;OMN zMCa^v#1u`R?Z;+92Avi%Wa{IU(=i2o!0v=nYjrdOR(Dy?*JBlfECOn@G z=?d1QQZ8a@V8ZEGZJ(o5w^btP&>NtREl`fORU~fB9zh2x`7FAG*93$YY!`KZ^vPeb?;J_keMR+S*zR`Kbbdn8Oi@1=JyvzBO3C zXf_W`6O=K}%sDuj;3lQ{M_og(a%-WphBP|3AJQg~b?Ehqjt+@V*CA2VEmU=MO0tp7 z!c?@Jq0Pz5%+%#+wHk~C50)3HC;QvREuy@g@2C28sUyAeUE=mesWiicKO-BY4(6RL zCS^z(WTKATvlNV6h(sY>fsxT@7=@sQGcNvOKUnq@_Bc`~$6;es&<-!NE z$}wr5#wS+1dRLRo7O;tQWeHAH+E@~p+Y1ZApti>+wVu49-uDQD$j=~F2!6V-Ch0It z;5D8;9wzh%2L=aPJwS`W4odbJ(rAKGCc8ob`6-luU=K(Exc2RbCqKd*{SY$+=sDQE zm}z^by>rJbX2^D+{J?~BzimHgsyk*sHgzugLgY;C(Xyjc=OZsh0|O@7L!NAkyp#CK zQ0GV|c&q*|&s5zb=#giv4pi@b5{ATvXhMr|nj(W5@?v=zNx`|H!9}SI8YEw#poy9A z;G(eL+{ENtFl-Z~E;4BFp~WE@3^MEqSlT?ecMuel!;ly}gI6?RVYiYKPY`AYXVS!q z6>=KHNF@mEOUmG3y-r!Nm16*Za zcocOJmc#wUyZ+m0;C6S9b_OXMO7nyDe7!rgd9bR=5x53z&;dHscE(5wcv3Y4`A3Tf zGOB8Sh?ahcF^PkdYpl7EB9=J4q?`uTH279nI@bS5BRSI(W@j&1_a%qmV0q!-4tH(S zz^`Ak*yr!;?7z?D{(tArWZDV5^^k%}hY!&(rv{>azu~HRDjr3RQ#swR+zFhr7X5XEM_}PSy}3uybVyxu|YVI zF68s+0wV0=?JXOm?i>wBl;E?Kcw$Z$vC2|Ki1`3RQWNkw3^zf9MA8TZ8WJfYfbORJ zleYtV3Qr!WG@cB1&$kqK&p+|^y-@{tZ&?`(E04>tSeaa|Dwq~7k7?cJa;1$1qfE{( zjZANp%k}xP;xk$_En9kXI&q1Q|?JwO;c5=eyi`S;YRH{`#K+Oq@HePuA6`zW+HUg0Uf4T!qkP zLHOmirvBLuVh40wSyoO4VN=Z2m4C}O;q@$$LdQi`>Cur55fKwH2u?By6`m7`)H%TK z^FO%kKX`!&gB{erWF)2Izm3{X-A)k*Ar40f2`E6@q!DN~$3%F&-okXMxty&Ng3qxE z7K5qcu!nM*;szrk{BgXkMk%YPJ#2;S}I0*-QpCyMVyq7zvbYMj`=$ zOkGJLtVm6z5`Z6NI@#T+faT{&kcwZ}Bh}W0-nNAY%~(N|;7a<$50gvS(J|v_0VuBK zC?D8|h0Tk-n-?`s63!}8_qLLO#oo{NyX3{u)Vm%O&;ecoi5YA9QcVNv(MHX1|y zX6;Uk(|R2R=B(8x=|}1Td$}lvvnlOtEECzSa|tg-|9X2{+^>$+)Bx#QKj8#HRLBc>eTQKN1MC*Qk$e%@NVbUw$$j zqut^#aqX1%a@uo#woo#d!84#2wl_lZ2BAT-Rg+na;VSCI{8sG ztZB^Qn*qJM6y5a?ghv$WP_Q?v4g6_6AW_6WTI5oUb;xsd?XU5&W$i7H zN`2eg!DKo@D-!h-mB-iV^cf)a_bX`p=W5@7zFQTE zWkJkWPvJI>b&zkBQ492{+-E5(!W^@nsP{gl@d2)?(iAjs6=NA~%fqP$l@Bh5 z)=U;_OU42$GlfO7Usw=kHcLH}_JT=wD2K{$TKQE@2x2%>8&}t1C zU}pbBu46(su5*A#JA^zcMZ}}iMWj%Lq7}z1L`5ycMqf%ha48yW*u&>jqyL}rMHJGc z3=xFNdovnYsQ~WXUYHj!0`_8c#OC%l8cH$sDekHTGKWjo5W-VsGTWK4#%?LELMhIl6V_U~Tq` zY^yEcw&}Li^!*QJ>-M~F3coqL{Pv;u39o?q01gNTtda)u0km-O*=2>~UZ7Ih>0tj5 zlR9L5XEfq1Z1o=d?kJmGKKSN7lg76Cy@jo+4rV0`o^6GA3tQ)}2lMOTAK$WJA^& zE5KXWYU*I-cf2uFb|V;`Mp*Qhz4=Qa+ZblIkW*vJ8-k^`u+>5K-N3=@Wx+@VycYm( zVXNZ@vstEyEslFwuczMq2Zg)kxN{LohK@|9H&=qSI!5QS?(LpDA+f+N0BNxKJ$vBi zKdv_eX8QbHR@Qe#^VGfUkO1`Qxa?H!tn^fNUbN3aKwgZ?l{;ytNx?tGFJkjA4({u@ z=R?N{fNc8C@IcIe`Wu-E=gt6lI*Fjk44gYTJ~0gR_0>z6f3;-b!5Ok&zZD(dgwoV#~PhrI$hmAN#|3ILV_9ektYTGnU&7P4~X&j8OpJMuOF zyxhtB_{BFb=GJ_&hybe~K*0AoqiZg8T>r3f!ni)>MV?yx{bVchL}98RN0WpOVGM4a zXf>#K6EZ)j>`AD$3M(HqkM#Aa6ZwO?hoy`dm01rWJt)N`s3zbT%CjjD z9ni_TgG_0k-&JOYyu^XBvfT=ffrGJ3AU6d%-Qthu$8WyXLnXLLLRu^^-$CX7++oP$ z!R+e5XrHvxSRH~cMW&exidlIjQj=r#2#3ulk{SwXJpu#J?X6|Z>Rgi8{c_{7DP_X_ z+m7u~b{AOIflkm?`-;jN*ooV{3E5|m0|z4%NBO1gvg3$Q0Z|4xCNU!1^RK~&y(;(| zm_l1;lz_&a2fe_6&zIb5=#*WmbS(@bEz04Tz{R=ei^0d;D&-uQgSwx*KGD(u81VVR z&O8FAT*wehl9WVB3)gBtA=$#YS7^s>+M{rCc8=%PXNkQR;ggBr>!wx& zHj>2-mH0AA?~B(!0Pwhl@KzfbRyA` zP+4Jpj`IstmwW-F0V@Ih66k*eflx$LOk6@zO1KD-qC|@kD^9!wiIQxzNivuea0sc8 zP|(s~VBz2q5Rs5kP|?saFtM<4q|1>MXUeWtIbyJIz0571=pN%I>F%MjvLN6>w=5ka?W{g>vPN%uey{F qaPWIVS8496R4YVxf*W5eCzAza$0^=N$dIW*(W?J1#vz$Xr7!?H$%aM% literal 0 HcmV?d00001 diff --git a/common/css/poppins-v12-latin/poppins-v12-latin-regular.eot b/common/css/poppins-v12-latin/poppins-v12-latin-regular.eot new file mode 100644 index 0000000000000000000000000000000000000000..ec62940554671f9b7dc19601a65f6d354674bf50 GIT binary patch literal 8633 zcmZX4bx<1&^Jb9X5}>#RCpaN!ae{;b#T|-6acH4XD1>0a-Q`7!OYx#D5-3vK3dN;( z3lu30RRtR008@6-~#?*!2j(504zW<)_j z{u|N&0Pue}v96N&f3^RKWB^@&7r^^pyaadxUj17j1Ly-B0nPwFfIGkz;QOya1b_jA z03!ba_HV}W|4e}YzkUEf*+5qbrv z{!u&C-$33XsGW(N2Ys*tdB9aH zH~mv`>F;cnAg7kRi_OR4(zlXm7G+hnBPT8%B0OTX#6!gh?t`Y3XCDe1t;r?d1~41# z%pJH!s=d2CPkz^=psK8JRz9GVX;`7&o4KSi=5A`+`oUf@sCPMCAV3!~Xr|N4ZzJPK zlO~folC#e(EHzYtQy)qEBIAM9X?aT8i;*dZ@|SSGQFi7y+-;U`F@I7eCrKO0RILnv zZ=AW}NhE60j)Mc}RKYPn*XZ-HOUo;;s7$2Swv`gK=Xgh6(K7D1PAO%R;eqh}-mQgN z9$3q_&p&ORdHDOG{bk2R+xtyECv$m_ntL^NJXwVxr9gg*jcPg5yeLA9kgBineHf$5 z*7NYAT(-?WR1?p`lxEO9>%__}>Jmp*X>BUIZ-b$}HHrOu5QXhn)i-O~S7x*x=Bl4$ z32ECL2OSG!a^+XCP*+cwNC3}U|? zTfaG-EhPM#uR)aN(2r7ncH?V#sQSRVnfKJUmV2dabiPP!%Yr_OgGBGB9P!N?vz$^w zBAR0-D3zTpWPY5_2l|zp21mdOy4{er>Wp*sD&6?>?d0M1?{EbBUv~bW59s|EYRAbn z+idbeQP$hGISl)cmq;v}n}AZVdU{nzyVqVNcK5h6IFIT(ko2Ydv_{-8)ANRVe12>; zz3(;|^&Ty~@=XbtokG)`&t)XvuRCiVf4#}FV>$+3x6XHUMWV%V3G&Y0DQ zh>kU^peC6xzT+QjheK3q8;49dL)2^_$dgJAa`iyAo!={>T4J|lKMd4(pt|{T_Ux89 z)QI1+D_qKNcQm3MD@Y(_5<`!N5C{0lttpoSS>;>^Yk^)TUZ#y^d`Knf3#t#4u3(Br zQ+Zt3b_Q<5Z^u5Wc~-~e>D%yjQ59?yBxob^`}6TeY#gyT9F=v`?)kC42=6CGDQU^k z_Cv^a=tA;hHI65Ro5p|-`zY=$x$KsX!v^#xZIEDfc{!B3GzV{9&bgA&sci6oboV&- zww2kGifo^aml$2mP?DTVecYJ8cQ%}{xSVu|aBp^+@Gv!Yc^bxuD<04fCt=`v6Rx$? z655Y%-BhuDT_&4YG%)hvM#+gsk#W~-6^8e2;A+LI=ZpREY@uaaz6A2o7SCyEyWJG&WpoWTE;G3e z*|87R2xkrstXR#;=>jfUC}~y*ztQn5U#(`wKS~UDexJ`Qds6BX7=OD#D_CZum&PkX z-bgU3aWvk=2S;DN1j(A=Y{U*QB7V!*lQ*&xz0k}t*>V5v&MI9yVlL}7d!Ta1)-U{i zi0yCK2D5n@Nj+uIM6$Vl048R59hUlu#H#o+pAYbPQ6@qIE0d99QJaYE#OmTAt;8KX zhopM;cjLg6Iw}}G{8m{6Rmwb!4j}YC4Ad`Ke3sMB-Q*b&s+Yl?L*j)tF^K_|eL55m zc2s*Srwd+Eoh5{9Ewz0eXU$vU^}4Z_-mY3%^?)lH3o`~Aaa~YIBz9{u(0Pt}o9(Nr zYE&Dy7~#u^!6kLC8{xfKR#_mtPT-#q>RKt>SclK4oWaptY5mr%v!al&Fg|NaykMei z!bS$GW*Qg*d}+qnA+D%D>|}f&W4}XmOKNa$S@~L;;An_KdIREyNyK{-?@4>;oOouN zB(yMp#mSy-9Yg&Pt+eJTNI-K37*i`d zFWIx&-1S9JaIX3;bt(cB)xvVij#r9R(zBwHh_&DxdfG#7N;q%hPz~tUW`9pqh|l!y zq2C~XD@7;(?)3GdeO2Rp9u9!-5>6{~f^sde2O(V7d>i6jnIht`Gw(4m99Q&_QBi<>{SoC3N3Y)D%h-0j0hKWJ z=^!z$szdMH?WV|RfthC`0i`ZjEwrB(Ylh!*H79euy#yu)F&z+~kX-=7gPIOb-zTovi(Y0Ueo<|8Dqd_;v|_d>Tf-muC{-NxNbCUocNiwBrH>Y{ z=sv8q;C9Sc;&B4pKpZ>5+cA-MU1n)5_iE%cCus~*n4(+YJWa7j78cldfvSks?8D;f z$E%YBD2i}g*&o`K?ZHo~&TCU8&nWausoelYtJV5VlIqjE4I^!!j~ITuFGsiF@7ML5 z=K&h{l;O%4z>|Hr?hiqw7j=_#1auPO&bEuYc#%oNUx{NA^?&h$C1gNRB^`RSRDSFP zX#ZAhI?8v%uQ@dHxo0*;n%_xs#5i+dZGQCvdao-B(`!DB{Z0#}R;r2El(p0+jE#mn ze-PQL3#H|xLN-I4i&d6 zlL{@AP1_I~nIq;4E&R%H5A!E#?_20Q-)nhEpZrmp#=A5QGL*f7z|x8Mv+WDp?G;9j2L=@PK3{o5O>{L@;C zxQeWWQDsoFf@`-_m0>(c?ol{%3F|g(H$Dw|V?ZTF1ludN zD#TaS77lgO9X@it{-(_H;**?MeLmdmBa&i%E~t!`0b4W7D~o4PJX6mTiq*|N|7&Z~ z!~+v`gXK;W?aueM^@Jc74Zh$ro+N*Jm(lNATeD;Hbacw(2o1n$NI?Q1ABB8BvY*N@ z>UShNvTL4(_hWGe6ibBUcwG*wZ$@hoXj`*>K2Zd7(q?It);*7pblgO>0W*}gEo_x! z-?C}kblj1FePi`44(S@E8l;0&T6zl(sI}Li5G-~=hh31y_FiTmA1DtiJUKbbmf(3# zRj(>klLH;BQ5eeQgo#|}O`q=g`Wog#ztym6PJRcqA$h8(&&5qD7l16QYMBCF0@-$0 z)q*n#ZYcvWzUk{TNGa@jm`ND^3l~#s-l$(;b@$BG0)P*~ESEe{Y)W?-7 z4X=+mjx~KKq7Q1zUTDSQnPVxfkZ*RQbz*?R5c$l%lsh{!#;1lyO}hkT6sY5i(?{Ti zhhyVY;yL0-EbtX&bjorgf~{PU5)`|@Lejb<$!8SfOG_KRoKoZWk*nNsrQf>BN==%keI1S`gtpc}7>_$Bz~ht$mwi z2+R|BA4ztTzXCfA`SHXXXFy67$n_oqGoEv>_51Sh7n%_AeVC4_Hq#UAIm(r%$kPvg zqSS&HuA}Vg#rnJH$!Le3kWulf`$aCq}Y>EOJisyQ9Q3c*`hBh$KS-`M^&Ua zD(3o?!DN$S-Se^gd}fB&%Snvi_TMUCHyGjA(oBW;o=-(kTJVg@BCa_;mG(EyjHcz# zsCN8AQF>lkh8@KoY*)Vblg9`=0H&? zh-JSq?$x?Z81@c2L@{bnTSTLn`t~;=!9B89I;104DgQZ1i0!S`*EperVJNHrSxTp( zGZmNqupQKxbJRhwBO>9Ks4?GPdZoqa7+d;7UgjdY9%{Faa!5M_&s3_%XV;)KfuZNUw6X2S%- z^h<2B;OWR-OU8Eo-*+lOJeG8(L?chn5{*e2pA79Q#aE!3Sn&A^tMcrEt^pq%@Sj61#JS$R_r@H1N-vzsiVsfouxlE2NQ^ zeYfd*c$S2Q#Q8rTo<+FrWF`YY}Y}bmBZE*o{3%artj&> z5_chamcx9HN;N&+^46OMK55q@b86W|)koo1myN=Nks!V-*<;f@(s7DTeif3^WG#x` zKo-l}93rN#+^qR+*Q*9I(A}+aQ8w~UuZTa8r-p$JgsIzUPEdQI;_8WgL?fwGG#Na*+_4?2w~;1K~nTHnlgT%kbROa zz{hVxj8%MnLqm7AR|KCObF*~p%D^Nx#hbGY3pdSf>1~1km@g~;}`&Ly+>x-I;aFAj}oir{Ldy~RnZF3*)nGYTU z4~H!FT^dvxAX0scaVWaOu;t|o7fOga=;b?bR{W{+&7?2YtNtdx`6{7i4&kI+qB_8S z0CsaOb(>~U^#^m2Z-17AV3rJC6lss4ZvI)t)ES7pGw>%o9IW7sr@hBNFPv+a;xzgH;15&!w8GG=@)i3`h21f)^)9u}=egCf;PbwKJ2+3=aq|xhI0* zb;AvuPZea~p1Fr~q{NOQT1qE^F@e$7-&};qt49^h<1byO^Q>mGz%lKGl6GJLWy;Q( zci5S95!1)q>a3n^!b6repE!|A`hEb4A86^nd2hPP!+BeNIEcALMw3nb(OC#R*(XB* zg7pd(J#BdM9aQiD-E_==LQlI>)ovyIh5BbZx6OUh{k*h3;d%hk7e_`@>ew>VTUL{a z>C@e(6586tPY20ZI`>+*fYofhVM|6ej5dKrJ8fMEfwZ7^!o-U9(#EujH6pBQbMg*& ze9!&UwNj+0G7=!K_X`+^1m0`M2~LN^x3Mh_lNnmPg*DK}7fZ_IVQeW_3DFVLdb7Kf!Xz80bI$zOM(BuaGo zi+M&yeb6_neDt^@SacI+MZCa$%D8dwXzyufuoq9Gd zGNE&8Flyd2>{fj08j(qL`gzy`GPg~YbHRm4bLo1xKY6kg{>)}_m-00oHY)dWmV=G% zWixMX={sl!J~Bk@w$&R4DZguHsO+|3b1x!vm}X~7%OEf|+W$Z|#K+{!)tYy0D?~t6 zsfIsrbwGyT$oWnoIxMdxJ;8rkV6e^^?wwI3VL;0x+A-z8J42g2aYH>fpmf#;GIoOX zaU{Tk>xeg{_CEY%pSb87eZHb{EW0X~i_S)imCkSh=s4BsT1fKaojIG9KG-z$A$G@MGctvXFU;`<@??7_>>>(DnDwcBLvR$t$Wm6NC zY~m%pDS`O-!Q?HAj}-%A)@qVH&@j);u7oQ;_6v-vx<KRnhP1Ci$rPVH zE7aC-f;t87&aoCw?Z;yUEvQwSfFYT3|C%97m?-SXxjMk0|fu!fy9a$h3#6!Vc*iF z|C;zxIqE#&EbNGjJ3VDp_*QBYNBMVK{}##M=i^+8^pzR$&*qx3Pa5ZaIhEpLV?KIm zvV0>^)kM2`CH^d`E5k7bY$n4sC8-LSDa@=g3tY_aKzTqB8u-F4G!`|gssBWccw59) zPp_8PUGBF8>Y5}jwb>Eyer*_Ppq(cUlSKBbo;P-I0X zi~~vJBb}U+#ux@%?Q>G zT&6*(HF*F#w&{rIV7w_Him0!H(Kxb295p1bHs~XCiM%lKzR859Y7GzRdi3%1QB&nt zQxqkqu@hOl(ydtw5Tp@&J5c{R68%N+{V>fG>2<;O;Fu2GSnYMyzh}rl)dr61MlT7Y zA&j=aANb7~L!J8Fe>k1;Jl;$zteJsJOO-PcW$Uw6!=DdbtV(@n->)PJ8=k8tFsu!w zAT7uCzU~=oe$VGPSl^vd=2>;3Fa*6hYYVvMOmNmJw$5G!I?zmIWCbJ_pGE*cpZQ2Ag z$wNSNx#=!Hk4Cn&V#-T~BLGHH9K^g@r#iLm=;-f==^MRqPfCKOaaqPBe&wo+enKN` zVJA#Pw>j2R0{nJPjSLU6Pmn(jC5mS|JsM*42G>71%bo-_Wv~~?6AryGtrP{7hAA5I z>;|etd|vSbB;ZN(lKVWI(yz2IS$O_BJ62Jo-TI-|fh#oXh}60Vl+21RX~s@~I+?#L zI;teBuA9f$%XCV3!0v8T9Uap|P`-i^q3%^YH?!}?;VO-gJjhC+aqAtEeQxUt8d^}~ zmPi)VRrd0Gm6P*t<;=Z5PqE_tHJ@*ZB$ecXi%#K__wG~hUX=`D1yDktDO;E9)RfEh z->Z>42E>L;^TD&zk6uO<=T{Z?NFETGR_!3+gu`4*^d3>SU8?$tn(mmMx8PcuuzNO3 z%T;!abh5K~SVU!*`Sj(R?;ARtc5fwm;P+T7hz~1YP2$N$$MC~BkUMo z6R4L*ExwR)OlJRHx66Kl;~ePh9?vbz37EMEbV~+g2AKn7wnK#+t$z&}TX4A$ZZ4E) zVb@(q?-(Yx+E1`;i@8no1&hQC4UjnLyIl$;;4bttb&N7nOt>WJ7;RC=c8WK!%VyV8=oQAKaOMe zScLARAS+1D)VRWlK+00ZD1?D${K^vgY}{`5azD-(UqE%8nfSt9j6q{098E&K?s> zDRsJb-=*{RL~#v;`^l>MdmQ>A6)btxzu1hLY8sa5^%Av?#=Y?Zmo92{j8Iy-yJ%}ij>ezLfO?Nqmw~hyZVKOC>EN2F+S5Glic91S`+Ig720~u zMyph?1M?MNHZ_X@!R4998Bk~|6ox(1Vplc7Bg7eu;D=k?8A!Xxd=<(v5;-CivYO(_ zenw%E{C@b;R5-_qQ9H?u^-C->htwVP2asOvRSUt;x~KO2yvXlENKK`T(2IXS47$v` zC5AT26u{Muz;K+=h9{Dv=ZU{oIT|M`67zT%3Dk=|VMGJF^GA^6o7{30-!=FmxpWSZ z(i>yf0f0&b_+z1RW~YQu!?h3*0kn8naQDuBng_=By;2u7|DGR*6&eCjDcxnOd7IkI z^R;|6rau2L8neXbv-^0g>vA}tB>d5RxT3gm&l_L(x2*ThO{UjSJ$te5N-z}@J+oGp z!|;(1+NPs^5N)_~!-d=2#65!jY^E!#-4@V6-KX`L(rzD^D^3#cM9lHpanH2Ny@|yX zpnv0Wf%dNH6ey7Z(Pj_9e-?4!5M;>Mvawi3|Ky_UO<`M~;h4%z)UbNp7y#y3G-czf z7vX=rKw%9EpuIfViofp@l5YV-QpA<`ILNZ4KbP#Tg~=f5-iDCAW+l~IMo^Wf1rc}a zXSWZ$NEa7-65sFHWx<_KqOit&B1)kK4PT5zjXLT`q>TLlsmQe6n@@d3dX0D`Z@Lz{ zN?UJu`pTZIeT!3>d~q-HZD3Uj|DJ)bO~yvvOWav*E*Lpn6?J=pR~AZdI^4)?wW*L* zA}j>ih}%xJqj0)?#{K5(SGM&~kEYhr7yPG=*5m4%oBD@UYF(+Ex6pCbZC+ue4!-mv z5ApMJl0kOW8ab=>ZSJJIcTaJ5=$1Td3k)9*+*OS=<5Tp-zhEb6MV;9Y zgfBh6(6n2-E3ivhA!b~kj=3ti!6g9-7(vX{cO-%$?otdq6<-D<$Dy3q>D0K + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/common/css/poppins-v12-latin/poppins-v12-latin-regular.ttf b/common/css/poppins-v12-latin/poppins-v12-latin-regular.ttf new file mode 100644 index 0000000000000000000000000000000000000000..24dd9ea9ecd752852bd529ea98ce514a8d3ee858 GIT binary patch literal 16136 zcmb7r34BvkzW+HVY15T1X_~gsB~9COUy`Q#p0r8ZbYE%GeSt1Op-@CtfngLBME~xC zAUcZ3h~qZm;OL-(%p0BOjN*!pGm4JmHZm?FlAHHE_a>zvZ~mW`_U7LEyJz{G-+q3- z8$t;o0b~o2kqS$5Q=56#wuX?hrvQz!v~^U)T6L4Se-roFO>J5F#sAok%fg@GYhZZU z;Pj)9zUqVf3%Gx6$<(^BBWoXi0@p7QV$d%g9UO`JeZn9iM&3VfDF6X$7_JMi!hOQh zWvj0`y*v31JPIa6wsdO6@ZeX~XU7Q1jU$9Uxoq&NY3iWqxJPpmw|sEfX!290078mh z!SgfID`r+d*gJD8Atgr$VgAI6H=|#(<5-P1@x{7=2no@IXsAXl%h%Bmg;J-WUkd^B zKHzrN^63;nVCnVdfIogDglEMiNLG(SzLH-U^l0n3SY5gomq*nGB1`HyTv9 z(E_N7VJZT+x3?-Z&zK7U3(D@T%(JhegYta6skLZjUtY&jpFywOw5qm3VP{c6ZrOXK zCHZ^0isUUVKBJAPWj^Oa5^NPM6W(oYihi56(D&;Qt*w%(azj4$Dl`byRhc=);Liy7 zlXsIBbxTY2PG=2!IwLDHGdm|EGfSuf$lTge-J6w} zk(C7q1c@X9yLZ@&B$?z8qS1MKYvYqR@AJiPj%T<+o0p`G=cuUF`QVecLY8SVLb&B@G8vy+l@G`d$p%|opr>V3lMF5SypI?N8EA$Opnc12uL zMN+yYIki4BB`ZT4Q;_nfMXPqlX!cd5rvEW#qPUSzE>mQ^C{v37ihLq}-ZpzpZw*8aPMk0yN4Q-hv8 zQctxpFVvXJbVfsXs49#pvX@M*obDfAIXUpO?*xsyYd_VE`wj}Hj~o)->w~zGQo58L zV(*a<+^7|5g-)%_SLpI}`D#cz-IlQH`lNNi^+D@&yLKgR2)2c=yDN(dP2IQMw%A-$ zU|M|p?HHqrtY95%8RURaEu<4d50Nymj?*2lz1DG>THbuK;jOpu&?UH5l84A9$Ti8A zX_XI6m)33){zU_c%SDQ)mHwXI0?xhp1;;EMntMN)<)enr)7fUXzIx9oD%u)do%9~r z!+cx{siXG@U-Zxr*~32^l6P}iD8rW#tMrGQULvCjNn8Lp!?~2^8Ox@x-!(nG>-uTB zPi--oEo!yJY_h0X^lyKAK@FS1XJ}l_A0koN~0k}8I zwv3sF4VJ=6Tkg`@iEDkj740=OwIieI2uELaMVU>pn5|oy({3#53G@o?vlZHNSB#a| zYK!WtY_zz{SW%G&`Xz&Y-RvdeM*_h)BQ=D;%z@KNs!68(%SJ|eFvOc&r!zy1}Z0l8=$dzj>MwI2W#{&jtihl z9{SK<&n)hy>dC4l>y4APC95+j8JhNMf6SKE-CEPu+`w+VZeMQkmX+qI3dg~*Y%>+sG8)ueQ{CKFWomoB z&)(3`*+e`Ag42G_}qAr!P-&8qhG!9mp214JgswyimR~I~AU0u=GSYfh=^m4IW z$WauR-aJl|i?&hni;_5bM2KVcOl?_P6H^V9n8r&sth#<>#$@lNR zghbF^0Joq>PTzKNEq#i$ajiE3|q!Hh2fVew8#qw zTju;X^T9zH8s2DV;N$dRoad!+lm<1tavuhnImg=0e)N&#A;zF0E%4%8f!o%( zDGzpNIlI_A+e3%0-nv58B#$1Rww9JzI`f7r7kk2o6VrX;qy2Z6w3XDDic0KyXTh9- zV#MkylpSH$kOES}XPVOiQFA4!Q0E(DkO0i?R$XtEH<**J=G>4Zhh2OGp0G#m>&_jn z(&x!z`;E4)@@Y%I#=l7~GbR_u?Ax>U*(rKpcb_$2@#N&ai?@D!W3?^4FgLq487sP` z{kGwzy*>K0G<|PV{njRHneZ27aEWcEVB3u|r`B!X6JM6ta@)uapX_ixYqaO(Ru=Z^ zjogHC$!FKFCqQ>U@J6H1Dh*1lP9~$D2(J_jTp0ghpmo!xyY6C7IP1^S0pS4W5m*6v zI|d#{NpzN0uL<#JLZX}E2oSi@(y9#fmGZ>AB{jl@^Oh04DPIuosHmx_y6vp3*>v|k zbWmTHYV62i$FiFBWi6qJB}QY3^WBQVBGb2=>uIj@?7zU(Xl^IDy79;e+T}6w`383= zkmlGwxazQOS@ben?dqzk)wMQU>JG0O-0z^z-|JXDT5dLPY;W6WHkFSovmYG8`uSRJ z$6EY|@**F#AqF?*AqIN;1B(|wuFYLFXZMt;1Fi)xlY)*(k57ryKyta0Y$+V_+Y`eek54zUJajRqS zKyUAX!4(hb=$EA?)5g};4W_G?*41?GX~Wvb?zJx;apTU$FeCT%z(j+?fNwTt7xvlh zbQmkO&=TPVgwubd2w26{l0)bL->gLILqOYU5phm&eNT_z3K0(tf$||{bUU#SdSs%j zd%{i)27?~$ot;a@?S_idEGCmigvIAvAR3N@A%q$zr7sG91qN|5!V9#VmI)_-!ZXw) z+$-GYrsL1h2Q~$P6@>55*TOIDb#(wqPi4XEaqKn3RbiXJhow{&Z2zd@WBU+A8}_)< z#^lZm%**)$u3um!?w)KVcnSV!v?4Mz#K2bCg`0rOayv_No@P%wUuUV1o;26@>|^jK zi0>5S7sF7|gNqTuMLDI(B0Gi-I2;FtIImXM)ve|nQ`qn2+^`>9vgDw>$-JqpeWNI* zo6K(cj1?&p3iN1V3;$2okr?^-a2?#O}6 zqjdKs^Bl@v_^XVH}+?ttIoY_MID!!dSKa&Hn1Ve5Gg8w3`=2L zk}>3ddrPz3UbD8YZf!MW*wWk6(@T#D)~>ZhMQgk0Qy3u}%(?+1xFZmQQps)*z8@F9 zAAIK>Nxhs8Ffmq9yIitkXvrlTVl7k1&=~)+WB)aF@X+YBQ?x9@sy6`t`9x2gayFxQ_-4|HKx*SNM{0*Us04 zX!{sJPJzlm0^W-mKd^r|dIah&Gz#BS1$|W5PX~GHOniNT*3h7Q9uiY-uLfP zmO(*X!F2h7LVly1Aw-Ys7hG zEW6ygwXM{VlkF%g@6E~S6}@zW>pQj%8434XZa>SFSqG9CLSTC4`NKTp3sco~vt~?a znOq2~wHj0L**f%msxQlGHn+EJwU%X%vJZu~rySWiy`^P*u5!NOG|Xkdy2O3erTPW^ zz36Mr>l#P5sfHG`lr#=sM^cuCF-eM`{Mx9W9{4qH~9 zPLv(toG3f71c?ov-tia<&z{di7LF|J-X+YXvy)MdinUEsHwN|u^;OmPOC$ofUz#sc zEQ1TwEA?xt#=7;TeH}B|6_Bj<%{6D{3zz84Sphf`#xV(3LA%9$CciL*V0wDjNMTQ_ z#oA%FFYGU7nZ^klyl`G?S5K$#CkW8F)J*UfVoIK3-@~%N_s`GBsWHxwJETsxvyGk@ zda?5iO8_lgXN3#o*J4l5bAC@H0tl!xQcWR-5v?{V3P(nr1*x*wdE+<(YRwHX3G5Co zyF3p20c+uLgrphyJdW7>hTZ<^W&~rhbLW6@!@qrD=fVYpU@~$pG$lPBwma|ATRT_rQX`h;*c*lT52~n zHg2k|-_n@VY0PcU(YNVyT626M-|g2_S8wU)xTdB#(@|CB$jES1nH=0{kOtubEYO^_ zn{R=*pr|glK+nU-t>qS|W^&PwEYKI_k_9Ty5^j?vk1o5!0zrQ<*Oe@5$bYaEmdQwm zBWlWOy^>`u&m6h%CLPb@3UG;Ol_X{{Xb+EwY^F*ZFUq~@xy2O`cL4A6xqbHwud@Wv z^Jcleqi=u)X_v(!|63@c<^jMfBSo@4d38Z$*MHw7jL>JHz zo}5!1k54tV+H4k!eGe?oGs&8Unr3RM-?@|TI;^gL!>T86Ek{i2F)utw;o+Y#gc+9*Bx;nHRcU9A!h$~>9 zl?b(UV$OgQoNqeSVmvEm>J(CLM`A^8K5sfc=I7U9E=tiQ`A|P&e!kI<`XuR6ip(v3 zeq;0wWoMFODBWsn(k4fD1P!DcEdeaRYD^yp>WEI(HrcG{Lyn|QC2$yV-AbO7E#%fo z4IO*dZl93-1aLEO8-HX;x?Hm1OBKjQ97QdMS8!5o{zEL+<3Ii& zZ~-Hgt_N5;8|M2jB>IsEkcufH5j;f{iD?G9xxv4~cV$=J)Kyna<#ny}?Fg`y+WPx# z&G|WXLyEpW-y0?;Z}4?E6hpPy1%sWP0~kLYxkwHBZ=P98RB3daq&iS^&cwP?5nL!B z1DwuGBUA;arueS32QJ7Tt{7V`Z)c|RqS^%uPCV>usk7x~b(TjZRA|eSD*AJ0dy1{* z8clI>MM6}611M2W4%4?-otR-n?1JQ_0P?tiC-dlU;)+vB zvWiO5ic^bY;!0CX(~67JOH)cT*Oe5fr4|;X(bCM~)RLHJJkKmC%P2`LjgBr&ElDq* zEzi%dC@&}|!&)Q3iekj=$Zk`EN}&)l8B+3Jhx&uGRk-cCUo1Rz%6{t9q9fP+eC(lz z#^~lMma8-E+h@|{vMO369H0Z7rx&FcnyEynr-TfT*!f4cP}t%8hOS4eOjijDVW)_Z zRDy$?^PKgbFen#WK9STHOFS0|&V>%`6-lB6le{v0x)33=V-2&*iwpCLqsMY+ zr9>sht2BUis#aB*vh@{J*}z=QmQyWz12TJA+@cpHSE@(m#m0uKVq;a;$Hat(guj@lnoaZ4VTm}4{MLHm)LA2=@o(P%H=lpoc*39OYX5t z-^oq8`+D~@H}C1~+uhVwFkVwLUf5!8>uhT7OiQ*jV#OM2r#GWI7)qeDSJ?50HbAOU zs5I%etSnQA)f#Nd%x*}pugJ=-sL0N$U^T57i7}fyKka_Wu5!;o+-}x<6d^Q;;?8qmS?m5Jl+%8RI^?kVGGO z?Rx7a)hAT3iJaup6#9E)5_n}Zg;!oLW^Fmc^4uvuNu%<-x$5zP2sfSz?jpGZ#Kt7^y$+buhMl-HZ(lhaQHCK7R1m2s$nNZdw}+Ce=@)1rBG0f;9929 zMyn$h%4(UpxUf1sr-|NGoZG!HCwgJb!icPrip-?q1fEGzV@0VL4_?@_9(TFx5|y9x zWw34vZCq_pfh~T~qQr*Ml3KY{u35N9qg|Ai5*;76C@R*gn(fIiNsCGLVSZ^bDFp?F zg;9$lA{J#wMW~}Ac(8NH4qjo*|LF8-_UtP2Mm*s$Z2_VI6`FZsBAvMH@dQN$_Ne~S zWRt3=r^8}t<1x!fUVe;5I4MgOUh8roEXu+-@IA~MxyA*ETEu-|h}(M^n0HGy@&X2dKZL`I`Ime>UexJQ;xv}zZL04AxPsxjxy3~FLy zHTqKI{Id#*!y?pS>tHfrwP9{=gY|$GNEOS-O;&bo0nBi+sIxty&T^@D>#WDfCK=}o zk|w(&*Vvw&gYUL%np~NgRbG~rS;h4=qczXimYLa_S5#G1TvRD)s~*~Vz@x279WTZt zir=>kFNVHS^^kbddDK6>j!^S8Dr_5;LBNX zS#1n5tpQc8k?lt|ECDkqh>5&R_Fe%#dkOrSx%MZ?lk?gyo`atvznBMKItQO1Pt1d# zn1jDa-Xwb=`3MhXkQUfG=oGhjVpYb75*O8|@G1dIziUfb^@LVGmop#d=0%k7cEt$=&L9{CEPYzd{KMtH@9D2 zqpCHPJEnY$bWW|8dH3!c8k=9P0u>v8$_pZOQMnhXd$qXw%i*(RKAclmYJZXp&uh=A zD8VPlkO)VNM$U-ir%U6zzP%!RR)V|!34FX{e0-_>N!MR^d)GIBQyCv$f={^K6S;vM z7j%Z#1z?9fo|os+@!~AC0TYHl>Ao#r}kxOwZ= zoBq-MDX&9g^=ze#%Sw)j^(k^(#9FM&h^yg#9uUPf{rgMy|Ey@=zLI@+-zr`g^XvWG zf@x7Z_!1SGNQ{;S>WSuG41!VLzPQiGH^6@;L0P?32|6l;gKT$NCW=YrD>KUL22-<8 z>=Q4YcjVI*=0Q}K7|RoGG!LSB!&*a8d9!qdeJE^@#k0m&#kp%bXt5{1A$49vhyqP5jLdg7 zjMr3`?6I@mYcg%=*(R+zIygKoJfZ=i;6Qs$QK~K>J#=A7rZ!g-o4zQ+aHI2WmII3N z>|7UW2=T;>mC0Zk|42BcFNe?0hqHgqwLeLIb+JA6N}h2}5x79lIM|7J;1jTTSb zA`6<5d3wFfI5BSE*?gp^3yq_r%d6K~D;rWAOtcJ6ZxVchAc>9fC0oqpGq+w9(IOM4%^I!TA%m~Xt*`6`9B(1Vl`UtbVHo;k?g+8%D${D zdu3HW*9WfY1)?0ci1a%}?w+GZhfIZaw{oe3o*X9%H@)Y>XXnG&cXRDelAm8}kDQHX zoKs}qJotNa@CkAsW|5IbVrMqC9adY6lF7XNyBbmC{F($cx}zhfz&>_gG9OP^G}F)^ zob=pqO-};F?T}P8Dp5T5=&|j{ZO)l?WH_&2*+b*B$j=YfrB+(ww8+Vn8CvR> zU4wKzoz@E9W>w{M8tH3^Lq$l~LxYlri;=%C%oYwBX+jE8_YFD1nIt6gx%7znUr}be z-7!#&rB@8txZHwu=JAmb$ki0&eT$M&Isjc{cy`@(G=JL`1Pg~CqVb=`gY9FBdx z-8*%3Rygat*Zro1_`U?)X8GE>$J&V3CE#~$mR%O%jtyq>hSt`N{AC>A!|iY&q$2?@ z(w6|sODmPSOA$eWf}7yWZ7-3Mtr~ftTtLCRwnQvr4%e-TjbC5ixPg~?>egxEW^IjY ztDFO!xrUCM9I@QPW>Da?40@r!84%gp%Pp{_qQW8-fojU}4(n{)*{r^*s@}}Z-YQdX z7ENeMakO$?$6??19AY`fe@_4khv2RHB*+Tifx?KWRX^LcYbQJ0VQp)JVZ%Fste>2P zACfXR5iT+Y5`bvWg0`qheztBje(bp5$}& zQVVPcZp0kIT;f@bm?UCoBaF$)g~|otfgusHT<^SOWprq;GB89fGqRiV0t5W~!&Umc zz(7C0aJ+UwiH%wr-csih!gDaJ$9az4f)@_OC$f}_Ph=@ht@}v?Xu#jX;8LZ{H*6Xk zsHCrdz(?~?hd;s33+$r<73>&)f_J5FB>Tw>?}O}?wrF&qa^?fj2V+sZLj^d`lwvfz zu`Q0cL>l!2^k#fqIyBb`{rMPt^mj21W)NHPIjBjT17qez!L-fIratgdqjPp3E#ET?}bS_y#54OoQRDjiw2by-DJRAfYX?TXUnqh(c{w(^L`Xmv$h z8`g>Z3OkJqgM!!2lo*_6vJ*qJu;DUp!j#I$a~)RN$&Q=oGQ(6=@3Lw3T!HW=O-2sJ z<)Sjdi5Dloq5fD6B#pjvQJ&~K!b&brptI+FcgAi~XLRm8oUTvJu%)+23Vf z%ZWT#o*>VakIP?{f9w_O)!;SlwZrR9uRnTy?De&Guy?9=p?9bEl=nXGXS}~rL@W9f z(~7-{`xP%J-dB9*6W|l$li^e5)9lmhGvRZ<=XGD|o9{d6d#&#ueZTTs;Fs%X^IPn< z$L|rpzxu2F8~lg;@Adz!|A+qH280D<2ABgD2iz6#K)@$~!T8Gv>n!;E2@!*+$;7Itsg(Xd~Ky{OWumZ)Y_n^n71x2X=QexZ6w^?bM@Tp1o4 zo)(@TZVGP--w^)W@R!5i3O^hERk%}aP?xFe)w|RmtG`scA`&B-A{-Ip5wj87BKAZa zjCdmA#fWz!K96ul21Z6l_C;=w+#8AL4xB_TntJzCHv9Jnm3%{FvcCgD-n{R@-|+K0 z;dw7PKX<<1r;sCFfXs1D<3qo8pLx=lAE~69CJ?R6N;GUaDM1vJ%056k|lVl2q zhJHj!*+Y;SO*w20Nd~Nzt;Z3M@z!FzSyD?* zqrDI69BHH-zla!R3rQafAc?YXh?N~gyHV00lan;|JZWI?v-ID%_rv|;@VVat7D`fB z7vPTo-i!NZaSp|E6V72c4**tA3SnR3*}bHm-ABS@uVB7qBm;YBCE%I#0rC@e6WNCI za^RWB-X-Iddx87V|338Z7td*Iilot6^yTm^;{0Xg->$QGyHvzQ?v1v9!8g#>R0c>zAmKfnitbYQ3Ot?L_hn)rJ7 zz;<6E0WsGLj}QK(6E+_{4nB>t7^@E(RTcPHeI@#0Gc-e@32m33LOz z>jt#z!}ZTd8>@y)N01C0din+Nm8FqLSs;l7k8E5wxPHo`go9+n_jBjx-!J!5h#D&? zpY;7Uk;~fXjXc_6I~k9H>!ma8!qTd0uZk=nbjEjg{B(^TRq&0PYjfkaHqAsoR0Bw7-M3=SC1^iI2GPD27}k&`R1|)UGL-H6{9k6N)FZVhDGv0+~1%rbBZ z4v%meQuZnNoLmR_94C{Ivnfc|0dQa?xWeU=%jzsyOa6gK`)bJCda{vhAWxBd$Y$7x zE#w;V8To=dP2PZR{Sx`^H_5xm13pR~LzeJY@HLNNYF;lBz&GPZ=?88Y8Xu9{ozttuk}fC79pMg{=tf4vyu2mc@CKlcAOSv6Hn004^QL!xg5Q{swNxfhvx9Xl|Nvrf0_?4cLch8Xk8yX7iYD1ZL^If&;kIUs{XLy{SQQAG(ejV@k87H;N%~mLG^@Qv2pb90RX6B zKfcET0AOqu6Bx1_oXtP%XbC?2lzgD&TKd4s5$N;bm+n8m6#oIr2#VPW=xF(&ZG7;Z z54#P9Hc3<$XLk<(fWGg8TYrp+Qeo_#4uJZwKn9Qi$N*4MGD=ziM8JnX0O0-ozb63T zvu18;VQRWEqCBcBAQQc6PQN2avP`R0A~ngfN>#3P!%iMaK0j z`DZ3@Y?^fxQxs8@Qj`^x6#O(T-7cz^QJ0sOlfQcphR4{3J2eDok;3Y-R8tgE!00$e z7iC|+FTW?glRt}H2k(eY2crgq-vVz<*TbgJc}4WzO{c>2(dk5IJ9_W88vJELE~!42 zs)dM$;A2hF1QAR%Wg9!0%;(}AE!wxK6kCjF4ZHQzwX4nA$Bo_Cwvm5kVhHX(;>*c7 zXB3wh4PgFZGFnRx_~VaAd9Q#~OD`)}P$u>-k0$o!#}4k)<@B`5`f65`73Jd~IJpcH zeYjY_MpQwZK|PgWfQnL;X*l}Df{{FUbaK?2D+;YA07B98u&s@N4k`=tYUCQ~B1h(c z zrv~^z8BOYfc%Fou*_@by@M}fT_rXC7FFj}L-nZc4IUGYgi{gZ`F3TVlrPl^Vjk(!d)U_YxG6jEbDyvR3Dc3;%iaz-chEd znI~5D^O^x@?cEA}Kia+e@$tpjw@`5v>B6huXZvDv!rPAUASzl3dCaB5!>ZeQg3)0V zyfOydR6JLQA9V003lMkuh>uNwFACF+iexpV^2?Zi%D#Ajbl8FRdISFMlci!|5)z#rGMi$0^ z2D+~~it?Dq%@oBxJ!(aB3i@lm3%<6mT^N|`*iY(ftW_^^<6wxfPOvfH%Y#)K|MJly z|7EXQFL8FTZ9rI1(5@Tq7N!S-zV0$JR3_t&D-P>-40xwkZ{*UhnX`QMZ3i(+47 z{FQf#Q>K1)q{~{64a>4uX!k~30uDC6Zu9bu;oGLSB@vs3_?a_nTVkp3{3}-j@g~}fH26_BXJ-E1+%9E`=P|$`vruac{;Bdre$k)_HtojZAS?=L% zEc2#MK>zqeqR)5QQ3ltfT?h;&s0LA2rf-YU*uLmFA{fgmp8cqNJWr@DmN|9Bpnyt% z*0vTgkKJudl~;{k!&xP+PvWd?lTd_2+2$b*XcGMXHXA0JD7w-zy{Est#?n^)U zBN5{n+c)vK+M=0LJty57Oa*d} z&<|fSpwTGJ)cS(s={WNpC+Y*mPZo52wI?=;dvi9Yooj2o(9w`IVK&iXS0}D0&eGHP zs-|*LtXNJTPG2hz2I=b7)y(hBiuD~EY%rjRB}#I;5)O;tCcBUDx2j{-!ZTyy;?BzJ3Tc>rG33IG!-^uhm@w?CTKCvT|d1X4}6+2C9<KGQ0-pv;fe@z35~2!_YUyGefjr&fzCs^hnPGDGcrgH2t_Gv()5JD#(1v`rMWsM6YLGxx?9 zWK7&+b-_iGPq_@I#O9B5@s${~hlH)Gx~j0RbnD-32gj>^DvWkS>P|ZabvCaWUf5T5 z{^`2VEmgR%nOb?ECtLUMKC_s(7qwO{*gSATm^ft4+AlIXwZzEZx~2?4=_l@z8O$(P1C5Zp7+pC1LsL_i%JsU5`Z6`*WTrrA6Mbu{y+4Gb$uq zxfvm;7An%ppIp*eN>{)d47)VpZJx6TtsKo5gdLj*%vAv69GzE~-|?l_Vu*HO^u(pQ z|N3WLet)UkQ(R%sP!9VU9{YUa(SP3Form6W@tcbc7Yog3&e0~?hpYf@!ynFs<-N6< z>PFSam36B+SDak=^lY5Ix+g7PJ5LWhb&XQ&r|r8eA*a2Uh@xc=_FCG{tPyK*ZF*4- zw23g_qi+sU0j`al`pgH{kgr*-p4~?>(+|9kYaahD_ODH+GTJg$RV`tQ0D(erSYP&r zxT^4JWtb`1c3VJgQR30y+R1t58msACSG3O#29fPk8pe*@2a3*Nj#s2@symDtt*I%4 zH}Dbd9E>w1IzPVU8{EOKqidZG7jo@uC)v^6r)arJT>Gk+RH0V+yPAFlkB9w|7C2bR!ZSAeH4+h`-D|tLa{^4k@ zIS;>nFd@8Hv;1g!G3fn7k1+Tv1(=z9c`qJ~$V$60R-eDR_jeCUuLAo=CO&0O5H`~Q z^(+)GwCvdIzmR+{pe-xvYaDvNA@uO@#psSQB_=tMqdob(d8tN4$XowXDRoe3sf3CT zkZ7_RCke3$)|7VSk@hfA{LA#`LusSvsY!K;9YP25OS4O~+v{a^_y8zaoq_;_9&@q> ze__C`fp6?@a~sjt&-`?1zX)#eo_ZT|ZvL7dOOm1Z$s0jPvT%h_uGp|N!^t)G5z`Xo z;#Sq86*v#9YY`0SUQ76Wa!8PZ#A7g^2w#;{LgTQG)Oy+eyp)QG;tJ`MuNyM&J_;ou*7>}dH`!YWjMlf4L z@_VfRypKL3#n1euX!4C3-K$*<<;oIE8O#ouq+B*Y#nWSv6uy+o;03?@;h`H>34r z!clu1TG~$nRMMgVHdzAesR6Z)GD=w#rmLDi3wervVU>796_~tG@(?lO5xuQ`7pPy{ z_Oxh6=qraWcZd=lTcB#IA@ktJ`b4v}=j;IaSGDXXY)@J+I9)qE%^HyD+FZj!u+*|s z29QLS*tc`z#|mXgNf}$5oS~ka2_z4m%+iIJ42*mpQ2Xvp;HNPK-+XxOJ4^U>i`FX` za1>gI|Li2f-u2GwrQ{1?LG5^EuRs@7umd_UPHNz`+*=SZsaPTG&7r4nbvhqEA`But zpzi_P`Amia!eH8BpNQsba%*GDfg28j^gQ$m`Oh{Z8?OdLdGnt9xz=s{tHADE; zU{^8~MM*Oy(xo~VF7tlnN$N+r!0y=nrOtvQw(XqaqfP9c8Z6f8s}tWiZ`CP*8ot^L zvvo2%TE-1|Q@nd*RW3G9v)BH%hbDvqPb~I*Hv+3@O4BHmBT;yU1RvkJh1qN0axLNa1*69CE02e`%yHeFlsKIH>STC>F1Ps9Mbbm=Dxp<5G@M31 z_cuZXQb~t#xa$6S^Ao6vwdZSld=EMgLwi4dywG1?6D_eAOOfxrrijj5I*W=rEw!`Y z^cK6?pHuXlT>s^w(KKbo2Ah%^RZlt%vWxTts)1McJ(?e12}NY6G!y-R_)FZ)o-LeL zA<((3AlD<;JDjJiDU!mKxEu_~U6kZ0me?vmbfM6LtepE8dzUz}SxIVQ zb~1X?eEDu@K+k4bs}}VI<**h;uzuI5k0+ln-@L!HdNP@>uvNfZx)XsV6x#V|4uTUT zd$x`}oGYu=_iI-*bhj#Xcrus*Vs3uk2o!*)3`rAMSXd0Jh%KP1c+?Dt>erx4s}anm zLlHiAry`i0bj`wav*Rs|oi@fcQA1bB4gMV88@V3k3=wS%&e+>@iVl{dknu=orbX!M%95#A`#Qeh`?}j zj6|9eGbTMNmUcyKB?`=^;mV>7)CSZ3B8R4;1#QIJG8jyr{ZO0KFJlqMR5>}=!nuYP z_BVdHD(^hou6c|Yi#mL!hEvnIcMChnuTrT}5;Y_qzC z@}kI1IvgcuB++}{1Wm&6dmo5yoe!^=l~E;czK6$Cvg6Mt2_HsZUaLl-ketS|tBk zk|_rUwr6TVtiz3b?hKYBlmm()g9mQG?7NiVK}1P=2=|e6iNI?4sq71VSIYgW)-|<1 zvnS${5p=zqwv4NcotK%PNsfr4vfmdgI~_N_pqx)vN-7F^4AUK=jEt0Daw1l;r-{l> z$_F}SY0^+gjwHJtD9%Y1mhpX$?yu zprjd6Krxd)@2H*)h*)WOgvwk;MOt0DVNOp&-3H6pmJ<*E#B;b!!it&G(o&*x(t?!- zSKGo$2PaG6a~V^!fnuqOY#@+GVn_~c{+w3_`7r>(n7rSMbBey9zLU;$HRJPS`98tM zCg5@49C_90OyJytmA24gov2(%rQ=}wuxBEUQ{4S)3I0-u(8Fg|_1%YXGGY6#kH{S; zLWw51D{i42na0QUv%ps(mTRMPvvzmOpf;w6U1~qbSt!pCx%Gm5T$a}aBxL?4tf{3b z&-E?926}tewE5L2Wl#rf(YoBpd}F4oZfIOl+s4nLO7q*XcBz@ROk2ao-#EIbja`II zmjc?R%CvM*=V!g%M2H(@){vRo?rxhj=56iRvgGDe59R$OCG1U(sJmm;8h$g{K3v*g+w=bGYY%9jt{k1gLL1HVd#kIsZGZOK zIZesf3E-7@QeuBJz0lPyYnkcK<_MqA&iuR5>$pP`^JXgtZ*F=jOAhiFZ+4yqb|jyk zVg?p(E*pSn4UD#{i`ym6NBP7(*^w-bZ-!E^s1enpby-_!JB(r-8XMO@M6q3yW{fF@ za-N#DCOUBLWsF>^mzu=qyxm(?i!cuw9)vxl!68=aS9O+6LkbT;p3csreIdPNW$vci zjR=Fm-|r9elbl{K;=~E=v`XkUgXqY`?%uR(Z!1+}L&{v`B2ccG_8Dp%2IPi^15{!f z7?g#1L>fZe^ImLrCCJq(py8>ziH%7~S-lN^baJss>*}YMpH8tD8S=AH0!=6dDla(+ zIu=iz!U`3qjIdogVeb4ihW_qEMq-1`e?8qEPVG%+7+&K*Qb!NEuW_34U&?Z=g3Ek935`LAI;l?u+)zX*<% zE^M-YCE+?ap)ni6>X1g0KwAD1Y+dh-8g31q<(1b27Cmf#$!7UI(5)wxP^gu_yQ0d< z?0fyBHxy1MwW|cQgP&18m+3Ap=^_I=X*FA?T3cCImW(Uo>G!Bha4|~gsbg+4#nsYx zMVn|{#4u7Hw0#nEz68Vg*yvd` zBhIr2pVM5_nTwRMY;O3fMVoT78f~bh4l%QuF%5&bG4m_FPaYxNW36}*leSZWHiqwGN2G7c0I9sP|zTlSzSiaHW2ZgMz#+0F_w&!iE>+*I7`1*W7 zeohm2$rx1kc+OuyfF#l2P*n}+xkHs@QVruA1(!AC67>b+yGs)11-xQ)OiV3|sr)*? zvO{IUq?ST!^fQX_`2F}kcNnW{c+-2*nx+r_R@Wx2qECsS^OA@R_7V*{eiQuOOG9g8 z@{0;@NqJzaSz#v*nW4gDyB`94osRu%UP9w{ykx9Kj1tkNfaOds_hn!S*75k0$0qIe z{84|a%+Ba6HU}hu;lK{kF_b)h;Hw0A(HRDChO!SeRooF-wvyA1!4;Sc zpudqDYj^+n8P1VWY=feDXD1j0$ z0vNG)0f*hB?59)i#oa$U+w|1S9JFY|k62f^E>zR+c0SypkET~iP}U9%xiwHsZcYI2 z@dwLh!kps=5(`5K9vc|~aPFI2L|>l6hcyRw&|h8TAGs0G17UoupxzK)^p4%}-bDI1 zwiEkgCG#8pWDc&O)}UAnEv<$`%^46gQPGOZojGdKudk_Gu5|m4{yfT0T-tE)<jAE}oV_o-cn{S?Dm8RykS(Q^G2$8-N0u7&*TCPhA?1sr_wXQ#MfOC8dP{AGyt8pY zEY%+wo{4m#=QKRH#wb`%v2RN@Wce_vQLf4VUT|IfYX;7c&F6LVHC@R(_ayqUb8J5o zede|esUe^gPSM+mH6Jjk!9wCFGsI#%9Qe}MsRut?GG6gVLG^1gi30DrJ%pFV#OW%` z?h_@^p@BcSma|-OKrzaxqDFM!FNZMqN7m;N8{i!jANqw+oM@2LD$9D|Kf`O+ z(vXweZNp-h`aOb2PUOU9-P-iNU5<$BbJ=BSCS%z?Cpe?hSQbPnJL4y=Vb=GAll#AI zg%-bHW(+(<1l%^qryUcJ-Fe*MffmTG;_0_Oa)c?RyVJ)5v4LFPE#J?vxNpr3I@dS~ zn3=}q(zM%aBuO1pUH~)YNlXgA;uBuFjFJaE;`7fYAnkPW=3rj;+OBKQ4&U%KUy(#9Ave2dGF{XGD1{G2gdl+A35$UP+tx{ z!t%}(^+oCvNoWWB>3xf6M})f<7L3dQU$ErW*< zvU((2d&}S2`pBz`;Af|ZBd|*48W7D%|EQ+#t*zZ^bXnKrfHGn>l^6#F0|a2Qvo*Gh)fBg(r2MN}9PRdx zmpbwr99@o5GvU^1qCfXO5t&b4oFeW-g2d{;03`qVf)^<2{i}P+$y_^T#_)weM}b>; zQJS03R-?C!#XPTZ_w?3`Z~q%C{19IFASz@8G7bKW2+M2O0UsxcxsLu)ri|!}N+U8- zcUMoC<>TSBiC+G;j?no&qyB#=w|?GAI}{QyiiRQc&+%M5Wb#V!vJza28_UG5h+bPB zkZ?p<=pmE<@(|W%soe=v3~P3wQr#BsD%5vK5ibz67s$9R|xbh8j=R(ymXqv$y0cEq7(kJi4?d()dXWyynn;d zY$6jTk7u?0%>I;jRwL0mm%)0?uyu*(+)pJ_}{$z>t7z$Q|Fi*Ql zlj+-rFC%n>RsXkkcTEij6*jMAl>ki|1WCcLvTNn$W+Rk3m!A>31UONK8lebLgJALK z=5gi0Ztce~G09d2Z<|;U+XMQ&!EfLimYKwIQJ@X3qk7D40dmACHJ!|$ zVomXX;P!|8m6s6i4N(Lqu@vgLtFB5$GV)~;UvD5GFek~~cy@?s4Y-(OK%*sw@{N)qyef9-eKqU_$h&7T2;Fdi$t%#%e zw83XNHfCF9Xw;S_>^O)$?rOh0gnZML@PvUcPDP0`AWZk&KkMpRSS24a%Jm#BX7#gN zG(uwTY7;pCmjP zkndP_??kB@NOs(i!{p0_B?_HngmRvrrHhlJ6y=hLe=qDXfUu-&IsP;wX?Vh#@#|LY z$q`%;5C4-X!qaUB!*3BKF8L7#E|429LM4ybFC2fqJPV_fp&mMO&$-?spmNQM4EFoa1E>^UY@8RTe!@rlC6cOQqnCpS?-%?>-!r?p>DrD{Y0amNGM1? zUoNR{U9vRW>^}$lC%*~2p!v79K<){BYjlDCsH1x4Y>#C>@ijeu;zF_dNvv*q z{rZ(?QKK`tKlo)XxP5ja!7tfyp>KEB&FrZWxJYh{+CZyRJ9hhcY0&YtXw9;1|CkE~Pd?Sv6Kq9mK84pcGd%thL$4 zSh+U+5LoT9d#e|&`mVicXExQ?V#wxTwOqfxdUlTeVE?Z!EH^*}w=BA8a&^mTS)V4l7VPS#J;n zf4CUJ-Gx{;xDKHVNU)&Kl@sHPQKF9hZO|BTPG458f~ldaWP80v?>Xrhh?6MA~F`T;U`kpGL|Uf>ucdN;ydbGO-mEuDPwDCY@kcf}UEYsTqx>k%(Z>ZH?Gbn1=36I>(O2m)q z6B$%p3tLN~3u9BOgwj9-Jjyo>U?SK=JGco8DwmgHQYehi$_sq4WZjFFk_lDvM zc=~hK0@rUTvHh=Bt;MbDb7yU3Dj6FgIlp`oQ~9g8=$6Y~^7(=)Z*JuNOMX6U4*g-F z|0TLU6zBDpcmH)S-bjb6^a{8RY}iw6%&7%LSQtu5Ad5k>?Q)@JhLecj{RyAxY!Z-K zCZ3QF_$Sqt%W5jC)pQPI$)r=G-wK>hcNFrvSoNmZolQ2USIHId-uaVe&*!w+{&#yW z#hT5e+xPFze1@}F(CZUEE_OyzDkwcUEk##NOG5`KoEWx$P>15b>F8g1*G`?AvXl8BhJG*Ij8{SF(mrKT{(_IAfy7d$JOb^@(i5U#oDnOP^)S zmu(#(Ry4cGbn#PHxwKSxq2?j zfpBDeMu~j4xuT)(o;%|qq>gL(-3@2I^U!kr?y~=suK%Kmmx&|td(i19>$cvvxJJ3Z s2D+h{u}w{Iv%7GI{9(md8^ci|77%D^OUFA1b%7 literal 0 HcmV?d00001 diff --git a/common/css/poppins-v12-latin/poppins-v12-latin-regular.woff2 b/common/css/poppins-v12-latin/poppins-v12-latin-regular.woff2 new file mode 100644 index 0000000000000000000000000000000000000000..36195bdd0448c44d795b6350ceef890671400940 GIT binary patch literal 7900 zcmV<29wXs*Pew8T0RR9103O@`3;+NC06(Ar03M0}0RR9100000000000000000000 z0000RARI6TU;u$s3g=AHHVcC`00A}vBm;(M1Rw>2TnB^;8-g;kBG@bY793wHgXU{)h3~&N~A+Rr0th(9`*;t03cuZHMbJ7tS z`y`j=>G$J*YwvTvThsLCS8E~`4TwHnD;2K{kqFr{Su7;+_|EYBHhYRQHW#TqjG{`S zKkYM~{x z4_E-}B})}{{vu)q(INom1VlR!kYKuwd9EZ#1F2T<@o1t&FT<2Y1_6DmcEB~iTOOeW zejUEb8P`}mM_2AE^x!CPa92d)%4Wq&Z5#Ik@HRjXcRygi2tWY?uoFfY3q;7&IVyTA zV*#7A`VwkPJ=oK|-yipn!6sr;vFX@sEEg-o?m3X2J}P~z%0L{6wXwf(htb%0Y_gQ| zvuft6`Nupy7ti{Yn9n}__UZp$_x<|quiyOI_v@Zt*ZjKpSKKe({e1f8lOW7u;1AYS zJ_Y;*Z2A`1@gXp_1NqmO(LNs$#vtLsKrsY0&%)PPjPSX5Q>vUhjLWfzU(Od>wt~}-%=6IyS>W{ z(Zf5SsZ|?Q-TJ;UQ@hzs6ILxK%JS4|znZs?H{5!}Y&&8f_;B%%hD}Gqt|6Df<685n!-?Pc}otkQ2uMe)n^#{2=JfU>}tVJ zXz0nWJT^=?$j(B;yGHH!)d56mF@bO-Emd5rlUo$-Q$GRJ;w#DAE_ zHHRKs-+^-P>;T-pN5u`S9TvLy4z>>@$RBR8w_wfY-h1?(F@NbWx{txGo}|F3!HdVU zQtUk)`zSJJS5NN{tPi_(p7sa?O5k+~Lk-Q|cxZE7f!f_ZcN{9LmNeT|a9vCkE2s|6 zK)&*0QeZ%cu6!&;vB9>kLY{y>rg-NHh*MC!Od5iqQbrU*x;H1|StAeM`5ZvloB$nv zFOBkPO*lrz36DN5(KXFSXJj*5&ZziY0R5uQQ1cdfHh1ekpZ%u-w!q+}K|MlaRiZ0{ z@u|{;547%xY*PEUXF_KYz7G`u$!~2Kpu6~dRQ12z3L8Q4ea1~I!?|_?;PQk>=qAgK zP!m9a<>y7NX`V0^3ES|E+SgiIqp3QnkHl^$UpufwQVy5Yp)n`bM~=9P(2tdok=XBF_wgm-E#O{~V#e^g32 zITa|T%EbrK7CL)3wv!R;IcmE*{gODJU0#@3G;6>6U<{;&bd$@a773aXfc5nxi9QBloL&(2^E z+sR@JotEvKO1I#&jz$g52J21E)*|R-AXEty=yJ%SU>yY;#}+t02F3MELuP3MRtfPc zcY(wK$5dHz>#^iq&4iOAz~wLf?e(VUuCiz0`S(kA=)Lho{C6Mo%7W?DAk#ik1reu+ zprII@jHS2%;rI4(>i7)m5zcZw@c_a^1U+nUkzDa{mxp)a`hw4~_L?=8M9Kwx7mK}6 z=K?3EKv(j=oI-)3+=0?geR{y(+rOTg-kKBSgN?AB0;xKPTnDX*=T(RcPrOyQztEj} zeIpo-o9#1S>*-LV896bg)DzPq_Zegs5RIB}oOGhe7CKyP!H#r{(#2wLOK=V@uvVX) zL$kAWq%F+>=1MP?-L?a4&-N|8c8ut=Kx;VfAe)86dY*$dX+r`4yTXnabF5muPCy1L zy7w!r6%&zgPG>h`r|x~XFn{h+u@yIc9~C=3G|VI|vf5%<$LFBLSj*|Ke$X}_5VLuI zGzF33ZR5fL^@}$a$bwse_?xh!plySSyq2Q&Wz3V?id(n2%xy1h*@aEa4JsaBO>;`I zTY!Rx#x~XAS{<-Rt=%N~xlT6peVn8XmYuqb?0DNqRbt7mZ7oIpzGZ^pJmw3y);Tas z<-2d>RqFxwFl)oId~WCfS|Ag>4P=}SRrZcmjG%7dF79cg0iPIA>MEg((o=i}&AJU1 zBV>hl9_q>*%R$TsDwbinpNV15#Em?f3UfMV5FtsOS%znhF`uVm)`xEANggy zxOaCtkqP6Cn?rsZ^R430x9K|)tHNyifq|tKb7llpM45J<(hc9RN58>KSdu7E9TBUO z1t=eGdX%OU4=-ig#0;`_$|nsJddmbq2GY$*>`M6qqKm%=IX&+NiWWKR0yJ5lMc$by zW0A!&scWBO^+gJK!(|nxIN0t_Gaij~-P7@5Nu2O@XYjjR*kRr5b5ZIjvJ{?|)2lG> zFETwQe^!&DzXBLvb?LYPXRA*1dKNtJ0N9l8c#yd6qP!T`p*#Y*v*plzjX1`+8nT8{e z#>!9y#{F1NSO_e{V_Upxe# z-f?5ZevchgmD$PgfeM4VnOtgkyF6oHE^1^LWTztg@4ch`e8+?Qbkx9o;Dza}xM(!d zhZ4>T!+VkYtgea%v*jQ)9$amBDz5)L*PKW}@g~gu|4Igsok&n{1MpSGW<8se1xIM& zKm>2mh@e?-o?DD(|F7n|XN$S-H}H%Qy8Kf|%g7{08}xg_xUJvw+x`3u-|%jx;l8l` z>HvDZn6JNic5w8a$ft{z(YW&f`Y|H6wk-Sdn_Ct$Wy?RKdVPKjn=VUMy42t%CB5a zg6jQ-`9llWt(z;c=2c$2)JCb`nYA(y^={hSpxap69ikL+Q3;ieJv-n1#=LIOxjsWYhclO*C7oy+zCtr>#YB5HG>0=M zKT|rzK71uIVkIyuZr!!qy{Wx<&vNe;*fq5_RshF>=0V1ocjD;Yk(qYq$T4;xNUl9P zZ!UZ6>8m|9ciyi1)>+3*RHz^sl1**Sagz)g1cX0&PLS1RI(Wm?4!-VP*y&#&mk8Ag znc5t#uw!c5CY6*;tS>hC*G&!jbav!736M@~D=U@xDKryPsBp|1Bp$ADBOJQ3jIOGf zSrb)auQX{C3K-^UiXlWF z%~uv%j7p6OMHEIGtTNbiKsNK~!(Sd8dG_Gfhf?)L>$Oq0hd6K>v*bwko$wu-RO<Xcrr@+&N0F-YbhpR6R{7E%1e9t`^IAOeSZfD<7oW>N#A!6x#556TlruH*Y|F4L#M_#nqRq zAVk#&Nm|S%Ao*9MLaL;ftFw!Gsv3M7oam-fuySC#*}lHA(!OrHvEg3m-i+$`3pzR% zES}Mt*$Q^l{PS7!`DuV=!u|;waC<;a{_nN=H5Uy5*W-)TQkAMnDs3?urBj-us?x4W zgUiOLCn%yU=z`@&m#^FD+EiNV+T88*)$Xd!E&?S3A(UUlM?)yBhz52HgwPP!J%F(W zN^SN)If{mp>GWhW2Arn~glGtb#!DM{E+Gnbs9vh|Arw%<`}@&|hZymn5rdlj{x7`A zQ;$~T@aTTDIuD0}oXBpcYjby+pEgA|m6aiymmk(OLDH!vv$UlVQmcVrm`yGUzlT*I zb$PI1@{9~L^jmOpy>n};QX=SBHUrE6Q@ZBNAu@fnOgAf%&rKRZYHK!NG0G zH7RK5H+>b8iSl4$wQ*!`MtjK&wF(vpVMsFrJcz8K2&~aQu|g`7sKxZ$uO$hsvXRCN zE+XM@Y~^H`zr`0-P^?t(1so-pncesILfI%&CJ&L)nT|j{4Bic>57(l#N7P{3K*;TM z7z)_V9YP0e@?emoRx2A>&^7?(4MYwEOvHEJZk|rSTM{}qP`Zh-gHjBRhkPq_J9MSp z$SMQ`&|7HP_Td|bm)t~exk`78=pIoD7z4k59fd~y@pZ}WLRBkRtuyP7!iF@Rem@LG zFWs*3p7SF8h2TKX=w)^%HG{NJKN5M`HT|G-r{~`xmj8x$zgr7hvdm-5;Nc?K&3Zk+ zl|ijRxe5*lHWa%uU8Q{$LZzx%33ZsR@TsVoLZ_R^(kv8FU8Wnkh-wsq6OStea&@yD zYBignj-XPdtPu2-pbyaO#>)2*GM)A&Lvsm)tZ2-ssEev6%5^23zA;w+wE_-b=dJJ; zc`J2%ef}T*v8Jx#B3&s7wON&^s1{dqucW&kxXLyL)IJEln#8e$eGvu4PMD`-ee#dh zb@~0e$#QwS#R9cWmKEqGK;odrtsts(*%W!9EmG?Q_`8kw(0fXaGRNgH2N3=+R!$>m zCRFHP^(h)rQ&6I>T38ZmbN=S$OEn(1rLiv{>IF6H>l|J9p)c!s4Y7#94j_<|Wi(io zu-RcHqYuzwJsu(t_*%|h6XETdXeKCX`SP!phwwtBf|N{ccJ`yp)hKAY{p|T~cHdrq z-WE0@d=%L62Tkz+(85VY3{K;>T40qcO-?K6WgVlLsD77|m@f|q)&>G12{=HUGO?jA zsJKkJ9v6`f9!Iyx73~%?+&)#N({UAWo5iATZ56r)FRe=w=5)05I=|M#gji6Gw8 zbH#T%qhho116o7ot_)AtH|BqXp4}PlsTXEma8J89V#S8kr~+$l@0_C)OWp{dshvQ2>En`kbVR^RuSB^T^;Ae$c8%SQ{AgQqFK#{^Yi=gxCLzXR6JPGI$OFYY)j5r=)^wHRP zKWRU=5ZjCc&yK8jS~r%JF%qMs6vU=Q+q_F%IkR=D`5w1w!EC+THA_#1+vD2J(zygi ze?F&Nq0qK|HeXX+Fd8za7|}Cg(HEd9KH>ctJ4#WlMF3WgH)sfCvNUt30QSKAkNvz! z6oiB~GSwUrM5c(O91d(KWRZje=1uVS)*~GL-Vvy$H{cAH1-SceqVw*{z}%5EMVLzOz#>WjL#eL-;g2S4aoy_ zCuM~)kmU4xbvmC{&m`&#@N`{aVL=?5D<%@uGH`ech{PjY&@pk}4eclGt$nvtWS3=^ z?rQ;d4KIvQWgCo5NxBplzbi+T3h{UxnTV9VAEV0$;}^gzE?dLHr^bCB9#W^~A^8G6 zoKJ(fF-gfo;^XnjcuHPMLVVoEikR!nbrNi5 zRH-yNtYi>rsMb~+Qin88sC7Cg);GNe-?Qa(3K`00HS&CEf5gZAkw%*&kbwA^?AAg! z7hvUNgPFi!nh0cKF)2nf5d)3HmCfOZB_y&?!s80WWRgU}0n4)ey^hgNj_dWk)Pt-h z?%h|^=8&~Hw4;e4hvnbn)<5$-qBQr`^wt8$OqTG@-|VOg*{VYq+QwsF#Lq=yoffim zg;q3?J9LrHScJdwoU2V|Z0&mm@bynVDn7pQgPYe5v92ka6Y7JT7B2mL3AhfstG7D? zT~S#a#oRcKcW$+F&=QwvoxjxKJtOFGaBHf+N41%4jC<1?<}c~&oWFQR>%T|MNB?UD zzb@afXa}0?+O=!eK|6pc*KYvx3wntyunReBQC;>4A*3!0bd#ni9YSAr%F?qeWz9l} z?Q;NI!YY_>ZPIHU#z1O>joEDpx*uIU2Pa z#j;N*nL2$AL2P3E!O04J;CiJ{Zb?)xYn>oRpmKIZ2~wh{o`W>WL_yds zCLsm6RJa_C)V1`{)v&zqDj5UyknMCsMr)h=wn*9(+&Pu9$N&CK8QiBvG6a zDcNJ7&;TQ9MqT^I2JL6=;qQgbdxN`ZJ({lR?H15lU$|JDPI;wOfeeurq51u1mbJ4?0$^F>r(OE z$&XW{Zc;oMKUtyCO>vj1Q%{r+``j!?bU{ectnPkbA<^AZDa~ajQmIBJF8egN3?ynp z22rQWr6>#02!j)>?U`eS=NM-jVenw(SrYLcnS75(I!jSKj*EMoknqGV%aa5Uw^*J# zdJq1dbLhzCOoqYowduv=cX`#6WHEtbnRb{K&=xP({-gy{Z*RDRaq8&r5w%GQaLEoGOowZQl!=SERR z2GW;-lr$(m?R)uIeew$XHaO#+6P821kp|_bt=*u)YVr6L3i?0ZQ&8sguY)RnVFqQK z8<4T!UG$=o9oBXWx8&ufJ><|vBkOrXv6<9_D%td0$8CFnub!1&^J7lB-{=iHS zitofxM|)#6Sac8ZDbX+8j}J*E*wcU;IOnn)VZOJ$>EdR+lg%jmw#bRolcmytzB#&m zcZb{IE+4bwv_QTY-R=%^xhTL-@FO&zLR(cDIA4i@gLuMMh68@S>tEpct_~F=%V|VA z2kwrZ6Vexs?;N!mOlx)o6YI@xjDG5BjiWSHW5ZFyCU>zQQIun zMpd1HS5CULPQY)F$}NOMgSg_EdqYW+cp3|`#w&0)OKS=3hyeJWpluk?<}K|Q4Djuz z^%~obl2=ik|RP!l?ViJj8IrpH8@R?-YqoUYTURguGNTzjZRHW$_~@JL>DU8 zv{_bv5=a;r`HtW@uC13L2vzy0#Kp9|>z+by=fh$U)h>~s?Q1LplmTh3p@RWARTA3{ zE>-Mch|MpCmM)df$jfDcWGGf0vPOX{y)Uqr^Ye z3HU6&m~N;D5*W+?<^ms^aoL3M3me`Ku*o;l3&Z0;#cqR)W{4le^RBV>&(CQQkM4o- zR9eSWIYQzQv0z#riy3$cV<<>y4&=Ca0fYg5uw1O5NMXXIiUd3d7{UQ-mBI*HVgT?F zz;+5V%w{p%y>}-JzQa33NcDcFK?Wy&r%0(uzi-2^A_l2dXOad1Wy&?dqM@)TmN^hh zXaRxL)$tmQY0{ucMVc0oqY}+R%0t>9qPdMMtVx|lTx4Wr0X32?Yg%ADgPuc$Co)`9nlPi}Xn9 zYIKhzX(Uw|v_i^Clj$iS!YvMVeuie+AAmFr12Df%`cF=@7=sNFYp7v{8)2kTMjK Date: Mon, 17 Aug 2020 18:50:48 +0200 Subject: [PATCH 3/4] new small logos, corrected 'other' guide section, new openmage style --- _layouts/m1x.html | 25 +++++++++++-- _layouts/m1x_rest.html | 22 ++++++++++- _layouts/m1x_soap.html | 22 ++++++++++- common/css/stylesheet.css | 30 +++++++-------- guides/m1x/images/icon-important.png | Bin 943 -> 1579 bytes guides/m1x/index.html | 2 +- guides/m1x/other/appsec-900_addhandler.html | 28 +------------- .../m1x/other/discover-card-validation.html | 25 +------------ guides/m1x/other/ee_connect_patches.html | 27 +------------- .../m1x/other/ht_extend_magento_rest_api.html | 34 ++--------------- guides/m1x/other/ht_install-patches.html | 29 +-------------- guides/m1x/other/php5.4_patch.html | 30 +-------------- guides/m1x/other/remote-code-exploit.html | 25 +------------ guides/m1x/other/solr-ee-patches.html | 35 +----------------- 14 files changed, 95 insertions(+), 239 deletions(-) diff --git a/_layouts/m1x.html b/_layouts/m1x.html index 987a49430c..db79a9c048 100644 --- a/_layouts/m1x.html +++ b/_layouts/m1x.html @@ -11,9 +11,28 @@ {{ page.title }} - - header - {% include m1x/eol_message.html %} + + +
    + + + + + + + m + + + openmage + + +

    {{ site.title }}

    +

    {{ page.title }}

    {{ content }} diff --git a/_layouts/m1x_rest.html b/_layouts/m1x_rest.html index 26672ce8a0..5a373a0a6e 100644 --- a/_layouts/m1x_rest.html +++ b/_layouts/m1x_rest.html @@ -31,8 +31,26 @@ - header - {% include m1x/eol_message.html %} +
    + + + + + + + m + + + openmage + + +

    {{ site.title }}

    +

    {{ page.title }}

    Edit this page on GitHub

    diff --git a/_layouts/m1x_soap.html b/_layouts/m1x_soap.html index 2bb5962848..f868ecc8f5 100644 --- a/_layouts/m1x_soap.html +++ b/_layouts/m1x_soap.html @@ -31,8 +31,26 @@ - header - {% include m1x/eol_message.html %} +
    + + + + + + + m + + + openmage + + +

    {{ site.title }}

    +

    {{ page.title }}

    Edit this page on GitHub

    diff --git a/common/css/stylesheet.css b/common/css/stylesheet.css index a246a6bd70..ecfc1fa25b 100644 --- a/common/css/stylesheet.css +++ b/common/css/stylesheet.css @@ -26,7 +26,7 @@ body { #content-2 { float:right; width:700px; } #left-nav h4 { color:#666666; border-bottom:2px dotted #dddddd; padding:5px; } #left-nav li.highlight a:link, #left-nav li.highlight a:visited { - color: #F47027; + color: #FB0E70; text-decoration: none; } #left-nav ul.related-documents li { @@ -46,7 +46,7 @@ h3, h4, h5, h6 { font-weight:100; color:#444444; margin:25px 0 2px 0; } h1 { font: 36px/46px 'Poppins', Helvetica, sans-serif; letter-spacing: 0; } -h2 { font: 31px/41px 'Poppins', Helvetica, sans-serif; color:#f47027; } +h2 { font: 31px/41px 'Poppins', Helvetica, sans-serif; color:#A447A4; } h3 { font: 27px/37px 'Poppins', Helvetica, sans-serif; letter-spacing: 0;} @@ -68,9 +68,9 @@ p.toc a.first { padding-left: 0; } p { letter-spacing: 0.05px; color:#555555; line-height:20px; margin: 8px 0 17px;} /* LINKS */ -a:link, a:visited { color:#0090c0; text-decoration:none; } -a:hover{ color:#ff613d; } -a:active{ color:#0090c0; } +a:link, a:visited { color:#A447A4; text-decoration:none; } +a:hover{ color:#FB0E70; } +a:active{ color:#FB0E70; } /* NOTES TIPS ETC. */ @@ -100,9 +100,9 @@ a:active{ color:#0090c0; } border-left: 5px solid #f7941d; } .important { - background-color: rgba(229, 122, 63, 0.04); - border:1px solid #EE6933; - border-left: 5px solid #EE6933; } + background-color: rgba(251, 14, 112, 0.04); + border:1px solid #FB0E70; + border-left: 5px solid #FB0E70; } .note { background-color: rgba(0, 0, 0, 0.025); @@ -115,7 +115,7 @@ a:active{ color:#0090c0; } border-left: 5px solid #fbe841; } .msg-box span { position:relative; left:10px; padding-right:5px; } -.msg-box img { position:relative; top:-3px; left:5px; } +.msg-box img { position:relative; top:-3px; left:5px; width:30px } pre { font-size:14px; line-height:20px; overflow: auto; } @@ -606,7 +606,7 @@ a.image:hover { } .soap-api-menu ul li a:hover, .soap-api-menu ul li a.active { - color: #f47027; + color: #FB0E70; } .soap-api-content { float: right; @@ -636,7 +636,7 @@ a.image:hover { left: 3px; content: ''; border: 7px outset transparent; - border-top: 7px solid #ed6739; + border-top: 7px solid #FB0E70; } .soap-api-menu li.parent > .arr:after { position: absolute; @@ -650,7 +650,7 @@ a.image:hover { } .soap-api-menu li.parent.open > .arr:before { border: 7px outset transparent; - border-bottom: 7px solid #ed6739; + border-bottom: 7px solid #FB0E70; top: -3px; } .soap-api-menu li.parent.open > .arr:after { @@ -663,7 +663,7 @@ a.image:hover { font-weight: bold; } .introduction-menu { - background: #f7f3eb; + background: #fdf2fd; margin-left: 0; padding: 20px; list-style: none; @@ -673,10 +673,10 @@ a.image:hover { padding: 0; } .introduction-menu a { - color: #c14800 + color: #A447A4 } .introduction-menu a:hover { - color: #ef672f; + color: #FB0E70 } .message-banner { diff --git a/guides/m1x/images/icon-important.png b/guides/m1x/images/icon-important.png index d052f684af9ec781f11d625b3eca87da8f89a1a7..9a0368b4c28e3087a447e39c1059d0b69db5b50e 100644 GIT binary patch literal 1579 zcmV+`2Gse9P) zK~z}7&6r(m99I>9zjJqH*WP+(cb%p!i2M{qO%XJzt304SfCK{MNQF|;7f=&LAjCsA zJL{Unq?bDwYsZ3o0VPAf*Wf0&ctBv1@xhKZl2% zwZ}AecWoScq>=8NbMD-4&bjy8J0omBw0IP0ewEO1vk`hDVs>{7oHyu;DX%`K!zJX^ z@pX?O>xScQgdY$T%J0-j9s@=I6PqL8c~K5nGxa}peXkneLcYR4t45Ih%#d0Gmw@6b zuCGe4u)~^rc(&W8Uoq<*;%z}XdW$~?kC!gV80F@E|zT+N1*_$v;Sf=fy z7Q-Ack?643ciaP==CRFB@%-D4F!0j637qsf;HDS?k#MKwjb8)^9Ct?qFD4%TSIfKM z=J^|cA7(E+zIhSUVwu60P7pZh2bSOfF?w$o4#4v27mY|M(REkg{PRoM3y(9Ozjt#Z z806h|sq#WX^~Wf(Mp7w1uv(4Sr$P|6Qz?^v4%pKjNmcixy~Ych0;rS-@?xXrC%^}m z4YJ>!shzq~A3yJY4CTp$>KPFoO|^=?^f(_)uc;NrA(Hp3gyR`|rgrKNJpH;pO={S! z`YC0F@%=>Ry~44cQ{5AwG#hb4ew0wpijlhj_G~@ z{BHoerNMXHM}VP(=^?+}8Ca&iiSM{0zT-CIYefF>?M^>mJm8_k1G9eKeWcg2^M-)) zJ0|gSW4nNlC$O7V##9FvYRTE`0tKKDw*eTOt7B#CI>O5d$WMerW4l|o|9azq*^A!? z2~PsqB^KchnX0yRxReZa?n-UF_Or;;@wTXZH1XKMC>2!;6K6LL=oj2WAfpM@_pDaq zH$n09J)KhI<*yMq6)dmzEXt#am)Pg$4w#K-NNu-`m`>W$^~ua@{crr4*>UVvV-lf} zJWNESN&xc(x4%NI*B;p#EQbG1s4m!E{q3tx1;_m%(4A+eZLfaUs=m4MUl7^VCGdr} zWT)$w`$}=p4u6@vRip8VWaFZ65D2zgGDX(@pDBQnBDH?+ydIH!6Y$J%C@C#$BpNJfn zlvls3%E5$sXJ)apfC9(8@*?pacQ5d}gz9-wxjnR^g|(yCzqE%cq*CF4s+ovCxVk{^ zw!HdpR{-j8iN(OS4AB|jeF@_}%d7v4O_abXk1F!hgz9W0@}abtK&DS1e!ha;suASN zA5>kjntp71^*j9HgV@c_y}@oX27Z_#CEGd^C;A(agtoVK)cxWE*v&8C=iJi>cP`C4 zF{7zg_2<4*=|s>UzV8|We+n3keWuiy-RbFSQ+qts`uWN|s6H0Y+)vtGBx3%HOtW!*%^hPCB!(l?Y@8?Y4Wq(s26!#; zD%W*)3@skLYJgfiy0lB_@;HDJwsdTIUifI?`Bki3$19B^HKj@!<@c#f6#$z7?ZcTgD dr`v@x{{dimLA`hT2z~$n002ovPDHLkV1fxG1dadz literal 943 zcmeAS@N?(olHy`uVBq!ia0vp^x**KK3=%maw1R|OHXz{*eEiJvEA{JDGK_mv|bo5Ow_TK%EI|J>&-TL8-s+SvP-tEcyzHRpRP1F8;e)plu>r+SUw>7=LZ=C!*HUHO{oj;Fn z`nG=3mj$)|zkm9^bN=7w_r7nR`|rcc&y%wLeSH1v@}aNG+J2te_P*5l&;3hZW|sVU za?`;v^D!`1>`Q|Df*CHkvK*c{ZN8kb&8}HfwkD|GzL%r<_N21+=j}xmE31XgN`+Jo zWbTXFdnWvdy}_bDX}>KSf99`V@j+^itPbm|bFWr+0%LZLr;B4q#jUp&nXfAwO0+$^ zVs>p??vs;Ow(Z^awtk=1q>GOZC%)hHzLbqKa@#Z6yYIfq6;<=S|7UHR#+@)P`~Lj5 zTTe4wI)D3T-0rVSxMukOWz6qb^lhV4dg?r0hHkxmRkEG=AsS!RI=QRd`yOPso%$Wn z;v4O5ICE0P+|O~Min=+DNmWnM`tJ7VS4d8rob|?ilfhi?o{hKvybxZSZP{n|H0sf= zpu=)g`5t}Ek@>$eKky!RPH2+4Rrg2PV@XZt4llj3`$LA|xo0U>lUqC&ZeMuj`6Qpq zCV#m0%GcWUJx|%iyxd9tU~;0~$r5q5)^AGsXCCtg+8^<2{kA}rsgp}|qw_-k1umsp z2OLCh2G(eHtU1zOCmy!wjl!v>ybovnmu?JP>MXJ3$3n^b=M=vQm8R`^biB{7Ecw^l zzZ`bFwM?Fg&9BbhEG;RVm63Yzxqe7sR?h*^MK>!$>`#8YU2Y+*W_7b6$o0Ts!6v4# zvUf^ZOP7CNKD$Vtcg{|ie-rMqG4Km@x_o-R{HFWANwue+`Tm%CFiYkCl)DcLW}K+n a@`hcobbIA9Pc2Y(WbkzLb6Mw<&;$U9YWDE} diff --git a/guides/m1x/index.html b/guides/m1x/index.html index 106baf1ddf..509f15282e 100644 --- a/guides/m1x/index.html +++ b/guides/m1x/index.html @@ -1,6 +1,6 @@ --- layout: m1x -title: Magento 1.x Reference +title: Openmage 1.x Reference ---

    Welcome to the home page for Magento 1.x documentation for installation, configuration, developers, patches, and more. Here you'll find articles that were formerly located on http://magentocommerce.com/knowledge-base.

    diff --git a/guides/m1x/other/appsec-900_addhandler.html b/guides/m1x/other/appsec-900_addhandler.html index a8e52fb04d..0bbc88c618 100644 --- a/guides/m1x/other/appsec-900_addhandler.html +++ b/guides/m1x/other/appsec-900_addhandler.html @@ -1,28 +1,8 @@ --- +title: 'Discover credit card validation issue: Magento EE 1.9.1.1—.13.1.0 and CE 1.4.2.0—1.8.1.0' +layout: m1x --- - - - - - - - - - - - Discover credit card validation issue: Magento EE 1.9.1.1—.13.1.0 and CE 1.4.2.0—1.8.1.0 - - - - -header -{% include m1x/eol_message.html %} - - - - -

    Table of Contents

    The regular expression in this setting matches .php only to the final extension in the file name, applying the handler only to PHP files and preventing PHP from executing. - - - - diff --git a/guides/m1x/other/discover-card-validation.html b/guides/m1x/other/discover-card-validation.html index b3f276aac2..3c72ca3d9d 100644 --- a/guides/m1x/other/discover-card-validation.html +++ b/guides/m1x/other/discover-card-validation.html @@ -1,29 +1,8 @@ --- +title: 'Discover credit card validation issue: Magento EE 1.9.1.1—.13.1.0 and CE 1.4.2.0—1.8.1.0' +layout: m1x --- - - - - - - - - - - - Discover credit card validation issue: Magento EE 1.9.1.1—.13.1.0 and CE 1.4.2.0—1.8.1.0 - - - - - header -{% include m1x/eol_message.html %} - - - - - -

    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

    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.

    diff --git a/guides/m1x/other/ee_connect_patches.html b/guides/m1x/other/ee_connect_patches.html index 5ce120646e..6e28fc4824 100644 --- a/guides/m1x/other/ee_connect_patches.html +++ b/guides/m1x/other/ee_connect_patches.html @@ -1,28 +1,7 @@ --- +title: 'Patches for Magento Enterprise Edition (EE) Versions 1.10–1.12' +layout: m1x --- - - - - - - - - - - - - Patches for Magento Enterprise Edition (EE) Versions 1.10–1.12 - - - - - header -{% include m1x/eol_message.html %} - - - -

    Patches for Magento Enterprise Edition (EE) Versions 1.10–1.12

    -

    We'd like to draw your attention to new patches that were recently posted to the Partner Portal and Support Center. These patches deliver important improvements, such as improving security of the Magento Connect Manager and making it easier to install community-created translation packages.

    @@ -52,5 +31,3 @@

    Solr Search Results and Indexing

    To get this patch, contact Magento Support.

    - - diff --git a/guides/m1x/other/ht_extend_magento_rest_api.html b/guides/m1x/other/ht_extend_magento_rest_api.html index 4ac541c6f8..d7d179f123 100644 --- a/guides/m1x/other/ht_extend_magento_rest_api.html +++ b/guides/m1x/other/ht_extend_magento_rest_api.html @@ -1,31 +1,8 @@ --- ---- - - - - - - - - - - - -How to Extend the Magento REST API to Use Coupon Auto Generation - - - - - - - - -header -{% include m1x/eol_message.html %} - - -

    How to Extend the Magento REST API to Use Coupon Auto Generation

    +title: How to Extend the Magento REST API to Use Coupon Auto Generation +layout: m1x +---

    Table of Contents

      @@ -871,8 +848,3 @@

      Next Steps

    --> - - - - - diff --git a/guides/m1x/other/ht_install-patches.html b/guides/m1x/other/ht_install-patches.html index 8be502b5e9..5ac1aa3a6a 100644 --- a/guides/m1x/other/ht_install-patches.html +++ b/guides/m1x/other/ht_install-patches.html @@ -1,29 +1,7 @@ --- +layout: m1x +title: How to Apply and Revert Magento Patches --- - - - - - - - - - - - - How to Apply and Revert Magento Patches - - - - - -header -{% include m1x/eol_message.html %} - -

    How to Apply and Revert Magento Patches

    - -
    - @@ -170,6 +148,3 @@

    Troubleshooting

  • Try running the patch again.
    If problems persist, contact Magento Support.
  • -
    - - \ No newline at end of file diff --git a/guides/m1x/other/php5.4_patch.html b/guides/m1x/other/php5.4_patch.html index 94407a0e6a..36c7826508 100644 --- a/guides/m1x/other/php5.4_patch.html +++ b/guides/m1x/other/php5.4_patch.html @@ -1,30 +1,7 @@ --- +layout: m1x +title: Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community Edition (CE) --- - - - - - - - - - - - - Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community Edition (CE) - - - - - header -{% include m1x/eol_message.html %} - - - -

    Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community Edition (CE)

    - - - @@ -44,6 +21,3 @@

    Getting the PHP 5.4 patch for Magento Enterprise Edition (EE) and Community
  • In the right pane, click Magento Enterprise Edition.
  • Follow the prompts on your screen to download the PHP 5.4 Compatibility patch.
  • Apply the patch as discussed in How to Apply and Revert Magento Patches.
  • - - - \ No newline at end of file diff --git a/guides/m1x/other/remote-code-exploit.html b/guides/m1x/other/remote-code-exploit.html index 477e881093..a7f3349628 100644 --- a/guides/m1x/other/remote-code-exploit.html +++ b/guides/m1x/other/remote-code-exploit.html @@ -1,26 +1,7 @@ --- +title: Resolving a Remote Code Execution Exploit +layout: m1x --- - - - - - - - - - - - - Resolving a Remote Code Execution Exploit - - - - -header -{% include m1x/eol_message.html %} - -
    -

    Resolving a Remote Code Execution Exploit

    Table of Contents

    • Overview
    • @@ -154,5 +135,3 @@

      Resolving the File System Vulnerability

    - - diff --git a/guides/m1x/other/solr-ee-patches.html b/guides/m1x/other/solr-ee-patches.html index 3d6283ab15..9102038009 100644 --- a/guides/m1x/other/solr-ee-patches.html +++ b/guides/m1x/other/solr-ee-patches.html @@ -1,34 +1,7 @@ --- +title: 'Information About Enterprise Edition (EE) Patches for Apache Solr' +layout: m1x --- - - - - - - - - - - - - Information About Enterprise Edition (EE) Patches for Apache Solr - - - - - header -{% include m1x/eol_message.html %} - - - -

    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. @@ -376,7 +349,3 @@

      Troubleshooting

      Typically, this means running it as the web server user or as a user with root privileges.
    3. Try running the patch again.
      If problems persist, contact Magento Support.
    4. - -
    - - From 82b3f3f9f5f4b2bd5d31ce31bd644de7261d319c Mon Sep 17 00:00:00 2001 From: Splendid Internet Date: Mon, 17 Aug 2020 20:10:05 +0200 Subject: [PATCH 4/4] corrected two articles --- .../m1x/other/discover-card-validation.html | 3 -- guides/m1x/other/payflow.html | 32 ++----------------- 2 files changed, 2 insertions(+), 33 deletions(-) diff --git a/guides/m1x/other/discover-card-validation.html b/guides/m1x/other/discover-card-validation.html index 3c72ca3d9d..07931b4e37 100644 --- a/guides/m1x/other/discover-card-validation.html +++ b/guides/m1x/other/discover-card-validation.html @@ -2,9 +2,6 @@ title: 'Discover credit card validation issue: Magento EE 1.9.1.1—.13.1.0 and CE 1.4.2.0—1.8.1.0' layout: m1x --- - -

    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

    -

    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.

    This fix applies to:

    • Magento Enterprise Edition (EE) versions 1.9.1.1–1.13.1.0
    • diff --git a/guides/m1x/other/payflow.html b/guides/m1x/other/payflow.html index db4121f67a..bcac4103f3 100644 --- a/guides/m1x/other/payflow.html +++ b/guides/m1x/other/payflow.html @@ -1,34 +1,9 @@ --- +title: 'Error Using Payflow with Magento Enterprise Edition (EE) 1.12.0.2' +layout: m1x --- - - - - - - - - - - - - Error Using Payflow with Magento Enterprise Edition (EE) 1.12.0.2 - - - - - header -{% include m1x/eol_message.html %} - -
      - -

      Error Using Payflow with Magento Enterprise Edition (EE) 1.12.0.2

      - -
      - - -

      Problem

      A customer applies a coupon code when checking out in a web store that runs EE 1.12.0.2 and is configured to use the Payflow Pro or Payflow Express payment methods. The following error displays:

      PayPal gateway rejected the request. Field format error: 10431-Item amount is invalid @@ -36,6 +11,3 @@

      Problem

      Solution

      To resolve this issue, contact Magento Support and request the patch for support issue ID SUPEE-1474.

      Then apply the patch as discussed in How to Apply and Revert Magento Patches.

      -
      - - \ No newline at end of file