nextcloud / nextcloud/calendar
Recurring daily events end one day before
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
- In the Calendar App click on a time slot to create a new entry (lets say Monday 10:00)
2.In the pane opening on the right enter the title and on the bottom edit the recurring options (sorry I use a german version, there its saying "Keine Wiederholung") - On recurring ("Wiederholung") choose daily ("Tag")
- At stop ("Wiederholung beenden") choose date ("Am Datum")
- Choose the date of the friday thats following your chosen monday
- Choose Save
Expected behavior
Recurring Event from Monday to Friday
Actual behaviour
Recurring Event from Monday to Thursday
Calendar app version
4.6.5 (happens since a long time an lots of version ins the past)
CalDAV-clients used
- none - WebFrontent of NextCloud
Browser
Firefox 115.6 (Debian 12 Current Package)
Client operating system
Debian 12
Server operating system
Debian 11
Web server
Apache
Database engine version
MariaDB
PHP engine version
PHP 7.4
Nextcloud version
25.0.13
Updated from an older installed version or fresh install
Updated from an older version
List of activated apps
Enabled:
- activity: 2.17.0
- admin_audit: 1.15.0
- bruteforcesettings: 2.5.0
- calendar: 4.6.5
- circles: 25.0.0
- cloud_federation_api: 1.8.0
- comments: 1.15.0
- contacts: 5.5.1
- cookbook: 0.10.5
- dashboard: 7.5.0
- dav: 1.24.0
- deck: 1.8.8
- federatedfilesharing: 1.15.0
- federation: 1.15.0
- files: 1.20.1
- files_pdfviewer: 2.6.0
- files_rightclick: 1.4.0
- files_sharing: 1.17.0
- files_trashbin: 1.15.0
- files_versions: 1.18.0
- firstrunwizard: 2.14.0
- logreader: 2.10.0
- lookup_server_connector: 1.13.0
- mail: 2.2.9
- nextcloud_announcements: 1.14.0
- notes: 4.9.2
- notifications: 2.13.1
- oauth2: 1.13.1
- password_policy: 1.15.0
- phonetrack: 0.7.6
- photos: 2.0.1
- privacy: 1.9.0
- provisioning_api: 1.15.0
- recommendations: 1.4.0
- related_resources: 1.0.4
- serverinfo: 1.15.0
- settings: 1.7.0
- sharebymail: 1.15.0
- support: 1.8.0
- survey_client: 1.13.0
- systemtags: 1.15.0
- tasks: 0.15.0
- text: 3.6.0
- theming: 2.0.1
- twofactor_backupcodes: 1.14.0
- updatenotification: 1.15.0
- user_status: 1.5.0
- viewer: 1.9.0
- weather_status: 1.5.0
- workflowengine: 2.7.0
Disabled:
- contactsinteraction: 1.3.0
- encryption
- files_external
- richdocuments: 7.1.9
- suspicious_login
- twofactor_totp
- user_ldap
Nextcloud configuration
{
"system": {
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"hinderuex.ch",
"www.hinderuex.ch"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"dbtype": "mysql",
"version": "25.0.13.2",
"overwrite.cli.url": "https:\/\/www.hinderuex.ch",
"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": "CH",
"memcache.local": "\\OC\\Memcache\\APCu",
"mail_smtpmode": "smtp",
"mail_smtpsecure": "ssl",
"mail_sendmailmode": "smtp",
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"mail_smtpauthtype": "PLAIN",
"mail_smtpauth": 1,
"mail_smtphost": "***REMOVED SENSITIVE VALUE***",
"mail_smtpport": "465",
"mail_smtpname": "***REMOVED SENSITIVE VALUE***",
"mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
"maintenance": false,
"theme": "",
"loglevel": 2
}
}
Web server error log
No response
Log file
No response
Browser log
No response
Additional info
No response
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
Start by reproducing the issue in the Calendar App web frontend using a daily event from Monday through a Friday stop date. Trace where the recurring options are saved and interpreted, then verify that the final Friday occurrence is included and repeat the reproduction after the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mariadb, php
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100