Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make purging unread items an optional feature #1077

Closed
3 tasks done
Grotax opened this issue Jan 21, 2021 · 3 comments
Closed
3 tasks done

Make purging unread items an optional feature #1077

Grotax opened this issue Jan 21, 2021 · 3 comments
Assignees
Labels
1. to develop API Impact API/Backend code
Milestone

Comments

@Grotax
Copy link
Member

Grotax commented Jan 21, 2021

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 don not fill out all items in the issue template.

Description

In older versions of News read items where deleted if the amount of read items exceeded a certain threshold defined in the admin settings. Current version doesn't delete anything, News 15.2.0 will feature the old behavior in a refactored version.

The next minor version will introduce a new option to also delete unread items, to make it easier for administrators to keep their instance clean.

Task

  • add option to delete unread && read items
  • announce via changelog
@Grotax Grotax added 1. to develop API Impact API/Backend code labels Jan 21, 2021
@Grotax Grotax added this to the 15.3.0 milestone Jan 21, 2021
@Grotax
Copy link
Member Author

Grotax commented Jan 21, 2021

related #1065

@anoymouserver
Copy link
Contributor

also related to #110

@Grotax
Copy link
Member Author

Grotax commented Oct 10, 2022

done in #1931

@Grotax Grotax closed this as completed Oct 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop API Impact API/Backend code
Projects
None yet
Development

No branches or pull requests

3 participants