Just updated some modules on a site with better messages enabled and had a bunch of update.php errors. This caused better message to display the popup and "overflow" the screen. I could not see all the messages and could not "reach" the OK button to clear them.

Of course, I have now added update* to the excluded pages... but valuable error information was lost since watchdog does not really capture all the info.

I would suggest a test to see if the system is in maintenance mode before using the popup method.

Maybe a quick alternative would be to have the default settings be to exclude all admin and update pages. E.g. show on every page except:

admin
admin/*
update*

I know I end up doing this for all my admins because they complain about closing the message box when doing admin functions. (But love it for end users).

Comments

Leeteq’s picture

Title: Disable Better messages in maintenance mode (e.g. during updates.php runs). » Sensible defaults for url exceptions
Version: 6.x-1.13 » 7.x-1.x-dev
Issue summary: View changes

PS. I think that many of us are working extensively in Maintenance mode on several sites, so we definetely do NOT want to disable this module on all urls or "only admin" urls while in Maintenance mode. That is not a solution, IMO. And those who want to exclude BM on admin pages can already simply add admin* to that list manually.

There are some pages where we should offer a standard block, though:

I always add the following urls to the "Show on every page except the listed pages" list..:

admin/config/user-interface/better-messages
admin/modules
update*
authoriz*

We do not want to 'risk'..:

- affecting critical processes and/or loosing important on-screen information at critical moments (updates, etc.)
- if this module malfunctions for some reason, we need to ensure that we can get to either reconfigure it, or disable it, hence we do not want to 'risk' having it run on the modules page or on its own settings page, just in case...

So I suggest simply adding those 4 paths to the default settings, perhaps/preferably with a small comment under that text field about why those 4 are "suggested".

  • UsingSession committed a0f50881 on 7.x-1.x
    Issue #1154416 by UsingSession: Sensible defaults for url exceptions
    
usingsession’s picture

Status: Active » Fixed

Added for review about the page update.php (or MAINTENANCE_MODE)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.