<?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>OMB.C</title>
	<atom:link href="http://www.ombing.com/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ombing.com</link>
	<description>My 2 packs worth...</description>
	<lastBuildDate>Mon, 17 Oct 2011 01:09:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>How to create a WordPress Widget</title>
		<link>http://www.ombing.com/php/how-to-create-wordpress-widget</link>
		<comments>http://www.ombing.com/php/how-to-create-wordpress-widget#comments</comments>
		<pubDate>Wed, 12 Oct 2011 08:22:18 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://localhost/?p=177</guid>
		<description><![CDATA[To create a wordpress widget is tantamount on saying that you would want to create a wordpress plugin. There would be differences though, but it goes without saying that you should learn how to create a plugin first. I have covered the basics of that here in my tutorial series How to create WordPress plugins [...]]]></description>
			<content:encoded><![CDATA[<p>To create a wordpress widget is tantamount on saying that you would want to create a wordpress plugin. <span id="more-177"></span>There would be differences though, but it goes without saying that you should learn how to create a plugin first.</p>
<p>I have covered the basics of that here in my tutorial series <a href="http://localhost/wordpress/how-to-create-wordpress-plugins">How to create WordPress plugins</a></p>
<p>so lets get going with the widget&#8230;</p>
<p>after you have created the file for your plugin/widget and the necessary details for it to be activated, add the following code&#8230;</p>
<p><span style="color: #0000ff;">function widget_content(){</span><br />
<span style="color: #0000ff;"> $sdstr = &#8220;this is where your widget code goes.&#8221;;</span><br />
<span style="color: #0000ff;"> return $sdstr;</span><br />
<span style="color: #0000ff;"> }</span></p>
<p><span style="color: #0000ff;">function cc_widget($args) {</span><br />
<span style="color: #0000ff;"> extract($args);</span><br />
<span style="color: #0000ff;"> echo $before_widget;</span><br />
<span style="color: #0000ff;"> echo $before_title;</span><br />
<span style="color: #0000ff;"> echo &#8220;YOUR WIDGET TITLE&#8221;;</span><br />
<span style="color: #0000ff;"> echo $after_title;</span><br />
<span style="color: #0000ff;"> echo widget_content();</span><br />
<span style="color: #0000ff;"> echo $after_widget;</span><br />
<span style="color: #0000ff;"> }</span></p>
<p><span style="color: #0000ff;">function cc_widget_init()</span><br />
<span style="color: #0000ff;"> {</span><br />
<span style="color: #0000ff;"> register_sidebar_widget(__(&#8216;YOUR WIDGET NAME&#8217;), &#8216;cc_widget&#8217;);</span><br />
<span style="color: #0000ff;"> }</span></p>
<p><span style="color: #0000ff;">add_action(&#8220;plugins_loaded&#8221;, &#8220;cc_widget_init&#8221;);</span></p>
<p>activate your plugin/widget and add it to your sidebar throught the admin dashboard-&gt;appearance-&gt;widgets then of you go&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/php/how-to-create-wordpress-widget/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hawud Currency Converter Widget</title>
		<link>http://www.ombing.com/hawud-wordpress-plugins/hawud-currency-converter-widget</link>
		<comments>http://www.ombing.com/hawud-wordpress-plugins/hawud-currency-converter-widget#comments</comments>
		<pubDate>Sun, 09 Oct 2011 19:09:06 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[Hawud Wordpress Plugins]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://localhost/?p=130</guid>
		<description><![CDATA[<img src="http://www.ombing.com/wp-content/uploads/2011/10/hcc-screenshot.jpg" alt="" width="336" height="228" />The Hawud Currency converter widget is a good widget to add if you have an online shop on your wordpress website. This will help your international clients decide on their purchase as they will be able to check how much it would cost them on their local currency. The widget utilizes jquery for loading up [...]]]></description>
			<content:encoded><![CDATA[<img src="http://www.ombing.com/wp-content/uploads/2011/10/hcc-screenshot.jpg" alt="" width="336" height="228" /><p>The Hawud Currency converter widget is a good widget to add if you have an online shop on your wordpress website. This will help your international clients decide on their purchase as they will be able to check how much it would cost them on their local currency.<span id="more-130"></span></p>
<p>The widget utilizes jquery for loading up the results so your users will not be redirected to another page/ have their page reloaded. This is for the ease of using the widget while browsing your products.</p>
<p>Check on the sidebar of this page to view a live demo of the widget.</p>
<p><strong>INSTALLATION</strong></p>
<p>1. Download the package. click <a href="http://www.ombing.com/wp-content/uploads/2011/10/currency-converter-widget.zip">here</a>.</p>
<p>2. login to your wordpress admin dashboard.</p>
<p>3. go to Plugins-&gt;Add New</p>
<p>4. on the Install Plugins page select &#8220;upload&#8221;. then browse for the currency converter widget package and click &#8220;Install&#8221;. Let wordpress do its thing and then click &#8220;Activate&#8221;</p>
<p><strong>To show the widget on your sidebar</strong></p>
<p>5.  go to Appearance-&gt;Widgets.</p>
<p>6. the widget will already be listed on the available widget and you could now click &#8220;Add&#8221; to add the widget to the sidebar(or others depending on your site&#8217;s theme) of your site.</p>
<p><strong>Developer&#8217;s Notes:</strong></p>
<p>-  This is my first version of the plugin/widget.</p>
<p>-  I plan on extending the code to have a shortcode if in anycase you would want to show the converter form on the content area.</p>
<p>-  You are very much welcome to suggest enhancements to the features of the widget.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/hawud-wordpress-plugins/hawud-currency-converter-widget/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to create WordPress plugins Part 3: Creating Admin Options</title>
		<link>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-3-creating-admin-options</link>
		<comments>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-3-creating-admin-options#comments</comments>
		<pubDate>Wed, 21 Sep 2011 08:18:09 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[MySql]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=93</guid>
		<description><![CDATA[we are almost done with our tutorial series How to create WordPress plugins.]]></description>
			<content:encoded><![CDATA[<p>we are almost done with our tutorial series <a href="http://localhost/wordpress/how-to-create-wordpress-plugins">How to create WordPress plugins</a>.<span id="more-93"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-3-creating-admin-options/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to create WordPress plugins Part 2: Working with data and Forms</title>
		<link>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-2-working-with-data-and-forms</link>
		<comments>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-2-working-with-data-and-forms#comments</comments>
		<pubDate>Wed, 21 Sep 2011 08:14:50 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[MySql]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=91</guid>
		<description><![CDATA[This is part 2 of my tutorial series on How to create WordPress plugins. first let us create our database table. this will be the table holding the data that will be saved from the form that we will be creating. execute the following Mysql command on your wordpress database to create the table. CREATE [...]]]></description>
			<content:encoded><![CDATA[<p>This is part 2 of my tutorial series on <a href="http://localhost/wordpress/how-to-create-wordpress-plugins">How to create WordPress plugins</a>.<span id="more-91"></span></p>
<p>first let us create our database table. this will be the table holding the data that will be saved from the form that we will be creating.</p>
<p>execute the following Mysql command on your wordpress database to create the table.</p>
<p><span style="color: #0000ff;">CREATE TABLE IF NOT EXISTS `wp_contactf` (</span><br />
<span style="color: #0000ff;">  `contactid` bigint(10) NOT NULL AUTO_INCREMENT,</span><br />
<span style="color: #0000ff;">  `c_name` char(40) NOT NULL,</span><br />
<span style="color: #0000ff;">  `c_email` varchar(40) NOT NULL,</span><br />
<span style="color: #0000ff;">  `c_message` text NOT NULL,</span><br />
<span style="color: #0000ff;">  PRIMARY KEY (`contactid`)</span><br />
<span style="color: #0000ff;">) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;</span></p>
<p>take note that the prefix wp_ on the table name wp_contactf may vary depending on your wordpress installation. apply the prefix accordingly.</p>
<p>after the database table creation, create a directory on your <span style="color: #0000ff;">wp-content/plugins</span> named <span style="color: #0000ff;">contactform</span> and inside it <span style="color: #0000ff;">contactform.php</span></p>
<p>on your <span style="color: #0000ff;">contactform.php</span> put in this code as our starter file.</p>
<p><span style="color: #0000ff;">&lt;?php</span><br />
<span style="color: #0000ff;">/*</span><br />
<span style="color: #0000ff;">Plugin Name: Sample contactform</span><br />
<span style="color: #0000ff;">Plugin URI: http://www.ombing.com</span><br />
<span style="color: #0000ff;">Description: sample of a simple contact form</span><br />
<span style="color: #0000ff;">Author: your name</span><br />
<span style="color: #0000ff;">Version: 1.0</span><br />
<span style="color: #0000ff;">Author URI: http://www.ombing.com/</span><br />
<span style="color: #0000ff;">*/</span></p>
<p><span style="color: #0000ff;">function contactform($content=&#8221;){</span></p>
<p><span style="color: #0000ff;">}</span></p>
<p><span style="color: #0000ff;">add_filter(&#8216;the_content&#8217;, &#8216;contactform&#8217;);</span></p>
<p><span style="color: #0000ff;">?&gt;</span></p>
<p>let us assign a short code for showing the contact form. &#8220;show_contact_form&#8221;.</p>
<p>and modify the contactform function as follows:</p>
<p><span style="color: #0000ff;">function contactform($content=&#8221;){</span><br />
<span style="color: #0000ff;">     $shortcode=&#8221;show_contact_form&#8221;;</span></p>
<p><span style="color: #0000ff;">     if(!preg_match(&#8216;|['.$shortcode.']|&#8217;, $content)) {   </span><br />
<span style="color: #0000ff;">           return $content;</span><br />
<span style="color: #0000ff;">     }#preg_match</span></p>
<p><span style="color: #0000ff;">     $sdstr = &#8220;&#8221;;</span><br />
<span style="color: #0000ff;">     if(strstr($content, &#8220;[".$shortcode."]&#8220;)) {</span><br />
<span style="color: #0000ff;">           $sdstr .= ccf_show_contactform();</span><br />
<span style="color: #0000ff;">           $content = str_replace(&#8216;['.$shortcode.']&#8216;, $sdstr, $content); </span><br />
<span style="color: #0000ff;">     }#if shortcode</span></p>
<p><span style="color: #0000ff;">     return $content;  </span><br />
<span style="color: #0000ff;">}#contact form</span></p>
<p>what we did here was we specified a shortcode to show our form &#8220;show_contact_form&#8221; and if that shortcode exists on the content call up a function ccf_show_contactform() with the following line:</p>
<p><span style="color: #0000ff;">$sdstr .= ccf_show_contactform();</span></p>
<p>needless to say lets create that function&#8230; and put in an html code to show the form.</p>
<p><span style="color: #0000ff;">function ccf_show_contactform(){</span><br />
<span style="color: #0000ff;"> $sdstr =&#8217; </span><br />
<span style="color: #0000ff;">    &lt;form cellpadding=&#8221;2&#8243; cellspacing=&#8221;2&#8243; method=&#8221;post&#8221;&gt;</span><br />
<span style="color: #0000ff;">    &lt;p&gt;</span><br />
<span style="color: #0000ff;">    &lt;label Name:&lt;/label&gt;&lt;BR&gt;</span><br />
<span style="color: #0000ff;">    &lt;input type=&#8221;text&#8221; name=&#8221;c_name&#8221; id=&#8221;c_name&#8221; size=40&gt;    &lt;/p&gt;</span></p>
<p><span style="color: #0000ff;">    &lt;p&gt;</span><br />
<span style="color: #0000ff;">    &lt;label&gt;Email:&lt;/label&gt;&lt;BR&gt;</span><br />
<span style="color: #0000ff;">    &lt;input type=&#8221;text&#8221; name=&#8221;c_email&#8221; id=&#8221;c_email&#8221; size=40&gt;   &lt;/p&gt;</span><br />
<span style="color: #0000ff;">    &lt;p&gt;</span><br />
<span style="color: #0000ff;">    &lt;label&gt;Message:&lt;/label&gt;&lt;BR&gt;</span><br />
<span style="color: #0000ff;">    &lt;textarea name=&#8221;c_message&#8221; id=&#8221;c_message&#8221; cols=40 style=&#8221;vertical-scroll=yes;&#8221;&gt;&lt;/textarea&gt;    &lt;/p&gt;</span></p>
<p><span style="color: #0000ff;">    &lt;p&gt;</span><br />
<span style="color: #0000ff;">    &lt;input type=&#8221;hidden&#8221; name=&#8221;isposted&#8221; id=&#8221;isposted&#8221; value=&#8221;1&#8243;&gt;</span><br />
<span style="color: #0000ff;">    &lt;input type=&#8221;submit&#8221; name=&#8221;submit&#8221; id=&#8221;submit&#8221; value=&#8221;Save Message&#8221;&gt;     &lt;/p&gt;</span></p>
<p><span style="color: #0000ff;">    &lt;/form&gt;</span><br />
<span style="color: #0000ff;">    &#8217;;</span><br />
<span style="color: #0000ff;">    return $sdstr; </span></p>
<p><span style="color: #0000ff;">}#function ccf_show_contactform</span></p>
<p>now, have your plugin activated and add the [show_contact_form] shortcode. on one of your pages then navigate to that page to view what we have done so far.</p>
<p>now let us work on the function that would be saving our form data to the database. let us create a function named ccf_save_data();</p>
<p><span style="color: #0000ff;">function ccf_save_data($postdata){</span><br />
<span style="color: #0000ff;">    $sdstr = &#8220;&#8221;;</span><br />
<span style="color: #0000ff;">    global $wpdb;</span><br />
<span style="color: #0000ff;">    $tblname=$wpdb-&gt;prefix.&#8221;contactf&#8221;;</span><br />
<span style="color: #0000ff;">    $rows_affected = $wpdb-&gt;insert( $tblname, array( &#8216;c_name&#8217; =&gt; $post['c_name'], &#8216;c_email&#8217; =&gt; $post['c_email'], &#8216;c_message&#8217; =&gt; $post['c_message']);</span><br />
<span style="color: #0000ff;">    if($rows_affected &gt; 0){</span><br />
<span style="color: #0000ff;">        $sdstr .= &#8220;Your message was successfully recorded.&#8221;;     </span><br />
<span style="color: #0000ff;">    }#rows affected</span><br />
<span style="color: #0000ff;">    return $sdstr;</span><br />
<span style="color: #0000ff;"> }#function ccf_save_data</span></p>
<p>$wpdb is the global wordpress database class that handles the interface between the site and its database.. to read more about it click <a href="http://codex.wordpress.org/Class_Reference/wpdb">here</a>.</p>
<p>and add the following code on our contactform function below the <span style="color: #0000ff;">$sdstr .= ccf_show_contactform();</span> line.</p>
<p><span style="color: #0000ff;">       if(isset($_POST["isposted"]) &amp;&amp; $_POST["isposted"]==1){</span><br />
<span style="color: #0000ff;">             $sdstr .= ccf_save_data($_POST);</span><br />
<span style="color: #0000ff;">        }</span></p>
<p>test out your code. you would be able to have your data saved now to your database. To check your data use whatever mysql client(like phpmyadmin) that you like.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-2-working-with-data-and-forms/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to create WordPress plugins Part 1: Hello World</title>
		<link>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-1-hello-world</link>
		<comments>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-1-hello-world#comments</comments>
		<pubDate>Wed, 21 Sep 2011 08:12:17 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=88</guid>
		<description><![CDATA[WordPress is the leading blogging platform used on websites. The main factor that contributed to this is the fact that WordPress is fairly simple to use. Its installation is straightforward enough that almost anybody could do it. I do not think anyone could actually get lost on its admin dashboard cause that is also relatively [...]]]></description>
			<content:encoded><![CDATA[<p>WordPress is the leading blogging platform used on websites. The main factor that contributed to this is the fact that WordPress is fairly simple to use. Its installation is straightforward enough that almost anybody could do it.</p>
<p>I do not think anyone could actually get lost on its admin dashboard cause that is also relatively simple.</p>
<p>Creating plugins for wordpress is also simple. That fact contributes greatly on the very rich library on <a href="http://wordpress.org/extend/plugins/">wordpress plugins</a>.</p>
<p>So, without complicating things, lets start creating our &#8220;Hello World&#8221; plugin.<span id="more-88"></span></p>
<p>First, you should have installed your wordpress on your localhost or your server. for a guide on how to install wordpress click <a href="http://codex.wordpress.org/Installing_WordPress">here</a>.</p>
<p>if you have not yet noticed, plugins installed are located on <span style="color: #0000ff;"><em>wp-content/plugins</em></span></p>
<p>though it is not necessary to put your plugin code file into a directory, it goes with out saying that it is recommended to do so.</p>
<p>so go on and create a directory under the <span style="color: #0000ff;">wp-content/plugins</span> and name it as <span style="color: #0000ff;">hello_world</span></p>
<p>then lets create a php file on our <span style="color: #0000ff;">hello_world</span> directory and name it <span style="color: #0000ff;">helloworld.php</span></p>
<p>so, you will now have <span style="color: #0000ff;">wp-content/plugins/hello_world/helloworld.php</span></p>
<p>open up your helloworld.php using your preferred editor and insert the text below.</p>
<p><em><span style="color: #0000ff;">&lt;?php</span></em></p>
<p><em><span style="color: #0000ff;">/*</span></em><br />
<em> <span style="color: #0000ff;">Plugin Name: Hello World</span></em><br />
<em> <span style="color: #0000ff;">Plugin URI: http://www.ombing.com/hello-world</span></em><br />
<em> <span style="color: #0000ff;">Description: My Hello World Plugin</span></em><br />
<em> <span style="color: #0000ff;">Author: Norbert Christian L. Feria</span></em><br />
<em> <span style="color: #0000ff;">Version: 1.0</span></em><br />
<em> <span style="color: #0000ff;">Author URI: http://www.ombing.com</span></em><br />
<em> <span style="color: #0000ff;">*/</span></em></p>
<p><em><span style="color: #0000ff;">?&gt;</span></em></p>
<p>&nbsp;</p>
<p>of course, you could change the values of their but maintain the fields.</p>
<p>right after that, we will create a function that will serve as the main function to handle our plugin on the front-end.</p>
<p><span style="color: #0000ff;">&lt;?php</span></p>
<p><span style="color: #0000ff;">function helloworld(content=&#8221;){ </span></p>
<p><span style="color: #0000ff;"> $shortcode=&#8221;show_helloworld&#8221;;</span></p>
<p><span style="color: #0000ff;">if(!preg_match(&#8216;|['.$shortcode.']|&#8217;, $content)){</span></p>
<p><span style="color: #0000ff;">return content;</span></p>
<p><span style="color: #0000ff;">}#if not preg_match</span></p>
<p><span style="color: #0000ff;">if(strstr($content, &#8220;[".$shortcode."]&#8220;)) {</span></p>
<p><span style="color: #0000ff;">$content =  &#8220;hello world!&#8221;;</span></p>
<p><span style="color: #0000ff;">return $content;</span></p>
<p><span style="color: #0000ff;">}#if strstr</span></p>
<p><span style="color: #0000ff;">}#function</span></p>
<p><span style="color: #0000ff;">?&gt;</span></p>
<p>what just happened!?! well, we created a function that would identify if our predefined shortcode is in the content.. and if so, then we will show the &#8220;hello world!&#8221; on the content.</p>
<p>so we have the plugin file, and we have the function to handle it.. but when and how will wordpress know when to use the plugin?</p>
<p>for that we need to use actions or filters&#8230; in a nutshell, these are called by wordpress whenever there are activity on the site&#8230;</p>
<p>so, let us add the code below right after the function</p>
<p><span style="color: #0000ff;">&lt;?php</span></p>
<p><span style="color: #0000ff;">add_filter(&#8216;the_content&#8217;, &#8216;helloworld&#8217;);</span></p>
<p><span style="color: #0000ff;">?&gt;</span></p>
<p>there you go, your helloworld.php is done and your plugin is ready&#8230; but before that let us first activate the plugin.. go to your wordpress admin dashboard and click on plugins-&gt;installed plugins look for the hello world plugin and click &#8220;Activate&#8221; right below the plugin name.</p>
<p>now that our plugin is activated, create a post or a page and on the content textarea put in the shortcode that we have specified <span style="color: #0000ff;">[show_helloworld]</span> then your done. congratulations.. when you navigate to the page or post that you have created the hello world! text will show up.</p>
<p><a title="How to create WordPress plugins Part 2: Working with data and Forms" href="http://www.ombing.com/php/how-to-create-wordpress-plugins-part-2-working-with-data-and-forms">How to create WordPress plugins Part 2: Working with data and Forms</a></p>
<p><a title="How to create WordPress plugins Part 3: Creating Admin Options" href="http://www.ombing.com/php/how-to-create-wordpress-plugins-part-3-creating-admin-options">How to create WordPress plugins Part 3: Creating Admin Options</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/php/how-to-create-wordpress-plugins-part-1-hello-world/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Timthumb Vulnerability for Possible Server exploit</title>
		<link>http://www.ombing.com/php/timthumb-vulnerability-for-possible-server-exploit</link>
		<comments>http://www.ombing.com/php/timthumb-vulnerability-for-possible-server-exploit#comments</comments>
		<pubDate>Sun, 18 Sep 2011 10:36:20 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Vulnerabilities]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=42</guid>
		<description><![CDATA[<img src="http://www.ombing.com/wp-content/uploads/2011/09/vulnerability-485x302.jpg" alt="" width="485" height="302" />The other day I was installing a theme for one of our wordpress sites and I got the following email from our host &#8230;. &#8221; Dear customer, This is a courtesy notice that we have found and corrected exploitable timthumb.php file(s) on your _____.com account, which are listed below. While we have corrected these files, [...]]]></description>
			<content:encoded><![CDATA[<img src="http://www.ombing.com/wp-content/uploads/2011/09/vulnerability-485x302.jpg" alt="" width="485" height="302" /><p>The other day I was installing a theme for one of our wordpress sites and I got the following email from our host &#8230;.<span id="more-42"></span></p>
<blockquote><p>&#8221;<br />
Dear customer,</p>
<p>This is a courtesy notice that we have found and corrected exploitable timthumb.php file(s) on your _____.com account, which are listed below. While we have corrected these files, we do recommend you ensure all potential exploits are corrected on your account. This is best done by updating all scripts, plugins, modules and themes on your account to the latest version&#8230;&#8230;.</p>
<p>The timthumb.php file is a script commonly used in WordPress&#8217;s (and other software&#8217;s) themes and plugins to resize images. The exploit allows an attacker to arbitrarily upload and create files and/or folders on your account, which can then be used for a number of malicious tasks, including but not limited to defacement, browser high-jacking and infection, data harvesting and more. After a site has been exploited, it may lead to becoming labeled a &#8220;Malicious Website&#8221; by Google or other security authorities.<strong>Any timthumb.php file below version 1.35, but above version 1.09 is considered vulnerable, unless patched. To prevent being compromised, we advise you update all instances of timthumb.php to version 2.0, or patch the existing vulnerable files</strong>. Note that patching the files requires more in-depth knowledge of the PHP scripting language.</p>
<p>The updated version of timthumb.php can be found here:</p>
<p><a href="http://timthumb.googlecode.com/svn/trunk/timthumb.php">http://timthumb.googlecode.com/svn/trunk/timthumb.php</a></p>
<p>Additional information regarding the compromise can be found at the following two websites, as well as others; &#8230;.</p>
<p><a href="http://markmaunder.com/2011/08/01/zero-day-vulnerability-in-many-wordpress-themes/">http://markmaunder.com/2011/08/01/zero-day-vulnerability-in-many-wordpress-themes/</a></p>
<p><a href="http://redleg-redleg.blogspot.com/2011/08/malware-hosted-newportalsecom.html">http://redleg-redleg.blogspot.com/2011/08/malware-hosted-newportalsecom.html</a><br />
&#8220;</p></blockquote>
<p>You actually just have to update your timthumb.php file by replacing it with the one from the link provided above</p>
<p>This must have been an old vulnerability but for those who have downloaded WordPress themes that were using the problematic version, then this article could most certainly help them with their security as did mine.</p>
<p>timthumb.php script is a very great php script and I like using it. Used it to most sites(if not all) I helped create. For more detailed information about the script visit the project&#8217;s website at</p>
<p><a href="http://www.binarymoon.co.uk/projects/timthumb/">http://www.binarymoon.co.uk/projects/timthumb/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/php/timthumb-vulnerability-for-possible-server-exploit/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to create WordPress plugins</title>
		<link>http://www.ombing.com/wordpress/how-to-create-wordpress-plugins</link>
		<comments>http://www.ombing.com/wordpress/how-to-create-wordpress-plugins#comments</comments>
		<pubDate>Sun, 18 Sep 2011 10:34:48 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugins]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=40</guid>
		<description><![CDATA[<img src="http://www.ombing.com/wp-content/uploads/2011/09/tutorials.jpg" alt="" width="441" height="325" />In this tutorial series you will be able to learn how to create WordPress plugins from the very start of every programming learning the &#8220;Hello world&#8221; up to the creation of Administration options for your plugin. This is not the only article about creating wordpress plugins that is for sure, but this is how I [...]]]></description>
			<content:encoded><![CDATA[<img src="http://www.ombing.com/wp-content/uploads/2011/09/tutorials.jpg" alt="" width="441" height="325" /><p>In this tutorial series you will be able to learn how to create WordPress plugins from the very start of every programming learning the &#8220;Hello world&#8221; up to the creation of Administration options for your plugin.<span id="more-40"></span></p>
<p>This is not the only article about creating wordpress plugins that is for sure, but this is how I learned how to do it as a noob.</p>
<p>So, With out further delay here are the links for the tutorial series:<br />
<BR><br />
<a title="How to create WordPress plugins Part 1: Hello World" href="http://www.ombing.com/php/how-to-create-wordpress-plugins-part-1-hello-world">How to create WordPress plugins Part 1: Hello World</a></p>
<p><a title="How to create WordPress plugins Part 2: Working with data and Forms" href="http://www.ombing.com/php/how-to-create-wordpress-plugins-part-2-working-with-data-and-forms">How to create WordPress plugins Part 2: Working with data and Forms</a></p>
<p><a title="How to create WordPress plugins Part 3: Creating Admin Options" href="http://www.ombing.com/php/how-to-create-wordpress-plugins-part-3-creating-admin-options">How to create WordPress plugins Part 3: Creating Admin Options</a></p>
<p>Read up and I would be very happy to read additional inputs you may have for the series..</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/wordpress/how-to-create-wordpress-plugins/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Install XAMPP on Ubuntu 10.04</title>
		<link>http://www.ombing.com/ubuntu/install-lampp-on-ubuntu-10-04</link>
		<comments>http://www.ombing.com/ubuntu/install-lampp-on-ubuntu-10-04#comments</comments>
		<pubDate>Sun, 18 Sep 2011 10:33:49 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[LAMPP]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=38</guid>
		<description><![CDATA[This tutorial will show you the steps to fully install xampp on ubuntu 10.04 without problems. so, lets get on with it. 1. first download the latest version of xampp which is 1.7.3a (at the time that i wrote this tut) here is the link. 2. from where you have downloaded the package execute this [...]]]></description>
			<content:encoded><![CDATA[<p>This tutorial will show you the steps to fully install xampp on ubuntu 10.04 without problems. <span id="more-38"></span>so, lets get on with it.</p>
<p>1. first download the latest version of xampp which is 1.7.3a (at the time that i wrote this tut)</p>
<p><a href="http://sourceforge.net/projects/xampp/files/XAMPP%20Linux/1.7.3a/xampp-linux-1.7.3a.tar.gz/download">here is the link.</a></p>
<p>2. from where you have downloaded the package execute this on the terminal</p>
<p><span style="color: #0000ff;">$ sudo tar xvfz xampp-linux-1.7.3a.tar.gz -C /opt</span></p>
<p>when the execution of the above script is done, you now have an installed xampp and to start enter this on the terminal</p>
<p><span style="color: #0000ff;">$ sudo /opt/lampp/lampp start</span></p>
<p>note: to stop the lamp</p>
<p><span style="color: #0000ff;">$ /opt/lampp/lampp stop</span></p>
<p>now, as mentioned lampp is already installed for you. but there several things that we need to do to ensure that everything is working.</p>
<p>by default, the web root directory is <span style="color: #0000ff;">/opt/lampp/htdocs</span></p>
<p>and at first you would not be able to create files on this directory. run this command on the terminal while your on<span style="color: #0000ff;"> /opt/lampp</span></p>
<p><span style="color: #0000ff;">ls -l</span></p>
<p>and you will be able to see that the user associated with the htdocs directory is not the user that you are currently using.<br />
to &#8220;own&#8221; the directory enter this command:</p>
<p><span style="color: #0000ff;">/opt/lampp# chown -R yourusername:yourusername htdocs</span></p>
<p>then, edit the httpd.conf so you could add your username:</p>
<p><span style="color: #0000ff;">sudo gedit /opt/lampp/etc/httpd.conf</span></p>
<p>look for the following lines:</p>
<p><span style="color: #0000ff;">User nobody</span><br />
<span style="color: #0000ff;">Group nogroup</span><br />
<span style="color: #0000ff;">&lt;/IfModule&gt;</span><br />
<span style="color: #0000ff;">&lt;/IfModule&gt;</span></p>
<p>and change them to :</p>
<p><span style="color: #0000ff;">User yourusername</span><br />
<span style="color: #0000ff;">Group nogroup</span><br />
<span style="color: #0000ff;">&lt;/IfModule&gt;</span><br />
<span style="color: #0000ff;">&lt;/IfModule&gt;</span></p>
<p>we should also &#8220;own&#8221; the config.inc.php of the phpmyadmin that goes with the installer. to do this</p>
<p><span style="color: #0000ff;">cd /opt/lampp/phpmyadmin </span><br />
<span style="color: #0000ff;">chown yourusername:yourusername config.inc.php</span></p>
<p>now, restart your lampp</p>
<p><span style="color: #0000ff;">$ sudo /opt/lampp/lampp restart</span></p>
<p>and now your ready to go on your way&#8230;.</p>
<p>Just a warning your lampp installation is not fully secured yet</p>
<p>The MySQL administrator (root) has no password.</p>
<ul>
<li>The MySQL daemon is accessible via network.</li>
<li>ProFTPD uses the password &#8220;lampp&#8221; for user &#8220;nobody&#8221;.</li>
<li>PhpMyAdmin is accessible via network.</li>
<li>Examples are accessible via network.</li>
</ul>
<p>to fully secure your installation: run the following command and follow on screen instructions</p>
<p><span style="color: #0000ff;">/opt/lampp/lampp security</span></p>
<p>now, your of to go. I hope I had helped someone up. ^^</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/ubuntu/install-lampp-on-ubuntu-10-04/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITX PEAR Templating</title>
		<link>http://www.ombing.com/php/itx-pear-templating</link>
		<comments>http://www.ombing.com/php/itx-pear-templating#comments</comments>
		<pubDate>Sun, 18 Sep 2011 05:41:07 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[PEAR]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=14</guid>
		<description><![CDATA[Ever since my ids-media days, I have always worked with a web development team. There are always two major parts of the web dev team I have worked with, Front-end (designers) and the back-end (programmers). The most common hurdle that we encounter is how to be able separate the presentation layer with the logic layer. [...]]]></description>
			<content:encoded><![CDATA[<p>Ever since my ids-media days, I have always worked with a web development team. There are always two major parts of the web dev team I have worked with, Front-end (designers) and the back-end (programmers). The most common hurdle that we encounter is how to be able separate the presentation layer with the logic layer. <span id="more-14"></span>This is simply illustrated with the code below.</p>
<p><span style="color: #00ccff;">&lt;table border=&#8221;0&#8243; cellpadding=&#8221;2&#8243; cellspacing=&#8221;2&#8243;&gt;</span><br />
<span style="color: #00ccff;"> &lt;?php</span><br />
<span style="color: #00ccff;"> while($result = mysql_fetch_array($query))</span><br />
<span style="color: #00ccff;"> {</span><br />
<span style="color: #00ccff;"> ?&gt;</span><br />
<span style="color: #00ccff;"> &lt;tr&gt;</span><br />
<span style="color: #00ccff;"> &lt;td&gt;&lt;?php echo $result["name"];?&gt;&lt;/td&gt;</span><br />
<span style="color: #00ccff;"> &lt;td&gt;&lt;?php echo $result["address"];?&gt;&lt;/td&gt;</span><br />
<span style="color: #00ccff;"> &lt;/tr&gt;</span><br />
<span style="color: #00ccff;"> &lt;?php } ?&gt;</span><br />
<span style="color: #00ccff;"> &lt;/table&gt;</span></p>
<p>With the example above the backend programming with php is mixed up with the html tags which are used to present the data. The problem with this when working in a team is that the backend programmer will have to deal with the presentation layer while doing his job and when the design has to be changed or modified the designer will have to deal with the backend side thus forfeiting the idea of having a design focused developer and a backend focused programmer. This will result to have the two to compromise in order for their work to be harmonious.</p>
<p>In an effort to find solution for this hurdle, I tried to develop a sensible templating system that would separate the html front end from the php files. I was however stopped when I discovered the PEAR ITX Templating system. Unlike other templating systems that are beefed up with so many features that as a programmer I have no intention of using, the ITX templating system is as simple as it can be.</p>
<p>To start of with PEAR ITX templating system you need to have PEAR installed with your php. For info on how to do this, visit http://www.php.net.</p>
<p>You could also include these files to your code&#8221;<br />
IT.PHP<br />
IT_ERROR.PHP<br />
ITX.PHP</p>
<p>Let us start with the html side&#8221;. Create a html file named index.html</p>
<p><span style="color: #00ccff;">&lt;html&gt;</span><br />
<span style="color: #00ccff;"> &lt;head&gt;&lt;title&gt;IT TEMPLATE SAMPLE&lt;/title&gt;&lt;/head&gt;</span><br />
<span style="color: #00ccff;"> &lt;body&gt;</span><br />
<span style="color: #00ccff;"> {var_message}</span><br />
<span style="color: #00ccff;"> &lt;/body&gt;</span><br />
<span style="color: #00ccff;"> &lt;/html&gt;</span></p>
<p>* note that we inserted a token inside the body. a token is inclosed with the { } brackets. In this example we have the var_message token.</p>
<p>Now let us move on to the php file. Create a php file and name it as index.php.</p>
<p><span style="color: #00ccff;">&lt;?php</span><br />
<span style="color: #00ccff;"> include(&#8220;IT.php&#8221;);</span></p>
<p><span style="color: #00ccff;">$tpl = new HTML_Template_IT(&#8220;./&#8221;);</span><br />
<span style="color: #00ccff;"> $tpl-&gt;loadTemplatefile(&#8220;index.html&#8221;);</span></p>
<p><span style="color: #00ccff;">$tpl-&gt;setVariable(&#8220;var_message &#8220;,&#8221;Hello World&#8221;);</span></p>
<p><span style="color: #00ccff;">$tpl-&gt;show();</span><br />
<span style="color: #00ccff;"> ?&gt;</span></p>
<p>What we did here was<br />
1. first we included IT.PHP<br />
2. Then we initiated the template object and named it as $tpl.<br />
$tpl = new HTML_Template_IT(&#8220;./&#8221;);<br />
the argument for the HTML_Template_IT is &#8220;./&#8221; which means the current directory&#8221; you could put your html files on a different location and would just have to specify through this argument the location of the html file.<br />
3. after which we loaded the Template file which is the html file we created a while ago.<br />
$tpl-&gt;loadTemplatefile(&#8220;index.html&#8221;);<br />
4. we then replaced the token on the template file with our desired content.<br />
$tpl-&gt;setVariable(&#8220;var_message &#8220;,&#8221;Hello World&#8221;);<br />
5. Lastly, we parsed the tpl object.<br />
$tpl-&gt;show();</p>
<p>There you have it. when you point your browser to index.php it will display Hello World. This is the basic way of using the ITX system. ITX system also enables you to process tokens by blocks which will let you show data on a tabular format.</p>
<p>Let me take you back to this.</p>
<p><span style="color: #00ccff;"> &lt;table border=&#8221;0&#8243; cellpadding=&#8221;2&#8243; cellspacing=&#8221;2&#8243;&gt;</span><br />
<span style="color: #00ccff;"> &lt;?php</span><br />
<span style="color: #00ccff;"> &lt;while $result = mysql_fetch_array($query)&gt;</span><br />
<span style="color: #00ccff;"> {</span><br />
<span style="color: #00ccff;"> ?&gt;</span><br />
<span style="color: #00ccff;"> &lt;tr&gt;</span><br />
<span style="color: #00ccff;"> &lt;td&gt;&lt;?php echo $result["name"];?&gt;&lt;/td&gt;</span><br />
<span style="color: #00ccff;"> &lt;td&gt;&lt;?php echo $result["address"];?&gt;&lt;/td&gt;</span><br />
<span style="color: #00ccff;"> &lt;/tr&gt;</span><br />
<span style="color: #00ccff;"> &lt;?php } ?&gt;</span><br />
<span style="color: #00ccff;"> &lt;/table&gt;</span></p>
<p>let us modify this by elimating the php code and inserting tokens and a block</p>
<p><span style="color: #00ccff;">&lt;table border=&#8221;0&#8243; cellpadding=&#8221;2&#8243; cellspacing=&#8221;2&#8243;&gt;</span><br />
<span style="color: #00ccff;"> &lt;!&#8211; BEGIN row &#8211;&gt;</span><br />
<span style="color: #00ccff;"> &lt;tr&gt;</span><br />
<span style="color: #00ccff;"> &lt;td&gt;&lt;/td&gt;</span><br />
<span style="color: #00ccff;"> &lt;td&gt;&lt;/td&gt;</span><br />
<span style="color: #00ccff;"> &lt;/tr&gt;</span><br />
<span style="color: #00ccff;"> &lt;!&#8211; END row &#8211;&gt;</span><br />
<span style="color: #00ccff;"> &lt;/table&gt;</span></p>
<p>now to process this on the php side,</p>
<p><span style="color: #00ccff;">while($result = mysql_fetch_array($query))</span><br />
<span style="color: #00ccff;"> {</span><br />
<span style="color: #00ccff;"> $tpl-&gt;setCurrentBlock(&#8220;row&#8221;);</span><br />
<span style="color: #00ccff;"> $tpl-&gt;setVariable(&#8220;var_name&#8221;,$result["name"]);</span><br />
<span style="color: #00ccff;"> $tpl-&gt;setVariable(&#8220;var_address&#8221;,$result["address"]);</span><br />
<span style="color: #00ccff;"> $tpl-&gt;parseCurrentBlock(&#8220;row&#8221;);</span><br />
<span style="color: #00ccff;"> }</span></p>
<p>That is how simple it is to process tabular data through ITX. You just have to set the template directory and the load the template file as we did a while ago then</p>
<p>set the current block<br />
$tpl-&gt;setCurrentBlock(&#8220;row&#8221;);<br />
replace the tokens inside that block with your desired output.<br />
$tpl-&gt;setVariable(&#8220;var_name&#8221;,$result["name"]);<br />
$tpl-&gt;setVariable(&#8220;var_address&#8221;,$result["address"]);<br />
then parse the current block<br />
$tpl-&gt;parseCurrentBlock(&#8220;row&#8221;);<br />
you will just have to parse the entire template with<br />
$tpl-&gt;show();<br />
and your good to go!</p>
<p>As you can see clearly, with the PEAR ITX Templating system the presentation layer(html) is separated with the backend php file. This will enable your designer to design the page at will and the programmer to do his thing uninterrupted with the design hurdle. This website uses PEAR ITX TEMPLATING SYSTEM.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/php/itx-pear-templating/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL Fulltext search</title>
		<link>http://www.ombing.com/mysql/mysql-fulltext-search</link>
		<comments>http://www.ombing.com/mysql/mysql-fulltext-search#comments</comments>
		<pubDate>Sun, 18 Sep 2011 05:30:17 +0000</pubDate>
		<dc:creator>Ombing Feria</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Fulltext Search]]></category>
		<category><![CDATA[MySql]]></category>

		<guid isPermaLink="false">http://www.ombing.com/?p=11</guid>
		<description><![CDATA[There are several ways to search for something in a MySql database. One of these techniques is the use of the LIKE clause.SELECT field1, field2 FROM Table_Name WHERE field2 LIKE &#8216;%search_string%&#8217; While this technique works like a charm and is actually advisable to some scenarios, it is however cumbersome to use when you have thousands [...]]]></description>
			<content:encoded><![CDATA[<div id="post-body-6051381778905664534">There are several ways to search for something in a MySql database. One of these techniques is the use of the LIKE clause.SELECT field1, field2 FROM Table_Name WHERE field2 LIKE &#8216;%search_string%&#8217;</div>
<div><span id="more-11"></span></div>
<div id="post-body-6051381778905664534">
<p>While this technique works like a charm and is actually advisable to some scenarios, it is however cumbersome to use when you have thousands of records in the table and you have to sort the results according to the relevancy of the resulting record to the search string. This technique does not scale at all. This is where FULL-TEXT SEARCHING comes to play.</p>
<p>MORE ON FULL-TEXT&#8230;</p>
<p>Full-Text is a type of index created on a table. The Full-Text index basically creates an index of all of the words of the field specified in your table. Each entry in this index references a row in your table. These indexes are created in separate index files by MySQL. When you perform a search against the Full-Text index, the MySQL Full-Text search functions use this index to return the related rows from the table back through the result set. Through this index, the search performance is enhanced through its speed in returning the results and could also give you the ability to sort the results according to its relevance.</p>
<p>SETTING UP THE DATABASE&#8230;</p>
<p>As an example let us use the table with the structure defined below:</p>
<p>CREATE TABLE `Table_Name` (<br />
`field1` INT( 10 ) NOT NULL AUTO_INCREMENT PRIMARY KEY ,<br />
`field2` VARCHAR( 100 ) NOT NULL<br />
);</p>
<p>The field where we will match our search queries against is the string field2. to create the Full-Text index for field2 use the sql statement below:</p>
<p>ALTER TABLE Table_Name ADD FULLTEXT (field2);</p>
<p>THE QUERY&#8230;</p>
<p>With the database set, let us move on the query statement that would be used to return the resulting records from the search&#8221;.</p>
<p>SELECT * FROM Table_Name WHERE MATCH(field2) against(`search string`);</p>
<p>Full-Text searching uses the MATCH() and AGAINST() syntax. As parameters, MATCH() takes the list of all the field names from where we will &#8220;match&#8221; the search string into. While AGAINST() takes the search string. The search string can contain any phrase that you would like to search in database. Stopwords like `else`, `any`, `at`, `as` would not be considered by the full-text search. For a list of all the stopwords visit http://dev.mysql.com/doc/refman/5.0/en/fulltext-stopwords.html</p>
<p>THE RESULT&#8230;</p>
<p>If a certain word in the phrase returns 50% or more of the records on the table, it will be disregarded. Though this may seem annoying with tables containing small number of records, this rule actually makes sense with a large database because if that word is contained in most records it is mostly irrelevant. For example, you have a database of Cars, and a user would search `Toyota cars` since all of your records contain the word `cars`, the relevant word would only be `Toyota`. The user would more often than not, need results that would contain `Toyota`.</p>
<p>MORE ON RESULTS&#8230;</p>
<p>As I have mentioned, we would most likely want to order the results according to the relevancy to the search phrase. To do this,</p>
<p>SELECT field1, field2, MATCH(field2) against(`search string`) AS relevancy FROM Table_Name WHERE MATCH(field2) against(`search string`) order by relevancy DESC;</p>
<p>As you can see, we used the MATCH() AGAINST() phrase to have a new field in our results as relevancy and sets the order of the returned results to that relevancy field. MySql acknowledges this technique and will perform the MATCH() AGAINST() phrase only once.</p>
<p>CONCLUSION</p>
<p>Give it a try and you will see that this technique will scale well in performance compared to creating a query using the LIKE clause and scan through the result to compute each records` relevancy score. Full-Text Search does not stop here, you could also perform Boolean searching and query expansions.</p>
</div>
<p><a href="http://www.ombing.com/wp-content/uploads/2011/09/mysql.jpg"><img class="alignnone size-full wp-image-46" title="mysql" src="http://www.ombing.com/wp-content/uploads/2011/09/mysql.jpg" alt="" width="640" height="283" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ombing.com/mysql/mysql-fulltext-search/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

