After upgrade from 6.1.8 to 7.5.6 all logins fail

[qpoint]

Ok, so that post sounds like the issue I have.
The is_active database field type is tinyInt, and values in it are integers 0 or 1.
I don't have a BaseEntity method called prepareAttributeValue().

There is however a method public function populateFromArray()
and this doesn't look right:

                switch ($valueType) {
                    case self::VARCHAR:
                        break;

                    case self::BOOL:
                        $value = ($value === 'true' || $value === '1' || $value === true);
                        break;

Would return false for a value of 1.

Before I just hack that, is this saying that the upgrade didn't happen and somehow the container application code did not get reflected onto the bind mount at www/var/html?

What's the best way to check the version of the code that it's actually running (and presumably would be what is present on the bind mount)?

[yuri]

The issue is that you still have v6.1 and PHP 8.1 which are incompatible.

[yuri]

It's Sunday evening. I go offline.

Do not hack anything. See forum links I posted.

[qpoint]

Thanks for all the help...getting closer.

[yuri]

Maybe try to upgrade to v7.0 first.

[qpoint]

I think that would be prudent. It looks like I have to do this step from CLI, and its not clear that I can control the version it will upgrade to.

[qpoint]

Things are working again. Searching through dockerhub, picked the last Php 7.x as image tag 7.0.10.
Stop the container, change to this image version:

espocrm:
# 10/22/23: from 6.1.8 to 7.0.10 (the last php 7.x release).
image: espocrm/espocrm:7.0.10
...

Up the container:

Up the container: `docker-compose up -d espocrm

Follow the logs:
Espo logs show a bunch of database operations.

Docker log:

docker-compose logs --timestamps --tail 100 -f espocrm

espocrm | 2023-10-22T22:18:51.493200612Z Run "upgrade" action.
espocrm | 2023-10-22T22:18:51.532031242Z Start upgrading process from version 6.1.8.
espocrm | 2023-10-22T22:19:04.788334427Z Start upgrading process from version 6.1.9.
espocrm | 2023-10-22T22:19:15.642838828Z Start upgrading process from version 6.1.10.
espocrm | 2023-10-22T22:21:52.239583298Z Upgrade process is finished. EspoCRM version is 7.0.10.

And this time it did the upgrade, whereas before there was no upgrade activity.
ersion in config.php is updated to 7.0.10.

Logins are working again.

The earlier attempt was indeed too big a leap in version. There were however no errors or indications that it couldn't do the upgrade...I guess because of Php 8.x incompatibility?

Now to find out if the next upgrade, which does move to Php 8.x, will proceed ok.

Many thanks to Yuri.