-
Notifications
You must be signed in to change notification settings - Fork 177
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
Calendar interface unable to select / print the proper date #796
Comments
I just did some quick checks and it seems that a general problem exists in the date picker. Independently which date or year you're entering, the month is always reduced by one, e.g. December becomes November, July becomes June, February becomes January, etc.. So dates in January couldn't be entered at all because an |
Thanks for your validation and more precise diagnostic. Happy to see that this is not just another code 18 :-) |
is this related to new vue datepicker we use? |
@violoncelloCH the title is misleading. It’s not calendar app related but contacts app related. Moved it to the correct repo |
GitMate.io thinks possibly related issues are #277 (Select multiple contacts), #638 ([Vue] Scroll to the selected contact), #278 (The date fields are not working), and #442 (Another display issue). |
ahh, sorry @georgehrke... didn't get this... moving issues is restricted to admins I guess? would be handy if I could do this sometimes, I always ask people to open new issues at the correct repo... |
@violoncelloCH I think it is related to the new vue date picker which not only asks to select a date but also a time. |
I'll probably ask a stupid question, but, you do click the ok button, right? Clicking outside the picker will just cancel your action. |
@skjnldsv Yes, I clicked the ok button 😉 I've just updated the contacts app to v3.0.1 an checked the date picker behavior of the date of birth and date of death field. The date of birth field allows to select a date only, the date of death field allows to select a date and time. Both fields are still showing the month-1 problem. |
@j-ed so saving is not an issue, but the data saved is wrong, correct? |
@skjnldsv Yes, that's right. If you select a date in December, it is stored as it would have been in November. Only selecting a date in January causes an |
Which make sense! :) |
I'm on nextcloud 15 and contact app version 3.0.1. It's a fresh install on raspbian, the stated versions are the initial versions installed (i.e. there never was a previous version of either nextcloud or the contact app on the system). The following is currently the case:
|
@giorgosspam yes, this will be fixed on 3.0.2 |
When is v3.0.2 going to be released? |
The calendar app is unable to set the proper birth date. The person is born 28th dec 1928. Whenever I try to select that date in the Web interface, the sub menu closes and shows a date in November. I did again, no luck. Clicked on the month itself, tried any other date in Dec 1928, nothing is doing.
I deleted the field and switched to my iPad which sync the contacts over CardDav. I configured the date properly there. Back in the web interface, the date re-appeared but again, in the month of November instead of December.
-Update :
Forgot to mention that contact imported from VCF files with a brith date in December are showed properly. Difference is that when imported, the field mentions only the day itself, no hour, while when setting it from the Web Interface, the interface requires an hour.
-End of the update...
Steps to reproduce
Expected behaviour
Have the proper date configured and printed in the contact...
Actual behaviour
Date is switched back one month, to November.
Server configuration
Nextcloud Docker, latest
Operating system:
Alpine
Web server:
Apache
Database:
MariaDB, separate docker on a different server
PHP version:
Docker image nextcloud:latest....
Nextcloud version: (see Nextcloud admin page)
15.0.0.10
Updated from an older Nextcloud/ownCloud or fresh install:
Fresh install
Where did you install Nextcloud from:
Downloaded the nextcloud:latest image from Docker Hub, using Portainer
Signing status:
Signing status
The text was updated successfully, but these errors were encountered: