I'm catching the exception, and re-throwing it as a MigrationException; because these are simply logged.
However, since this exception isn't breaking the migration itself (just the storing of the notification about it) I added a NonBreakingMigrationException which will be caught earlier and logged; but will not break the migration process.
This PR resolves an issue where the notification could not be stored, and this exception bubbles up to the end user. https://wordpress.org/support/topic/php-fatal-error-notifications-could-not-be-stored/#post-16788286
I'm catching the exception, and re-throwing it as a
MigrationException
; because these are simply logged.However, since this exception isn't breaking the migration itself (just the storing of the notification about it) I added a
NonBreakingMigrationException
which will be caught earlier and logged; but will not break the migration process.