Database update issue with mailer_html_to_text

Did you try clearing caches?

I can confirm seeing this issue as well. Performing a cache rebuild prior to the update had no effect on the result.

We added

drush pmu -y symfony_mailer symfony_mailer_bc
drush en -y symfony_mailer symfony_mailer_bc

to our update script temporarily to get around it.

The "mailer_html_to_text" policy should have been removed in symfony_mailer_update_10006(). I wonder how come you still have some remaining? Please can you check your configuration and look for them?

Could it be related to 🐛 Update body policy to add text format update 10003 breaks policy translations. Closed: outdated and policy translations? I only use single-language so I'm afraid I don't know much about translations.

Strange 😃 - thanks for the update

After verifying that all pending database updates had been completed, I found that the mailer_html_to_text configuration still existed via:
drush cget symfony_mailer.mailer_policy._ configuration.mailer_html_to_text

I was able to resolve this in drush by deleting said configuration and rebuilding cache:

1. drush cdel symfony_mailer.mailer_policy._ configuration.mailer_html_to_text
2. drush cr

It's possible to force rerun database updates. It would be interesting to see the effects of that when the cget symfony_mailer.mailer_policy._ configuration.mailer_html_to_text is present.

The issue is that if the schema version is less than 10006 and the module is upgraded to any commit after the removal of the mailer_html_to_text plugin, then the plugin will still be in config but won't exist. Any db update or probably cache clear will show the error.

The attached patch checks whether the plugin exists on each hook_update_N before 10006, and if not, runs the 10006 update to update the config so the error is not shown.

@bgilhome That sounds like a different issue - the OP had an error running symfony_mailer_update_10007(). Please raise a new issue with a description of the steps you take and the error you see.

then the plugin will still be in config but won't exist

True - but why is this a problem? As far as I can see, the update hook won't try to load any of the EmailAdjuster plug-ins for the policies that it updates.

Same issue.

Same issue.

Thanks - but same as which person commenting? There seem to be a few different reports, and I still don't know how to reproduce any of them.

anup.singh → made their first commit to this issue’s fork.

Created a merge request using the suggestion from #9,
But I added the call on the new update hook too, as it is failing when upgrading core to D10

Note: this is still not the final fix for this issue, but just a workaround to unblock the broken updb