nextcloud / nextcloud/calendar
"+ Event" button always defaults to current date even if display is a different date
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Chose a date in the future and view the calendar
- Click '+ Event' button
Expected behavior
The new event should have the displayed date which is the way every other calendaring program does.
Actual behavior
Observe the start and end dates being set to the current date vs the displayed date
Calendar app version
5.0.9
CalDAV-clients used
No response
Browser
Firefox 134.0.1, Qutebrowser v3.4.0
Client operating system
NixOS x86_64, unstable
Server operating system
Docker image on Arch
Web server
Nginx
Database engine version
MariaDB
PHP engine version
Other
Nextcloud version
Nextcloud Hub 9 (30.0.5)
Updated from an older installed version or fresh install
Updated from an older version
List of activated apps
- activity: 3.0.0
- app_api: 4.0.5
- bruteforcesettings: 3.0.0
- calendar: 5.0.9
- cloud_federation_api: 1.13.0
- contacts: 6.1.3
- contactsinteraction: 1.11.0
- dashboard: 7.10.0
- dav: 1.31.1
- dav_push: 0.0.1
- federatedfilesharing: 1.20.0
- files: 2.2.0
- files_downloadlimit: 3.0.0
- files_trashbin: 1.20.1
- files_versions: 1.23.0
- firstrunwizard: 3.0.0
- integration_mastodon: 3.0.1
- logreader: 3.0.0
- lookup_server_connector: 1.18.0
- mail: 4.1.2
- nextcloud_announcements: 2.0.0
- notifications: 3.0.0
- oauth2: 1.18.1
- password_policy: 2.0.0
- photos: 3.0.2
- privacy: 2.0.0
- provisioning_api: 1.20.0
- serverinfo: 2.0.0
- settings: 1.13.0
- theming: 2.5.0
- twofactor_backupcodes: 1.19.0
- user_status: 1.10.0
- viewer: 3.0.0
- weather_status: 1.10.0
- webhook_listeners: 1.1.0-dev
- workflowengine: 2.12.0
Nextcloud configuration
{
"system": {
"debug": false,
"memcache.local": "\\OC\\Memcache\\APCu",
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_proxies": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"cloud.trex-halfbeak.ts.net"
],
"dbtype": "mysql",
"version": "30.0.5.1",
"overwrite.cli.url": "https:\/\/cloud.trex-halfbeak.ts.net",
"overwriteprotocol": "https",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"default_phone_region": "us",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_smtpmode": "smtp",
"mail_sendmailmode": "smtp",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"mail_smtpauthtype": "LOGIN",
"mail_smtpauth": 1,
"mail_smtphost": "***REMOVED SENSITIVE VALUE***",
"mail_smtpport": "587",
"mail_smtpname": "***REMOVED SENSITIVE VALUE***",
"mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
"maintenance": false,
"maintenance_window_start": 1,
"theme": "",
"loglevel": 2,
"filelocking.enabled": "true",
"memcache.locking": "\\OC\\Memcache\\APCu",
"updater.secret": "***REMOVED SENSITIVE VALUE***",
"upgrade.disable-web": true,
"app_install_overwrite": [
"calendar",
"contacts"
]
}
}
Web server error log
Log file
Browser log
Additional info
Addition info: PHP 8.3.15
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by selecting a future date in the calendar and using the “+ Event” button, then trace that button’s entry point and the date passed to the new-event form. Done means the form uses the displayed calendar date rather than the current date, with the behavior verified for a future date.
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