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
OK, I did some more testing and figured this one out. In the paragraphs field setting for each content type you are using them, you can make the following selection for Default Edit Mode. I was in...
How to use 'Paragraphs Editor Preview'
Typically in a basic site, and as far as I know (I may be wrong) Backdrop doesn't store cookies for anonymous users, EXCEPT if you have things that need to persist, for example, if you create a View...
Does Backdrop set any Cookies / session variables for guests?
A couple of other things to keep in mind: - Roles in Backdrop do not use numeric IDs, but machine names. I see that the database insert command is trying to insert a numeric id as a role - Is this a...
Importing users from D7 site using Feeds - uses insert rather than update