<?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: Point 72 Beta 1 Available</title>
	<atom:link href="http://wordpress.org/development/2003/08/point-72-beta-1-available/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/</link>
	<description>WordPress development and updates</description>
	<lastBuildDate>Thu, 19 Nov 2009 14:58:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9-beta-1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Phil</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-165</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Sun, 07 Sep 2003 15:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-165</guid>
		<description>No matter what I do I can&#039;t log into this thing, the password it game me doesn&#039;t work. It keeps going to back the login page without any error. I even tried rubbish text for the user name and password and there isn&#039;t even a error.

Why is this so? If I can&#039;t log in, how am I supposed to post?</description>
		<content:encoded><![CDATA[<p>No matter what I do I can&#8217;t log into this thing, the password it game me doesn&#8217;t work. It keeps going to back the login page without any error. I even tried rubbish text for the user name and password and there isn&#8217;t even a error.</p>
<p>Why is this so? If I can&#8217;t log in, how am I supposed to post?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rakhesh Sasidharan</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-142</link>
		<dc:creator>Rakhesh Sasidharan</dc:creator>
		<pubDate>Sun, 31 Aug 2003 21:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-142</guid>
		<description>Any place where I can see the new default style?</description>
		<content:encoded><![CDATA[<p>Any place where I can see the new default style?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tsanghan</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-141</link>
		<dc:creator>tsanghan</dc:creator>
		<pubDate>Sat, 30 Aug 2003 07:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-141</guid>
		<description>it super nice...i juss did a clean install worked fine got couple errors from upgrade so i juss did clean install on a new db thanks again</description>
		<content:encoded><![CDATA[<p>it super nice&#8230;i juss did a clean install worked fine got couple errors from upgrade so i juss did clean install on a new db thanks again</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-129</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 28 Aug 2003 01:54:53 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-129</guid>
		<description>FYI, Zaaba&#039;s problem was resolved in the forums.</description>
		<content:encoded><![CDATA[<p>FYI, Zaaba&#8217;s problem was resolved in the forums.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zaaba</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-120</link>
		<dc:creator>Zaaba</dc:creator>
		<pubDate>Wed, 27 Aug 2003 11:41:01 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-120</guid>
		<description>I received an error after running the upgrade 0.71 script. I realised that the start and end motor of the blog syntaxes were different, changed them... but got this error instead:   

1.  SQL/DB Error --
2. [Unknown column &#039;post_status&#039; in &#039;where clause&#039;]

Eh? Can anybody help?</description>
		<content:encoded><![CDATA[<p>I received an error after running the upgrade 0.71 script. I realised that the start and end motor of the blog syntaxes were different, changed them&#8230; but got this error instead:   </p>
<p>1.  SQL/DB Error &#8211;<br />
2. [Unknown column 'post_status' in 'where clause']</p>
<p>Eh? Can anybody help?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jouno</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-117</link>
		<dc:creator>jouno</dc:creator>
		<pubDate>Tue, 26 Aug 2003 19:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-117</guid>
		<description>please make default charset of meta-tag of index.php,comment.popup.php
 to $admin_area_charset.then,we can change easily the chaset of our site.
or make another variable something like $site_charset.
but in almost all case, charset of admin and index.php is same.

the change is important in CJK users.</description>
		<content:encoded><![CDATA[<p>please make default charset of meta-tag of index.php,comment.popup.php<br />
 to $admin_area_charset.then,we can change easily the chaset of our site.<br />
or make another variable something like $site_charset.<br />
but in almost all case, charset of admin and index.php is same.</p>
<p>the change is important in CJK users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-116</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 25 Aug 2003 23:35:50 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-116</guid>
		<description>Glad to hear things worked out David. Next time it might be better to start a forum thread rather than use the comments here.</description>
		<content:encoded><![CDATA[<p>Glad to hear things worked out David. Next time it might be better to start a forum thread rather than use the comments here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mattison</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-2/#comment-115</link>
		<dc:creator>David Mattison</dc:creator>
		<pubDate>Mon, 25 Aug 2003 21:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-115</guid>
		<description>Wow! Renamed all b2* tables with phpMyAdmin to dev_*. Only complaint upgrade script had was about missing b2settings table. Everything else rolled over ok. Check it out at http://www.davidmattison.ca/wordpress

Need to move around some stuff, tweak it, etc. At least no data conversion delirium tremors!</description>
		<content:encoded><![CDATA[<p>Wow! Renamed all b2* tables with phpMyAdmin to dev_*. Only complaint upgrade script had was about missing b2settings table. Everything else rolled over ok. Check it out at <a href="http://www.davidmattison.ca/wordpress" rel="nofollow">http://www.davidmattison.ca/wordpress</a></p>
<p>Need to move around some stuff, tweak it, etc. At least no data conversion delirium tremors!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mattison</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-1/#comment-114</link>
		<dc:creator>David Mattison</dc:creator>
		<pubDate>Mon, 25 Aug 2003 20:50:42 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-114</guid>
		<description>Me again. Ignore the b2evolution theory. I want to give WordPress 0.72 a crack. The old tables are still there. I&#039;ll delete the dev_* tables that were added when I ran wp-install.php and rename the b2* tables, and try running the upgrade script again.  Can&#039;t get any worse than this.  If worse goes to catastrophic failure, since I haven&#039;t had the pleasure of importing a saved SQL zipped file to an existing DB, any tips if I reinstall 0.71 and need to import the SQL zipped file? I saved both the Structure and Data and just the Data as zipped files. Thanks people!</description>
		<content:encoded><![CDATA[<p>Me again. Ignore the b2evolution theory. I want to give WordPress 0.72 a crack. The old tables are still there. I&#8217;ll delete the dev_* tables that were added when I ran wp-install.php and rename the b2* tables, and try running the upgrade script again.  Can&#8217;t get any worse than this.  If worse goes to catastrophic failure, since I haven&#8217;t had the pleasure of importing a saved SQL zipped file to an existing DB, any tips if I reinstall 0.71 and need to import the SQL zipped file? I saved both the Structure and Data and just the Data as zipped files. Thanks people!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mattison</title>
		<link>http://wordpress.org/development/2003/08/point-72-beta-1-available/comment-page-1/#comment-113</link>
		<dc:creator>David Mattison</dc:creator>
		<pubDate>Mon, 25 Aug 2003 20:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/08/point-72-beta-1-available/#comment-113</guid>
		<description>Bummer. Slept on this. Couldn&#039;t ruin it more, so I tried running the plain old wp-install.php, which did ruin it more. Will go back to previous version or try b2evolution. I think one change you might want to think about is to not install on top of existing files, but to install in a new directory. Then when things are working in the new installation, which reads from and converts the existing database, delete the existing installation. This won&#039;t allow you to rollback your database, but by backing up the data first, at least you&#039;d preserve your original site in its own directory. This is the method I use for Tiki.</description>
		<content:encoded><![CDATA[<p>Bummer. Slept on this. Couldn&#8217;t ruin it more, so I tried running the plain old wp-install.php, which did ruin it more. Will go back to previous version or try b2evolution. I think one change you might want to think about is to not install on top of existing files, but to install in a new directory. Then when things are working in the new installation, which reads from and converts the existing database, delete the existing installation. This won&#8217;t allow you to rollback your database, but by backing up the data first, at least you&#8217;d preserve your original site in its own directory. This is the method I use for Tiki.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
