Open
Bug 473927
Opened 16 years ago
Updated 2 years ago
Invitations from Multiple calendars not always required.
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Tracking
(Not tracked)
NEW
People
(Reporter: tsneller, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/1.0.154.43 Safari/525.19 Build Identifier: Thunderbird 2.0.0.19 - Lightning 0.9 If you have multiple Network calendars set up, it is possible to ignore alarms from any individual calendar, but not possible to ignore invitations. I have 5 calendars set up, for various work colleagues, so I can see what the rest of the team is doing, but I only want to deal with invitations sent to me personally. Reproducible: Always Steps to Reproduce: 1. 2. 3. Ignoring invitations for some calendars would also reduce processor usage.
Comment 1•14 years ago
|
||
Sounds like a valid request, confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
The new Bug #733695 (duplicate of this one?) mentions the preference calendar.registry.<HASH>.showInvitations. At the moment, this preference seems to be ignored. This preference would resolve this request, and it should also be accessible from the calendar properties dialog.
As mentioned in Bug #532993, this preference, if handled correctly, should possibly default to "false" for read-only calendars and to "true" for read-write calendars.
Comment 6•12 years ago
|
||
With TB17/Lightning1.9 (and an updated Connector/Integrator) this issue still remains unresolved: calendar.registry.<HASH>.showInvitations (as mentioned in #733695) is set correctly according to read/write permissions. Invitations from wrong calendars are still shown although "showInvitations" is set to false for the respective calendar. It would be really great if someone could give at least a pointer to which part of Lightning requires modifications to respect/use "showInvitiations" property.
We too are affected by this bug. And it shows up even more frequently, now that we have migrated to SOGo 2 and Thunderbird 17/Lightning1.9.1 (from 3.1.19).
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•