Bug 286800

Summary: Renaming of remote calendar names isn't saved
Product: [Frameworks and Libraries] Akonadi Reporter: Andreas Pietzowski <andreas>
Component: DAV ResourceAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: greg
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 4.7.4
Sentry Crash Report:

Description Andreas Pietzowski 2011-11-16 20:32:15 UTC
Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

I have a davical server which offers collections or calendars as follows:

/user/home
/user/office

I can work with them in korganizer (nice feature btw!) but it is always displayed as "home" and "office". I renamed the ressource in akonadi-console but it wasn't remembered very long.

Reproducible: Always

Steps to Reproduce:
Create a CalDAV ressource

Actual Results:  
The mounted calendars are shown up as the last string-part of the path.

Expected Results:  
Renaming of a Calendar (children nodes of the caldav ressource) should always show up with the new given name.
Comment 1 Grégory Oestreicher 2011-11-19 08:55:11 UTC
Hi Andreas,

How have you tried to rename the calendars?

There's a way to do it, slightly hidden as it will change it on the server as well: from the configuration dialog edit the URL that contain your calendars and click the 'Fetch' button; once your collections are listed you can double-click on the name to edit it to your liking; then just press 'Enter' to validate.

Please keep in mind that this will change it globally (for all clients). If that's not what you want, could you explain more precisely what you wish?

Cheers,
Grégory
Comment 2 Andreas Pietzowski 2011-11-21 11:46:49 UTC
Hello Grégory,

your way of renaming was exactly what I tried before (btw: this dialog is hard to find and absolutely NOT intuitively ;-). Anyhow, I double clicked the ressource name in the list view below the "Fetch" button. After renaming, the new name is displayed. But after a few milliseconds the original name was restored again. I guess it is reloaded from the server.

Is renaming really working on your side? I tried a lot of stuff but no success yet.

Andreas
Comment 3 Grégory Oestreicher 2011-11-21 20:35:00 UTC
Hi Andreas,

This used to work, but I've just tested on my DaviCal server and it's now failing with a 500 error… I'll have a look into this and post my findings.

Cheers,
Grégory
Comment 4 Grégory Oestreicher 2011-11-21 21:16:37 UTC
Got it! Now I'm wondering how this worked before. A fix is underway and will be part of the next cycle of updates.

Cheers,
Grégory
Comment 5 Grégory Oestreicher 2011-11-21 21:29:45 UTC
This has been fixed with commit a4d9060d857eb03aca28d538a3b94fbac7055faa in master, and backported to 4.7.