Jens Hatlak schrieb:
I also ran into some issues (namely the "feed already exists" case), but
wasn't sure whether it was due to me accidentally removing some feed
folders which might have broken some connections between feed sources
and corresponding destination folders.

In my case, I'm 100% sure, I hadn't changed anything recently for weeks.

In the end I went through feeds.rdf and compared the folder paths listed
there with the actual (designated) destination folders. Whenever the
folder paths listed in feeds.rdf were different, I created any the
folder hierarchies that were missing. After that, the missing feed
sources reappeared in the Feed Subscriptions dialog, from where I could
re-associate those entries with the designated destination folders.
Finally I removed the newly created folder hierarchies and I was done.

Ah, okay, I did not delve that deep into the structures.
But I guess deleting the entries would also "rectify" the misalignment you describe.

Maybe there's a regression involved here. The whole feeds/subscriptions
code has been refactored quite a bit lately by the responsible TB
developer.

Seems like. One reason I posted here. (Collecting evidence.)
Maybe related to updating? Or maybe a new check (comparing folders stored in feeds.rdf with reality) which was not there before? So that folders which were redirected in the UI towards other folders (something I do usually to not have 1 folder per feed, but per topic/source) now suddenly were invalid, where checking was different/lacking beforehand (relying on some other place for the mapping)? (Just a guess. My profile is... ah... really old. If there was data corruption in a previous release, that could have been long ago.)

I could go back into TimeMachine and check, whether the file was "corrupted" at the point of update, or whether the (assumed) folder misalignment was present beforehand.

BR/Philipp

_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to