Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thunderbird lightening calendar export/import

  • 4 replies
  • 8 have this problem
  • 102 views
  • Paskiausią atsakymą parašė yolk100

more options

Since updating Thunderbird to 102, I can no loger import the lightening calendar. Exporting a .ics file from one pc works but on trying to import it into any other pc or the same one, I get "No importable items found in the file". Any help would be appreciated.

Since updating Thunderbird to 102, I can no loger import the lightening calendar. Exporting a .ics file from one pc works but on trying to import it into any other pc or the same one, I get "No importable items found in the file". Any help would be appreciated.

All Replies (4)

more options

Are you importing the .ics file to a local calendar or to a network calendar (e.g. CalDav)?

more options

I found a workaround but it's not very good. Create and .ics file, import it into a Google calendar, export into an .ics file and import the .ics file into Thunderbird. The problem is that the import will fail if you try importing into an existing calendar. It will work only if you import it into a new one.

Tom, to answer your question: the problem is with a local calendar. It happens even when I export and try importing to the same calendar. Has nothing to do with networks.

more options

Thank you for the advice. I have not used Google calanders but might try your work-around. In the past I had no problem in updating Thunderbird calanders on several different systems by just exporting and importing. If this is no longer possible, it seems to be a serious flaw, making Thundirbird no longer a useful tool. Will Thundirbird be updated to correct this fault? It would also be helpfull if Thunderbird updated, as it used to, without having to re-install.

more options

I wish that someone at Mozilla paid attention and corrected this problem. Hopefully the next update.