Problem/Motivation

We suffer from random Draft deletes in Conductor.

Sally found that it could be because the DraftCleanup services takes in consideration the site and only one database, but for devs, we have 1 site and multiple databases.

If I create a draft (dev1), and a second dev (dev2) executes the DraftCleanup in the background, the services detects that the draft created by the dev1 in dev1’s databases is considered as orphan, so it’s deleted.

This could also affect prod with staging sites.

We should disable this cleanup and configure a setting for enable it in production sites.

Issue fork conductor-3576222

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

isholgueras created an issue. See original summary.

isholgueras’s picture

isholgueras commented
Assigned: isholgueras » Unassigned
Status: Active » Needs review

isholgueras opened merge request !163

justafish’s picture

justafish
she/her
Primary language English
Location London, UK
commented
Status: Needs review » Reviewed & tested by the community

  • isholgueras committed c6264d9f on 2.x 
    feat: #3576222 Disable DraftCleanup process in Conductor by default

By...
isholgueras’s picture

isholgueras commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.