"Install" button at admin/*/install should be labeled "Continue"

It does hurt too much just calling it "Continue", this because people will be constantly looking for that button.

Sorry for being so short, but of course I don't think that people will just give up and navigate away. My point was, that people are looking for the word "install" - this is the trigger word here.

The problem is; by saying "Continue" we indicate there is a next step, but give the user no clue what is next (even by common sense). This to the contrary of other uses of "Continue" (the most usable one in the installer) which are part of a flow, and thereby list out the steps - where you are in the process.

So by removing the word install (which is a clear word), we are moving it to "Continue" which will leave the user wondering for a second what is happening next. So now that we are choosing between surprise the user and confuse the user, I am opting for not choosing at all, because its all bad choices - and fixing it properly in D8 (e.g. we need an in-overlay wizard indicator).

I think push it to D8, we can fix this by introducing a wizard indicator for the overlay.

The problem is; by saying "Continue" we indicate there is a next step, but give the user no clue what is next (even by common sense).

Then, in that case, we should explain what's going to happen. Part of that is already slated for #686060: Explain that the Update manager only works if you have FTP or SSH access to your server. So based on whether the user needs to be redirected to authorize.php, the button should say "Continue", or "Install". D8 is nonsense for this issue; update manager may not even make it to D8.

I agree with @carlos8f on this:

based on whether the user needs to be redirected to authorize.php, the button should say "Continue", or "Install"

The logic here would need to be:

if (fileowner(_update_manager_extract_directory()) == fileowner(conf_path())) {
  // Show "Install" button
}
else {
  // Show "Continue" button
}

Workflow will still remain problematic on shared hosts though until #1008328: Uniqueify update-cache and update-extraction directories to prevent "Permission denied" errors or similar is solved, as another user's Drupal installation might create the update_extract directory causing us to select the wrong branch of the if statement.

This is really a duplicate of #1207354: Install new module v/s Add new module and probably #2577407: Action of uploading module/theme files should consistently be called "Add", not "Install" too? Not sure which one(s) we should keep open but probably not all 3. I will comment on the other 2 issues too.

Perhaps, but we should make sure it covers all the ground of the others, and includes the info about why this is such a usability SNAFU, etc. Plus, which has a good patch?

The issue title here has an opinion of how to solve the usability problem; the others may have a different opinion about how to solve the same problem?

Actually I think this one is not a straight duplicate of the other two. The other two issues are about what you see on admin/modules. This one is about what you see after you click the button that currently says "Install new module" and should probably say "Add new module".

Also, the other two issues have had a lot more comments and usability team involvement. If anything, we should close this one, and incorporate it into the others. We don't always choose to close the newer ones as duplicates.

See #3158126-5: Change text to "You must manually enable newly added modules, here. Steps here." -- Upon further reflection, I really think we should consolidate these 3 issues into 1, because they're all steps of the same process. See also #2577407-173: Action of uploading module/theme files should consistently be called "Add", not "Install" (which is the issue I think we should consolidate on) -- I think the next step would be to bring this process in to a Usability group meeting, get the group to decide what to do.

The patch to fix all 3 of these will only affect a few lines of code -- it's just UI text -- and I really think thinking of it as the usability of the whole process is the way to go.

There's a meta issue that should be this issue's parent.

FYI -- on the parent issue #2888657: [meta] Less confusing and more consistent wording needed in module/theme add/install/update the Usability team is discussing the UI text for this and about 10 other issues. Until decisions are made, making another patch here would probably be premature.

We now have a plan to fix this on #2577407: Action of uploading module/theme files should consistently be called "Add", not "Install", so marking this issue as a duplicate. I've asked people on this issue to be credited there.