Hi,

I came across this issue from here: #286035: Remove update.php number dropdowns

While the referenced issue clearly states the case for removing the current update.php UI, I think taking it out completely is a mistake. Sure, contrib can add the UI back in with hook_form_alter, but surely core should do this? Why can't we have an Advanced Updates module, disabled by default that can be enabled by site admin to allow the old (but complex) UI to be reinstated? I have needed to use that feature on numerous occasions in previous versions of Drupal and for me taking out useful and necessary functionality *completely* is effectively a bug.

To illustrate how I think this should be tackled, think PHP Filter in Drupal 6. It was no longer automatically installed, but still available as a part of core. I think the Advanced Update UI should get the same treatment. Thoughts?

Comments

moshe weitzman’s picture

moshe weitzman CreditAttribution: moshe weitzman commented

There are so many developer tasks that are useful and not in core. This is one of those. Viewing database queries, viewing the theme registry, viewing the structure of a form/node/user/$page, ...

I'll let someone else mark this Won't fix.

Damien Tournoud’s picture

Damien Tournoud CreditAttribution: Damien Tournoud commented
Project: Drupal core » Devel
Version: 7.x-dev » 7.x-1.x-dev
Component: update system » devel
Category: bug » feature

Moving to Moshe's plate (sorry...).

greg.harvey’s picture

greg.harvey
Primary language English
CreditAttribution: greg.harvey commented

I'm still not convinced it's not a core issue, but if it goes to contrib, so be it. For the record I think it's crazy to say the logic for granular updates is in core but the UI is not. That's just weird and asking for trouble, IMHO. What's to stop future core developers thinking the update functions are obsolete? I would have no objection if the whole bag either moved to contrib *or* core, but splitting it like this feels like a bad idea to my management side.

I'll get my coat. ;-)

greg.harvey’s picture

greg.harvey
Primary language English
CreditAttribution: greg.harvey commented

Oh, another point that just came to mind. I hope this will be a separate module in the Devel package, rather than part of Devel, once a patch is in. Sometimes I've had trouble running devel (on Windows and Linux) so would prefer something like this to be a standalone module in the Devel package, just in case, so it's never unusable because of some system quirk that stops Devel.

If I get time, I'll look at this, but it won't be for at least a week, looking at my schedule... =(

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented

I also vote for this being a core issue, to at least have a configurable option to decide if they're shown or not.

willzyx’s picture

willzyx CreditAttribution: willzyx commented
Issue summary: View changes
Status: Active » Closed (outdated)

Closing for lack of activity. Feel free to reopen if the issue still exists