Hi,
summary: 2 feeds "went missing" after update. 1 could not be added
again, since SM believed still to be subscribed to it.
Removing entries from feeds.rdf helped to be able to re-subscribe.
Anybody else?
Long version:
I updated to SM2.25b2 beginning of this week. (Directly from
SM2.24b/latest.)
I noticed 1 folder in my Feeds section did not update since.
Today I checked the subscriptions for that folder, and SM showed there
to be none.
I shrugged (no drama, like e.g. with missing mails; it's temporary and
autogenerated data anyway.) and wanted to re-activate the feeds from the
original web page. (heise.de and some sub-area of it.)
First feed went fine, was registered from browser bar quick item.
I moved the output to the desired folder, move the already downloaded
new items, deleted the newly generated folder (not the subscription
itself, of course) and was happy.
With the second feed, SM tells me: "feed already exists / subscribed".
I exported the list from the Mail/Feeds folder subscription management:
Feed URL is not in there.
I went to my profile:
/Users/pvh/Library/Application
Support/SeaMonkey/Profiles/XXX.default/Mail/Feeds
and feeds.rdf _does_ contain the URL.
1x as "RDF" list entry.
1x as fs:feed item. With empty "lastModified" value.
I can only assume, the UI has some different "list" of feeds, and
accepts the new feed. But then validation in some "backend" fails, since
it's already registered there. However, that entry in feeds.rdf does not
make the mail component update the feed.
Actually, at this point I tried to manually delete the lines in
feeds.rdf about the "broken" one. After a restart of SM, I could now
re-add the feed via subscribing to it. Seems to work fine now again.
Still, something must be amiss for SM to get confused.
Was it just me (or my profile), or did anybody else see something
similar with SM2.25b/1-2 ?
BR/Philipp
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey