Posted by Senpai on March 31, 2007 at 6:27am
Jump to:
| Project: | Util |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
Here's one I've seen in other CMS's but Drupal hasn't implemented yet. A "clear logs" button that appears at the top of the Watchdog page. Why not?
Comments
#1
Senpai and I had an IRC chat about this.
dmitrig01: So we have a search box because then I can search for "blah blah blah", and delete everything that matches that from the logs.Senpai: But do you really have to search for yada yada?
dmitrig01: So you think no search?
dmitrig01: Because what would be really cool would be to save a search and then you can do things with it, like I can run a saved search at cron time, and do something with it, like delete everything that matches the criteria.
dmitrig01: We could also have an interface to add new categories to watchdog (if its extendible)
dmitrig01: And I can add a delete category, and search for everything with the word delete, that is in the user and node categories.
dmitrig01: So we automatically put node and user deletes in the delete category.
dmitrig01: and another action would be
dmitrig01: of course
dmitrig01: delete!!
dmitrig01: so I can search for everything with 'delete' in it, and delete that at the moment, or at cron, or I can delete everything from the user and node categories at the moment, or at cron, and that leaves the info people care about.
Senpai: I want a Delete All Now, so that I, as the dev, can see what pops up into the log on next page load.
Senpai: I should be able to set the log to display crons, php errors, or page-not-found errors, as my default view or
Senpai: is it possible to intercept the form, and set the default, without having to tie into the theme?
#2
Yeah, we were right about the Search-and-Destroy feature for log files. I just figured out exactly why too. One of my dev sites "accidentally" got a chunk of php in it that caused a parse error to be recorded in the logs, but didn't break the site.
If I'd had a search/delete feature in the watchdog, I could have nuked those 14 error lines, leaving my other log entries untouched for future reference.
#3
i'm taking over.
#4
#5
Litwol, what happened to this issue?
#6
nothing :-p
#7
subs
#8
See also this newer issue: #49333: A clear all logs button
#9
Fixed in the issue Dries pointed out. All is once again right with the Drupal World. :)