0 candidates when drafts are available

Created on 10 February 2021, almost 4 years ago

Updated 7 March 2024, 9 months ago

Problem/Motivation

I had created several revisions for a node and then created 2 drafts. With the first cronjob the old candidates were correctly deleted. However, the node did not disappear from the candidate list but he then appeared with 0 candidates to delete.

It nominates the node and finds 0 revisions to delete.

Steps to reproduce

- Set 2 keep revisions for a bundle
- Limit result to 30
- Sort by newest nid
- Create a node with some active default revisions and at the end two draft revisions
- Go to candidates

Proposed resolution

Instead of complicating the query, maybe the node which finally has 0 revision candidates should not appear at all and another node should move up as candidate.

🐛 Bug report

Status

Closed: outdated

Component

Code

Created by

🇨🇭Switzerland DanieleN

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment almost 2 years ago →
🇳🇱Netherlands seanB Netherlands
We just added a 2.x version of the module. This is a complete rewrite based on plugins to determine which revisions can be deleted. It also uses a queue worker to actually delete revisions. The queue worker handles translations and drafts of content separately. Could you please test if this solves the issues you currently experience?
Status changed to Closed: outdated 9 months ago6:22am 7 March 2024
Comment 9 months ago →
🇨🇦Canada adriancid Montreal, Canada
Closing because the current development is being made in branch 2.x

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024