<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: The New Blogger: Still Buggy after all this time!</title>
	<link>http://www.blogbloke.com/new-blogger-still-buggy-after-all/</link>
	<description>Better Blog Tips for Bloggers, by the Original Blogging Bloke</description>
	<pubDate>Fri, 09 Jan 2009 23:50:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: Blog Bloke</title>
		<link>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1043</link>
		<dc:creator>Blog Bloke</dc:creator>
		<pubDate>Fri, 19 Jan 2007 21:26:00 +0000</pubDate>
		<guid>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1043</guid>
		<description>&lt;b&gt;IMPORTANT UPDATE:&lt;/b&gt; After several hours on the phone with the domain registrar I think I might have a fix for all of these problems. I just have to wait another 24 hours for it to propagate further to make sure. So stay tuned and I'll keep y'all posted.</description>
		<content:encoded><![CDATA[<p><b>IMPORTANT UPDATE:</b> After several hours on the phone with the domain registrar I think I might have a fix for all of these problems. I just have to wait another 24 hours for it to propagate further to make sure. So stay tuned and I&#8217;ll keep y&#8217;all posted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog Bloke</title>
		<link>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1042</link>
		<dc:creator>Blog Bloke</dc:creator>
		<pubDate>Fri, 19 Jan 2007 20:54:00 +0000</pubDate>
		<guid>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1042</guid>
		<description>Last I heard they are charging $10 for a Custom Domain with Google Apps. But I would avoid using Google Apps right now. &lt;a HREF="http://Blog Bloke.blogspot.com/2007/01/how-i-got-custom-domains-to-work-with.html" REL="nofollow"&gt;Too many problems&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Last I heard they are charging $10 for a Custom Domain with Google Apps. But I would avoid using Google Apps right now. <a HREF="http://Blog Bloke.blogspot.com/2007/01/how-i-got-custom-domains-to-work-with.html" REL="nofollow">Too many problems</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brent Roos</title>
		<link>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1041</link>
		<dc:creator>Brent Roos</dc:creator>
		<pubDate>Fri, 19 Jan 2007 18:01:00 +0000</pubDate>
		<guid>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1041</guid>
		<description>So you have the problem with the www. prefix or not too? What is the deal with this? I was using wordpress.com before with domain mapping (I'm a beta tester), but I have become so frustrated with the limitations of wordpress.com, that I decided to give Blogger another chance.&lt;br/&gt;&lt;br/&gt;You're right, the new Blogger &lt;i&gt;is&lt;/i&gt; buggy, but I would expect this since it is new. Hopefully these issues will get worked out. God forbid I end up going &lt;i&gt;back&lt;/i&gt; to wordpress.com. You know they make you pay for just about every feature that Blogger tends to offer for free (custom css, domain mapping, etc)?&lt;br/&gt;&lt;br/&gt;We'll see what happens with this custom domain thing. I think it will be alright. Keep in mind that Google is huge, and it might take a minute or three to work out the bugs.&lt;br/&gt;&lt;br/&gt;Lastly, one thought comes to mind: I wonder if Google will start providing domain names. Will this also be free? Perhaps with Google ads? Just a thought.</description>
		<content:encoded><![CDATA[<p>So you have the problem with the <a href="http://www." rel="nofollow">www.</a> prefix or not too? What is the deal with this? I was using wordpress.com before with domain mapping (I&#8217;m a beta tester), but I have become so frustrated with the limitations of wordpress.com, that I decided to give Blogger another chance.</p>
<p>You&#8217;re right, the new Blogger <i>is</i> buggy, but I would expect this since it is new. Hopefully these issues will get worked out. God forbid I end up going <i>back</i> to wordpress.com. You know they make you pay for just about every feature that Blogger tends to offer for free (custom css, domain mapping, etc)?</p>
<p>We&#8217;ll see what happens with this custom domain thing. I think it will be alright. Keep in mind that Google is huge, and it might take a minute or three to work out the bugs.</p>
<p>Lastly, one thought comes to mind: I wonder if Google will start providing domain names. Will this also be free? Perhaps with Google ads? Just a thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog Bloke</title>
		<link>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1040</link>
		<dc:creator>Blog Bloke</dc:creator>
		<pubDate>Wed, 17 Jan 2007 08:28:00 +0000</pubDate>
		<guid>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1040</guid>
		<description>Thanks for the clarification phydeaux3, but I think I'll wait if it's all the same. They can continue beta testing at someone else's expense, not mine. Clearly they haven't got it right yet and I don't need the hassle...widget, widget...</description>
		<content:encoded><![CDATA[<p>Thanks for the clarification phydeaux3, but I think I&#8217;ll wait if it&#8217;s all the same. They can continue beta testing at someone else&#8217;s expense, not mine. Clearly they haven&#8217;t got it right yet and I don&#8217;t need the hassle&#8230;widget, widget&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: phydeaux3</title>
		<link>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1039</link>
		<dc:creator>phydeaux3</dc:creator>
		<pubDate>Wed, 17 Jan 2007 06:28:00 +0000</pubDate>
		<guid>http://www.blogbloke.com/new-blogger-still-buggy-after-all/#comment-1039</guid>
		<description>Well, keep in mind what I was talking about was only in one circumstance, the pageType doesn't appear to work as an 'attribute for a widget'.&lt;br/&gt;&lt;br/&gt;The pageType DOES work in conditional tags everywhere else (Every template uses them off the shelf), and can be used in many places successfully. Just per widget is the problem area.</description>
		<content:encoded><![CDATA[<p>Well, keep in mind what I was talking about was only in one circumstance, the pageType doesn&#8217;t appear to work as an &#8216;attribute for a widget&#8217;.</p>
<p>The pageType DOES work in conditional tags everywhere else (Every template uses them off the shelf), and can be used in many places successfully. Just per widget is the problem area.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
