<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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>Comments on: How to Get Your WordPress Plugin To DROP TABLE From The Database</title>
	<atom:link href="http://www.martin-gardner.co.uk/how-to-get-your-wordpress-plugin-to-drop-table-from-the-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.martin-gardner.co.uk/how-to-get-your-wordpress-plugin-to-drop-table-from-the-database/</link>
	<description>Technology - Gadgets - Programing - Gaming - Reviews - Tutorials</description>
	<lastBuildDate>Tue, 31 Aug 2010 21:41:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: jeremys.awesome</title>
		<link>http://www.martin-gardner.co.uk/how-to-get-your-wordpress-plugin-to-drop-table-from-the-database/comment-page-1/#comment-20619</link>
		<dc:creator>jeremys.awesome</dc:creator>
		<pubDate>Tue, 31 Aug 2010 21:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.martin-gardner.co.uk/?p=1438#comment-20619</guid>
		<description>I believe the currently suggested way of doing this is by creating an uninstall.php file in the root of your plugin folder.

From there it&#039;s really easy to remove options and database tables that have been created by your plugin. Jacob Santos explains the process here: http://jacobsantos.com/2008/general/wordpress-27-plugin-uninstall-methods/

I think it&#039;s a good idea to remove the database tables and options on Uninstall rather then on deactivation. This allows the data to persist say if, as @MostlyCarbon mentioned, the admin wishes to debug his site and not lose any data.</description>
		<content:encoded><![CDATA[<p>I believe the currently suggested way of doing this is by creating an uninstall.php file in the root of your plugin folder.</p>
<p>From there it&#8217;s really easy to remove options and database tables that have been created by your plugin. Jacob Santos explains the process here: <a href="http://jacobsantos.com/2008/general/wordpress-27-plugin-uninstall-methods/" rel="nofollow">http://jacobsantos.com/2008/general/wordpress-27-plugin-uninstall-methods/</a></p>
<p>I think it&#8217;s a good idea to remove the database tables and options on Uninstall rather then on deactivation. This allows the data to persist say if, as @MostlyCarbon mentioned, the admin wishes to debug his site and not lose any data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MostlyCarbon</title>
		<link>http://www.martin-gardner.co.uk/how-to-get-your-wordpress-plugin-to-drop-table-from-the-database/comment-page-1/#comment-17005</link>
		<dc:creator>MostlyCarbon</dc:creator>
		<pubDate>Thu, 22 Jul 2010 22:44:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.martin-gardner.co.uk/?p=1438#comment-17005</guid>
		<description>Hi there.  Just wondering - wouldn&#039;t it be better to register this functionality with &quot;register_uninstall_hook&quot; hook instead?  The admin may want to deactivate the plugin only temporarily (it&#039;s interferring with other plugins or causing some unwanted behavior which the admin must debug).</description>
		<content:encoded><![CDATA[<p>Hi there.  Just wondering &#8211; wouldn&#8217;t it be better to register this functionality with &#8220;register_uninstall_hook&#8221; hook instead?  The admin may want to deactivate the plugin only temporarily (it&#8217;s interferring with other plugins or causing some unwanted behavior which the admin must debug).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uwiuw</title>
		<link>http://www.martin-gardner.co.uk/how-to-get-your-wordpress-plugin-to-drop-table-from-the-database/comment-page-1/#comment-10637</link>
		<dc:creator>uwiuw</dc:creator>
		<pubDate>Sun, 14 Mar 2010 02:26:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.martin-gardner.co.uk/?p=1438#comment-10637</guid>
		<description>yeah, this is a good solution. I hope all plugin developer also follow this approach, especially with all their plugin information in option table 

cause they just become a mess or unneeded information if we have unplugged and delete the plugin.</description>
		<content:encoded><![CDATA[<p>yeah, this is a good solution. I hope all plugin developer also follow this approach, especially with all their plugin information in option table </p>
<p>cause they just become a mess or unneeded information if we have unplugged and delete the plugin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  www.martin-gardner.co.uk/how-to-get-your-wordpress-plugin-to-drop-table-from-the-database/feed/ ) in 0.25798 seconds, on Sep 9th, 2010 at 1:20 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Sep 9th, 2010 at 2:20 am UTC -->