-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Birthdays not shown in upcoming events widget #5592
Comments
If you go back to calendar version 4.4.5 all entries are back/shown. |
Tested in latest 4.6.0 and its still not working. |
Thanks for your bug report 👍 I've worked on two patches, which are also scheduled for the upcoming releases of Nextcloud 28 (2024-05-23) and Nextcloud 29 (2024-05-23), to address some issues regarding the upcoming events widget.
The birthday calendar uses reoccurrence and therefore, I think the second patch could also help for your case. Do you happen to remember if the widget showed the birthdays for the first seven of your contacts (ordered by their birthdate)? E.g You have 7 contacts with birthday in Jan, and another one in Feb. Those with birthday in Jan should work the others not. Thank you and stay tuned! |
I missed the merge window for 28.0.6 and 29.0.1. |
The releases are out and I will therefore close the report. Please let me know if it's still broken on your end. |
Steps to reproduce
Expected behavior
Birthday should appear in upcoming events widget.
Actual behaviour
Birthday didn't appear in upcoming events widget.
Calendar app version
4.5.3
CalDAV-clients used
No response
Browser
Chrome 119
Client operating system
Microsoft Windows 10
Server operating system
Debian 11
Web server
Apache
Database engine version
PostgreSQL
PHP engine version
PHP 8.2
Nextcloud version
27.1.4
Updated from an older installed version or fresh install
Updated from an older version
List of activated apps
No response
Nextcloud configuration
No response
Web server error log
No response
Log file
No response
Browser log
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: