nextcloud / nextcloud/calendar

Renaming Calendar - old name used in export

Open
#6,458 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage bug feature: caldav Feature: Importing
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce
  1. Create a calendar
  2. Rename the calendar
  3. Export the calendar
Expected behavior

The file name of the exported calendar should use the (new) calender name - not the old, initial name.

Actual behaviour

The file name uses the old, initial calendar name.

Calendar app version

4.7.16

CalDAV-clients used

DAVx5

Browser

Firefox 131

Client operating system

Manjaro Linux

Server operating system

Manjaro Linux

Web server

Apache

Database engine version

MariaDB

PHP engine version

Other

Nextcloud version

29.0.8

Updated from an older installed version or fresh install

Updated from an older version

List of activated apps

Enabled:

  • calendar: 4.7.16
  • cloud_federation_api: 1.12.0
  • comments: 1.19.0
  • contacts: 6.0.0
  • contactsinteraction: 1.10.0
  • dashboard: 7.9.0
  • dav: 1.30.1
  • deck: 1.13.2
  • federatedfilesharing: 1.19.0
  • federation: 1.19.0
  • files: 2.1.1
  • files_downloadlimit: 2.0.0
  • files_pdfviewer: 2.10.0
  • files_reminders: 1.2.0
  • files_sharing: 1.21.0
  • files_trashbin: 1.19.0
  • files_versions: 1.22.0
  • logreader: 2.14.0
  • lookup_server_connector: 1.17.0
  • maps: 1.4.0
  • nextcloud_announcements: 1.18.0
  • notes: 4.11.0
  • notifications: 2.17.0
  • oauth2: 1.17.1
  • password_policy: 1.19.0
  • photos: 2.5.0
  • privacy: 1.13.0
  • provisioning_api: 1.19.0
  • recommendations: 2.1.0
  • related_resources: 1.4.0
  • serverinfo: 1.19.0
  • settings: 1.12.0
  • sharebymail: 1.19.0
  • survey_client: 1.17.0
  • systemtags: 1.19.0
  • text: 3.10.1
  • theming: 2.4.0
  • twofactor_backupcodes: 1.18.0
  • updatenotification: 1.19.1
  • user_status: 1.9.0
  • viewer: 2.3.0
  • weather_status: 1.9.0
  • workflowengine: 2.11.0
    Disabled:
  • activity: 2.21.1 (installed 2.20.0)
  • admin_audit: 1.19.0
  • bruteforcesettings: 2.9.0
  • circles: 29.0.0-dev (installed 28.0.0-dev)
  • encryption: 2.17.0
  • files_external: 1.21.0
  • firstrunwizard: 2.18.0 (installed 2.17.0)
  • support: 1.12.0 (installed 1.11.0)
  • suspicious_login: 7.0.0
  • twofactor_totp: 11.0.0-dev
  • user_ldap: 1.20.0
Nextcloud configuration

{
"system": {
"instanceid": "REMOVED SENSITIVE VALUE",
"passwordsalt": "REMOVED SENSITIVE VALUE",
"secret": "REMOVED SENSITIVE VALUE",
"trusted_domains": [
"192.168.200.28",
"nubes.alpha"
],
"overwrite.cli.url": "http://nubes.alpha",
"htaccess.RewriteBase": "/",
"memcache.local": "\OC\Memcache\APCu",
"datadirectory": "REMOVED SENSITIVE VALUE",
"logfile": "/var/log/nextcloud.log",
"log_rotate_size": 1048576,
"dbtype": "mysql",
"version": "29.0.8.1",
"dbname": "REMOVED SENSITIVE VALUE",
"dbhost": "REMOVED SENSITIVE VALUE",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "REMOVED SENSITIVE VALUE",
"dbpassword": "REMOVED SENSITIVE VALUE",
"installed": true,
"default_phone_region": "DE",
"maintenance_window_start": 1,
"mail_from_address": "REMOVED SENSITIVE VALUE",
"mail_smtpmode": "smtp",
"mail_sendmailmode": "smtp",
"mail_domain": "REMOVED SENSITIVE VALUE",
"mail_smtphost": "REMOVED SENSITIVE VALUE",
"mail_smtpport": "465",
"mail_smtpsecure": "ssl",
"mail_smtpauth": 1,
"mail_smtpname": "REMOVED SENSITIVE VALUE",
"mail_smtppassword": "REMOVED SENSITIVE VALUE",
"maintenance": false,
"loglevel": 2,
"theme": ""
}
}

Web server error log

No response

Log file

No response

Browser log

No response

Additional info

PHP 8.3.3 (cli) (built: Feb 17 2024 02:04:07) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.3, Copyright (c) Zend Technologies
with Zend OPcache v8.3.3, Copyright (c), by Zend Technologies

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the Calendar app by creating, renaming, and exporting a calendar. Trace the export entry point from that flow; no source file or test is identified in the report. Done means the exported filename uses the calendar's new name rather than its initial name.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.