<?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>Denyerec&#039;s Log - Photography, Comments and Observations - © Denyer 2000-Present &#187; Coding</title>
	<atom:link href="http://www.denyerec.co.uk/category/coding/feed" rel="self" type="application/rss+xml" />
	<link>http://www.denyerec.co.uk</link>
	<description>Photography, Graphic Design, Art, Code...</description>
	<lastBuildDate>Wed, 24 Dec 2014 10:14:07 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.39</generator>
	<item>
		<title>Install PCRE 8 on Ubuntu 10.04 LTS</title>
		<link>http://www.denyerec.co.uk/install-pcre-8-on-ubuntu-10-04-lts</link>
		<comments>http://www.denyerec.co.uk/install-pcre-8-on-ubuntu-10-04-lts#comments</comments>
		<pubDate>Fri, 02 Nov 2012 01:42:01 +0000</pubDate>
		<dc:creator><![CDATA[Denyerec]]></dc:creator>
				<category><![CDATA[Coding]]></category>

		<guid isPermaLink="false">http://www.denyerec.co.uk/?p=342</guid>
		<description><![CDATA[You might find yourself wanting to install Bug Genie, or some other such newfangled toy onto Ubuntu 10.04 &#8220;Lucid&#8221;. You might find yourself stonewalled at the suggestion that your PCRE version (7.8) doesn&#8217;t meet the minimum requirements of 8.x You might then have found yourself here. The solution is thankfully straightforward. Just add the precise [&#8230;]]]></description>
		<wfw:commentRss>http://www.denyerec.co.uk/install-pcre-8-on-ubuntu-10-04-lts/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>TYPO3 FED + Flux Image Previews in BE</title>
		<link>http://www.denyerec.co.uk/typo3-fed-flux-image-previews-in-be</link>
		<comments>http://www.denyerec.co.uk/typo3-fed-flux-image-previews-in-be#comments</comments>
		<pubDate>Wed, 10 Oct 2012 23:33:42 +0000</pubDate>
		<dc:creator><![CDATA[Denyerec]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[TYPO3]]></category>

		<guid isPermaLink="false">http://www.denyerec.co.uk/?p=338</guid>
		<description><![CDATA[If you&#8217;re using TYPO3 along with the jolly-lovely FED/Flux templating system then you may well have tried to make an FCE preview in the backend that includes an image preview. Here&#8217;s where I started: However, this doesn&#8217;t work out so well. A quick showed that the returned image resource path was relative, such as: This [&#8230;]]]></description>
		<wfw:commentRss>http://www.denyerec.co.uk/typo3-fed-flux-image-previews-in-be/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Remove inline style from TYPO3 RTE Blockquotes</title>
		<link>http://www.denyerec.co.uk/remove-inline-style-from-typo3-rte-blockquotes</link>
		<comments>http://www.denyerec.co.uk/remove-inline-style-from-typo3-rte-blockquotes#comments</comments>
		<pubDate>Fri, 28 Sep 2012 23:50:01 +0000</pubDate>
		<dc:creator><![CDATA[Denyerec]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[TYPO3]]></category>

		<guid isPermaLink="false">http://www.denyerec.co.uk/?p=329</guid>
		<description><![CDATA[While we&#8217;re on a roll here, how about removing the ridiculous inline styles from Blockquote tags, and allowing your custom CSS classes to hold their ground? This one is buried right inside the bowels of the CSS Styled Content standard TypoScript, you can knock it on the head here: The above should appear on one [&#8230;]]]></description>
		<wfw:commentRss>http://www.denyerec.co.uk/remove-inline-style-from-typo3-rte-blockquotes/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Removing block types from TYPO3 RTE</title>
		<link>http://www.denyerec.co.uk/removing-block-types-from-typo3-rte</link>
		<comments>http://www.denyerec.co.uk/removing-block-types-from-typo3-rte#comments</comments>
		<pubDate>Fri, 28 Sep 2012 19:45:23 +0000</pubDate>
		<dc:creator><![CDATA[Denyerec]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[TYPO3]]></category>

		<guid isPermaLink="false">http://www.denyerec.co.uk/?p=321</guid>
		<description><![CDATA[When configuring the TYPO3 RTE, it&#8217;s a common requirement to restrict the tags available to the editor. The RTE has dropdowns for block types which, by default, contains everything from p, through h1&#8230;h6, section, aside and so on&#8230; Not good news if you&#8217;ve got creative editors. Removing these involved digging into the source here http://typo3.org/api/typo3/class_8tx__rtehtmlarea__blockelements_8php_source.html [&#8230;]]]></description>
		<wfw:commentRss>http://www.denyerec.co.uk/removing-block-types-from-typo3-rte/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Poor Performance in Magento Checkout (1.4.x &#8211; 1.5?)</title>
		<link>http://www.denyerec.co.uk/poor-performance-in-magento-checkout-14x-15</link>
		<comments>http://www.denyerec.co.uk/poor-performance-in-magento-checkout-14x-15#comments</comments>
		<pubDate>Fri, 15 Apr 2011 19:41:01 +0000</pubDate>
		<dc:creator><![CDATA[Denyerec]]></dc:creator>
				<category><![CDATA[Coding]]></category>

		<guid isPermaLink="false">http://www.denyerec.co.uk/posts/317</guid>
		<description><![CDATA[Just recently I&#8217;ve been plagued by an issue with a Magento cart checkout performing slowly between stages 5 and 6 of the standard one page checkout process. Some bad code in Magento&#8217;s core helped reduce the delays (Loop limit counters that are initialised INSIDE the loop? Hello?), along with judicious increases to DB and PHP [&#8230;]]]></description>
		<wfw:commentRss>http://www.denyerec.co.uk/poor-performance-in-magento-checkout-14x-15/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
