"container:deleteChildrenWithWrongPid" doesn't fix the error due to core behavior about container HOT 5 CLOSED

Hi @DenisMir, use https://github.com/lolli42/dbdoctor to fix general inconsistencies.

from container.

Thank you very much for the hint. I will have a look at the dbdoctor.

from container.

@DenisMir can i close this issue?

from container.

Yeah the issue can be closed. I'm sorry I forgot about giving feedback. After cleaning it up manually everything is fine and the integrity check is green.

from container.

@achimfritz @DenisMir I faced the same problem described here.
In my case, I got 7 records with pid = -1.
And upgrade wizard is being repeated over and over again, detecting the same wrong pid records (through CLI o through BE Upgrade Wizard in the Install Tool)
Example:

WrongPidError: container child with uid 13629 (page: -1 language: 2) but tx_
      container_parent 1045 has pid 120 language: 2

I guess that DataHandler cannot mark my tt_content with uid 13629 as deleted = 1, due to pid being -1 (page deleted?).

Instead of checking https://github.com/lolli42/dbdoctor extension, would it be safe just running a database query that marks that records as deleted?

UPDATE tt_content SET deleted = 1 WHERE uid IN (13629,......);

from container.