Improve update experience

[Graham-72]

I would like to propose that improving the update experience should become another objective for 1.5.

Ideally, I would like it to be able to happen automatically as with Wordpress, but at least it is something we should be able to delegate to a knowledgeable client.

As an example of something I find confusing with our current situation, here is a screenshot of what I was faced with this morning:

[Gormartsen]

👍 to add update process to 1.5

We could add option backup restore !

[quicksketch]

So some issues here aren't caused by core, some are:

• The first message is output when a module specifies hook_update_last_removed() and the current "schema_version" in the system table isn't past this number.
• The second message is coming from Backup and Migrate module. Maybe we could just remove it?
• The third message is caused by the first message's situation resulting in the updates being impossible.

So the only issue for core here is to resolve the double messaging between "No pending updates" message, which is inaccurate.

[Graham-72]

@quicksketch thanks for the explanation. Is there some easy wasy to find out which contrib module is causing the first message?

[klonos]

Is there some easy wasy to find out which contrib module is causing the first message?

The message says that some pending updates were not applied. I would try running update.php again (manually) to see it that lists the still pending updates. Each update says which module it is for.

[Graham-72]

try running update.php again

I have now tried this but it just produces exactly the same screen and no logs showing updates that have not been done. Perhaps I will have to look through the system table and check schema version records.

[Bojhan]

Just wondering - what is keeping us from going down the Wordpress path? Is our kernel not decoupled enough?

[docwilmot]

Just wondering - what is keeping us from going down the Wordpress path? Is our kernel not decoupled enough?

Now you've got me wondering too: whats the Wordpress path?

[klonos]

Now you've got me wondering too: whats the Wordpress path?

I believe that @Bojhan is referring to the one-click "upgrade" buttons that take care of fetching, unpacking and upgrading of WP core and plugins.

[klonos]

[klonos]

...there is even a bulk action for it:

[Graham-72]

I have a couple of Wordpress sites on my server and from time to time they update automatically, sending me an email to say they have done so. In their particular case this suits me just fine.

[klonos]

I wonder if this issue should be closed as outdated now @Graham-72 (and others). Between 2016 and now, we have implemented #3105 and #3271 and we have things like #1992 and #414 in our roadmap.

If we could have the specific modules and their respective before/after versions that caused the mess as shown in the screenshot in the initial report, then perhaps we could work something out to improve the situation. Without some steps to reproduce, it makes it hard 😓

[Graham-72]

I'm happy to close this issue as things are a lot better now and we have #2018 for automatic updating.