RSS Feed does not download articles after 38.x to 91.x. upgrade.
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: jhibbard, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; U; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.91 Safari/537.36
Steps to reproduce:
Clicked Save on new article (mp3)
Actual results:
Nothing.
Since update to 91.x from recent notification that there was an update available, RSS articles do not download at all. Previous version updated was the version immediately available - 38(?). Sorry, nothing left to look this up.
Notes:
The "Save" appears to initiate but never does; e.g. nothing d/ls and there are no error messages.
If I CTRL-J, there is nothing in the list
Interesting side affect: The d/l subdirectory does get updated to the current date. I am setup to have each target subdirectory specific to the feed name. So, if I 'Save' a file from Feed '123', the target is also called '123'; Feed '456' d'ls to subdirectory 456.
I am not sure if this is installer related or if it is something in the RSS d/l code.
Finally, your URL says that there is no auto update available for 38.x to 91.x.
Expected results:
'Save' should show a general view of previously used target subdirectories. In several cases, this sometimes chooses the correct subdirectory. Once I confirm a target subdirectory, the d/l begins.
In my case, as soon as I pick a target directory, this process closes this window and puts me back into the main window of TB. No error messages or non-functioning happens in any of this. As stated above, CTRL-J shows nothing d/ling.
Comment 1•4 years ago
|
||
Sorry but you cannot upgrade directly from 38 to 91 without loosing feed subscriptions. You have to go through the appropriate watersheds that automatic upgrades take you through.
The data format the feeds are stored in changed IIRC 60->68.
Updated•4 years ago
|
Your response is unclear / not complete:
- If upgrade is not working, why did TB 68.x notify that an update was available?
- "You have to go through the appropriate watersheds that automatic upgrades take you through." What does that mean?
a. Do I have to downgrade to 68 to continue d/ling
b. Is there some manner of 'adapting' 91.x -or- data? - "The data format the feeds are stored in changed IIRC 60->68." What does that mean? Are you saying that the data format of TB 60.x - TB 68.x Feeds is different than TB 91.x? If so, return to 1. above.
Comment 3•4 years ago
|
||
Did you upgrade from within product, automatically? Or did you download something and install manually?
Automatic upgrades will go through watersheds to migrate you properly, but if you downloaded something manally - there can be problems.
Yes, data format of feeds changed yes, actually from 68->78.
I got a notification that an update was available. I confirmed that I wanted to proceed. The process completed without an error message and told me to restart TB. I did.
RE: Versions involved on my side. I was using 68.x when I got the notification described above.
So, now the issue is, how do I fix the acknowledged issue?
Addenda:
It seems at least interesting that the process involved did not include anything to do with 78.x. I went from 68.x -> notification -> 91.x. I did not get a notification that 78.x was available.
Comment 6•4 years ago
|
||
Rob, do we have appropriate watersheds in place, see bug 1534163.
jhibbard:
1: we assume update is possible (investigating now if there's a bug)
2: it's not directly possible, data is not compatible downwards (you should have been brought through something like -> 45.02 -> 57.0x -> 68.0x.), it's probably easiest to resubscribe (or with the old profile, export an opml, import it in the new)
3: yes, feeds data was migrated to the new format in 78. If you skipped that version it can't be migrated.
- OK. Seems Probable given it happened for me as described.
- I started with TB whenever it was first made available (looks like my earliest RSS message is early June 2005) and have used update notifications since. It truly sucks that I was not notified that 78.x was available as an update. Can you expand on steps for opml export and 'import as new'?
- Didn't skip 78.x -- wasn't notified.
Is it even useful to consider trying to install 78.x to see if it helps and then updating to 91.x?
Comment 8•4 years ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #6)
Rob, do we have appropriate watersheds in place, see bug 1534163.
There is a watershed at 78.14.0.
So updates should have gone to 60.9.1 -> 68.12.1 -> 78.14.0 -> 91.1.2. (en-US, other locales should not go past 78.14.0)
So, it could be a clear case (on my part) of CRS or it could be a touch of desperation, but as I said at the beginning of this thread, I did NOT check what version I was running when I responded to the notification of a new version being available. In my mind, it was 68.x based on my thinking that it had been quite awhile since I had updated and, having checked several times with the website if the blurb that there was no automated update to 91.x had been changed. That blurb was still in place when I started this thread.
Also, since the only symptoms of this issue is that I cannot d/l articles from feeds. Might that indicate that I had 78.x installed when I responded to the update notification for 91.x? Please note that I have no other issues beyond this d/ling problem -and- the entire d/l process runs without pause or error message through the point that I confirm to save the d/l. And, even then, the only failure is that nothing d/ls and that CTRL-J shows no files in process. There are NO problems with running 91.x and I have a fairly active EMail flow.
Whatever the case, I do have backups but have no idea how to revert to a prior version to:
- Find out for sure what version I was running when I responded to the notification of update to 91
- Actually go back to whatever appropriate version I need to:
a. get back to a point where I can actually d/l new articles from feeds
b. get back to a point where I can actually update to 91.x without these feed d/l issues
So, what files that I have in my backups do I need to accomplish the above? And, are there necessary registry entries I will need to edited?
Comment 10•4 years ago
|
||
| Reporter | ||
Comment 11•4 years ago
|
||
So, TB just notified me that there is an update available. Do I take it or not? If I do, do all chances to get Feeds to d/l go away permanently?
Also, what does "Status: RESOLVED INVALID" mean? Am I wasting everybody's time with trying to get a resolution to this issue?
| Reporter | ||
Comment 12•4 years ago
|
||
So, this is not working for me.
Current status is that the TB installation (91.1.2) described above is now d/ling articles under very specific conditions. If I tell TB to "Open" an article, it works as expected. However, if I tell TB to "Save" (any of the available choices of save), then the behavior has not changed from above; it simply will not initiate the save.
To be clear: If I click Open a RSS article, a window pops up to that gives me a choice to open or save. If I then choose "Save", the d/l begins (and finishes). I just ran through a little over 30 d/ls doing it this way.
Does this not seem strange that I can Open - Save these articles WHILE Save - Save does not initiate the transfer?
What is it that I have to do to resolve this?
Comment 13•4 years ago
|
||
Upgrade to the latest, 91.2.1.
| Reporter | ||
Comment 14•4 years ago
|
||
91.2.1 resolved this. Save article now initiates the download.
Description
•