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
Thank you for all your help. In the meantime I just edited the export db-file and removed the top line with the sandbox comment. --> Still the same issue. I exported also with the...
Problem with utf8mb4 Format when importing database
Another possibility: The RRSB module has a forward option. If you don't want all the social-media sharing links, you can uncheck them all, then enable RRSB on the node types of your choice.
Forward/email this page ?
One person said: I use bee in mamp - but not sure what i can offer. I did a basic setup and it just works...
Problem with utf8mb4 Format when importing database