<?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>Blog Cube</title>
	<atom:link href="http://www.blogcube.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogcube.org</link>
	<description>just another wordpress blog!</description>
	<lastBuildDate>Wed, 27 Apr 2011 03:40:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Joomla1.6.3都出来了</title>
		<link>http://www.blogcube.org/web/joomla1-6-3%e9%83%bd%e5%87%ba%e6%9d%a5%e4%ba%86/</link>
		<comments>http://www.blogcube.org/web/joomla1-6-3%e9%83%bd%e5%87%ba%e6%9d%a5%e4%ba%86/#comments</comments>
		<pubDate>Wed, 27 Apr 2011 03:40:42 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Joomla]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=83</guid>
		<description><![CDATA[4月14号发布的1.6.2，而4月18号发布的1.6.3。 真不知道应该说Joomla团队勤奋好呢，还是业余好？ 其中在1.6.2中，共修复了8个安全问题，115个bug， 而1.6.3中，修复了4个bug。 看来软件没有认真测试就发布正式版，真是找罪受；不知道Joomla是否受到了教训？ 也不知道有多少用Joomla1.6.x建的站遭被黑。 相比较之下，Drupal就踏实多了，到目前为止，7.0还没有发布新版本，当然前提是Drupal在发布正式版前认真仔细的测试，和众多Beta和RC版本。 记得当时用Drupal的RC版本的时候，都感觉比现在的Joomla1.6.3要稳定的多。 个人感觉，Joomla还要经过2个版本之后，才能正式建站。 不知道Joomla1.6的发布是否会成为Joomla的滑铁卢？]]></description>
		<wfw:commentRss>http://www.blogcube.org/web/joomla1-6-3%e9%83%bd%e5%87%ba%e6%9d%a5%e4%ba%86/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Joomla1.6.1发布</title>
		<link>http://www.blogcube.org/joomla/joomla1-6-1%e5%8f%91%e5%b8%83/</link>
		<comments>http://www.blogcube.org/joomla/joomla1-6-1%e5%8f%91%e5%b8%83/#comments</comments>
		<pubDate>Tue, 15 Mar 2011 03:06:34 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Joomla]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[Drupal]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=80</guid>
		<description><![CDATA[经过近2个月的时间，Joomla发布了1.6.1版本；这两个月把Joomla Team忙坏了，竟然修复了12个安全问题和206个Bug。 看来上次Joomla的发布的确是在Drupal 7的压力下发布的，根本不具备产品成熟的条件啊。 这次的发布不知道情况怎么样，估计会比Joomla1.6安全不少，但是仍旧认为不具备Production的条件，再等待一个版本再上吧。 不过Joomla1.6的改进还是非常值得称赞的！]]></description>
		<wfw:commentRss>http://www.blogcube.org/joomla/joomla1-6-1%e5%8f%91%e5%b8%83/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>搞不懂Joomla1.6为什么发布</title>
		<link>http://www.blogcube.org/joomla/about-joomla16-publish/</link>
		<comments>http://www.blogcube.org/joomla/about-joomla16-publish/#comments</comments>
		<pubDate>Thu, 27 Jan 2011 17:27:25 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Joomla]]></category>
		<category><![CDATA[Drupal]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=72</guid>
		<description><![CDATA[最近一直在学习Drupal，对于我这个用习惯Joomla的人来说，Drupal学习起来还是比较吃力的。 对比Joomla和Drupal的代码，不难发现Drupal更专业一些；包括这次Drupal 7的发布，都非常严谨； 而Joomla1.6的发布流程简直让人不可以理解，发布了2个Alpha，然后就急着发布Beta版本， Beta一发就是15个，等Beta发布完后，只发了一个RC版本，就到正式版了。 发2个Alpha版本，急着发布Beta版本，估计是为了让大家一起帮忙测试， 而一直法律15个Beta版本，说明内部测试很不过关(Alpha)。 只发布一个RC版本，就发布正式版，是因为Drupal 7已经发布了，为了抢占市场。 然而，此时的Joomla1.6已经成熟了吗？ 估计像Alpha到Beta那样，测试还是非常不够的。 现在Joomla1.6的文档都没有（Drupal7将文档的完全作为正式发布的必要条件），程序的安全隐患更不知道有多少？ Joomla1.6是做了许多有有益的改善，然而如此忙不迭的发布版本，有没有考虑到用户的体验和用户的损失？ 建议Joomla用户继续用Joomla1.5的版本，至少等Joomla发布3个正式版后，才敢真正用来上线。]]></description>
		<wfw:commentRss>http://www.blogcube.org/joomla/about-joomla16-publish/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SyntaxHighlighterPro document</title>
		<link>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro-document/</link>
		<comments>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro-document/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 06:29:39 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Syntax Highlighter]]></category>
		<category><![CDATA[document]]></category>
		<category><![CDATA[wordpress plugin]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=44</guid>
		<description><![CDATA[It is quite easy to use the wordpress plugin SyntaxHighlighterPro. You need just activate the plugin, and then assign the brush to the pre tag. For example: &#60;pre class="brush:java"&#62; public class HelloWorld{ public static void main(String [] args) { System.out.println("Hello world!"); } } &#60;/pre&#62; Then it will render the code as following: public class HelloWorld{ [...]]]></description>
		<wfw:commentRss>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro-document/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>SyntaxHighlighterPro demo</title>
		<link>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro-demo/</link>
		<comments>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro-demo/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 06:03:11 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Syntax Highlighter]]></category>
		<category><![CDATA[demo]]></category>
		<category><![CDATA[wordpress plugin]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=37</guid>
		<description><![CDATA[C Example: #include main() { printf ("Hello World!\n"); } Java Example: public class HelloWorld{ public static void main(String [] args) { System.out.println("Hello world!"); } } XML Example: Tove Jani Reminder Don't forget me this weekend!]]></description>
		<wfw:commentRss>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro-demo/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SyntaxHighlighterPro</title>
		<link>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro/</link>
		<comments>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 05:05:49 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Syntax Highlighter]]></category>
		<category><![CDATA[code highlighter]]></category>
		<category><![CDATA[wordpress plugin]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=34</guid>
		<description><![CDATA[SyntaxHighlighterPro is a wordpress plugin which uses the SyntaxHighlighter to highlight code snippets. Major features: Support up to 24 languages, including Java,C++,C#,Php,JavaScript,Groovy,Ruby,Python,Perl,XML,SQL etc. Support up to 5 theme styles, that are Default,Django,Eclipse,Emacs,FadeToGrey,Midnight,RDark. You can easily change the theme in plugin settings. Allow you to choose what languages will support, which is great to avoid unnecessary [...]]]></description>
		<wfw:commentRss>http://www.blogcube.org/wordpress-plugins/syntax-highlighter/syntaxhighlighterpro/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>prevent people from using the addon domain as a subdomain of your primary domain.</title>
		<link>http://www.blogcube.org/web/prevent-using-addon-domain-as-a-subdomain-of-primary-domain/</link>
		<comments>http://www.blogcube.org/web/prevent-using-addon-domain-as-a-subdomain-of-primary-domain/#comments</comments>
		<pubDate>Wed, 23 Sep 2009 03:39:21 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[mod_rewrite]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=29</guid>
		<description><![CDATA[To prevent people from using the addon domain as a subdomain of your primary domain, just put the following code into the .htaccess file located at the subdomains folder RewriteEngine On RewriteCond %{HTTP_HOST} ^subdomain.primarydomain.com$ [OR] RewriteCond %{HTTP_HOST} ^www.subdomain.primarydomain.com$ [OR] RewriteCond %{HTTP_HOST} ^addondomain.com$ RewriteCond %{REQUEST_URI} ^/$ RewriteRule ^(.*)$ http://www.addondomain.com/ [R=301,L]]]></description>
		<wfw:commentRss>http://www.blogcube.org/web/prevent-using-addon-domain-as-a-subdomain-of-primary-domain/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Add an Expires Header to static components with mod_expires</title>
		<link>http://www.blogcube.org/web/add-an-expires-header-to-static-components-with-mod_expires/</link>
		<comments>http://www.blogcube.org/web/add-an-expires-header-to-static-components-with-mod_expires/#comments</comments>
		<pubDate>Mon, 17 Aug 2009 03:06:26 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[expires header]]></category>
		<category><![CDATA[mod_expires]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=19</guid>
		<description><![CDATA[According to Yahoo&#8217;s Best Practices for Speeding Up Your Web Site, adding an expires header to static components can improve web site&#8217;s performance greatly. Here is the simplest way to add expires header. Open .htaccess file, and append the code. &#60;IfModule mod_expires.c&#62; &#60;FilesMatch "\.(ico&#124;gif&#124;jpg&#124;JPG&#124;jpeg&#124;png&#124;swf&#124;css&#124;js&#124;html?&#124;xml&#124;txt)$"&#62; ExpiresActive On ExpiresDefault "access plus 1 years" &#60;/FilesMatch&#62; &#60;/IfModule&#62; More details [...]]]></description>
		<wfw:commentRss>http://www.blogcube.org/web/add-an-expires-header-to-static-components-with-mod_expires/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Autolinks Document</title>
		<link>http://www.blogcube.org/wordpress-plugins/images-autolinks/autolinks-document/</link>
		<comments>http://www.blogcube.org/wordpress-plugins/images-autolinks/autolinks-document/#comments</comments>
		<pubDate>Sun, 16 Aug 2009 13:49:52 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Images AutoLinks]]></category>
		<category><![CDATA[autolinks]]></category>
		<category><![CDATA[document]]></category>
		<category><![CDATA[wordpress plugin]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=11</guid>
		<description><![CDATA[Autolinks is quite easy to use. Just enable the plugin, and you can use it with the default settings. Of cause, you can set up the setting by yourself. Go to /wp-admin/options-general.php?page=wp-autolinks.php and you will find the following set up page. By now, there are three setting items. Images title prefix: When images are lack [...]]]></description>
		<wfw:commentRss>http://www.blogcube.org/wordpress-plugins/images-autolinks/autolinks-document/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Autolinks</title>
		<link>http://www.blogcube.org/wordpress-plugins/images-autolinks/autolinks/</link>
		<comments>http://www.blogcube.org/wordpress-plugins/images-autolinks/autolinks/#comments</comments>
		<pubDate>Sun, 16 Aug 2009 03:26:08 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Images AutoLinks]]></category>
		<category><![CDATA[autolinks]]></category>
		<category><![CDATA[download]]></category>
		<category><![CDATA[wordpress plugin]]></category>

		<guid isPermaLink="false">http://www.blogcube.org/?p=3</guid>
		<description><![CDATA[Autolinks is a very smart wordpress plugin, it automatically generate a hyper links for images of the post summary. For category list,search result etc, if topic summary have images, autolinks will generate hyper links for these images, these hyper links will link to the topic&#8217;s full text. Additionally, Autolinks can also automatically generate title and [...]]]></description>
		<wfw:commentRss>http://www.blogcube.org/wordpress-plugins/images-autolinks/autolinks/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

