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 everyone! This was really helpful. Regards, Alex
One-page navigation, how do I add attribute ID's?
Hi Enthusiast, This is probably a very good method, but at the moment a bit too complex for me. I might take you up on your offer to explain further in the future. Thanks! Kind...
One-page navigation, how do I add attribute ID's?
Thank you! I did all as you suggested. I now get the error message: ------------- Requirements problem Warning message The staging configuration directory (./...
Upgrade from Drupal 7 troubleshooting request