EspoCRM 7.1.0 released

[paul]

In my opinion it is a development instance. Because you are checking things before installing it on the productive instance.

[dev77]

I have two Linode instances both using Ubuntu 20.04... one is a small test server and the other is my large production server. I've installed Espo on my test server and added one record to it in order to test it with PHP 8.0. is that what you would call a "development instance?"

I thought a dev. instance might be a different download version.

[paul]

@dev77: You can install Espo (or other software) as a "development instance" to check new updates or develop own extensions without "playing" on the "productive instance". If you don't find any bugs or your extension is ready, then you can install it on the "production instance". So, both are normal installations of Espo, but only in the "production instance" you store your data an so on. I hope I could explain it understandable

[dev77]

What are "production instances?" vs. "development instances"? I got the notice from GitHub that 7.1.2 is now out so I'll do that one later this afternoon.

[murugappan]

I have upgraded all our development instances to 7.1.2. Everything is good. Will soon upgrade the production instances when downtime available.

Fantastic, good work.

[yuri]

"-s" only needed for 7.1.0->7.1.1 and 7.1.*->7.1.2 (not released yet, the message will be displayed in the terminal, so no need to remember about this).

[dev77]

OK. so if there is no message saying:

Reverting...
Package Archive doesn't exist.

.. then the update went through.

Should we continue to use the "-s" ?

[yuri]

Upgrade from 7.0.9 to 7.1.0 or upgrade from 7.0.9 to 7.1.1 went through. The only upgrade affected is from 7.1.0 to 7.1.1.

Displaying upgrade steps is a new improvement: https://github.com/espocrm/espocrm/issues/2234

Too many questions for me. Most are already answered here. Please spare me.

[dev77]

Are you saying that from now on we will get all of these messages when we update. Should I go ahead and run the update on my production server? Did you bring out a 7.1.2 version to fix this? Does the "-s" give us all the messages?

[murugappan]

Its odd. The problem happens only when we upgrade from 7.1.0 to 7.1.1. When we upgrade from 7.0.9 to 7.1.1 there is no problem at all. Now looking at the replies, did the upgrade from 7.0.9 to 7.1.1 go through? Anyway, i reset and upgrade as Yuri suggested. It works fine now but the messages still appear with success at the end.

[yuri]

It's success. No reverting and error message as it was before.

[dev77]

I change the data/config and I ran with -s and still got the messages.

$ sudo -u www-data php command.php upgrade -s


Current version is 7.1.0.
EspoCRM will be upgraded to version 7.1.1 now. Enter [Y] to continue.
Y
This may take a while. Do not close the terminal.
Downloading...
Upgrading...
Initialization...
Copying before upgrade files...
Rebuilding...
Before upgrade script execution...
Rebuilding...
Copying files...
Rebuilding...
Copying after upgrade files...
Rebuilding...
After upgrade script execution...
Rebuilding...
Finalization...
Upgrade is complete. Current version is 7.1.1.
You have the latest version.

Did the update actually happen or did it not. It says 7.1.1 in the "About" screen but did the files get updated?

[yuri]

Yes. The next upgrade package will handle it. You can change the version back to 7.1.0 in the data/config.

To upgrade w/o the error, try running the upgrade command with -s parameter. It will run in a single process, the error won't occur.

[dev77]

Edit. Actually. files correspond to v7.1.0. So it's reverted.

So you are saying the update did not 'take' and that everything is now as it was before the update?

[yuri]

I don't know why these mysterious messages are displayed. We will investigate it. I just tested the upgrade, got same messages.

Edit. Actually. files correspond to v7.1.0. So it's reverted.