Skip to content

[4.0] Quadruple optin for update #36151

@StefanSTS

Description

@StefanSTS

Steps to reproduce the issue

In the update view of Joomla 4 in backend you see an update button.

You cannot press the button until you "opt in" with a tick in the input that the extensions are compatible.
After you tick a popup comes up if you really want to do that. 2nd "opt in".
Now I can press the update button. (But it's not the button for update, it's another opt in.)

Now I come to the next screen that shows an update button. (huh?)
I cannot click the update button, I have to tick another input, 4th "opt in".
There is no popup this time. (Wonderful, but why not, it was there in the screen before, shouldn't it be consistent?)
Now after clicking the 4th "opt in" I can finally click on Update and the button is doing what it says it would.

Expected result

If I see an update button, I like to see the action performed, otherwise I might want to read something like "Next step to Update". But I would prefer it even shorter.

What I actually expect is that the user is not held for a Dummy and gets one "opt in" and can then press the Update button without being hassled with unnecessary steps.

A hint towards the compatibility of extensions and the backup on one page would suffice.
With the tick of the input the "opt in" process should be good and done.
A popup to ask the user again, what he just now said he wants to do, is Kindergarten.

System information (as much as possible)

Came to me on updating two Joomla 4.0.3 to 4.0.4. I have to lie about the backup because for the test page I did not do that. So now I am a liar, or I have to do a backup for a test site where I do not even think about doing a backup. Being a liar is an ugly thing for me, btw, I don't like white or grey lies.

If you think this was a pretty long thing to read for a small issue like that, you exactly feel what I feel.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions