I encountered an issue with the parent deletion process when running it on a custom entity type without bundles that has its relationship defined on a UI-defined field: details below.
The parent deletion query identifies any parent entities which should be deleted after the child entity has been deleted, though this functionality seems to centered around bundles. If the relationship is defined on a base field, the query runs for all bundles of the parent entity type. If the relationship is defined on a non-base field type, such as a config field, the query adds a condition to specify the bundle (via bundle key).
However, bundles are optional — if the entity type does not use bundles and the entity relationship is defined on field created via the UI, this condition yields a null value for the bundle key and causes an error in the query. Thus, this prevents the parent deletion process from completing.
drush queue:list in the terminal to see the list of items for deletion.drush queue:run entity_reference_delete_parent_query to encounter the error in the console.One solution would be to check the list of bundles an entity type reports using. If only one is found, omit the condition to specify the bundle type.
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
It's been a long time since I wrote this module, so I don't remember how it all works.
But even entity types that have no bundles actually have a bundle -- it has the same name as the entity type ID. I think the change should be doing something with that.