| Summary | Receiving notification for own events - even if disabled |
| Queue | Kronolith |
| Queue Version | 4.2.28 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | |
| Requester | admin (at) layertec (dot) de |
| Created | 07/09/2020 (1823 days ago) |
| Due | 07/10/2020 (1822 days ago) |
| Updated | 07/09/2020 (1823 days ago) |
| Assigned | |
| Resolved | 07/09/2020 (1823 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Priority ⇒ 2. Medium
['private']
the "check" in line 2145 of lib/Kronolith.php
if (!$vals) {
continue;
}
never returns true
Has this change been tested at all?
Priority ⇒ 3. High
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Due ⇒ 07/10/2020
Summary ⇒ Receiving notification for own events - even if disabled
Type ⇒ Bug
State ⇒ Unconfirmed
have been hidden in this release.
Creating a (private) event triggers a notification to the creator even
if it is disabled by configuration "event_notification_exclude_self".
Furthermore the time format within notification changed to 12h-Format
but there is no way to change it back to 24h. The general user setting
"twentyFour" is ignored in notification emails
Do not change application behavior on security fixes!