<?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>..::\\ www.christiano.ch //::.. &#187; Wordpress</title>
	<atom:link href="http://www.christiano.ch/wordpress/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.christiano.ch/wordpress</link>
	<description>christiano.ch blog - personal knowledge base, news, memoires et cetera</description>
	<lastBuildDate>Thu, 29 Jul 2010 06:18:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
		<item>
		<title>Fix for WordPress &#8220;Allowed memory size exhausted&#8221; fatal error</title>
		<link>http://www.christiano.ch/wordpress/2009/10/23/fix-for-wordpress-allowed-memory-size-exhausted-fatal-error/</link>
		<comments>http://www.christiano.ch/wordpress/2009/10/23/fix-for-wordpress-allowed-memory-size-exhausted-fatal-error/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 11:48:07 +0000</pubDate>
		<dc:creator>christian</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.christiano.ch/wordpress/2009/10/23/fix-for-wordpress-allowed-memory-size-exhausted-fatal-error/</guid>
		<description><![CDATA[&#160; While trying to upgrade a few WordPress plugins, I got this error message: Fatal error: Allowed memory size of 33564432 bytes exhausted (tried to allocate 7680 bytes) After struggling with trying to fix this, I found a really easy solution – increase the WordPress memory allocation size from 32 MB to 64 MB.&#160; To [...]]]></description>
			<content:encoded><![CDATA[<table border="0" cellspacing="0" cellpadding="2" width="675">
<tbody>
<tr>
<td valign="top" width="590">
<p>&#160; </p>
<p>While trying to upgrade a few WordPress plugins, I got this error message: </p>
<p><code>Fatal error: Allowed memory size of 33564432 bytes exhausted (tried to allocate 7680 bytes)</code></p>
</td>
<td valign="top" width="84"><a href="http://www.christiano.ch/wordpress/wp-content/uploads/2009/10/Logo_Wordpress1.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="Logo_Wordpress" border="0" alt="Logo_Wordpress" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/10/Logo_Wordpress_thumb1.png" width="115" height="115" /></a> </td>
</tr>
</tbody>
</table>
<p> <span id="more-659"></span>
<p>After struggling with trying to fix this, I found a really easy solution – increase the WordPress memory allocation size from 32 MB to 64 MB.&#160; To do this, edit your <strong>wp-settings.php </strong>and change line 13 from:</p>
<p><code>define('WP_MEMORY_LIMIT', '32M');</code></p>
<p>to</p>
<p><code>define('WP_MEMORY_LIMIT', '<strong>64M</strong>');</code></p>
<p>Simple, easy and delicious. No more memory issues for any plugin upgrades!</p>
<p>Another way is to edit php.ini and define the memory_limit there:</p>
<p><code>memory_limit = 48M </code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.christiano.ch/wordpress/2009/10/23/fix-for-wordpress-allowed-memory-size-exhausted-fatal-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protect your email addresses from spam</title>
		<link>http://www.christiano.ch/wordpress/2009/10/20/protect-your-email-addresses-from-spam/</link>
		<comments>http://www.christiano.ch/wordpress/2009/10/20/protect-your-email-addresses-from-spam/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 12:54:55 +0000</pubDate>
		<dc:creator>christian</dc:creator>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Antispam]]></category>
		<category><![CDATA[Content]]></category>

		<guid isPermaLink="false">http://www.christiano.ch/wordpress/2009/10/20/protect-your-email-addresses-from-spam/</guid>
		<description><![CDATA[Before you publish your email addresses somewhere on your webpage, blog or personal site, you should think about protecting it from spammers respectively from bots crawling the net looking for email addresses. There are several methods to accomplish this. I&#8217;ll list a few of those methods: Convert the email address to Unicode characters This was [...]]]></description>
			<content:encoded><![CDATA[<table style="width: 675px" border="0" cellspacing="0" cellpadding="2">
<tbody>
<tr>
<td valign="top" width="597">
<p>Before you publish your email addresses somewhere on your webpage, blog or personal site, you should think about protecting it from spammers respectively from bots crawling the net looking for email addresses.</p>
<p>There are several methods to accomplish this. I&#8217;ll list a few of those methods:</p>
</td>
<td valign="top" width="77"><a href="http://www.christiano.ch/wordpress/wp-content/uploads/2009/10/Antispam1.jpg"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="Antispam" border="0" alt="Antispam" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/10/Antispam_thumb1.jpg" width="97" height="98" /></a></td>
</tr>
</tbody>
</table>
<p> <span id="more-614"></span>
</p>
<p><a href="http://www.google.ch/search?q=email+address+unicode&amp;ie=utf-8&amp;oe=utf-8&amp;aq=t" target="_blank">Convert the email address to Unicode characters</a></p>
<p>This was not a bad idea in the past, but also bots evolve&#160; It can just as easily interpret the special character entities #64;, #46; for the @ and the . characters respectively. A minor plus in this case is that, the user may be able to use their email client.</p>
<p>   <br class="spacer_" /></p>
<h3>HTTP redirection</h3>
<p>Write a server-side script to return &quot;mailto:foo@host.com&quot; link as an HTTP redirect. All modern browsers recognise this, but perhaps not many harvester bots do. This can be done with Apache&#8217;s mod_rewrite, Javascript or server-side scripting. Here is an example in PHP:</p>
<p>/* Will be displayed in browser like*/</p>
<p><a href="http://www.christiano.ch/common/scripts/blog/MailToRedirect.php" target="_blank">foo&#8217;s email</a></p>
<p>/* In email_foo.php file */</p>
<p>&lt;?php</p>
<p>header (&quot;Location: mailto:foo@host.com&quot;);</p>
<p>exit();</p>
<p>?&gt;</p>
<p>In this case the user has to follow the link and rely on their mail application to get a hold of the email address. The user has to copy the email address from the application instead of doing it directly from the webpage.</p>
<p>   <br class="spacer_" /></p>
<h3>Using a JavaScript (my favorite)</h3>
<p>   <br class="spacer_" /></p>
<p>/* Will be displayed in browser like*/</p>
<p><a href="javascript:email('foo',2)">contact foo via mail</a></p>
<p>&#8212;- script &#8212;</p>
<p>&lt;script language=&quot;JavaScript&quot; type=&quot;text/javascript&quot;&gt;</p>
<p>function email(n, d) {</p>
<p>if(d == 1){</p>
<p>document.location.href=&#8217;mailto:&#8217; + n + &#8216;@gmail.com?Subject=contacting from webpage&#8217;;</p>
<p>}</p>
<p>if(d == 2){</p>
<p>document.location.href=&#8217;mailto:&#8217; + n + &#8216;@hotmail.com?Subject=contacting from webpage&#8217;;</p>
<p>}</p>
<p>if(d == 3){</p>
<p>document.location.href=&#8217;mailto:&#8217; + n + &#8216;@someotherdomain.com?Subject=contacting from webpage&#8217;;</p>
<p>}</p>
<p>if(d == 4){</p>
<p>document.location.href=&#8217;mailto:&#8217; + n + &#8216;@christiano.ch?Subject=contacting from webpage&#8217;;</p>
<p>}</p>
<p>}</p>
<p>&lt;/script&gt;</p>
<p>&#8212; end of script&#8212;</p>
<p>however, there are several good methods, it’s almost impossible to list them all .. if you’re interested in protecting your email address using other ways, here are a few keywords to use when searching in Goggle or Bing..</p>
<p>Hex values</p>
<p>HTML Comments</p>
<p>Fake email</p>
<p>Obfuscate AJAX</p>
<p>CSS pseudo-element</p>
<p>Images</p>
<p>CSS unicode-bidi</p>
<p>CSS display be none</p>
<p>Flash</p>
<p>Forms</p>
<p>   <br class="spacer_" /></p>
<h3>Links</h3>
<p><a href="http://www.csarven.ca/hiding-email-addresses" target="_blank">Methods to hide email addresses from page source</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.christiano.ch/wordpress/2009/10/20/protect-your-email-addresses-from-spam/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress: Stop WordPress visual WYSIWYG editor from removing multiple linebreak in your posts</title>
		<link>http://www.christiano.ch/wordpress/2009/08/27/wordpress-stop-wordpress-visual-wysiwyg-editor-from-removing-multiple-linebreak-in-your-posts/</link>
		<comments>http://www.christiano.ch/wordpress/2009/08/27/wordpress-stop-wordpress-visual-wysiwyg-editor-from-removing-multiple-linebreak-in-your-posts/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 06:04:04 +0000</pubDate>
		<dc:creator>christian</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.christiano.ch/wordpress/?p=506</guid>
		<description><![CDATA[If you want to prevent WordPress from filtering line breaks &#60;br&#62; and &#60;p&#62; from a post, then go ahead reading this post .. In spite of trying various methods such as putting line breaks &#8220;&#60;br&#62;&#8221; inside &#8220;&#60;code&#62;&#8221; tag and many other such HTML tricks (many of which can be easily found at WordPress) just to [...]]]></description>
			<content:encoded><![CDATA[<p>If you want to prevent WordPress from filtering line breaks &lt;br&gt; and &lt;p&gt; from a post, then go ahead reading this post .. <br />
 <span id="more-506"></span>In spite of trying various methods such as putting line breaks &#8220;&lt;br&gt;&#8221; inside &#8220;&lt;code&gt;&#8221; tag and many other such HTML tricks (many of which can be easily found at WordPress) just to be able to put multiple intentional line breaks in a post, wordpress would eventually manage to filter those line breaks. Even if the tricks were successfully applied, when it came to re-editing a post, all efforts would go to vain when TinyMCE initiates its own filtering process.</p>
<p>WordPress has a built-in powerful post/text editor commonly known as the “Visual” editor, which uses the open source project named “TinyMCE“. When switching from Visual to HTML editor in WordPress or vice-versa TinyMCE executes a back-end filtration process which removes empty tags, and &lt;br&gt; tags from the post.</p>
<p>TinyMCE-Advanced from WordPress is a WordPress plugin, which adds the option to disable the removal of &lt;p&gt; and &lt;br&gt; tags when saving a post and in the HTML editor. After installing and activating, the option to enable line breaks can be found in the Settings =&gt; TinyMCE Advanced panel.</p>
<p><strong>=&gt; Stop removing the &lt;p&gt; and &lt;br /&gt; tags when saving and show them in the HTML editor</strong></p>
<h3>
<div id="attachment_507" class="wp-caption alignnone" style="width: 650px"><img class="size-full wp-image-507" title="TinyMCE-Advanced_StopRemovin_p_br_tags" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/TinyMCE-Advanced_StopRemovin_p_br_tags.jpg" alt="TinyMCE-Advanced_StopRemovin_p_br_tags" width="640" height="61" /><p class="wp-caption-text">TinyMCE-Advanced_StopRemovin_p_br_tags</p></div>
</h3>
<p><br class="spacer_" /></p>
<p>Aditionally, this plugin adds 16 plugins to TinyMCE, WordPress’ WYSIWYG editor: Advanced hr, Advanced Image, Advanced Link, Context Menu, Emotions (Smilies), Full Screen, IESpell, Layer, Media, Nonbreaking, Print, Search and Replace, Style, Table, Visual Characters and XHTML Extras. Together these plugins can add over 40 new buttons to the toolbar.</p>
<p><br class="spacer_" /></p>
<div id="attachment_517" class="wp-caption alignnone" style="width: 685px"><img class="size-full wp-image-517" title="TinyMCE_Advanced_Button_Arrangement" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/TinyMCE_Advanced_Button_Arrangement2.png" alt="TinyMCE_Advanced_Button_Arrangement" width="675" height="296" /><p class="wp-caption-text">TinyMCE_Advanced_Button_Arrangement</p></div>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<h3>Tags</h3>
<p>Stop WordPress from removing Linebreak, Linebreaks, Line Break, Line Breaks</p>
<p>Force Line Break in WordPress</p>
<p>Enabling Line Break &#8220;&lt;br&gt;&#8221; in WordPress</p>
<p>Linebreak in Posts</p>
<p>Stop remving &lt;br&gt; &lt;p&gt; tag in WordPress</p>
<p>Line break conversion</p>
<p>Formatting WordPress Posts using Line Breaks</p>
]]></content:encoded>
			<wfw:commentRss>http://www.christiano.ch/wordpress/2009/08/27/wordpress-stop-wordpress-visual-wysiwyg-editor-from-removing-multiple-linebreak-in-your-posts/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Make your WordPress Blog iPhone, iPod and Android friendly using WPTouch Plugin/Theme</title>
		<link>http://www.christiano.ch/wordpress/2009/08/08/make-your-wordpress-blog-iphone-ipod-and-android-friendly-using-wptouch-plugintheme/</link>
		<comments>http://www.christiano.ch/wordpress/2009/08/08/make-your-wordpress-blog-iphone-ipod-and-android-friendly-using-wptouch-plugintheme/#comments</comments>
		<pubDate>Sat, 08 Aug 2009 14:53:15 +0000</pubDate>
		<dc:creator>christian</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[iPhone]]></category>

		<guid isPermaLink="false">http://www.christiano.ch/wordpress/?p=268</guid>
		<description><![CDATA[In this post i’m going to explain you how to make your website iPod touch player or iPhone and Android Mobile Phone friendly using an absolutely cool plugin called WPTouch. By default, your site may look pretty good already, but i&#8217;m sure you will agree, this plugin (WPTouch) makes your site much more accessible for [...]]]></description>
			<content:encoded><![CDATA[<p>In this post i’m going to explain you how to make your website iPod touch player or iPhone and Android Mobile Phone friendly using an absolutely cool plugin called WPTouch.</p>
<p>By default, your site may look pretty good already, but i&#8217;m sure you will agree, this plugin (WPTouch) makes your site much more accessible for the mobile crowd.  It also provides a more iPhone, iPod and Android friendly experience.</p>
<p>The brilliant thing with this approach is, you do NOT need to re-code a theme, or do any programming of any sort.  All you have to do is install the plugin (WPTouch), activate it, and your done!</p>
<p>Installing the plugin WPTouch is pretty straight forward.</p>
<p><span id="more-268"></span></p>
<p><strong>Switch to your WordPress Admin, choose <em>Plugins</em> (to the left), click <em>Add New</em></strong></p>
<div id="attachment_269" class="wp-caption alignnone" style="width: 184px"><img class="size-full wp-image-269" title="Wordpress_Plugins_AddNew" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_Plugins_AddNew.PNG" alt="Wordpress_Plugins_AddNew" width="174" height="215" /><p class="wp-caption-text">Wordpress_Plugins_AddNew</p></div>
<p><strong>Now, search the plugin named <em>WPTouch</em> ..then click on <em>Install</em></strong></p>
<div id="attachment_270" class="wp-caption alignnone" style="width: 613px"><img class="size-full wp-image-270" title="Wordpress_Plugins_WPTouch_Install" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_Plugins_WPTouch_Install.PNG" alt="Wordpress_Plugins_WPTouch_Install" width="603" height="147" /><p class="wp-caption-text">Wordpress_Plugins_WPTouch_Install</p></div>
<p><strong>Next click on <em>Install now</em></strong></p>
<div id="attachment_271" class="wp-caption alignnone" style="width: 667px"><img class="size-full wp-image-271" title="Wordpress_Plugins_WPTouch_Install_2" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_Plugins_WPTouch_Install_2.PNG" alt="Wordpress_Plugins_WPTouch_Install_2" width="657" height="269" /><p class="wp-caption-text">Wordpress_Plugins_WPTouch_Install_2</p></div>
<p><strong>WordPress will download the plugin automatically.. when done, click on <em>Activate Plugin</em></strong></p>
<div id="attachment_272" class="wp-caption alignnone" style="width: 641px"><img class="size-full wp-image-272" title="Wordpress_Plugins_WPTouch_Downloaded_ActivatePlugin" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_Plugins_WPTouch_Downloaded_ActivatePlugin.PNG" alt="Wordpress_Plugins_WPTouch_Downloaded_ActivatePlugin" width="631" height="212" /><p class="wp-caption-text">Wordpress_Plugins_WPTouch_Downloaded_ActivatePlugin</p></div>
<p>The the installation of the plugin&#8217;s done and WPTouch should be activated. You can check this in the plugins section of WordPress Admin.</p>
<p>Optional step is configuring the WPTouch plugin. .i will not describe this in this post.. but it is pretty easy and not really necessary since that basic setup runs smooth.</p>
<div id="attachment_273" class="wp-caption alignnone" style="width: 593px"><img class="size-full wp-image-273" title="Wordpress_Plugins_WPTouch_Configure" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_Plugins_WPTouch_Configure.PNG" alt="Wordpress_Plugins_WPTouch_Configure" width="583" height="107" /><p class="wp-caption-text">Wordpress_Plugins_WPTouch_Configure</p></div>
<h2>Before installing WPTouch plugin and after installing WPTouch Plugin Screenshots</h2>
<h2>
<p><div id="attachment_274" class="wp-caption alignnone" style="width: 330px"><img class="size-full wp-image-274" title="Wordpress_Iphone_Theme_Without_WPTouch_Plugin" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_Iphone_Theme_Without_WPTouch_Plugin.png" alt="Wordpress_Iphone_Theme_Without_WPTouch_Plugin" width="320" height="480" /><p class="wp-caption-text">Without_WPTouch_Plugin</p></div></h2>
<h2>
<p><div id="attachment_275" class="wp-caption alignnone" style="width: 330px"><img class="size-full wp-image-275" title="Wordpress_Iphone_Theme_WPTouch_PluginActivated" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_Iphone_Theme_WPTouch_PluginActivated.PNG" alt="Wordpress_Iphone_Theme_WPTouch_PluginActivated" width="320" height="480" /><p class="wp-caption-text">WPTouch_PluginActivated</p></div></h2>
<h2>
<p><div id="attachment_276" class="wp-caption alignnone" style="width: 490px"><img class="size-full wp-image-276" title="Wordpress_iPhoneTheme_without_Plugin" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_iPhoneTheme_without_Plugin.PNG" alt="Wordpress_iPhoneTheme_without_Plugin" width="480" height="320" /><p class="wp-caption-text">without_WPTouch Plugin</p></div></h2>
<h2>
<p><div id="attachment_277" class="wp-caption alignnone" style="width: 490px"><img class="size-full wp-image-277" title="Wordpress_iPhone_Theme_WPTouch_Activated" src="http://www.christiano.ch/wordpress/wp-content/uploads/2009/08/Wordpress_iPhone_Theme_WPTouch_Activated.PNG" alt="Wordpress_iPhone_Theme_WPTouch_Activated" width="480" height="320" /><p class="wp-caption-text">Wordpress_iPhone_Theme_WPTouch_Activated</p></div></h2>
<p>That&#8217;s it. As usual, feel free to comment..</p>
]]></content:encoded>
			<wfw:commentRss>http://www.christiano.ch/wordpress/2009/08/08/make-your-wordpress-blog-iphone-ipod-and-android-friendly-using-wptouch-plugintheme/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
