nextcloud / nextcloud/server

[Bug]: Video verification for mail shares buggy

Open
#51,993 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 31-feedback bug feature: sharing
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

⚠️ This issue respects the following points: ⚠️
Bug description

I found 3 Bugs:

  1. When creating an email share, it's not possible to tick the checkbox for the video verification.
  2. When editing a share, the checkbox for the video verification only appears after removing the password share once.
  3. There are errors saving the share even after ticking the checkbox.

Keep in mind that everything only happens for mail shares - normal links work fine.

Steps to reproduce
  1. Create a test file.
  2. Share it via email.
  3. Create a password.
  4. Try to activate video verification - should already not work (Bug 1)
  5. Safe the share without the video verification
  6. edit the share - the checkbox should be active but is not (Bug 2)
  7. deactivate and activate the password again - the video verification checkbox is visible again
  8. save the share - there should be an error with the password (shown message) (Bug 3)
Expected behavior

Mail shares should work exactly like link shares.

Nextcloud Server version

31

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

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

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

Might be similar to #22408

Tested on company NC instance.

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

Reproduce the three failures using the listed steps, comparing email shares with normal link shares and observing the checkbox and save behavior. Trace the share-edit and save paths involved in video verification, then verify that creating, editing, and saving a password-protected mail share works like a link share without the reported errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.