When updating nodes, set the latest revision as published

Created on 28 June 2019, almost 6 years ago
Updated 21 December 2024, 4 months ago

Problem/Motivation

On search and replace, when updating nodes, the latest changed revision is draft. So when using the scanner, if it changes a lot of nodes, it is inefficient to have to go to each one of them and publish the latest revision.

Proposed solution

I think that the scanner should set the latest changed revision of the affected nodes (at least the published nodes) as the current published one. In this way, the replacements of the scanner will be immediately visible.

✨ Feature request
Status

Closed: outdated

Version

1.0

Component

Code

Created by

πŸ‡¬πŸ‡·Greece mariaioann

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

Production build 0.71.5 2024