<?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"
	>
<channel>
	<title>Comments on: Blogger &#8220;Next Blog&#8221; Solution?</title>
	<atom:link href="http://weblogg-ed.com/2007/blogger-next-blog-solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/</link>
	<description>The Read/Write Web in the Classroom</description>
	<pubDate>Sat, 17 May 2008 00:34:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Sheryl Nussbaum-Beach</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-15041</link>
		<dc:creator>Sheryl Nussbaum-Beach</dc:creator>
		<pubDate>Thu, 15 Mar 2007 15:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-15041</guid>
		<description>This is for Classic Blogger

1. copy this code 
2. log in to your blogger blog
3. click on template
4. scroll down until you see the word  with these brackets and not {body} (that is a style code)
5. replace  with the code in #16. republish your blog.</description>
		<content:encoded><![CDATA[<p>This is for Classic Blogger</p>
<p>1. copy this code<br />
2. log in to your blogger blog<br />
3. click on template<br />
4. scroll down until you see the word  with these brackets and not {body} (that is a style code)<br />
5. replace  with the code in #16. republish your blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Monica</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14747</link>
		<dc:creator>Monica</dc:creator>
		<pubDate>Sun, 11 Mar 2007 16:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14747</guid>
		<description>We talk and talk and talk about teachers using technology in the classroom. Here is a perfect example of why they are reluctant: CSS, navbar, 0px, open and closing braces. ("Enlightened" ones may know that a missing closing brace will have serious side-effects.)

Perhaps the poor usability factor has scared them away....</description>
		<content:encoded><![CDATA[<p>We talk and talk and talk about teachers using technology in the classroom. Here is a perfect example of why they are reluctant: CSS, navbar, 0px, open and closing braces. (&#8221;Enlightened&#8221; ones may know that a missing closing brace will have serious side-effects.)</p>
<p>Perhaps the poor usability factor has scared them away&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Mercer</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14641</link>
		<dc:creator>A Mercer</dc:creator>
		<pubDate>Sat, 10 Mar 2007 20:28:01 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14641</guid>
		<description>It's one of the many reasons I prefer edublogs even though I started my blogging in blogger/blogspot. Reason 2 - Word Press templates are prettier. 

Also the "adminwall" that Scott McLeod recently talked about is more easily convinced to unblock a blog environment that is specifically set up for education purposes.</description>
		<content:encoded><![CDATA[<p>It&#8217;s one of the many reasons I prefer edublogs even though I started my blogging in blogger/blogspot. Reason 2 - Word Press templates are prettier. </p>
<p>Also the &#8220;adminwall&#8221; that Scott McLeod recently talked about is more easily convinced to unblock a blog environment that is specifically set up for education purposes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glenn E. Malone</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14611</link>
		<dc:creator>Glenn E. Malone</dc:creator>
		<pubDate>Sat, 10 Mar 2007 07:27:43 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14611</guid>
		<description>Will, Sorry for the delay in my reply; looks like you have a solution and I left out an important step.  

The HTML for my Blogger Beta site http://AlmostMonday.BlogSpot.Com is located here for review if needed:  http://docs.google.com/Doc?id=acsgnjpc9x7h_57cdtvkt.

Kathy, I did consider your point before I decided to remove the navbar by but I came to the conclusion that Google had not explicitly address the NavBar...
http://labnol.blogspot.com/2005/12/disable-hide-blogger-navbar.html

Here's the full text:
http://www.blogger.com/terms.g

I wonder if Darren has upgraded to the beta version yet?
http://adifference.blogspot.com/

Will...Great job on the keynote today &#38; yep you did close your eyes :)</description>
		<content:encoded><![CDATA[<p>Will, Sorry for the delay in my reply; looks like you have a solution and I left out an important step.  </p>
<p>The HTML for my Blogger Beta site <a href="http://AlmostMonday.BlogSpot.Com" rel="nofollow">http://AlmostMonday.BlogSpot.Com</a> is located here for review if needed:  <a href="http://docs.google.com/Doc?id=acsgnjpc9x7h_57cdtvkt" rel="nofollow">http://docs.google.com/Doc?id=acsgnjpc9&#215;7h_57cdtvkt</a>.</p>
<p>Kathy, I did consider your point before I decided to remove the navbar by but I came to the conclusion that Google had not explicitly address the NavBar&#8230;<br />
<a href="http://labnol.blogspot.com/2005/12/disable-hide-blogger-navbar.html" rel="nofollow">http://labnol.blogspot.com/2005/12/disable-hide-blogger-navbar.html</a></p>
<p>Here&#8217;s the full text:<br />
<a href="http://www.blogger.com/terms.g" rel="nofollow">http://www.blogger.com/terms.g</a></p>
<p>I wonder if Darren has upgraded to the beta version yet?<br />
<a href="http://adifference.blogspot.com/" rel="nofollow">http://adifference.blogspot.com/</a></p>
<p>Will&#8230;Great job on the keynote today &amp; yep you did close your eyes <img src='http://weblogg-ed.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathy Schrock</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14546</link>
		<dc:creator>Kathy Schrock</dc:creator>
		<pubDate>Fri, 09 Mar 2007 22:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14546</guid>
		<description>Not to put a damper on things, but, if your blog is hosted on Blogger itself, you are violating their user agreement policy that you "signed" when you signed up by removing the NEXT BLOG header.

However, if you use another server for hosting the Blogger site (one where you have FTP rights), and just use the Blogger interface for posting to your blog, you are permitted, by Blogger, and are even given a drop-down box, to disable the NEXT BLOG hyperlink.

At least that is the way I understand the rules to be...

Just wanted to keep everyone on the up and up!

Kathy</description>
		<content:encoded><![CDATA[<p>Not to put a damper on things, but, if your blog is hosted on Blogger itself, you are violating their user agreement policy that you &#8220;signed&#8221; when you signed up by removing the NEXT BLOG header.</p>
<p>However, if you use another server for hosting the Blogger site (one where you have FTP rights), and just use the Blogger interface for posting to your blog, you are permitted, by Blogger, and are even given a drop-down box, to disable the NEXT BLOG hyperlink.</p>
<p>At least that is the way I understand the rules to be&#8230;</p>
<p>Just wanted to keep everyone on the up and up!</p>
<p>Kathy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LoriB</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14545</link>
		<dc:creator>LoriB</dc:creator>
		<pubDate>Fri, 09 Mar 2007 22:25:36 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14545</guid>
		<description>Never mind.  It keeps erasing itself.  Should have left well enough alone.  :-)</description>
		<content:encoded><![CDATA[<p>Never mind.  It keeps erasing itself.  Should have left well enough alone.  <img src='http://weblogg-ed.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LoriB</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14539</link>
		<dc:creator>LoriB</dc:creator>
		<pubDate>Fri, 09 Mar 2007 21:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14539</guid>
		<description>Sorry.  The code I copied into my comment above about where I put the hide nav bar code, didn't print for some reason.  Instead of saying just "]]&#62;"  it should say "]]&#62;&lt;/b&gt;" which is right at the end of the "head" section of the html.</description>
		<content:encoded><![CDATA[<p>Sorry.  The code I copied into my comment above about where I put the hide nav bar code, didn&#8217;t print for some reason.  Instead of saying just &#8220;]]&gt;&#8221;  it should say &#8220;]]&gt;&#8221; which is right at the end of the &#8220;head&#8221; section of the html.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LoriB</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14538</link>
		<dc:creator>LoriB</dc:creator>
		<pubDate>Fri, 09 Mar 2007 21:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14538</guid>
		<description>I've had good luck using the code in the comment above, and putting it in the html template just before 

]]&#62;&lt;/b&gt;



which is near the bottom of the template.

There also used to be a hack that let you edit people's comments.  The old code stopped working but I haven't had any luck with the new one.  I've gotten it from this site:
http://blogger-templates.blogspot.com/2005/07/edit-comments.html

Does anyone else know of a source for this that will work to let you edit comments?  In using blogs with elementary level students, it is rather a necessity to be able to go back in and edit the comments the kids write so that others will be able to read them.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had good luck using the code in the comment above, and putting it in the html template just before </p>
<p>]]&gt;</p>
<p>which is near the bottom of the template.</p>
<p>There also used to be a hack that let you edit people&#8217;s comments.  The old code stopped working but I haven&#8217;t had any luck with the new one.  I&#8217;ve gotten it from this site:<br />
<a href="http://blogger-templates.blogspot.com/2005/07/edit-comments.html" rel="nofollow">http://blogger-templates.blogspot.com/2005/07/edit-comments.html</a></p>
<p>Does anyone else know of a source for this that will work to let you edit comments?  In using blogs with elementary level students, it is rather a necessity to be able to go back in and edit the comments the kids write so that others will be able to read them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LoriB</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14537</link>
		<dc:creator>LoriB</dc:creator>
		<pubDate>Fri, 09 Mar 2007 21:26:10 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14537</guid>
		<description>I've had good luck using the code in the comment above, and putting it in the html template just before 

]]&#62;&lt;/b&gt;



which is near the bottom of the template.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had good luck using the code in the comment above, and putting it in the html template just before </p>
<p>]]&gt;</p>
<p>which is near the bottom of the template.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Whipple</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14520</link>
		<dc:creator>Jeff Whipple</dc:creator>
		<pubDate>Fri, 09 Mar 2007 19:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14520</guid>
		<description>We have used blogger for a couple of years for class blogs and have hidden the whole navbar as a solution to the "next blog" button...we did this by a small code insertion in the template

The move to New Blogger simply required a different bit of code...add the following lines anywhere in the template [enclosed by  tags] and the blogger banner will disappear.

       #navbar-iframe {
              height:0px;
              visibility:hidden;
              display:none;
        }

This removes the whole navbar at the top of the blog, which solves our NEXT BLOG dilema...</description>
		<content:encoded><![CDATA[<p>We have used blogger for a couple of years for class blogs and have hidden the whole navbar as a solution to the &#8220;next blog&#8221; button&#8230;we did this by a small code insertion in the template</p>
<p>The move to New Blogger simply required a different bit of code&#8230;add the following lines anywhere in the template [enclosed by  tags] and the blogger banner will disappear.</p>
<p>       #navbar-iframe {<br />
              height:0px;<br />
              visibility:hidden;<br />
              display:none;<br />
        }</p>
<p>This removes the whole navbar at the top of the blog, which solves our NEXT BLOG dilema&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Thompson</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14504</link>
		<dc:creator>Tim Thompson</dc:creator>
		<pubDate>Fri, 09 Mar 2007 17:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14504</guid>
		<description>Will,

Text Edit works fine for opening the XML file properly if you go through the Open dialog and check "ignore rich text commands."  I'll go through the rest of the procedure and see if I get any different results with the button...

Tim</description>
		<content:encoded><![CDATA[<p>Will,</p>
<p>Text Edit works fine for opening the XML file properly if you go through the Open dialog and check &#8220;ignore rich text commands.&#8221;  I&#8217;ll go through the rest of the procedure and see if I get any different results with the button&#8230;</p>
<p>Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan Silverman</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14502</link>
		<dc:creator>Susan Silverman</dc:creator>
		<pubDate>Fri, 09 Mar 2007 17:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14502</guid>
		<description>I'm a pc user and used the first Gecko &#38; Fly template but still have the next blog button.
http://kidspired.blogspot.com/
Any suggestions?</description>
		<content:encoded><![CDATA[<p>I&#8217;m a pc user and used the first Gecko &amp; Fly template but still have the next blog button.<br />
<a href="http://kidspired.blogspot.com/" rel="nofollow">http://kidspired.blogspot.com/</a><br />
Any suggestions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Meyer</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14493</link>
		<dc:creator>Dan Meyer</dc:creator>
		<pubDate>Fri, 09 Mar 2007 17:07:09 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14493</guid>
		<description>TextEdit Preferences &#62; Open and Save &#62; Ignore rich text commands in HTML files.

I use a Gecko &#38; Fly template for a personal blog and it's bye-bye "Next Blog" button.</description>
		<content:encoded><![CDATA[<p>TextEdit Preferences &gt; Open and Save &gt; Ignore rich text commands in HTML files.</p>
<p>I use a Gecko &amp; Fly template for a personal blog and it&#8217;s bye-bye &#8220;Next Blog&#8221; button.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Richardson</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14489</link>
		<dc:creator>Will Richardson</dc:creator>
		<pubDate>Fri, 09 Mar 2007 16:55:07 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14489</guid>
		<description>Thanks Bob...tried it and it worked...but that dreaded Next Blog button is still there! AAARRRGGHHHH! Hey Glenn, maybe it's just some of the templates??? Help!</description>
		<content:encoded><![CDATA[<p>Thanks Bob&#8230;tried it and it worked&#8230;but that dreaded Next Blog button is still there! AAARRRGGHHHH! Hey Glenn, maybe it&#8217;s just some of the templates??? Help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Cotter</title>
		<link>http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14488</link>
		<dc:creator>Bob Cotter</dc:creator>
		<pubDate>Fri, 09 Mar 2007 16:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://weblogg-ed.com/2007/blogger-next-blog-solution/#comment-14488</guid>
		<description>I used drag and drop to open the file with TextEdit, but the resulting text file when pasted into Blogger generated errors. I then drag and dropped the file onto Word and the resulting text file not only looked different, but when copied and pasted into Blogger worked as expected with some minor issues.

I have lost some of the side elements, my Flickr badge, my Clustmap, and a few other things and so did not save the changes until I can figure out how easily it would be to get those elements back. 

So, I did not save the changes. Nothing to look at there, as I did not want to lose what I had. Next step... figure out how to incorporate those elements again.</description>
		<content:encoded><![CDATA[<p>I used drag and drop to open the file with TextEdit, but the resulting text file when pasted into Blogger generated errors. I then drag and dropped the file onto Word and the resulting text file not only looked different, but when copied and pasted into Blogger worked as expected with some minor issues.</p>
<p>I have lost some of the side elements, my Flickr badge, my Clustmap, and a few other things and so did not save the changes until I can figure out how easily it would be to get those elements back. </p>
<p>So, I did not save the changes. Nothing to look at there, as I did not want to lose what I had. Next step&#8230; figure out how to incorporate those elements again.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
