Hi Johan,
I know you're an experienced developer, so I will be curious to hear what you find in your debugging. I'll offer a few comments that I hope might be useful.
First, from what I can tell from your post, it seems you're using a pretty non-standard installation configuration - looks like OpenSUSE, MariaDB, Apache - plus if I recall correctly, you also have a lot of local AtoM code customizations. I don't know what PHP version you're using, or other details I might be missing, but from this alone there could be a number of issues... and there is also limited support we can offer.
However:
First, we've already found issues with MariaDB compatibility - see for example:
If you're using a custom collation, that could be causing issues.
Additionally, in the 2.6 version we have stopped using the STRICT_TRANS_TABLES sql_mode, as we found it was causing issues. We intend to revisit this for future releases, but for now if you have this mode (or an equivalent one) in place, this could also be contributing to issues. See the
installation docs here to see what SQL modes we are recommending that users set for 2.6.
In terms of the hashing error trying to create a user - in 2.6, we upgraded our password hashing algorithm to Argon2. This requires PHP 7.2 support for it to work. If you're trying to use PHP 7.0, then you can try changing the algorithm used to
bcrypt in
config/app.yml (the relevant section is near the bottom of that config file) - be sure to restart your services and clear the application cache. However, we did not do thorough testing with PHP 7.0 and you may encounter other issues - be warned!
Ultimately, If you have already loaded your data, I'm surprised you got past running the upgrade task, as there are migrations in there that should convert existing data to use the new collation, and to re-salt existing user passwords. When you manage to sort out your installation configuration, you may want to purge the database and reload your sqldump from before the upgrade, so you can re-run the upgrade task.
Either way, good luck with the debugging - please let us know how it goes!