../admin/reports/dblog can be filtered to show only "page not found" messages. Providing a "fix via 303 redirect" link on the Details page would be a nice feature. Even better it could analyse the Log and show the top 404 errors.
../admin/reports/dblog can be filtered to show only "page not found" messages. Providing a "fix via 303 redirect" link on the Details page would be a nice feature. Even better it could analyse the Log and show the top 404 errors.
Comments
Comment #1
dave reidThe top 404s can already be found at admin/reports/page-not-found with the dblog.module enabled. I like the idea of letting people fix the not founds in the log details, so I'm looking into it.
Comment #2
dave reidI can't find any easy way to do this yet. I might have to literally use hook_cron() and modify the actual watchdog records. For now I'm setting this as postponed.
Comment #3
mikeytown2 commentedAnother option would be to query the dblog, and create a new item on the menu.
Comment #4
dave reidIt would seem silly to duplicate the code of the dblog module when I should just be able to make one little alter and have it show up on the dblog pages.
Comment #5
mikeytown2 commentedCreate your own hook_watchdog() that modifies dblog_watchdog(). Inside of pathredirect_watchdog() if $log['type'] == 'page not found' then modify DB entry where everything matches up. Gotta make sure it runs after dblog_watchdog() though.
Comment #6
dave reidWould maybe make sense to do these on cron, rather than hook_watchdog() since we'd probably want to avoid another db query on what is potentially a fatal error.
Comment #7
mikeytown2 commentedDoing it on cron would work
Comment #8
andyf commentedHi, this is a cool idea, did you get any further?
Comment #9
mikeytown2 commentedsee #1272344: Improve create redirect workflow.