nextcloud / nextcloud/tables

Email notifications from Tables changes sent with "deleted user" instead of actual user

Open
#2,745 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Steps to reproduce
  1. When the Tables are being edited and the notifications to all users that are allowed to view the change are set to be sent via email, instead of listing the actual user who made the change, the email always says "deleted user", although the Activity App shows the same change with a correct user name. In Nextcloud Tables 2.2.0, activity payloads for row_create and row_update contain an empty table.ownerDisplayName even when table.ownership is a valid existing user ID. For table_create, ownerDisplayName is filled correctly. Activity email notifications then render "deleted_user" for row activities.
Expected behavior

Notification email should contain the name of the user who made a change to the table

Actual behavior

Instead of the user name, email states "deleted user" as the user who made the change

Tables app version

2.2.0

Browser

Safari

Client operating system

Windows

Operating system

Linux 5.15.0-181-generic #191-Ubuntu GNU/Linux

Web server

Apache

PHP engine version

PHP 8.3

Database

MariaDB

Additional info
    • installed: true
  • version: 33.0.5.1
  • versionstring: 33.0.5
  • edition:
  • maintenance: false
  • needsDbUpgrade: false
  • productname: Nextcloud
  • extendedSupport: false
    • activity: 6.0.0
  • flow_notifications: 4.0.0
  • notifications: 6.0.0
  • tables: 2.2.0

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

Start by tracing how activity payloads are generated for row_create and row_update, then compare them with the table_create payload where ownerDisplayName is populated. Verify the notification email uses the actual user name for row changes rather than "deleted user", and add or update regression coverage for these activity types.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.