Bug 359314

Summary:	Folder property "Block reminders locally" is never applied
Product:	[Applications] korganizer	Reporter:	Enrico Tagliavini <enrico.tagliavini>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	montel, till2.schaefer
Priority:	NOR
Version:	5.4.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Enrico Tagliavini 2016-02-12 12:11:15 UTC

Version of Korganizer (it's missing in the drop down list): 4.14.10
KDE Development Platform version: 4.14.14
OS: Fedora 22 fully up to date as of the time of this writing

Calendar is a Google calendar

Reproducible: Always

Steps to Reproduce:
1. Add a google calendar of type Google Calendar
2. Right click on its folder in the bottom left corner of the main interface of korganizer and select Folder properties...
3. Check the "Block reminders locally" option

Actual Results:  
wait for the correct time and notice the reminder (being it email or display) is actually dispatched

Expected Results:  
no notification should be shown for any reminder set in this calendar

The only workaround is to disable reminders by right clicking in the systray icon, but this applies to all calendars, not only the one I want to ignore.

Comment 1 Till Schäfer 2017-01-20 17:15:26 UTC

I can confirm this bug for KOrganizer 5.4.1 (16.12.1) on Gentoo. 

It seems that the settings form the "folder properties" dialog are never applied. When changing the setting, pressing ok and opening the dialog a second time, the settings are reset to the old ones.

Comment 2 Laurent Montel 2017-05-05 05:13:02 UTC

(In reply to Till Schäfer from comment #1)
> I can confirm this bug for KOrganizer 5.4.1 (16.12.1) on Gentoo. 
> 
> It seems that the settings form the "folder properties" dialog are never
> applied. When changing the setting, pressing ok and opening the dialog a
> second time, the settings are reset to the old ones.

it was fixed in 5.4.3

Comment 3 Till Schäfer 2017-05-05 12:18:33 UTC

i can confirm, that 5.5.0 fixes the problem (although the other custom-symbol option is still not working)