Open nkakouros opened 2 years ago
So currently the name is defined by the client (this app) instead of the server, which does pretty much nothing other than passing information to SabreDAV and handling refreshment.
Since we can't fetch data directly from the browser (because of CORS and CSP), it needs to be handled on server's side :
Otherwise we can still update the subscription afterwards it's created based on refreshed data, but that would be poor UX.
I am not sure this is the correct repo to report this, sorry if not.
Steps to reproduce
+ -> New subscription from link
I am using a Nextcloud calendar but any endpoint with a calendar would work the same.
Expected behaviour
The calendar should be named after the
X-WR-CALNAME
orNAME
calendar properties.Actual behaviour
The calendar gets named after the domain name of the subscription link.
It could be argued that this is preferrable as it allows the usre to identify the calendar by the domain name instead of whatever cryptic name the ics file may contain. However, the user most probably copied the share link of the calendar from an application that already depicted the calendar name to the user and this is how the user identified the calendar they wanted to sync. Changing the name of the calendar upon subscribing in Nextcloud probably causes more confusion. Also, if the user wants to use the same calendar name as in the original app where the calendar lies, they have to go back and forth between Nextcloud and the other app, or look into the ics file which is much more complex for casual users.
Calendar app
2.3.4
CalDAV-clients used: None
Client configuration
Browser: Firefox Nightly 95.0a
Operating system: Macos
Server configuration
Operating system: Ubuntu 20.04.2 LTS
Web server: Apache
Database: MariaDB
PHP version: 8.0.3
Nextcloud Version: 22.2.3
Updated from an older installed version or fresh install: updated from 21
List of activated apps:
Nextcloud configuration:
Logs
Web server error log (e.g. /var/log/apache)
Log file (data/nextcloud.log)
Browser log