Bug 452106 - Cannot add calendar from URL in KOrganizer
Summary: Cannot add calendar from URL in KOrganizer
Status: RESOLVED DUPLICATE of bug 358249
Alias: None
Product: korganizer
Classification: Applications
Component: embedded (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Cornelius Schumacher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-31 10:34 UTC by matthias.schrumpf
Modified: 2023-05-02 11:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matthias.schrumpf 2022-03-31 10:34:58 UTC
SUMMARY
Adding an ICal calendar via URL or via a local file only creates empty calendars. 
Downloading the ICal file and double-clicking it in the file browser opens a dialog for importing it into KOrganizer which yields properly working calendar entries. 


STEPS TO REPRODUCE
1. Right click and add a new calendar 
2. Select "ICal Calendar File" 
3. Paste the URL to an ICal file in the file name field
4. Add a display name
5. Click okay

OBSERVED RESULT
Two empty calendars are created named "akonadi_ical_resource_file_#"  where # increases by 1 each time and "calendar". 

EXPECTED RESULT
One new calendar should be added with the specified display name. That new calendar should have all the entries that are in the specified file, be it local or by URL, and not be empty. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.17.1-arch1-1
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Downloading the ICal file and double-clicking it in the file browser opens a dialog for importing it into KOrganizer and either adding it to another calendar or making a new entry. Making a new entry creates a calendar with the name of the file as display name and with all entries properly working inside.
Comment 1 Carl Schwan 2023-05-02 11:09:32 UTC

*** This bug has been marked as a duplicate of bug 358249 ***