Version: 1.5.0 (using KDE 4.6.1) OS: Linux I have a eGroupwareserver that has groupdav link if type "https://myserver.org/subdir/groupdav.php/". When I add this by the GroupDAV wizard (as well in akonadi-based KOrganizer or the Akonadi-Configuration itself) at the ~/.kde/share/config/akonadi_davgroupware_resource_6rc only the following server path is saved: "https://myserver.org/groupdav.php/". Same holds for all GUI elements where I try to edit or add this path. Changing the akonadi_davgroupware_resource_6rc file by hand to the correct server-path + restarting Akonadi solves the problem. Reproducible: Always
Hi Andreas, Le jeudi 24 mars 2011 12:57:30, Andreas Cord-Landwehr a écrit : > > I have a eGroupwareserver that has groupdav link if type > "https://myserver.org/subdir/groupdav.php/". When I add this by the > GroupDAV wizard (as well in akonadi-based KOrganizer or the > Akonadi-Configuration itself) at the > ~/.kde/share/config/akonadi_davgroupware_resource_6rc only the following > server path is saved: "https://myserver.org/groupdav.php/". The wizard is preconfigured with a default set of paths, and can't account for all installation subtleties. The /groupdav.php/ path is the "default" installation path for eGroupWare, and can be used as a basis for further customization. > Same holds for > all GUI elements where I try to edit or add this path. This is strange however. I've just tried with the latest Git snapshot and everything is working fine. How have you installed the resource? Cheers, Grégory
Hi Grégory, I just took the most current beta release, compiled and installed... Today I could try to compile the current GIT snapshot and see if it is working then. The KDEPIM-libs are from KDE SC 4.6.1 release, Akonadi is version 1.5. For the configuration dialog, I from my user's side would expect if I add the specific server path for groupDAV that the dialog at least uses the subdirectory that I tell him. Offering or testing the default path additional to that subdirectory would also be nice imho...
Hi Andreas, > I just took the most current beta release, compiled and > installed... Today There have been some changes since, particularly one that may address you problem. > For the configuration dialog, I from my user's side would expect > if I add the specific server path for groupDAV that the dialog > at least uses the subdirectory that I tell him. Good point, thanks for the idea. I'll add this to the wizard, though as a "hidden" feature as it's no longer possible to add new translatable strings IIRC. > Offering or testing the default path additional > to that subdirectory would also be nice imho... Not sure I got this right: are you speaking about adding the '/groupdav.php/' (or whatever the server default installation path is) part optionally if it was not specified? Cheers, Grégory
Ok, compiling is on its way... Will tell later if everything is already solved at GIT for me. To explain my sentence from before: If a user puts in a eGroupware path like, e.g., "https://myserver.com/A/B/C/D.php/", I would expect that at the testing step the following urls are tested for groupDAV capabilities (since not all users know what they do...): * https://myserver.com/A/B/C/D.php/groupdav.php/ * https://myserver.com/A/B/C/D/groupdav.php/ * https://myserver.com/A/B/C/groupdav.php/ * https://myserver.com/A/B/groupdav.php/ * https://myserver.com/A/groupdav.php/ * https://myserver.com/groupdav.php/
current GIT snapshot works, thanks.