Feeds aren't actually deleted when deleted (646)
Brought to you by:
toomastoots
Menu
▾
▴
#159 Feeds aren't actually deleted when deleted (646)
Another odd little one that might have wider ranging
consequences...
Enable the internal webserver and go to http://127.0.0.1/
to view it in a separate browser.
In FeedReader, add a new feed (I'm using http://www.
drobe.co.uk/rss-comments.php as the example 'cos it's in
the clipboard buffer) and when prompted for the name,
call it 'Dummy feed' and press Finish.
Now reload the internal webserver page. Notice that
'Dummy feed' is at the bottom.
Return to FeedReader, select 'Dummy feed' and delete it.
Reload the internal webserver page and see that 'Dummy
feed' is still in the list.
Return to FeedReader and add a new feed (again http:
//www.drobe.co.uk/rss-comments.php 'cos it's easy) and
this time give it the name 'Another dummy feed'.
Back to the internal webserver page and press reload.
You now have 'Dummy feed' and 'Another dummy feed' at
the bottom of the page.
Delete 'Another dummy feed' in FeedReader and then
reload the internal webserver page and you'll see that it's
still there.
All this is showing is that caching is not getting in the
way and that FeedReader really does think that those
feeds you deleted are still around. Whilst this is probably
not a huge problem, if you've had FR running a while it
may mean that it's leaked memory. If you've added things
and deleted them because you didn't want them
appearing on a 'public' server (you might be providing it
publically) then those deleted feeds are actually being
disclosed to people even though you think they're gone.
Logged In: YES
user_id=222505
<later that week>
I just got a 'Hierarchy error', I think it said, about 'Another
dummy feed'. The feed in question had been deleted as I
mentioned above two days ago. And yet I still get an error
about it. That can't be good :-)