<?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>Web design and development in London and Surrey &#187; Tips</title>
	<atom:link href="http://zorinweb.com/category/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://zorinweb.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 14 Apr 2010 21:07:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Problem with WordPress Plugin Activation</title>
		<link>http://zorinweb.com/2010/01/11/problem-with-wordpress-plugin-activation/</link>
		<comments>http://zorinweb.com/2010/01/11/problem-with-wordpress-plugin-activation/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 23:29:08 +0000</pubDate>
		<dc:creator>ZorinWeb</dc:creator>
				<category><![CDATA[Tips]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[php function]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://zorinweb.com/?p=200</guid>
		<description><![CDATA[If you&#8217;re running a number of memory hungry plugins, you might exceed the 32mb worth of memory allotted by the standard WordPress install. I&#8217;ve used an e-commerce solution plugin before that used significantly more memory than the others. So, if you try to activate a WordPress plugin, but can&#8217;t, due to a memory allocation problem, [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re running a number of memory hungry plugins, you might exceed the 32mb worth of memory allotted by the standard WordPress install. I&#8217;ve used an e-commerce solution plugin before that used significantly more memory than the others.</p>
<p><span id="more-200"></span></p>
<p>So, if you try to activate a WordPress plugin, but can&#8217;t, due to a memory allocation problem, you can either modify the wp-settings.php script, or, if that has no effect, increase the &#8216;memory_limit&#8217; variable in the php .ini file. If you can access the php .ini file yourself, great, if not, contact your host.</p>
<p>To change the wp-settings.php file, open it up and locate the following lines:</p>
<p><code><br />
if ( !defined('WP_MEMORY_LIMIT') )<br />
define('WP_MEMORY_LIMIT', '32M');<br />
</code></p>
<p>Now change &#8217;32MB&#8217; to &#8217;64MB&#8217;, so it reads:</p>
<p><code><br />
if ( !defined('WP_MEMORY_LIMIT') )<br />
define('WP_MEMORY_LIMIT', '64M');<br />
</code><br />
Again, if this doesn&#8217;t and you can&#8217;t change the php .ini file yourself, contact your host. Incidentally, if you&#8217;d like to see your &#8216;memory_limit&#8217; allocation, pop the following code into a php web page and upload it to the server:</p>
<p><code><br />
&lt;? php echo phpinfo(); ?&gt;<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://zorinweb.com/2010/01/11/problem-with-wordpress-plugin-activation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fantastic Footers in Web Design</title>
		<link>http://zorinweb.com/2010/01/06/fantastic-footers-in-web-design/</link>
		<comments>http://zorinweb.com/2010/01/06/fantastic-footers-in-web-design/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 21:11:51 +0000</pubDate>
		<dc:creator>ZorinWeb</dc:creator>
				<category><![CDATA[Tips]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web design London]]></category>

		<guid isPermaLink="false">http://zorinweb.com/?p=193</guid>
		<description><![CDATA[As a fan of big footers in web design, I thought I&#8217;d add a link to an interesting piece on the subject over at Design Shack. Big footers are great for organising content, giving a site a sense of structure and grouping/organising otherwise awkward pieces of content.]]></description>
			<content:encoded><![CDATA[<p>As a fan of big footers in web design, I thought I&#8217;d add a link to an <a href="http://designshack.co.uk/articles/inspiration/10-techniques-for-a-fantastic-footer">interesting piece </a>on the subject over at Design Shack. Big footers are great for organising content, giving a site a sense of structure and grouping/organising otherwise awkward pieces of content.</p>
]]></content:encoded>
			<wfw:commentRss>http://zorinweb.com/2010/01/06/fantastic-footers-in-web-design/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Collection of Handy WordPress Tips</title>
		<link>http://zorinweb.com/2009/12/30/collection-of-handy-wordpress-tips/</link>
		<comments>http://zorinweb.com/2009/12/30/collection-of-handy-wordpress-tips/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 14:26:02 +0000</pubDate>
		<dc:creator>ZorinWeb</dc:creator>
				<category><![CDATA[Tips]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://zorinweb.com/?p=147</guid>
		<description><![CDATA[When developing WordPress driven websites for Surrey and South London based businesses, more often than not, I find myself referring to a handy list of WordPress tips. Commonly, it&#8217;s the SQL commands for transferring the local site to the remote host. This is a convenient little resource featuring the abovementioned tip and plenty of others.]]></description>
			<content:encoded><![CDATA[<p>When developing WordPress driven websites for Surrey and South London based businesses, more often than not, I find myself referring to a handy list of WordPress tips. Commonly, it&#8217;s the SQL commands for transferring the local site to the remote host.</p>
<p><span id="more-147"></span></p>
<p><a href="http://www.greepit.com/2008/12/8-useful-wordpress-sql-hacks/" target="_blank">This is a convenient little resource</a> featuring the abovementioned tip and plenty of others.</p>
]]></content:encoded>
			<wfw:commentRss>http://zorinweb.com/2009/12/30/collection-of-handy-wordpress-tips/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Grabbing PHP Form variables with the Extract() Function</title>
		<link>http://zorinweb.com/2009/12/21/grabbing-php-form-variables-with-the-extract-function/</link>
		<comments>http://zorinweb.com/2009/12/21/grabbing-php-form-variables-with-the-extract-function/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 19:31:40 +0000</pubDate>
		<dc:creator>ZorinWeb</dc:creator>
				<category><![CDATA[Tips]]></category>
		<category><![CDATA[contact form]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[php function]]></category>
		<category><![CDATA[xhtml]]></category>

		<guid isPermaLink="false">http://zorinweb.com/?p=135</guid>
		<description><![CDATA[The extract() function is a quick and convenient way of grabbing form variables. Rather than going through the entire $_POST array assigning variables to each element, simply do the following: extract( $_POST ); This creates a value pair corresponding to each key/value pair in the $_POST array (the elements in the contact form). So, the [...]]]></description>
			<content:encoded><![CDATA[<p>The extract() function is a quick and convenient way of grabbing form variables. Rather than going through the entire $_POST array assigning variables to each element, simply do the following:</p>
<p><span id="more-135"></span></p>
<p><code>extract( $_POST );</code></p>
<p>This creates a value pair corresponding to each key/value pair in the $_POST array (the elements in the contact form). So, the names in the posted form fields become the variable names, whose values are automatically assigned to their respective form values.</p>
<p>Take the following basic form:<br />
<code><br />
&lt;form action="emailSent.php" method="post"&gt;<br />
&lt;fieldset&gt;<br />
&lt;legend&gt;Personal information&lt;/legend&gt;<br />
&lt;label&gt;Name&lt;/label&gt;&lt;input type="text" name="name" /&gt;<br />
&lt;label&gt;Email address&lt;/label&gt;&lt;input type="text" name="email" /&gt;<br />
&lt;label&gt;Telephone&lt;/label&gt;&lt;input type="text" name="phone" /&gt;<br />
&lt;/fieldset&gt;<br />
&lt;strong&gt;&lt;label&gt;Message&lt;/label&gt;<br />
&lt;textarea name="message" &gt;&lt;/textarea&gt;<br />
&lt;input type="submit" name="SUBMIT" value="SUBMIT" /&gt;<br />
&lt;/form&gt;<br />
</code><br />
Upon clicking &#8216;submit&#8217;, the form&#8217;s sent to the processing script, &#8216;emailSent.php&#8217;. There, the extract() function would appear:</p>
<p><code>extract( $_POST );</code></p>
<p>Which would immediately capture the $_POST array elements as:<br />
<code><br />
$name=name;<br />
$email=email;<br />
$phone=phone;<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://zorinweb.com/2009/12/21/grabbing-php-form-variables-with-the-extract-function/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixing Internet Explorer CSS Problems with Conditional Comments</title>
		<link>http://zorinweb.com/2009/12/17/fixing-internet-explorer-css-problems-with-conditional-comments/</link>
		<comments>http://zorinweb.com/2009/12/17/fixing-internet-explorer-css-problems-with-conditional-comments/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 16:13:15 +0000</pubDate>
		<dc:creator>ZorinWeb</dc:creator>
				<category><![CDATA[Tips]]></category>
		<category><![CDATA[conditional comments]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[IE6]]></category>
		<category><![CDATA[IE7]]></category>
		<category><![CDATA[Internet Explorer]]></category>

		<guid isPermaLink="false">http://zorinweb.com/?p=93</guid>
		<description><![CDATA[You&#8217;ve developed a site using W3C best practices; it validates, the markup&#8217;s semantic or as clean as possible, and looks great in Firefox. The problem is, Internet Explorer doesn&#8217;t quite see it as the designer intended. The CSS is out and in need of a few hacks; but there&#8217;s a better, more effecient and tidier [...]]]></description>
			<content:encoded><![CDATA[<p>You&#8217;ve developed a site using W3C best practices; it validates, the markup&#8217;s semantic or as clean as possible, and looks great in Firefox. The problem is, Internet Explorer doesn&#8217;t quite see it as the designer intended. The CSS is out and in need of a few hacks; but there&#8217;s a better, more effecient and tidier solution &#8211; conditional comments.<br />
<code><br />
&lt;!--[if lte IE 7]&gt;<br />
&lt;link rel="stylesheet" type="text/css" href="css/ie.css" media="screen" /&gt;<br />
&lt;![endif]--&gt;</code></p>
<p><span id="more-93"></span></p>
<p>The above piece of code targets selects all     IE versions less than or equal to 7, and is Microsoft&#8217;s recommended method for aiming CSS as one of its browsers.  Include all the problematic CSS in stylesheet &#8216;ie.css&#8217; and leave the conditional comment below the main stylesheet. Try this rather than resorting to a hack, or giving up entirely and whacking a table in.</p>
]]></content:encoded>
			<wfw:commentRss>http://zorinweb.com/2009/12/17/fixing-internet-explorer-css-problems-with-conditional-comments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
