FoF 0.1.8
I’ve had all these minor improvements in my private version of Feed on Feeds for the longest time, but didn’t think it was quite enough for a release. But the release of MagpieRSS 0.7 finally pushed it over the edge. So get 0.1.8 now!
I’ve had all these minor improvements in my private version of Feed on Feeds for the longest time, but didn’t think it was quite enough for a release. But the release of MagpieRSS 0.7 finally pushed it over the edge. So get 0.1.8 now!
REPLY))
[...] t i_xml — hipslu @ 07:41
endlich! mein liebster rss-reader steht in einer neuen version zur verfügung; neben dem upgrade zu MagpieRSS 0.7 wurden ein [...]
REPLY))
I just noticed the new version, I like the new [old_to_new] view :). A tiny issue: for some reason the age never changes from never to something else like it used to, even though the feeds do get updated. Anyway, thank you for the effort you put in this, I use feed on feeds every day :)
REPLY))
Those ages should still update. Actually, the naming convention for cached files changed in Magpie 0.7, but I made the appropriate change in the FoF code to reflect this. After you install 0.1.8, all of the dates should flip to “never” (or “∞” in the frames view), but after your first update they should be correct again.
REPLY))
I had a look myself, and it turns out MAGPIE_OUTPUT_ENCODING is not being defined, atleast not before the call to fof_rss_age (). Calling init() from magpierss/rss_fetch.inc at the appropriate place fixes it.
REPLY))
MAGPIE_OUTPUT_ENCODING is defined in config.php, which is the first thing included in all pages. Maybe when you installed 0.1.8 you copied your old config.php over from your previous installation? In that case it would be missing the (new) line required to define this.
REPLY))
woops, you’re right. my mistake :). i should’ve checked that, thanks.
REPLY))
Maybe I should have had some sort of warning that config.php has changed in this version. Well, at least anybody else reading this will know!