<?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: _pingme, _encloseme, headers sent WordPress Error</title>
	<atom:link href="http://www.actiononline.biz/web/_pingme-_encloseme-headers-sent-wordpress-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.actiononline.biz/web/_pingme-_encloseme-headers-sent-wordpress-error/</link>
	<description>Technology &#038; Business blog of YDS Web Solution</description>
	<lastBuildDate>Wed, 19 Oct 2011 23:11:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Benj Arriola</title>
		<link>http://www.actiononline.biz/web/_pingme-_encloseme-headers-sent-wordpress-error/comment-page-1/#comment-38113</link>
		<dc:creator>Benj Arriola</dc:creator>
		<pubDate>Sat, 08 Sep 2007 21:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://webgasm.actiononline.biz/content-management/2006/07/30/_pingme-_encloseme-headers-sent-wordpress-error/#comment-38113</guid>
		<description>Thanks Maggie, I&#039;m glad it helped you. Also a word of caution to other people, since this is indeed an old post, maybe in the future this may not fix the problem with the Wordpress guys do a major change database table structures.

So my tip and word of caution is always keep a backup of everything. So just in case everything gets mess up and makes things worse, at least you still have the original copies with less problems.</description>
		<content:encoded><![CDATA[<p>Thanks Maggie, I&#8217;m glad it helped you. Also a word of caution to other people, since this is indeed an old post, maybe in the future this may not fix the problem with the WordPress guys do a major change database table structures.</p>
<p>So my tip and word of caution is always keep a backup of everything. So just in case everything gets mess up and makes things worse, at least you still have the original copies with less problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maggie</title>
		<link>http://www.actiononline.biz/web/_pingme-_encloseme-headers-sent-wordpress-error/comment-page-1/#comment-38103</link>
		<dc:creator>maggie</dc:creator>
		<pubDate>Sat, 08 Sep 2007 19:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://webgasm.actiononline.biz/content-management/2006/07/30/_pingme-_encloseme-headers-sent-wordpress-error/#comment-38103</guid>
		<description>Ok, so this is over 1 year old but I just found it today!

OMG YOU ARE A GENIUS!  I have been having these issues after exporting and importing ( both done in MySQL4.1..) my blog tables (for 4 different blogs mind you!)

I knew there were some auto_increment issues but could never figure out which ones on the wp_post2cat table and another table.

I ran this quick query and PRESTO!  It&#039;s all working now! 
Thanks!</description>
		<content:encoded><![CDATA[<p>Ok, so this is over 1 year old but I just found it today!</p>
<p>OMG YOU ARE A GENIUS!  I have been having these issues after exporting and importing ( both done in MySQL4.1..) my blog tables (for 4 different blogs mind you!)</p>
<p>I knew there were some auto_increment issues but could never figure out which ones on the wp_post2cat table and another table.</p>
<p>I ran this quick query and PRESTO!  It&#8217;s all working now!<br />
Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

