<?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>Adrian&#039;s Web Log &#187; Work</title>
	<atom:link href="http://blog.inceweb.com/adrian/category/work/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.inceweb.com/adrian</link>
	<description>Adrian&#039;s second brain.</description>
	<lastBuildDate>Sun, 29 Jan 2012 21:50:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Magento 1.6 Customer Address Edit Error Invalid backend Model Specified</title>
		<link>http://blog.inceweb.com/adrian/2011/12/12/magento-1-6-customer-address-edit-error-invalid-backend-model-specified/</link>
		<comments>http://blog.inceweb.com/adrian/2011/12/12/magento-1-6-customer-address-edit-error-invalid-backend-model-specified/#comments</comments>
		<pubDate>Sun, 11 Dec 2011 23:49:12 +0000</pubDate>
		<dc:creator>Adrian</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[1.6]]></category>
		<category><![CDATA[address]]></category>
		<category><![CDATA[checkout]]></category>
		<category><![CDATA[edit]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[magneto]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/?p=371</guid>
		<description><![CDATA[Following an upgrade from Magento 1.5 to 1.6 the error: Invalid backend model specified: customer_entity/address_attribute_backend_region occurs during customer address edit or checkout address entry. This is because in the eav_attribute table, backend_model values are incorrect. Fix with the following SQL: 1 2 UPDATE `eav_attribute` SET `backend_model` = 'customer/entity_address_attribute_backend_street' WHERE `attribute_code` ='street' LIMIT 1 ; UPDATE [...]]]></description>
			<content:encoded><![CDATA[<p>Following an upgrade from Magento 1.5 to 1.6 the error:<br />
 Invalid backend model specified: customer_entity/address_attribute_backend_region<br />
 occurs during customer address edit or checkout address entry.<br />
 This is because in the eav_attribute table, backend_model values are incorrect. Fix with the following SQL:</p>

<div class="wp_syntax"><table><tr><td class="line_numbers"><pre>1
2
</pre></td><td class="code"><pre class="sql" style="font-family:monospace;"><span style="color: #993333; font-weight: bold;">UPDATE</span> <span style="color: #ff0000;">`eav_attribute`</span> <span style="color: #993333; font-weight: bold;">SET</span> <span style="color: #ff0000;">`backend_model`</span> <span style="color: #66cc66;">=</span> <span style="color: #ff0000;">'customer/entity_address_attribute_backend_street'</span> <span style="color: #993333; font-weight: bold;">WHERE</span> <span style="color: #ff0000;">`attribute_code`</span> <span style="color: #66cc66;">=</span><span style="color: #ff0000;">'street'</span> <span style="color: #993333; font-weight: bold;">LIMIT</span> <span style="color: #cc66cc;">1</span> ;
<span style="color: #993333; font-weight: bold;">UPDATE</span> <span style="color: #ff0000;">`eav_attribute`</span> <span style="color: #993333; font-weight: bold;">SET</span> <span style="color: #ff0000;">`backend_model`</span> <span style="color: #66cc66;">=</span> <span style="color: #ff0000;">'customer/entity_address_attribute_backend_region'</span> <span style="color: #993333; font-weight: bold;">WHERE</span> <span style="color: #ff0000;">`attribute_code`</span> <span style="color: #66cc66;">=</span><span style="color: #ff0000;">'region'</span> <span style="color: #993333; font-weight: bold;">LIMIT</span> <span style="color: #cc66cc;">1</span> ;</pre></td></tr></table></div>

]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2011/12/12/magento-1-6-customer-address-edit-error-invalid-backend-model-specified/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Editing Magento&#8217;s Invoice &amp; Despatch PDF Layouts</title>
		<link>http://blog.inceweb.com/adrian/2011/11/24/editing-magentos-invoice-despatch-pdf-layouts/</link>
		<comments>http://blog.inceweb.com/adrian/2011/11/24/editing-magentos-invoice-despatch-pdf-layouts/#comments</comments>
		<pubDate>Thu, 24 Nov 2011 17:01:08 +0000</pubDate>
		<dc:creator>Adrian</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[credit]]></category>
		<category><![CDATA[despatch]]></category>
		<category><![CDATA[invoice]]></category>
		<category><![CDATA[Magento]]></category>
		<category><![CDATA[pdf]]></category>
		<category><![CDATA[shipping]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/?p=364</guid>
		<description><![CDATA[Magento Invoice and Shipping (Despatch) PDF files are delivered with a reasonable layout, already suited toA4 printing, but benefit from some layout improvements, increasing font sizes, and lightening the greyscale boxes in the interests of readability. Take a copy of the relevant core files and place them in: /app/code/local/Mage/Sales/Model/Order/Pdf The relevant files are Invoice.php &#38; [...]]]></description>
			<content:encoded><![CDATA[<p>Magento Invoice and Shipping (Despatch) PDF files are delivered with a reasonable layout, already suited toA4 printing, but benefit from some layout improvements, increasing font sizes, and lightening the greyscale boxes in the interests of readability.<br />
Take a copy of the relevant core files and place them in:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;"><span style="color: #000000; font-weight: bold;">/</span>app<span style="color: #000000; font-weight: bold;">/</span>code<span style="color: #000000; font-weight: bold;">/</span>local<span style="color: #000000; font-weight: bold;">/</span>Mage<span style="color: #000000; font-weight: bold;">/</span>Sales<span style="color: #000000; font-weight: bold;">/</span>Model<span style="color: #000000; font-weight: bold;">/</span>Order<span style="color: #000000; font-weight: bold;">/</span>Pdf</pre></div></div>

<p>The relevant files are Invoice.php &amp; Shipment.php, but Abstract.php contains functions common to both, and the subdirectory Items contains formatting for the line items of each document type.<br />
The following snippet can be used to format database values as currency values:</p>

<div class="wp_syntax"><div class="code"><pre class="php" style="font-family:monospace;"><span style="color: #000088;">$formattedPrice</span> <span style="color: #339933;">=</span> Mage<span style="color: #339933;">::</span><span style="color: #004000;">helper</span><span style="color: #009900;">&#40;</span><span style="color: #0000ff;">'core'</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">-&amp;</span>gt<span style="color: #339933;">;</span>currency<span style="color: #009900;">&#40;</span><span style="color: #000088;">$Price</span><span style="color: #339933;">,</span><span style="color: #009900; font-weight: bold;">true</span><span style="color: #339933;">,</span><span style="color: #009900; font-weight: bold;">false</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span></pre></div></div>

]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2011/11/24/editing-magentos-invoice-despatch-pdf-layouts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento claims it is in Maintenance Mode (and it isn&#8217;t)</title>
		<link>http://blog.inceweb.com/adrian/2011/08/28/magento-claims-it-is-in-mainteance-mode/</link>
		<comments>http://blog.inceweb.com/adrian/2011/08/28/magento-claims-it-is-in-mainteance-mode/#comments</comments>
		<pubDate>Sun, 28 Aug 2011 10:49:07 +0000</pubDate>
		<dc:creator>Adrian</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[503]]></category>
		<category><![CDATA[flag]]></category>
		<category><![CDATA[lock]]></category>
		<category><![CDATA[Magento]]></category>
		<category><![CDATA[maintenance]]></category>
		<category><![CDATA[mode]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/?p=357</guid>
		<description><![CDATA[Assuming that Magento is not actually in maintenance mode (i.e. downloader is not being used) then the following error is the result of a lock file not being removed, probably as the result of an ungraceful exit from the downloader: Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance [...]]]></description>
			<content:encoded><![CDATA[<p>Assuming that Magento is not actually in maintenance mode (i.e. downloader is not being used) then the following error is the result of a lock file not being removed, probably as the result of an ungraceful exit from the downloader:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</pre></div></div>

<p>To take Magento out of maintenance mode, just delete the file:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">maintenance.flag</pre></div></div>

<p>from the Magento root.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2011/08/28/magento-claims-it-is-in-mainteance-mode/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento 1.3 to 1.5 upgrade notes</title>
		<link>http://blog.inceweb.com/adrian/2011/04/07/magento-1-3-to-1-5-upgrade-notes/</link>
		<comments>http://blog.inceweb.com/adrian/2011/04/07/magento-1-3-to-1-5-upgrade-notes/#comments</comments>
		<pubDate>Thu, 07 Apr 2011 15:06:06 +0000</pubDate>
		<dc:creator>Adrian</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[1.3]]></category>
		<category><![CDATA[1.5]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[mage]]></category>
		<category><![CDATA[Magento]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/?p=326</guid>
		<description><![CDATA[The upgrade to 1.5 has a number of &#8220;gotchas&#8221; so while I am debugging the process on the test / staging instance, here are a few notes. Basic process Empty some or all of the log tables as they are potentially huge and are not needed: TRUNCATE `log_customer`; TRUNCATE `log_quote`; TRUNCATE `log_summary`; TRUNCATE `log_url`; TRUNCATE [...]]]></description>
			<content:encoded><![CDATA[<p>The upgrade to 1.5 has a number of &#8220;gotchas&#8221; so while I am debugging the process on the test / staging instance, here are a few notes.</p>
<h3>Basic process</h3>
<p>Empty some or all of the log tables as they are potentially huge and are not needed:</p>

<div class="wp_syntax"><div class="code"><pre class="sql" style="font-family:monospace;"><span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_customer`</span>;
<span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_quote`</span>;
<span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_summary`</span>;
<span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_url`</span>;
<span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_url_info`</span>;
<span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_visitor`</span>;
<span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_visitor_info`</span>;
<span style="color: #993333; font-weight: bold;">TRUNCATE</span> <span style="color: #ff0000;">`log_visitor_online`</span>;</pre></div></div>

<p>Backup the 1.3 instance using Magento&#8217;s built in backup.</p>
<p>Edit the resulting .sql file and uncomment the FOREIGN_KEY controls at the top and bottom of the file:</p>

<div class="wp_syntax"><div class="code"><pre class="sql" style="font-family:monospace;"><span style="color: #993333; font-weight: bold;">SET</span> @OLD_FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span>@@FOREIGN_KEY_CHECKS<span style="color: #66cc66;">,</span> FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span><span style="color: #cc66cc;">0</span>;
<span style="color: #993333; font-weight: bold;">SET</span> FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span>@OLD_FOREIGN_KEY_CHECKS;</pre></div></div>

<p>If the domain or subdomain is changing, do a search &amp; replace e.g. replace www.myshop.com with test5.myshop.com</p>
<p>Create the new database instance, and execute the SQL from the previous step. Make sure it doesn&#8217;t time out, last table created is normally &#8220;wishlist_item&#8221;</p>
<p>Yoast Metarobots breaks product maintenance in Magento 1.4+, so remove relevant fields:</p>

<div class="wp_syntax"><div class="code"><pre class="sql" style="font-family:monospace;"><span style="color: #993333; font-weight: bold;">DELETE</span> <span style="color: #993333; font-weight: bold;">FROM</span> <span style="color: #ff0000;">`core_resource`</span> <span style="color: #993333; font-weight: bold;">WHERE</span> <span style="color: #ff0000;">`core_resource`</span><span style="color: #66cc66;">.</span><span style="color: #ff0000;">`code`</span> <span style="color: #66cc66;">=</span> <span style="color: #ff0000;">'metarobots_setup'</span>;
<span style="color: #993333; font-weight: bold;">DELETE</span> <span style="color: #993333; font-weight: bold;">FROM</span> <span style="color: #ff0000;">`eav_attribute`</span> <span style="color: #993333; font-weight: bold;">WHERE</span> <span style="color: #ff0000;">`eav_attribute`</span><span style="color: #66cc66;">.</span><span style="color: #ff0000;">`attribute_code`</span> <span style="color: #66cc66;">=</span> <span style="color: #ff0000;">'meta_robots'</span>;
<span style="color: #993333; font-weight: bold;">UPDATE</span> eav_entity_type <span style="color: #993333; font-weight: bold;">SET</span> additional_attribute_table<span style="color: #66cc66;">=</span><span style="color: #ff0000;">'catalog/eav_attribute'</span><span style="color: #66cc66;">,</span>entity_attribute_collection<span style="color: #66cc66;">=</span><span style="color: #ff0000;">'catalog/product_attribute_collection'</span> <span style="color: #993333; font-weight: bold;">WHERE</span> entity_type_id<span style="color: #66cc66;">=</span><span style="color: #cc66cc;">4</span>;</pre></div></div>

<p>Now FTP the Magento downloader.php onto the target site, check file permissions and execute it with http://test5.myshop.com/downloader.php</p>
<p>Follow the setup process including specifying the correct database name, user and password.</p>
<p>Use the same encryption key from the original site &#8211; find it in /app/etc/local.xml</p>
<p>If there are problems with the setup not accepting the admin user / password combination, simply re-run the installer by pointing your web browser at http://test5.myshop.com</p>
<p>Remember that the original admin user already exists in the database export, so create a temporary one and delete it later.</p>
<h3>Fixing problems</h3>
<h4>Can&#8217;t access the admin site, gives 404 error</h4>
<p>The database import will have incorrectly sequenced the sites, so run the following:</p>

<div class="wp_syntax"><div class="code"><pre class="sql" style="font-family:monospace;"><span style="color: #993333; font-weight: bold;">SET</span> @OLD_FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span>@@FOREIGN_KEY_CHECKS<span style="color: #66cc66;">,</span> FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span><span style="color: #cc66cc;">0</span>;
<span style="color: #993333; font-weight: bold;">UPDATE</span> core_website <span style="color: #993333; font-weight: bold;">SET</span> website_id<span style="color: #66cc66;">=</span><span style="color: #ff0000;">&quot;0&quot;</span> <span style="color: #993333; font-weight: bold;">WHERE</span> core_website<span style="color: #66cc66;">.</span>code<span style="color: #66cc66;">=</span><span style="color: #ff0000;">&quot;admin&quot;</span> <span style="color: #993333; font-weight: bold;">LIMIT</span> <span style="color: #cc66cc;">1</span>;
<span style="color: #993333; font-weight: bold;">UPDATE</span> core_store <span style="color: #993333; font-weight: bold;">SET</span> store_id<span style="color: #66cc66;">=</span><span style="color: #ff0000;">&quot;0&quot;</span> <span style="color: #993333; font-weight: bold;">WHERE</span> core_store<span style="color: #66cc66;">.</span>code<span style="color: #66cc66;">=</span><span style="color: #ff0000;">&quot;admin&quot;</span> <span style="color: #993333; font-weight: bold;">LIMIT</span> <span style="color: #cc66cc;">1</span>;
<span style="color: #993333; font-weight: bold;">SET</span> FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span>@OLD_FOREIGN_KEY_CHECKS;</pre></div></div>

<h4>Admin site is &#8220;white&#8221; i.e. CSS not working and plain HTML is displayed</h4>
<p>Delete contents of /var/cache/</p>
<h4>&#8220;There are no products matching the selection&#8221; when browsing front end</h4>
<p>Wrong customer group ID for users that are no logged in. Execute the following SQL:</p>

<div class="wp_syntax"><div class="code"><pre class="sql" style="font-family:monospace;"><span style="color: #993333; font-weight: bold;">SET</span> @OLD_FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span>@@FOREIGN_KEY_CHECKS<span style="color: #66cc66;">,</span> FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span><span style="color: #cc66cc;">0</span>;
<span style="color: #993333; font-weight: bold;">UPDATE</span> <span style="color: #ff0000;">`customer_group`</span> <span style="color: #993333; font-weight: bold;">SET</span> <span style="color: #ff0000;">`customer_group_id`</span> <span style="color: #66cc66;">=</span> <span style="color: #cc66cc;">0</span> <span style="color: #993333; font-weight: bold;">WHERE</span> <span style="color: #ff0000;">`customer_group_code`</span> <span style="color: #993333; font-weight: bold;">LIKE</span> <span style="color: #ff0000;">'NOT LOGGED IN'</span>;
<span style="color: #993333; font-weight: bold;">SET</span> FOREIGN_KEY_CHECKS<span style="color: #66cc66;">=</span>@OLD_FOREIGN_KEY_CHECKS;</pre></div></div>

<h4>No product images</h4>
<p>Check correct permissions and then copy the images directory structure from the source site eg:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;"><span style="color: #c20cb9; font-weight: bold;">cp</span> <span style="color: #000000; font-weight: bold;">/</span>httpdocs<span style="color: #000000; font-weight: bold;">/</span>media<span style="color: #000000; font-weight: bold;">/</span>catalog<span style="color: #000000; font-weight: bold;">/*</span> <span style="color: #000000; font-weight: bold;">/</span>subdomains<span style="color: #000000; font-weight: bold;">/</span>test5<span style="color: #000000; font-weight: bold;">/</span>httpdocs<span style="color: #000000; font-weight: bold;">/</span>media<span style="color: #000000; font-weight: bold;">/</span>catalog<span style="color: #000000; font-weight: bold;">/</span></pre></div></div>

<p>Now login to admin site and run a  re-index on everything, and update all of the caches.</p>
<h4>Error File does not exist: &#8230; media/catalog/product/no_selection</h4>
<p>Review the System Configuration and under Catalogue / Catalogue / Product Image Placeholders and add the missing placeholders. Add back in the watermarks too in General / Design / Product Image Watermarks. </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2011/04/07/magento-1-3-to-1-5-upgrade-notes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 2.7.1 auto upgrade fix</title>
		<link>http://blog.inceweb.com/adrian/2009/02/16/wordpress-271-auto-upgrade-fix/</link>
		<comments>http://blog.inceweb.com/adrian/2009/02/16/wordpress-271-auto-upgrade-fix/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 10:51:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[.htaccess]]></category>
		<category><![CDATA[1and1]]></category>
		<category><![CDATA[php4]]></category>
		<category><![CDATA[php5]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[x-mapp]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/?p=72</guid>
		<description><![CDATA[I discovered last night that the auto-upgrade function to take WordPress 2.7 to 2.7.1 failed &#8211; or rather it sat at the &#8220;downloading wordpress-2.7.1.zip&#8221; message indefinitely. At the auto-upgrade is a new feature of 2.7, I had never been able to test this functionality, although I had high expectations of it since the plugin upgrade [...]]]></description>
			<content:encoded><![CDATA[<p>I discovered last night that the auto-upgrade function to take WordPress 2.7 to 2.7.1 failed &#8211; or rather it sat at the &#8220;downloading wordpress-2.7.1.zip&#8221; message indefinitely.</p>
<p>At the auto-upgrade is a new feature of 2.7, I had never been able to test this functionality, although I had high expectations of it since the plugin upgrade has worked so well.</p>
<p>After searching the forums and Google for a while I found <a title="Wordpress 2.7.1 Upgrade Failed" href="http://bassmadrigal.com/blog/2009/02/11/wordpress-271-upgrade-failed/">bassmadrigal&#8217;s solution</a> &#8211; modify .htaccess for the WordPress installation in question and add:</p>
<p><code>AddType x-mapp-php5 .php</code></p>
<p>Works fine, and the auto upgrade of plugins stills works too.</p>
<h3>The science bit</h3>
<p>Using 1and1 as a host requires this directive in .htaccess as detailed in the <a title="Core Update Host Compatibility" href="http://codex.wordpress.org/Core_Update_Host_Compatibility">WordPress codex</a>. It forces the 1and1 server to parse .php files as php5 files (instead of, presumably, php4).</p>
<p>I had this before my upgrade to 2.7 (OK, technically a re-installation) and unfortunately the baby got thrown out with the bathwater.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2009/02/16/wordpress-271-auto-upgrade-fix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>1and1 contract secret</title>
		<link>http://blog.inceweb.com/adrian/2009/02/16/1and1-contract-secret/</link>
		<comments>http://blog.inceweb.com/adrian/2009/02/16/1and1-contract-secret/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 10:24:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[1and1]]></category>
		<category><![CDATA[cancel]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[secret]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/2009/02/16/1and1-contract-secret/</guid>
		<description><![CDATA[Shhh, 1and1 don&#8217;t want you to know this, but&#8230; &#8230; you can cancel or amend contracts at contract.1and1.co.uk As far as I can tell, this information is not to be found on the admin.1and1.co.uk FAQ or Help pages. I had to complete an online support request to find this info. Once you are in, it&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>Shhh, 1and1 don&#8217;t want you to know this, but&#8230;<br />
&#8230; you can cancel or amend contracts at<br />
<a title="1and1 Contract management" href="http://contract.1and1.co.uk">contract.1and1.co.uk</a><br />
As far as I can tell, this information is not to be found on the <a title="1and1 administration console" href="http://admin.1and1.co.uk">admin.1and1.co.uk</a> FAQ or Help pages. I had to complete an online support request to find this info.<br />
Once you are in, it&#8217;s easy &#8211; so I have started the process of releasing four unwanted domain names.</p>
<p>Update 2nd December 2010: the URL has changed to <a title="1and 1 Contract Cancellation" href="http://cancel.1and1.co.uk">cancel.1and1.co.uk</a> &#8211; still not well documented.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2009/02/16/1and1-contract-secret/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GS1 Prefixes</title>
		<link>http://blog.inceweb.com/adrian/2009/02/10/gs1-prefixes/</link>
		<comments>http://blog.inceweb.com/adrian/2009/02/10/gs1-prefixes/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 23:25:03 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[EAN]]></category>
		<category><![CDATA[epos]]></category>
		<category><![CDATA[POS]]></category>
		<category><![CDATA[prefix]]></category>
		<category><![CDATA[UPC]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/?p=66</guid>
		<description><![CDATA[GS1 is the organisation which deals with retail barcode number range issuing; they publish a handy table showing prefix codes.]]></description>
			<content:encoded><![CDATA[<p>GS1 is the organisation which deals with retail barcode number range issuing; they publish a handy table <a title="GS1 Prefix List" href="http://www.gs1.org/productssolutions/idkeys/support/prefix_list.html">showing prefix codes</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2009/02/10/gs1-prefixes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Smoke free signage</title>
		<link>http://blog.inceweb.com/adrian/2009/01/11/smoke-free-signage/</link>
		<comments>http://blog.inceweb.com/adrian/2009/01/11/smoke-free-signage/#comments</comments>
		<pubDate>Sun, 11 Jan 2009 15:42:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[no smoking]]></category>
		<category><![CDATA[sign]]></category>
		<category><![CDATA[smoke free]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/?p=63</guid>
		<description><![CDATA[Premises in England are required to display an A5 no smoking sign at all entrances (roundel only for staff only entrances). Here is a PDF containing the sign.]]></description>
			<content:encoded><![CDATA[<p>Premises in England are required to display an A5 no smoking sign at all entrances (roundel only for staff only entrances).</p>
<p>Here is a <a title="A5 no smoking PDF" href="http://www.smokefreeengland.co.uk/files/a5_sign_sf_premises.pdf">PDF containing the sign</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2009/01/11/smoke-free-signage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chinese Fonts</title>
		<link>http://blog.inceweb.com/adrian/2008/01/16/chinese-fonts/</link>
		<comments>http://blog.inceweb.com/adrian/2008/01/16/chinese-fonts/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 11:04:03 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[chinese-fonts]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/2008/01/16/chinese-fonts/</guid>
		<description><![CDATA[A couple of sources of Chinese fonts: sj00.com University of Heidelberg, Institute of Chinese Studies]]></description>
			<content:encoded><![CDATA[<p>A couple of sources of Chinese fonts:</p>
<p><a href="http://www.sj00.com" title="SJ00">sj00.com</a></p>
<p><a href="http://www.sino.uni-heidelberg.de/edv/sinopc/chinese_fonts.htm" title="University of Heidelberg Institute of Chinese Studies Fonts">University of Heidelberg, Institute of Chinese Studies</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2008/01/16/chinese-fonts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More building contacts</title>
		<link>http://blog.inceweb.com/adrian/2007/10/15/more-building-contacts/</link>
		<comments>http://blog.inceweb.com/adrian/2007/10/15/more-building-contacts/#comments</comments>
		<pubDate>Mon, 15 Oct 2007 12:17:11 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Work]]></category>
		<category><![CDATA[contacts-premises]]></category>

		<guid isPermaLink="false">http://blog.inceweb.com/adrian/2007/10/15/more-building-contacts/</guid>
		<description><![CDATA[Resin flooring &#8211; NIFL. Shopfront &#8211; Aluminium shop fronts. Also: Adams Glass &#38; Windows St George Street Leicester Leicestershire LE1 1QG Tel: 0116 2511715 Fire risk information. A search of Yell turned up: Fire Safety Management, 45, Montague Drive, Loughborough, Leicestershire LE11 3SB. Tel: 01509 237218 Bollards &#8211; Barriers Direct]]></description>
			<content:encoded><![CDATA[<p>Resin flooring &#8211; <a href="http://www.nifl.co.uk/" title="NIFL Resin Flooring.">NIFL</a>.</p>
<p>Shopfront &#8211; <a href="http://www.aluminiumshopfronts.co.uk/contact.php" title="Aluminium Shop Fronts Ltd">Aluminium shop fronts</a>.</p>
<p>Also:<br />
Adams Glass &amp; Windows<br />
St George Street<br />
Leicester<br />
Leicestershire<br />
LE1 1QG<br />
Tel: 0116 2511715</p>
<p>Fire <a href="http://www.leicestershire-fire.gov.uk/safety/risk_information_teams.shtml" title="Fire risk information.">risk information</a>. A search of Yell turned up:</p>
<p class="MsoNormal">Fire Safety Management, 45, Montague   Drive, Loughborough, Leicestershire LE11 3SB. Tel: 01509 237218</p>
<p class="MsoNormal">Bollards &#8211; <a href="http://www.barriersdirect.co.uk/" title="Barriers Direct.">Barriers Direct</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inceweb.com/adrian/2007/10/15/more-building-contacts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

