<?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/"
	>

<channel>
	<title>Code Styling Project &#187; English</title>
	<atom:link href="http://www.code-styling.de/blog/english/feed" rel="self" type="application/rss+xml" />
	<link>http://www.code-styling.de</link>
	<description>It's not a bug, it's always a feature.</description>
	<pubDate>Wed, 06 Jan 2010 00:25:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>jQuery 1.3.2 causes problems at IE 8</title>
		<link>http://www.code-styling.de/english/jquery-132-causes-problems-at-ie-8</link>
		<comments>http://www.code-styling.de/english/jquery-132-causes-problems-at-ie-8#comments</comments>
		<pubDate>Sat, 20 Jun 2009 19:08:04 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[jQuery at WordPress]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=951</guid>
		<description><![CDATA[ I have noticed after a lot reports from different users, that something went wrong while using jQuery 1.3.2 and Microsoft Internet Explorer 8 in normal v8 mode (not compatible mode). The effect of this bug is very annoying, all your handler using methods to show and hide portions of you webpage won&#8217;t do anything or [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/jquery-132-causes-problems-at-ie-8/feed</wfw:commentRss>
		</item>
		<item>
		<title>&#8220;Page Columnist&#8221; - Posts and Pages at Column Layout</title>
		<link>http://www.code-styling.de/english/page-columnist-posts-and-pages-at-column-layout</link>
		<comments>http://www.code-styling.de/english/page-columnist-posts-and-pages-at-column-layout#comments</comments>
		<pubDate>Sat, 13 Jun 2009 16:34:16 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=794</guid>
		<description><![CDATA[ Some time ago i was asked by a friend of mine if there is no easy solution to get pages edited at column layout without a knownledge about HTML and CSS simply at the editors. It should be a little bit flexible und easy to use. The upcomming solution was the plugin &#8220;Page Columnist&#8221;.
Unfortunately the [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/page-columnist-posts-and-pages-at-column-layout/feed</wfw:commentRss>
		</item>
		<item>
		<title>WordPress 2.8 changes the metabox model for admin pages</title>
		<link>http://www.code-styling.de/english/wordpress-28-changes-the-metabox-model-for-admin-pages</link>
		<comments>http://www.code-styling.de/english/wordpress-28-changes-the-metabox-model-for-admin-pages#comments</comments>
		<pubDate>Sun, 24 May 2009 13:49:54 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=705</guid>
		<description><![CDATA[ Some time ago i introduced a demo-plugin which shows how to deal with metaboxes inside your own admin pages based on WordPress 2.7 and higher. I&#8217;ve tested the WordPress 2.8 version and found out, that somehow the right sidebar have had disappeared. The reason of this behavoir has been detected at the new column based [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/wordpress-28-changes-the-metabox-model-for-admin-pages/feed</wfw:commentRss>
		</item>
		<item>
		<title>How to use Wordpress Metaboxes at own plugins</title>
		<link>http://www.code-styling.de/english/how-to-use-wordpress-metaboxes-at-own-plugins</link>
		<comments>http://www.code-styling.de/english/how-to-use-wordpress-metaboxes-at-own-plugins#comments</comments>
		<pubDate>Sun, 22 Feb 2009 00:38:39 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=520</guid>
		<description><![CDATA[ Starting with WordPress Version 2.7 a new kind of metabox handling has been occured at Backend. You are now able to drag/drop or hide this Boxes. This makes daily work easier.
But there is currently insufficient documentation available, how this metaboxes can be used at your own plugin pages. I try here to explain the needed [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/how-to-use-wordpress-metaboxes-at-own-plugins/feed</wfw:commentRss>
		</item>
		<item>
		<title>PHP function setlocale() &#8230; and numbers can be damaged</title>
		<link>http://www.code-styling.de/english/php-function-setlocale-and-numbers-can-be-damaged</link>
		<comments>http://www.code-styling.de/english/php-function-setlocale-and-numbers-can-be-damaged#comments</comments>
		<pubDate>Wed, 04 Feb 2009 02:29:40 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=439</guid>
		<description><![CDATA[ At many Blogs and forums you can read the same story about localized month name issues if a theme or plugin doesn&#8217;t use the WordPress build in functions for that purpose. In most cases this will be roughly handled by just take the setlocale() function and override the OS locale settings.
There are also WordPress plugins [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/php-function-setlocale-and-numbers-can-be-damaged/feed</wfw:commentRss>
		</item>
		<item>
		<title>WordPress Localization - Features and future Development</title>
		<link>http://www.code-styling.de/english/wordpress-localization-features-and-future-development</link>
		<comments>http://www.code-styling.de/english/wordpress-localization-features-and-future-development#comments</comments>
		<pubDate>Sun, 28 Dec 2008 02:30:13 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=249</guid>
		<description><![CDATA[ After i started the plugin project Codestyling-Localization i was impressed how big this will become. In the mean time the functional capabilities have been massiv extended but also the needs the user reported will grow daily.
While the plugin got a spreed at the community, i have to handle a huge number of wishes and reports [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/wordpress-localization-features-and-future-development/feed</wfw:commentRss>
		</item>
		<item>
		<title>WordPress Category Tree Chaos at &#8220;Write Posts&#8221;</title>
		<link>http://www.code-styling.de/english/wordpress-category-tree-chaos-at-write-posts</link>
		<comments>http://www.code-styling.de/english/wordpress-category-tree-chaos-at-write-posts#comments</comments>
		<pubDate>Sun, 07 Dec 2008 17:17:40 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=135</guid>
		<description><![CDATA[ While writing new posts you will realize, that something is wrong with the tree view of all categories. WordPress lists all categories as tree and i expect that the defined tree structure will be shown all the time.
Unfortunately WordPress steps in with an unexpected manner which forces the tree view to be shown damaged. The [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/wordpress-category-tree-chaos-at-write-posts/feed</wfw:commentRss>
		</item>
		<item>
		<title>WordPress 2.6.1 loads too many script.aculo.us components</title>
		<link>http://www.code-styling.de/english/wordpress-261-loads-too-many-scriptaculous-components</link>
		<comments>http://www.code-styling.de/english/wordpress-261-loads-too-many-scriptaculous-components#comments</comments>
		<pubDate>Fri, 29 Aug 2008 22:04:05 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=65</guid>
		<description><![CDATA[ If you are a developer of a plugin sometimes you have the desire to play around with effects. One thing comes up quickly: a lot of JavaScripts will be loaded and executed. Everybody using Javascripts inside blogs may know this.
I was pretty sure that I have had only parts of scripts actively requested. But WordPress [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/wordpress-261-loads-too-many-scriptaculous-components/feed</wfw:commentRss>
		</item>
		<item>
		<title>WordPress 2.6 and the Text/Diff fatal errors</title>
		<link>http://www.code-styling.de/english/wordpress-26-and-the-textdiff-fatal-errors</link>
		<comments>http://www.code-styling.de/english/wordpress-26-and-the-textdiff-fatal-errors#comments</comments>
		<pubDate>Wed, 23 Jul 2008 21:43:24 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=54</guid>
		<description><![CDATA[ The current released WordPress Version newly introduces the feature of revision history tracking and management. It is able to displays differences across revisions visual too.
But the initial developer ignores the fact, that serveral provider doesn&#8217;t permit to use the PHP function ini_set() - in this case for temporary change of PHP include_path. Moreover those provider [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/wordpress-26-and-the-textdiff-fatal-errors/feed</wfw:commentRss>
		</item>
		<item>
		<title>WordPress error during translation file usage - the reason</title>
		<link>http://www.code-styling.de/english/wordpress-error-during-translation-file-usage-the-reason</link>
		<comments>http://www.code-styling.de/english/wordpress-error-during-translation-file-usage-the-reason#comments</comments>
		<pubDate>Mon, 21 Jul 2008 23:16:37 +0000</pubDate>
		<dc:creator>codestyling</dc:creator>
		
		<category><![CDATA[English]]></category>

		<category><![CDATA[WordPress (US)]]></category>

		<guid isPermaLink="false">http://www.code-styling.de/?p=53</guid>
		<description><![CDATA[ After long retrieval, frustrating feedbacks about the previous made temporary patch, i had already published, finally i found the reason of this ugly issue! I have installed a fresh WordPress 2.6 at my local machines XAMPP system and reproduced it successfully. Intensive research at the web showed me a lot of massive problems related to [...]]]></description>
		<wfw:commentRss>http://www.code-styling.de/english/wordpress-error-during-translation-file-usage-the-reason/feed</wfw:commentRss>
		</item>
	</channel>
</rss>
