[Bug]: Calendar event recurrence
@SebastianKrupinski is already working on this.
Since Oct 31, 2024.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
Hello, I think there is a little bug in storing event recurrences. If you create an event like this:
01.01.2024, whole day
repeat: yearly (APR, MAI, JUN)
on: second Monday
endless
This event will be shown in the nextcloud web calendar but is not shown when accessing by another calendar app through nextcloud calDAV Server. I tried with Mac OS Calendar and Android (DAVX5).
There is also a little translation bug when you define the "on" (first, second, third, fourth, fifth, penultimate day, last day). the "second" is always in english language whether the locale is set to.
regards!
Steps to reproduce
set the event like described and you may see
Expected behavior
the event should be visible when requested by nextcloud calDAV server
Nextcloud Server version
30
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
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.
Assessment
This issue has not been assessed yet.