The logic of checking orphaned node should scan the node's current revision body field instead of the latest revision body field

Created on 12 April 2023, over 1 year ago
Updated 28 April 2023, over 1 year ago

Problem/Motivation

The logic of checking orphaned node should scan the node's current revision body field instead of the latest revision body field.

I am going to upload the patch soon.

Steps to reproduce

Proposed resolution

@@ -575,7 +554,7 @@ EOT;
     $and1 = $query->orConditionGroup()
       ->condition('body', $uuid, 'CONTAINS');
     $query->condition($and1);
-    $nids = $query->latestRevision()->execute();
+    $nids = $query->execute();
     if (!empty($nids)) {
       return TRUE;
     }

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇨🇦Canada jamesyao

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

Comments & Activities

Production build 0.71.5 2024