Description of the need While working on https://github.com/backdrop/backdrop-issues/issues/3979 I realized that the updater throws exceptions at an early stage of the process, when there's nothing broken (yet).
This might be confusing for admins, especially Backdrop novices, because an exception usually means, something's broken really badly. And that's not the case at that early stage of updating (files got downloaded and extracted, the install itself is untouched).
Doesn't this look like this Backdrop install is broken? It isn't.
Proposed solution If nothing's actually broken, it might be better to abort the update and show a helpful message. Log detailed information, possibly with links to documentation. We also need to consider that updating happens in batches. The fact that one project fails, doesn't mean all of them fail. (But that needs some more recherche...)
Alternatives that have been considered Sticking with UpdaterExeptions.
Recent comments
Thanks Meaghan. I have solved this error. The issue was that after the upgrade, I re-enabled the civicrm related modules at a time that leads to the error. But after that I tried and re enabled...
Facing an error after upgrading Civicrm version from 5.78.3 to 6.5.0
Ah yes. Thank you very much.
Porting of module Views Raw SQL
Go to admin/structure/views/settings and click on "Show information and statistics about the view during live preview"
Porting of module Views Raw SQL