These "auto-update" systems will - at some point - break your site in almost all instances where file customisation (essential for all custom templating) has been performed.

The "auto update" is simply a technique of replacing the files of an older version, with new files - and it is done indiscriminately. It does not have the "intellectual capacity" to judge whether it should keep custom files. It just overwrites everything.

It's like driving a bulldozer into your sitting room to re-arrange the furniture.

Unfortunately there is no easy recovery from this damage. The only way to restore previous behaviour is to roll back by restoring a previous backup. (I trust you did make a backup before you got Softalicious to march into your code?)

You need to make a backup of the database (or better still, clone a copy of it), then roll back the whole system (files and database) after which you can try pointing the file system to the copied database (done by editing your configure.php files). If this works, you will at least not lose data that may have been captured in the time between your "upgrade" and the point at which you roll back.

During all these procedures, you should set your store into maintenance mode so that no further data is written to the database (eg: cutomer registrations, orders, etc).

Simple moral... don't use an auto-update function - it has been stated not to do this on this forum for many, many years.