<?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: Feed2RSS: Minor Cleanups and Fixing My Goofs</title>
	<atom:link href="http://cogdogblog.com/2004/05/26/feed2rss-minor/feed/" rel="self" type="application/rss+xml" />
	<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/</link>
	<description>Alan Levine's blog space for barking about instructional technology</description>
	<pubDate>Sat, 22 Nov 2008 05:32:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Alan Levine</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-578</link>
		<dc:creator>Alan Levine</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-578</guid>
		<description>More doh! D'Arcy just ichatted me in the middle of a dull meeting (bless wireless)- with a parse error on line 100- it was a missing semi-colon on the end of line 97. Just uploaded a replacement.



-- King of typos</description>
		<content:encoded><![CDATA[<p>More doh! D&#8217;Arcy just ichatted me in the middle of a dull meeting (bless wireless)- with a parse error on line 100- it was a missing semi-colon on the end of line 97. Just uploaded a replacement.</p>
<p>&#8211; King of typos</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Schellenberg</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-579</link>
		<dc:creator>Dan Schellenberg</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-579</guid>
		<description>I have the script working properly at:

&lt;a href="http://educationaltechnology.ca/test.html"&gt;http://educationaltechnology.ca/test.html&lt;/a&gt;



Check the source out there, though it is essentially the same as described above by Allan.



It seems to be working fine, and is validating properly as well (click on the valid XHTML link at the bottom of the page).</description>
		<content:encoded><![CDATA[<p>I have the script working properly at:</p>
<p><a href="http://educationaltechnology.ca/test.html">http://educationaltechnology.ca/test.html</a></p>
<p>Check the source out there, though it is essentially the same as described above by Allan.</p>
<p>It seems to be working fine, and is validating properly as well (click on the valid XHTML link at the bottom of the page).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Levine</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-580</link>
		<dc:creator>Alan Levine</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-580</guid>
		<description>Thanks much Dan. The problem was I was testing the embedded JavaScript URLs directly to the browser (where &#038; is replaced by &#38; in the CGI params). When in the source HTML, the &#38; are rendered BACK to &#038; for the links, and thus it works well.



I will look into changing the build script to do this substitution, but if XHTML compliance is key, you can do some editing on your JavaScript embeds.</description>
		<content:encoded><![CDATA[<p>Thanks much Dan. The problem was I was testing the embedded JavaScript URLs directly to the browser (where &#038; is replaced by &amp; in the CGI params). When in the source HTML, the &amp; are rendered BACK to &#038; for the links, and thus it works well.</p>
<p>I will look into changing the build script to do this substitution, but if XHTML compliance is key, you can do some editing on your JavaScript embeds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: todd</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-581</link>
		<dc:creator>todd</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-581</guid>
		<description>It seems to be working for me at &lt;a href="http://idea.matc.tec.oh.us/feeds"&gt;http://idea.matc.tec.oh.us/feeds&lt;/a&gt; --thanks for your work! I need to look into the cache settings because I've had it up for about a day and I don't see any files in my cache directory.



Also, my blog doesn't publish date with dc but uses pubDate; got any hints for fixing that :) ?</description>
		<content:encoded><![CDATA[<p>It seems to be working for me at <a href="http://idea.matc.tec.oh.us/feeds">http://idea.matc.tec.oh.us/feeds</a> &#8211;thanks for your work! I need to look into the cache settings because I&#8217;ve had it up for about a day and I don&#8217;t see any files in my cache directory.</p>
<p>Also, my blog doesn&#8217;t publish date with dc but uses pubDate; got any hints for fixing that <img src='http://cogdogblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Levine</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-582</link>
		<dc:creator>Alan Levine</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-582</guid>
		<description>Todd, Magpie creates cryptic named cache files, e.g.



896308a033830edc06253e2838ad8644

37f206fd8a53505bc87d38dd63fb9f38

06c6631ffb0ab9639e4a631049b5ad8a



but I am not sure how/when it decideds to create a new one. It looks like they each correspond to a different RSS URL.



I am not sure how you are trying to view the files, it may be they are hidden becaise of their naming style? I'd have to investigate to see why it would not be writing files. If you are not getting PHP errors than it must be dealing with write permissions okay.



As far as the way the date values are accessed, this is the beauty of Magpie- no matter what XML tag is used to define the date (pudDate, dc:date. etc) Magpie finds it and returns it to an array always named dc:date-- it does not mean that your pubDate values are ignored, they are just referenced by a different name later. This way, my script does not have to do all kinds of branching depending on the RSS feed type.



I have tested this on RSS 2.0 feeds that use pubdate and it works as advertised.</description>
		<content:encoded><![CDATA[<p>Todd, Magpie creates cryptic named cache files, e.g.</p>
<p>896308a033830edc06253e2838ad8644</p>
<p>37f206fd8a53505bc87d38dd63fb9f38</p>
<p>06c6631ffb0ab9639e4a631049b5ad8a</p>
<p>but I am not sure how/when it decideds to create a new one. It looks like they each correspond to a different RSS URL.</p>
<p>I am not sure how you are trying to view the files, it may be they are hidden becaise of their naming style? I&#8217;d have to investigate to see why it would not be writing files. If you are not getting PHP errors than it must be dealing with write permissions okay.</p>
<p>As far as the way the date values are accessed, this is the beauty of Magpie- no matter what XML tag is used to define the date (pudDate, dc:date. etc) Magpie finds it and returns it to an array always named dc:date&#8211; it does not mean that your pubDate values are ignored, they are just referenced by a different name later. This way, my script does not have to do all kinds of branching depending on the RSS feed type.</p>
<p>I have tested this on RSS 2.0 feeds that use pubdate and it works as advertised.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Carter-Tod</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-583</link>
		<dc:creator>David Carter-Tod</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-583</guid>
		<description>I haven't installed these latest versions yet, but on the first version, I couldn't get the cache to work until I created a directory called "cache" (not "cached") with the right permissions (775 should do it by the way, not 777).



Also, although the code seems to support it, I'm not seeing etags coming through.  This is a critical bandwidth saver.



David</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t installed these latest versions yet, but on the first version, I couldn&#8217;t get the cache to work until I created a directory called &#8220;cache&#8221; (not &#8220;cached&#8221;) with the right permissions (775 should do it by the way, not 777).</p>
<p>Also, although the code seems to support it, I&#8217;m not seeing etags coming through.  This is a critical bandwidth saver.</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Carter-Tod</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-584</link>
		<dc:creator>David Carter-Tod</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-584</guid>
		<description>Oh, and those long, convoluted strings for file names look like MD5 encodings of the url requested.  It's a guaranteed way to get a unique id.



David</description>
		<content:encoded><![CDATA[<p>Oh, and those long, convoluted strings for file names look like MD5 encodings of the url requested.  It&#8217;s a guaranteed way to get a unique id.</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Levine</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-585</link>
		<dc:creator>Alan Levine</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-585</guid>
		<description>David,



I've not run into an issue with Magpie needing a specific name for the cache directory/ It looks like it tries to create on named "cache" if is not defined, but my tests show ti writing to ones name "cached"-- though it would not hut to suggest the default name.



As far as permissions (which I am hardly a master of mostly a slave), it may vary depend on how servers are set up and wether the process that runs the server is consider a "group" owner. The code comments read:



" * MAGPIE_CACHE_DIR - Where should Magpie cache parsed RSS objects?

 * This should be a location that the webserver can write to.   If this 

 * directory does not already exist Mapie will try to be smart and create 

 * it.  This will often fail for permissions reasons."



I usuallly go 777 for places my webserver needs to write to. But I cannot say I tested with 775.



And I would need to know more of what an "etag" is to comment. I would prefer not to try and do wild parsing on different versions of RSS feeds...</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>I&#8217;ve not run into an issue with Magpie needing a specific name for the cache directory/ It looks like it tries to create on named &#8220;cache&#8221; if is not defined, but my tests show ti writing to ones name &#8220;cached&#8221;&#8211; though it would not hut to suggest the default name.</p>
<p>As far as permissions (which I am hardly a master of mostly a slave), it may vary depend on how servers are set up and wether the process that runs the server is consider a &#8220;group&#8221; owner. The code comments read:</p>
<p>&#8221; * MAGPIE_CACHE_DIR - Where should Magpie cache parsed RSS objects?</p>
<p> * This should be a location that the webserver can write to.   If this </p>
<p> * directory does not already exist Mapie will try to be smart and create </p>
<p> * it.  This will often fail for permissions reasons.&#8221;</p>
<p>I usuallly go 777 for places my webserver needs to write to. But I cannot say I tested with 775.</p>
<p>And I would need to know more of what an &#8220;etag&#8221; is to comment. I would prefer not to try and do wild parsing on different versions of RSS feeds&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerry Paille</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-586</link>
		<dc:creator>Gerry Paille</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-586</guid>
		<description>I am not getting anything written to the "cached" directory either. I have tried using David's suggestion by renaming the directory to cache and double checking the permissions. I also deleted the "cached" directory all together to see if Magpie would create a new directrory and it did not.</description>
		<content:encoded><![CDATA[<p>I am not getting anything written to the &#8220;cached&#8221; directory either. I have tried using David&#8217;s suggestion by renaming the directory to cache and double checking the permissions. I also deleted the &#8220;cached&#8221; directory all together to see if Magpie would create a new directrory and it did not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerry Paille</title>
		<link>http://cogdogblog.com/2004/05/26/feed2rss-minor/#comment-587</link>
		<dc:creator>Gerry Paille</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2004/05/26/feed2rss-minor-cleanups-and-fixing-my-goofs/#comment-587</guid>
		<description>I have the cache working, but I'm not 100% sure what I did that caused the change. I think it is pretty much as Dave described above. I changed the name of the directory from cached to cache and edited the feed2js.php file to reflect the name change. The permissons for the cache directory look like this:



drwxrwxrwx  4 admin  admin    136 31 May 13:39 cache</description>
		<content:encoded><![CDATA[<p>I have the cache working, but I&#8217;m not 100% sure what I did that caused the change. I think it is pretty much as Dave described above. I changed the name of the directory from cached to cache and edited the feed2js.php file to reflect the name change. The permissons for the cache directory look like this:</p>
<p>drwxrwxrwx  4 admin  admin    136 31 May 13:39 cache</p>
]]></content:encoded>
	</item>
</channel>
</rss>
