trackUpdateOnDeletion throws exception but is never caught

Huh, actually the exception was thrown via trackUpdateOnEdition, not trackUpdateOnDeletion.
Updated patch to try catch that method too.

Nice find... the problem here is that \Drupal\entity_usage\Plugin\EntityUsage\Track\Link::getTargetEntities should not throw the exception. We should put the. try catch in there. Also I don't think we should be logging here either. I think we should just return an empty array and move on. That means other fields with entities will still be tracked for this entity.

Or perhaps even better would be to put the try catch inside field loop in \Drupal\entity_usage\EntityUsageTrackBase::trackOnEntityUpdate() and \Drupal\entity_usage\EntityUsageTrackBase::trackOnEntityCreation()... it's tricky - that'd be more robust but potentially more likely to catch something you would want to log - so if we do that we should log as well.

I pushed an MR that starts on #5 - just need to add logging service in a BC compat way...

Added logging...

Could do with adding an automated test here.

I think this is ready now. We log any exceptions thrown by track and have test coverage that the exceptions are logged.

Thanks for jumping in and for the generic solution in the base class 👍

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