<?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>the blog: knuts &#187; Wordpress</title>
	<atom:link href="http://blog.theknuts.com/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.theknuts.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 23 Nov 2009 01:58:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Wordpress Post Slugs and Permalinks</title>
		<link>http://blog.theknuts.com/2009/11/wordpress-post-slugs-and-permalinks/</link>
		<comments>http://blog.theknuts.com/2009/11/wordpress-post-slugs-and-permalinks/#comments</comments>
		<pubDate>Tue, 10 Nov 2009 03:59:07 +0000</pubDate>
		<dc:creator>the knuts</dc:creator>
				<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://blog.theknuts.com/?p=258</guid>
		<description><![CDATA[Wordpress Post Slugs and Permalinks by benz
A Post Slug is a permalink. Permalink stands for permanent link which points directly to a URL of a particular post. And we want the link of that particular post to be logical and easily track back. Example, if my post title is about &#8216;global warming issue&#8216;. The default permalink [...]]]></description>
			<content:encoded><![CDATA[<p>Wordpress Post Slugs and Permalinks by <em><span style="color: #993300;">benz</span></em></p>
<p>A <span style="color: #993300;">Post Slug</span> is a permalink. <span style="color: #993300;">Permalink</span> stands for permanent link which points directly to a URL of a particular post. And we want the link of that particular post to be logical and easily track back. Example, if my post title is about &#8216;<span style="color: #993300;">global warming issue</span>&#8216;. The default permalink will be &#8216;<span style="color: #993300;">http://blog.theknuts.com/?p=123</span>&#8216; and that cannot be easily identify. But we can define the post slug into &#8216;<span style="color: #993300;">http://blog.theknuts.com/global-warming-issue</span>&#8216;, which can be easily understood. Wordpress will automatically truncate the link title white spaces with (-) hyphen.</p>
<p>Wordpress self-hosted has options for defining slugs which is not available for wordpress.com. You can find them under <strong>Posts</strong>: <em>Post tags</em> and <em>Categories</em>, and under <strong>Links</strong>: <em>Link Categories</em>. You can also define Permalinks under Settings options. <strong>Setting</strong> &gt;&gt; <em>Permalinks</em></p>
<p><a style="clear:both" href="http://blog.theknuts.com/wp-content/uploads/2009/11/permalink-setting1.jpg"><img class="alignnone size-full wp-image-276" title="permalink-setting" src="http://blog.theknuts.com/wp-content/uploads/2009/11/permalink-setting1.jpg" alt="permalink-setting" width="408" height="413" /></a></p>
<p>Under common settings, I select the month and name of the post. That will depend on your preference. Hmm&#8230; I think in wordpress.com the automatic or default settings now for permalinks is with the month and name of post.</p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
]]></content:encoded>
			<wfw:commentRss>http://blog.theknuts.com/2009/11/wordpress-post-slugs-and-permalinks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>eval(base64&#8230;</title>
		<link>http://blog.theknuts.com/2009/10/evil-eval/</link>
		<comments>http://blog.theknuts.com/2009/10/evil-eval/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 12:01:26 +0000</pubDate>
		<dc:creator>the knuts</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://blog.theknuts.com/?p=94</guid>
		<description><![CDATA[I&#8217;m finding my way with wp themes to do some workaround and create my own  until I found some code embedded on some wp theme php script like this
"eval(base64_decode('Pz4gCQk...')"
I&#8217;m quite curious and suspicous about the code so I tried to look for any info in the net. And it&#8217;s just what I thought about&#8230;I learned [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m finding my way with wp themes to do some workaround and create my own  until I found some code embedded on some wp theme php script like this</p>
<pre><span style="color: #ff0000;"><em>"eval(base64_decode('Pz4gCQk...')"</em></span></pre>
<p>I&#8217;m quite curious and suspicous about the code so I tried to look for any info in the net. And it&#8217;s just what I thought about&#8230;I learned that this is an encrypted code that can be found on many wp themes. The codes are embedded can do some redirecting on another sites to increase their traffic or maybe in worsed case it  will let hackers go into your databases. Good thing the one I decode only shows a  link going to a site . hmm&#8230;</p>
<p>I found <a href="http://www.motobit.com/util/base64-decoder-encoder.asp" target="_blank">this site</a> helpful for decoding.</p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
]]></content:encoded>
			<wfw:commentRss>http://blog.theknuts.com/2009/10/evil-eval/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wordpress Self-Hosted quick guide</title>
		<link>http://blog.theknuts.com/2009/10/wordpress-self-hosted-quick-guide/</link>
		<comments>http://blog.theknuts.com/2009/10/wordpress-self-hosted-quick-guide/#comments</comments>
		<pubDate>Wed, 28 Oct 2009 13:44:14 +0000</pubDate>
		<dc:creator>the knuts</dc:creator>
				<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://blog.theknuts.com/?p=213</guid>
		<description><![CDATA[Wordpress self-hosted  quick guide by benz
1. Download the latest copy of WP (here) and EXTRACT!
2.  CREATE your DataBase. Hostings have different user interface or the control panel. In setting up your Database take note of your database name, database user name and password and the mysql host name.
3. Open the WP folder you just [...]]]></description>
			<content:encoded><![CDATA[<p>Wordpress self-hosted  quick guide <em><span style="color: #993300;">by benz</span></em></p>
<p><strong>1.</strong> Download the latest copy of WP (<a href="http://wordpress.org/download/" target="_blank">here</a>) and EXTRACT!</p>
<p><strong>2. </strong> <strong>CREATE </strong>your <strong>DataBase</strong>. Hostings have different user interface or the control panel. In setting up your Database take note of your <strong>database name</strong>, database <strong>user name</strong> and <strong>password</strong> and the <strong>mysql host name</strong>.</p>
<p><strong>3.</strong> Open the WP folder you just downloaded. Find the &#8216;<span style="color: #ff0000;">wp-config-sample.php</span>&#8216; inside wordpress folder and re-name it <strong> </strong>to &#8216;<span style="color: #ff0000;">wp-config.php</span>&#8216;.</p>
<p><strong>4.</strong> Open the file &#8216;wp-config.php&#8217; to a text editor (except word) and provide the following info.</p>
<p><a href="http://blog.theknuts.com/wp-content/uploads/2009/11/wp-config-db.gif"><img class="size-full wp-image-214 alignnone" title="wp-config-db" src="http://blog.theknuts.com/wp-content/uploads/2009/11/wp-config-db.gif" alt="wp-config-db" width="420" height="334" /></a></p>
<p>DB_CHARSET and DB_COLLATE. Just leave them as it is!</p>
<p><strong>5.</strong> <strong>Authenticate unique keys</strong> for security reasons. SCROLL down a little bit on the page (same file). And you can see this piece of code.</p>
<p><a href="http://blog.theknuts.com/wp-content/uploads/2009/11/wp-config-authkey.gif"><img class="alignnone size-full wp-image-215" title="wp-config-authkey" src="http://blog.theknuts.com/wp-content/uploads/2009/11/wp-config-authkey.gif" alt="wp-config-authkey" width="420" height="334" /></a></p>
<p>You can see commented (/* */) instructions on what to modify. You need to generate a unique key by going to this site &#8216;<span style="color: #ff0000;">https://api.wordpress.org/secret-key/1.1/</span>&#8216;. COPY THE CODE GENERATED and OVERWRITE it to the code shown above (the text with blue and red color) .</p>
<p><strong>SAVE</strong> the files!</p>
<p><strong>6.</strong> UPLOAD the wp files to your own directory(folder)  into your SERVER by ftp.</p>
<p><strong>7.</strong> Once upload complete, install WP by going to yourblogURL/wp-admin/install.php. (ex. http://blog.theknuts.com/wp-admin/install.php). If no error, you can see WP welcome page. Provide your <span style="color: #ff0000;">BLOG TITLE</span> , <span style="color: #ff0000;">E-MAIL</span> add and the checkbox &#8216;<span style="color: #ff0000;">Allow my blog to appear&#8230;</span>&#8216; (it is check by default). And click &#8220;<span style="color: #ff0000;">Install Wordpress</span>&#8220;.</p>
<p><strong>8.</strong> Installation SUCCESSFUL! Wordpress will provide you a default username and password which can be change later on in your admin settings.</p>
<p>WELCOME TO WORDPRESS!!!</p>
<p>&lt;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.theknuts.com/2009/10/wordpress-self-hosted-quick-guide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wordpress self-hosted</title>
		<link>http://blog.theknuts.com/2009/10/test/</link>
		<comments>http://blog.theknuts.com/2009/10/test/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 01:19:46 +0000</pubDate>
		<dc:creator>the knuts</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://blog.theknuts.com/?p=208</guid>
		<description><![CDATA[Though my hosting supports one-click wp install, I decided to do it manually. Yes, I&#8217;m new to wp and still finding my way with it. The first time I got this error,
&#8220;Parse error: syntax error, unexpected $end in /home/.wysiwyg/theknuts/blog.theknuts.com/wp-admin/includes/template.php on line 2033&#8243;
Yeah right, welcome me wordpress. Template.php probably has some issues. I tried to google [...]]]></description>
			<content:encoded><![CDATA[<p>Though my hosting supports one-click wp install, I decided to do it manually. Yes, I&#8217;m new to wp and still finding my way with it. The first time I got this error,</p>
<p><span style="color: #ff0000;">&#8220;Parse error: syntax error, unexpected $end in /home/.wysiwyg/theknuts/blog.theknuts.com/wp-admin/includes/template.php on line 2033&#8243;</span></p>
<p><span style="color: #ff0000;"><span style="color: #000000;">Yeah right, welcome me wordpress. Template.php probably has some issues. I tried to google for possible answers, parse error  is very common in wp I think, but can&#8217;t find an exact scenario. I might have made some mistakes during my first installation, so will try to install it the second time, but to my local server first for testing . I downloaded the tar file version of wp instead of the zip version which I used during my first installaltion. After going through the same process again. It worked!  hmm..</span><br />
</span></p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
]]></content:encoded>
			<wfw:commentRss>http://blog.theknuts.com/2009/10/test/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
