Removed Decks' data aren't deleted from database
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Describe the bug
All decks which were removed from web console or app are still has their data in SQL database and weren't removed from it.
To Reproduce
Steps to reproduce the behavior:
I just go inside to database and still can observe those data in the base 'oc_deck_cards'.
Expected behavior
After some decks were deleted from web console or app the data have to be removed from SQL database immediatly.
Screenshots
Client details:
- OS: Windows or Android
- Browser Firefox web-interface or Deck app
- Version 99.0 or 1.20.0
- Device: Desktop or smartphone
Server details
Operating system:
Ubuntu 20.04
Web server:
Apache 2.41
Database:
10.3.34-MariaDB
PHP version:
PHP: 7.4.3
Nextcloud version: (see Nextcloud admin page)
Nextcloud Hub II 23.0.3
Where did you install Nextcloud from:
From general site www.nextcloud.com
Signing status:
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing deck deletion from the web console or app, then inspect the oc_deck_cards table to confirm which records remain. Trace the deletion path for the affected deck data and verify that the related SQL rows are removed immediately after deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, php
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100