As a follow up to "Time to delete recently read is not configurable." issue, it should be good that beside the time based removal, we also create a count based removal of old items.
This means that we would have additional option on config page, where we can set the number of items we want to keep for each user/session. We can name it Count and add an input field with number of items.
This way we can make sure, that each user (no matter how old the record) has their recently read items.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | recently_read_add_count_2954822_5.patch | 5.93 KB | useernamee |
| #2 | recently_read_add_count_2954822_2.patch | 8.07 KB | nkoporec |
Comments
Comment #2
nkoporecCreated a patch for this feature request.
Comment #3
useernamee commentedHi @nkoporec.
Your patch does not apply after recent changes to dev version, so I have made some changes to your patch and now it applies.
Comment #4
useernamee commentedComment #5
useernamee commentedI was a bit sloppy with my first patch so here is the new one.
I have tested your patch @nkoporec and I found you had a small problem in condition for deletion of recently_read entity. I have made correction. I have also changed the order of deletion and creation of new entity so that max count gets checked after new entity is created.
Comment #6
icurk commentedNice catch @useernamee
Comment #8
boshtian commented