Created attachment 557510 [details] test case: Email exhibiting the issue I recently received the attached email (edited to for privacy reasons), containing a meeting invitation. The message body was completely blank with Lightning nightly enabled in Shredder nightly. Disabling Lightning allowed the to be viewed. Tested with most recent builds, as of this posting. Uploading the message to Gmail, the content, including the calendar/invitation content can be viewed without issue.
Do you get any error console messages?
What version / build of Thunderbird do you use? What version / build of Lightning do you use?
As I mentioned in comment 0, I use Shredder nightly (9.0a1) and Lightning nightly (1.1a1pre).
Figured out the causes: version confusion. There are two Lightning nightlies and both have the exact same version number. One is on the FTP server under http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-comm-central and the other is on the FTP server under http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly It would be great it these are named differently and given different version numbers, as this is needlessly confusing. Thanks
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
<https://developer.mozilla.org/en/Calendar/Calendar_Versions> links to the correct Lightning nightly builds for your Thunderbird version.
Thanks. Still would be nice to have different names/version numbers, though.
I filed bug 685528 to fix version numbers. Which nightlys have the same version? comm-central should have 1.1a1pre comm-aurora should (wrongly, currently) have 1.0b6pre there is no comm-beta nightly
There is also this link: http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly The builds in there have version number 1.1a1pre, but if you look at the install.rdf, it is not for Shredder nightly. Those builds don't seem to be targeted at anything, so I'm thinking they either should match comm-central or be removed. That is what I installed that gave me grief.
You need to log in before you can comment on or make changes to this bug.