Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Saved searches dead in TB 102.5.

  • 3 odgovora
  • 0 ima ovaj problem
  • 3 prikaza
  • Posljednji odgovor od Wayne Mery

jmacauslan
jmacauslan
more options

I just upgraded from TB 91.something to 102.5. (No, I didn't install 102.0, I just upgraded in the usual in-app fashion.)

(1) My saved-search folders are non-functional -- just blank lines. (2) Even the Saved Search item on the File>New menu is completely absent. So I also can't create new ones.

(Help! One of these functions as my "true" inbox for virtually all incoming email.)

FWIW: Windows 10 (latest rev) on MS Surface Pro.

I just upgraded from TB 91.something to 102.5. (No, I didn't install 102.0, I just upgraded in the usual in-app fashion.) (1) My saved-search folders are non-functional -- just blank lines. (2) Even the Saved Search item on the File>New menu is completely absent. So I also can't create new ones. (Help! One of these functions as my "true" inbox for virtually all incoming email.) FWIW: Windows 10 (latest rev) on MS Surface Pro.

Izmjenjeno od jmacauslan

Svi odgovori (3)

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

You will need to recreate them. Rename VirtualFolders.dat in your thunderbird profile.

jmacauslan
jmacauslan Vlasnik pitanja
more options

Thanks, Wayne! 1. Why in the world wasn't this documented, even by a week after the release? 2. Is the problem understood? A quick check shows that the old and new VirtualFolders.dat files (which are both text, and rather short) are extremely similar -- enough that surely at least a meaningful error message would have been feasible about whatever the incompatibility is.

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

> 1. Why in the world wasn't this documented, even by a week after the release?

Because it is an uncommon problem, and we don't flag uncommon problems.

> 2. Is the problem understood? A quick check shows that the old and new VirtualFolders.dat files (which are both text, and rather short) are extremely similar -- enough that surely at least a meaningful error message would have been feasible about whatever the incompatibility is.

No, it is not well understood. Which is one reason why no additional corrective work has been possible.