<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Magento Error Archives - Measured Designs</title>
	<atom:link href="https://www.measureddesigns.com/tag/magento-error/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.measureddesigns.com/tag/magento-error/</link>
	<description>Thoughtful design as standard</description>
	<lastBuildDate>Fri, 10 Mar 2023 15:01:02 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Magento &#8211; Source fields are not mapped. Document: catalog_eav_attribute. Fields: layered_navigation_canonical</title>
		<link>https://www.measureddesigns.com/magento-source-fields-are-not-mapped-document-catalog_eav_attribute-fields-layered_navigation_canonical/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-source-fields-are-not-mapped-document-catalog_eav_attribute-fields-layered_navigation_canonical</link>
					<comments>https://www.measureddesigns.com/magento-source-fields-are-not-mapped-document-catalog_eav_attribute-fields-layered_navigation_canonical/#comments</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Mon, 21 Jan 2019 11:47:59 +0000</pubDate>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento Errors]]></category>
		<category><![CDATA[Magento 2 upgrade]]></category>
		<category><![CDATA[Magento Error]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=2569</guid>

					<description><![CDATA[<p>Migrating a Magento 1 site to Magento 2, I hit the error 'Source fields are not mapped'</p>
<p>The post <a href="https://www.measureddesigns.com/magento-source-fields-are-not-mapped-document-catalog_eav_attribute-fields-layered_navigation_canonical/">Magento &#8211; Source fields are not mapped. Document: catalog_eav_attribute. Fields: layered_navigation_canonical</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-source-fields-are-not-mapped-document-catalog_eav_attribute-fields-layered_navigation_canonical/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Magento migration &#8211; Orphan records error</title>
		<link>https://www.measureddesigns.com/magento-migration-orphan-records-error/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-migration-orphan-records-error</link>
					<comments>https://www.measureddesigns.com/magento-migration-orphan-records-error/#respond</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Tue, 15 Jan 2019 19:19:33 +0000</pubDate>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento Errors]]></category>
		<category><![CDATA[Magento Error]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=2566</guid>

					<description><![CDATA[<p>When migrating from Magento 1 to Magento 2 you may encounter orphan record errors.</p>
<p>The post <a href="https://www.measureddesigns.com/magento-migration-orphan-records-error/">Magento migration &#8211; Orphan records error</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-migration-orphan-records-error/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Magento 2 &#8211; sitemap generation error &#8211; Environment emulation nesting is not allowed</title>
		<link>https://www.measureddesigns.com/magento-2-sitemap-generation-error-environment-emulation-nesting-is-not-allowed/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-2-sitemap-generation-error-environment-emulation-nesting-is-not-allowed</link>
					<comments>https://www.measureddesigns.com/magento-2-sitemap-generation-error-environment-emulation-nesting-is-not-allowed/#respond</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Wed, 09 Jan 2019 19:47:35 +0000</pubDate>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento 2 errors]]></category>
		<category><![CDATA[Magento Error]]></category>
		<category><![CDATA[Sitemap.xml]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=2558</guid>

					<description><![CDATA[<p>After upgrading to Magento 2.3.0 a client flagged up an issue with the sitemap.xml. I later found the error: Environment emulation nesting is not allowed.</p>
<p>The post <a href="https://www.measureddesigns.com/magento-2-sitemap-generation-error-environment-emulation-nesting-is-not-allowed/">Magento 2 &#8211; sitemap generation error &#8211; Environment emulation nesting is not allowed</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-2-sitemap-generation-error-environment-emulation-nesting-is-not-allowed/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Magento &#8211; missing blocks after 1.9.2.2 update</title>
		<link>https://www.measureddesigns.com/magento-missing-blocks-after-1-9-2-2-update/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-missing-blocks-after-1-9-2-2-update</link>
					<comments>https://www.measureddesigns.com/magento-missing-blocks-after-1-9-2-2-update/#respond</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Fri, 06 Nov 2015 11:18:28 +0000</pubDate>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento Errors]]></category>
		<category><![CDATA[Patches]]></category>
		<category><![CDATA[Magento Error]]></category>
		<category><![CDATA[missing blocks]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=2155</guid>

					<description><![CDATA[<p>Magento - missing blocks after 1.9.2.2 update. After updating a Magento site to v 1.9.2.2, I noticed that the randomised block code used on the homepage was missing.</p>
<p>The post <a href="https://www.measureddesigns.com/magento-missing-blocks-after-1-9-2-2-update/">Magento &#8211; missing blocks after 1.9.2.2 update</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-missing-blocks-after-1-9-2-2-update/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Magento – SUPEE-5994 – can’t find file to patch at input line 347</title>
		<link>https://www.measureddesigns.com/magento-supee-5994-cant-find-file-to-patch-at-input-line-347/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-supee-5994-cant-find-file-to-patch-at-input-line-347</link>
					<comments>https://www.measureddesigns.com/magento-supee-5994-cant-find-file-to-patch-at-input-line-347/#comments</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Mon, 18 May 2015 16:33:12 +0000</pubDate>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento Errors]]></category>
		<category><![CDATA[Patches]]></category>
		<category><![CDATA[Magento Error]]></category>
		<category><![CDATA[Magento patches]]></category>
		<category><![CDATA[Security Updates]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[SUPEE-5994]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=1940</guid>

					<description><![CDATA[<p>Magento has released critical patch being SUPEE-5994. However, when trying to apply the patch for one Magento site, I received the following PEAR (input line 347) error</p>
<p>The post <a href="https://www.measureddesigns.com/magento-supee-5994-cant-find-file-to-patch-at-input-line-347/">Magento – SUPEE-5994 – can’t find file to patch at input line 347</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-supee-5994-cant-find-file-to-patch-at-input-line-347/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Magento &#8211; Invalid backend model specified backend_startdate_specialprice</title>
		<link>https://www.measureddesigns.com/magento-invalid-backend-model-specified-catalogproduct_attribute_backend_startdate_specialprice/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-invalid-backend-model-specified-catalogproduct_attribute_backend_startdate_specialprice</link>
					<comments>https://www.measureddesigns.com/magento-invalid-backend-model-specified-catalogproduct_attribute_backend_startdate_specialprice/#comments</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Fri, 15 May 2015 11:14:54 +0000</pubDate>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento Errors]]></category>
		<category><![CDATA[Magento Error]]></category>
		<category><![CDATA[startdate_specialprice]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=1929</guid>

					<description><![CDATA[<p>I hit the following error when trying to reindex a client's website in Magento admin; Invalid backend model specified: catalog/product_attribute_backend_startdate_specialprice</p>
<p>The post <a href="https://www.measureddesigns.com/magento-invalid-backend-model-specified-catalogproduct_attribute_backend_startdate_specialprice/">Magento &#8211; Invalid backend model specified backend_startdate_specialprice</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-invalid-backend-model-specified-catalogproduct_attribute_backend_startdate_specialprice/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Magento 404 frontend error after upgrade</title>
		<link>https://www.measureddesigns.com/magento-404-frontend-error-upgrade/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-404-frontend-error-upgrade</link>
					<comments>https://www.measureddesigns.com/magento-404-frontend-error-upgrade/#respond</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Thu, 27 Nov 2014 18:35:00 +0000</pubDate>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento Errors]]></category>
		<category><![CDATA[Upgrading]]></category>
		<category><![CDATA[Magento Error]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=1615</guid>

					<description><![CDATA[<p>Magento 404 frontend error. After upgrading a Magento ecommerce store from v 1.4.1.0 to 1.6.1.0 the frontend displayed a 404 error. The admin section worked</p>
<p>The post <a href="https://www.measureddesigns.com/magento-404-frontend-error-upgrade/">Magento 404 frontend error after upgrade</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-404-frontend-error-upgrade/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Magento &#8211; Can&#8217;t login to Admin &#8211; Mysql error 28 from storage engine</title>
		<link>https://www.measureddesigns.com/magento-cant-login-admin-mysql-error-28-storage-engine/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=magento-cant-login-admin-mysql-error-28-storage-engine</link>
					<comments>https://www.measureddesigns.com/magento-cant-login-admin-mysql-error-28-storage-engine/#respond</comments>
		
		<dc:creator><![CDATA[Andrew Taylor]]></dc:creator>
		<pubDate>Mon, 17 Nov 2014 18:20:23 +0000</pubDate>
				<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento Errors]]></category>
		<category><![CDATA[Magento Error]]></category>
		<guid isPermaLink="false">https://www.measureddesigns.com/?p=1612</guid>

					<description><![CDATA[<p>A client contacted me today unable to login into her Magento site via the admin panel. There hadn't been any recent changes to the db or files, but every time she tried to login entering a correct username and password the page would just reset.</p>
<p>The post <a href="https://www.measureddesigns.com/magento-cant-login-admin-mysql-error-28-storage-engine/">Magento &#8211; Can&#8217;t login to Admin &#8211; Mysql error 28 from storage engine</a> appeared first on <a href="https://www.measureddesigns.com">Measured Designs</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.measureddesigns.com/magento-cant-login-admin-mysql-error-28-storage-engine/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 

Served from: www.measureddesigns.com @ 2026-06-18 22:24:51 by W3 Total Cache
-->