A link to update.php on admin/reports/updates, the same as there is on the admin/build/modules page would be useful --
Logical workflow is to download the updates from the links on this page, unzip them and install them straight away. A link here would mean you can get straight to update.php without going via other pages.

CommentFileSizeAuthor
#4 update.module.patch1.32 KBjoachim

Comments

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (duplicate)

#132746: Please add a link to update.php on the admin/logs/updates page

joachim’s picture

joachim commented
Status: Closed (duplicate) » Active

This isn't a duplicate of that issue -- that's on a contrib module and version 5.x. And it's closed for no particular good reason.
Reopening this.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (duplicate)

It's duplicate because this has already been discussed, and the maintainers of this module didn't think it was worth adding. The contrib vs. core split is irrelevant since this module lives in both, depending on the version. Besides, if you want this in core, new features only happen in 7.x.

joachim’s picture

joachim commented
Status: Closed (duplicate) » Needs review
StatusFileSize
new update.module.patch1.32 KB

Feature / usability bug. Room for debate there.

And the maintainer says 'I'm closing my own issue because I don't feel like working on this one again.'
That doesn't mean 'This issue is bad', it means 'I got bored / don't have time'.

I'm not, and I have time: here is a patch on DRUPAL-6 branch.

dww’s picture

dww
we/he/they
commented
Status: Needs review » Needs work

Senpai isn't a maintainer, myself and merlinofchaos are. I guess you didn't read the issue in full:

From #132746-1: Please add a link to update.php on the admin/logs/updates page:

dww - April 10, 2007 - 01:26
...
b) the /admin page already tells you if your schema is out of date an update.php should be run. i'm not convinced this module should duplicate that effort.

c) update_status.module doesn't have any way of knowing if an updated module will include a schema update. so, the only way to figure that out is to actually update the module, first. *all* kinds of documentation, the help text on and the /admin/build/modules page, and the /admin page, all tell you that after you update, you should be sure to run update.php. if you just switch back to your browser window which is still pointing to admin/logs/update, nothing will change unless you reload the page. and at that point, you'd expect it to say "there are no updates available -- your site is up to date", which is now true.
...

From #132746-2: Please add a link to update.php on the admin/logs/updates page:

merlinofchaos - April 11, 2007 - 16:32

I'm generally in agreement with dww. We don't know what the user's flow is going to be to update their module physically, and it changes a lot. The modules page contains code to see if update.php needs to be run.
...

I don't want to stay in a pushing match with you about this. However, I believe you're making some false assumptions with this patch:

A) Every module update changes the schema.
B) Breaking the strings in a stable series is going to happen for something of questionable usability improvement.

So, if you insist on pushing this forward, I recommend that you:
- Roll the patch against HEAD and move the version to 7.x-dev.
- Reword the text in your added message to be accurate.
- Find some other people to support and review this patch, since it certainly seems like the 2 co-maintainers are opposed.

Cheers,
-Derek

joachim’s picture

joachim commented

Sorry -- my misreading of that issue.
But I'm not sure everyone is talking about the same thing anyway: comment by dww - April 10, 2007 - 01:26 seems to be about automatic text that detects if an update run is required.
I was only talking about fixed help text.

I think you're wrong, because a site admin is far more likely to have their browser on admin/reports/updates while they're FTPing in another window than on admin/build/modules -- so then by your reasoning, the text should be removed from that page.

Anyway -- I can't be bothered to insist for something so minor. Meh.

drawk’s picture

drawk commented
Status: Needs work » Closed (duplicate)
joachim’s picture

joachim commented
Version: 6.2 » 7.x-dev
Status: Closed (duplicate) » Active

Reopening.
I find myself yet again looking at admin/reports/updates while I go fetch new updates and then wanting to get to update.php -- I don't think this is unusual workflow; the design of that page with links to d.org releases positively invites it!
I'll see about rolling a patch for D7.

dww’s picture

dww
we/he/they
commented

@joachim: If you want to solve this problem in D7, I suggest you take a look at #606190: Fix handling of database schema updates in update manager workflow first... That'd be a much better place for this than a link on the available updates report.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (won't fix)

Yeah, to the extent we should fix interaction between update status/manager and update.php, it should be at #606190: Fix handling of database schema updates in update manager workflow, not here.