I would like us to provide an instant filter/switch at the top of the "Status report" page at admin/reports/status
, so that when viewed by various roles/personas, entries can be filtered to their respective field/focus/role/task-at-hand. Looking at the current list of options, I am suggesting the following categories:
- Security & performance:
- Access to update.php
- Backdrop CMS update notifications
- Backdrop CMS update status
- Cron maintenance tasks
- File system
- Node Access Permissions
- PHP memory limit
- Trusted Host Settings
- Developer information:
- Backdrop CMS (version)
- MySQL Database (version)
- MySQL Database 4-byte UTF-8 support
- Pending database updates
- jQuery
- PHP (version)
- PHP extensions
- PHP register globals
- Display error messages
- Web server (version)
- GD library rotate and desaturate effects
- Unicode library
- Miscellaneous (or something else, like "Generic" or "Features")
- Telemetry
- Upload progress
Perhaps we could make this work in a tag-based manner, so that multiple categories can be assigned to each entry. That would allow showing certain entries in multiple filters (for more than one persona). For instance, things like the following (from the list above) may be of interest to both a "developer" or "system admin" persona, as well as a "security officer" persona: - MySQL Database (version) - PHP (version) - Web server (version) These reports will be of different use for a developer (compatibility/features that each version brings) than for a security auditor (any potentially insecure versions in use, with known vulnerability issues).
Recent comments
Hi patch-works I did something similar with Drupal 7: a block with aniversaries of historical dates. You can see it at https://lassalle-kreis.de/ down in the blue footer, the middle column...
How to get a list of upcoming birthdays?
@indigoxela - I agree, I mentioned the SVG topic specifically for the dev meeting. I think we'll definitely want Nate involved in that discussion. Good call!
Apr 18th Weekly Meetings
Hi colbyat, re display in the browser: the problem is that when a 500 occurs, this PHP process died before being able to render anything. So that won't work. Logging is possible, but...
Displaying 500 errors