<?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>Stone Studio&#187; WordPress Archives</title>
	<atom:link href="http://wei-jiang.com/tag/wordpress-links/feed" rel="self" type="application/rss+xml" />
	<link>http://wei-jiang.com</link>
	<description></description>
	<lastBuildDate>Wed, 28 Apr 2010 08:35:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WordPress Text Flow vs. Markdown</title>
		<link>http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown</link>
		<comments>http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown#comments</comments>
		<pubDate>Sun, 07 Feb 2010 12:00:50 +0000</pubDate>
		<dc:creator>Wei Jiang</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[Web & Internet]]></category>
		<category><![CDATA[markdown]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown</guid>
		<description><![CDATA[Michel Fortin reviewed his analysis in how to make PHP Markdown works with WordPress. 
It works since a year now, but there have always been many glitches. All this relates to the text flow model WordPress has adopted, which is very powerful but badly adapted to a writing syntax different from HTML. To work correctly, [...]]]></description>
		<wfw:commentRss>http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Fatal error: Allowed memory size of 16777216 bytes exhausted</title>
		<link>http://wei-jiang.com/it/web-technology/wordpress-fatal-error-allowed-memory-size-of-16777216-bytes-exhausted</link>
		<comments>http://wei-jiang.com/it/web-technology/wordpress-fatal-error-allowed-memory-size-of-16777216-bytes-exhausted#comments</comments>
		<pubDate>Mon, 18 Jan 2010 23:53:27 +0000</pubDate>
		<dc:creator>Wei Jiang</dc:creator>
				<category><![CDATA[Web & Internet]]></category>
		<category><![CDATA[TroubleShooting]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://wei-jiang.com/it/web-technology/wordpress-fatal-error-allowed-memory-size-of-16777216-bytes-exhausted</guid>
		<description><![CDATA[I received a message like this
&#34;Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 30720 bytes) in /usr/home/web/web276672/lan/wp-admin/includes/template.php on line 3186&#34; 
This is how I solved it (dirty quick solution).
 
It&#8217;s likely not a problem with your database, but rather a need for more PHP memory. Methods for increasing the amount of [...]]]></description>
		<wfw:commentRss>http://wei-jiang.com/it/web-technology/wordpress-fatal-error-allowed-memory-size-of-16777216-bytes-exhausted/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
