nextcloud / nextcloud/contacts

no birthday date possible in contacts from shared addressbooks

Open
#3,606 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug feature: contacts
Dominant language
JavaScript
Stars
642
Forks
220
Avg merge
14h 39m
Merged PRs (30d)
51

Description

Describe the bug

on shared addressbooks

  • it is not possible to save contact changes when a birthday date is set

  • changes or create new contacts have the same issue (only if birthday is set)

  • if a contact has a birthday it is not possible to move it to a shared addressbook

  • old contact can have birthday but can not be changed any more

Steps to reproduce
  1. Go to 'contacts' in a shared addressbook
  2. edit a contact with birthday
  3. make any change and try to save -> errormessage will be displayed (unable to update contact)
  4. delete the birthday
  5. click on save -> no error
Expected behavior

no error on saving contacts

Actual behavior

no error

Contact version

5.3.2

Operating system

Linux 5.15.116

PHP engine version

PHP 8.1

Web server

Apache (supported)

Database

MySQL

Additional info

errormessage in nextcloud log
OC\DB\Exceptions\DbalException: An exception occurred while executing a query: SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xF0\x9F\x8E\x82 A...' for column nextcloud.oc_calendarobjects_props.value at row 1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing the shared-addressbook save flow from the listed steps and trace the logged database exception for a birthday value; done means creating, editing, and moving contacts with birthdays saves without an error.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql, php
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.