Can't re-add deleted feed via API
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing the API add request after removing the feed in the UI, then trace the feed creation and deletion paths that produce the Feed with this URL exists response. Done means a feed removed through the UI can be added again through the API without a 409, while genuinely existing feeds still return the conflict.
Written by the indexing model from the issue text.
Description
IMPORTANT
Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
- I have read the CONTRIBUTING.md and followed the provided tips
- I accept that the issue will be closed without comment if I do not check here
- I accept that the issue will be closed without comment if I do not fill out all items in the issue template.
Explain the Problem
A feed that has been removed in the UI can not be re-added via the API (as it appears to still exist?). I haven't checked the DB, presumably it's still there.
Steps to Reproduce
Explain what you did to encounter the issue
- Remove a feed from the UI
- Use API to attempt to add the feed
- Recieve status code 409 with message
Feed with this URL exists
System Information
- News app version: 25.1.0
- Nextcloud version: 29.0.9
- Browser and version: Firefox 133.0
- Cron type: Cron
- PHP version: 8.3.14
- Database and version: MariaDB 10.5.23
- OS and version: Client or server? Either way Debian, 11 on server, testing on client.
edit: further server details
- Dominant language
- PHP
- Stars
- 1k
- Forks
- 200
- Avg merge
- 20h 28m
- Merged PRs (30d)
- 32
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from nextcloud/news
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
replace mkdocs with somethingMay be free again @Grotax claimed this 95 days ago, and no pull request is open. Open
nextcloud/news#3887 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
bug help wanted upstream
Difficulty 3/5 1-2 days Newbie friendliness 58/100
nextcloud/news#3840 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
0. Needs triage 35-feedback bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
wpgenius/stackfolio#22 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Automattic/static-site-importer#3024 ·
Maintainers usually reply within 1 day
-
[6.0]: Uncaught TypeError: can't access property "value", event.chart.scales.x.ticks[4] is undefinedOpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
phpmyadmin/phpmyadmin#20626 ·
Maintainers usually reply within 1 day