Since the last big release is a while back, I thought I’d let everyone know that the current Lightning 2.6 nightly builds on comm-central will become the release compatible with Thunderbird 24, the next big Thunderbird release.
What this means for localizers
When the current 6 weeks cycle ends, the code will merge down to comm-aurora as usual. At this moment you should be preparing your translations and signing off. There is no process change, you will still have time until the beta, but especially if you have a lot of untranslated strings you might want to start early. While the intermediate beta releases have not been so important, missing the deadline this time means up to 42 weeks of Lightning without your language.
What this means for developers
Have a patch you are working on? A nice new feature? Better get it in review soon, otherwise we might have to postpone it. Especially so if it contains string changes, additions or removals. Again, postponing means at least 42 weeks before its in the final release.
What this means for users
It is vitally important that you test the Lightning builds we offer. Given we haven’t had final releases in a while more regressions might have snuck in and its better we find them early. It would be super helpful if you could test the nightly builds, but if you want a little more safety, there is a test week in progress for Thunderbird and the current Lightning beta. You are of course encouraged to install the beta builds at any time. I personally use them for my production calendars.
While Thunderbird is having a test week, we’ve released the version that goes with it 2.4b1.
We are interested in catching regressions with regards to : Alarms, CalDAV Servers and Email Invitations.
The beta is on AMO now, I think the most user friendly link is https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/?page=1#version-2.4b1.
Hello Folks. If you have been using Lightning 2.3b1 with a localized version of Thunderbird, you probably had troubles with undefined entities. This happened due to a glitch with the Mozilla localization dashboard, the wrong changeset was used.
I have just uploaded Lightning 2.3b2, which should fix the issue. As always, you can download beta versions from the addons.mozilla.org site in the “Developer Channel” box. If you have previously installed a beta, you should get the update via automatic updates.
We are happy to announce that a Release Candidate for Lightning version 1.9.1 is now available for testing here. For those using linux, please use the build in the linux/ folder rather than the platform-specific folders. Windows users can find their builds in the “unsigned” folder.
This version fixes an issue that prevents some events from being modified and some reminders from being dismissed in CalDAV calendars with Offline Support enabled – those affected are encouraged to test this build. If you have seen an error message with “this.mItemInfoCache[aNewItem.id] is undefined”, this is you! Be sure to reset your cache, by unchecking the “Offline Support” checkbox, restarting, then checking it again.
The full list of changes in this version can be found here.
It is really important that you test this pre-release, as it will become the next release for Thunderbird 17. There is no additional beta phase, this is it! If you are using Thunderbird 17, please give it a try and let us know if you encounter any errors.
As you likely noticed, Lightning 1.9 was recently released. Aside from the common issues during an update, the most reported problem was that calendars were no longer working. In almost all cases, the solution for this issue is to also update the Provider for Google Calendar to version 0.18. A function in Lightning was changed that was used by the Provider version 0.17, hence the update.
For an unknown reason, the addons manager did not find the update of the Provider for Google Calendar to version 0.18. We have mitigated this by blocking the older version of the extension on addons.mozilla.org, but we have yet to find the reason this has happened in the first place.
The next release is still a while away, but if you experience issues in a future update, please make sure you are using the latest version of all relevant extensions.
If you are having a different error, please check out the Error Console in the Tools menu and comment with any relevant messages by comment. Also, in the advanced config editor (Preferences → Advanced → General → Config Editor) there is a preference called “calendar.debug.log” and “calendar.debug.log.verbose” which you can set to true to get additional messages regarding your problem.
I have heard a few reports that calendars are not showing after upgrading to Lightning 1.8. I’d really like to get to the root of the problem and find out if this a code regression or something different. If you are having trouble please comment with the following information:
- Make sure you are using the right version combination: Lightning 1.8 is compatible to Thunderbird 16.
- Do you have any other addons installed? I’ve heard about some trouble with the “Calendar Tweaks” extension for example.
- Open Tools → Error Console and tell me about any error messages you see there
- Are any calendars no longer in the calendar list on the left side?
- What kinds of calendars do you have? Local? CalDAV? Google Calendar via the Provider? Other?
- If you are using the Provider for Google Calendar, what version do you have installed?
Update, with a few common issues:
- If you are using the Calendar Tweaks Extension, make sure to update to version 4.3.
- If you are using Lightning 1.8 and the Provider for Google Calendar, please make sure you are using Provider version 0.17
- If you have a virus scanner that quarantines files, please make sure calbasecomps.dll is not quarantined. Reinstalling Lightning might help.
Lightning 1.9b2 is now available on addons.mozilla.org. It is compatible to Thunderbird 17 and its betas, which will also be released as Thunderbird 17 ESR. This means testing is more important than ever, since this is a version that will stick around a bit longer.
This is why we need you! Without your testing work, possibly critical bugs might go by unnoticed. Not only does this mean extra pain for the end user, it also means more work for us to do emergency releases.
Please take a moment to download Thunderbird 17 beta and Lightning 1.9b2 and report any issues you find. There have been quite a few fixes in printing support and some drastic changes to the cached calendar / offline support. Your main area of testing should therefore be printing and any kind of cached calendar, for example with a CalDAV server or the Provider for Google Calendar. For those of you using WCAP, support for the cache has been restored in this release too.
Of course I’m eager to hear about problems in any other area, so give it a try and either comment here or file a bug!
Hello Nightly testers,
I am happy to announce that we now have updated nightly builds for Daily and Earlybird. You may have noticed that for quite some time the builds were missing. The problem behind this was again our build machinery, there were some changes we needed to adopt so that the builds work again.
Fixing the issue wasn’t very hard, but since I was busy with exams and other patches that needed to be pushed before the last release, I haven’t gotten around to it. This again shows that we really need more people on the build side. If you know some python and are interested in fixing build configuration issues, please do email me.
Also, those of you using Thunderbird 16 Beta, I have just uploaded Lightning 1.8b1 to addons.mozilla.org. If you have installed a beta version in the past, you will automatically get an update from 1.7b3 to 1.8b1, otherwise you need to download the beta version manually.
As you may have seen, Lightning 1.7 has been released. There are no major UI changes, most of the bugs fixed are us running after the changes in the core Mozilla platform (most notably removing e4x support, fixing sqlite statement wrappers) and backend fixes (cure excessive getItems requests when accessing calendars).
We have some improvements for Mac users in this release though: there is now support for some gestures in the calendar views. If you are on mac (or another machine with a touchpad that supports gestures), try the usual pinch, rotate and swipe gestures in the day, week, multiweek and month views.
Also, as mentioned in the previous blog post, I have rewritten the printing support to accommodate for the e4x backend changes. There might be some kinks, so please continue testing the print support in the release and file bugs or at least comment here as necessary. We have already noticed the “All day – All day” bug.
You can view the full list of changes here on bugzilla.
Note also that if you are using the Provider for Google Calendar, you must update it to version 0.16. If you do not get the new version via automatic updates, please download it here from addons.mozilla.org.