Currently the only settings DBlog offers is located on a separate page. This is a waste of code and too complicated for users. The attached patch simplifies the form element, fixes a bug where the default value would always be the same and moves it to the general logging & alerts settings form, which is created by system.module, like you can see in the screen shot.
![]()
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | dblog_cleanup_03.patch | 6.45 KB | dawehner |
| #5 | dblog_cleanup_02.patch | 3.01 KB | xano |
| #2 | dblog_cleanup_01.patch | 2.99 KB | xano |
| dblog_cleanup_00.patch | 2.96 KB | xano |
Comments
Comment #1
xanoComment #2
xanoComment #3
mr.baileysI agree that the "database logging" form is too small to warant it's own page/tab/form. Applied the patch and it works as advertised. Manually reviewed the patch:
I guess it should either be preceded by a comment (something like 'ensure that the buttons are displayed at the bottom of the form') or replaced by something like:
Since the title reads 'Database log entries to keep', it might make sense to talk about 'entries' instead of 'rows' in the description too?
Comment #4
xanoNew patch is on its way.
Comment #5
xanoFixed both issues as posted in #3.
Comment #6
dawehnerare there reasons for not using hook_form_FORMID_alter?
additional, there is also syslog module which has its settings.
here is a patch which fixes both problems, i'm wondering why the form_alter works in the admin.inc file.
Comment #7
dries commentedLooks great to me, and simplifies the experience a bit. Committed to CVS HEAD. Thanks!
Comment #8
xanoWe had an issue dedicated to Syslog already...
Also see #394332: Logging and alerts cleanup.
Comment #9
dawehnersry for that
Comment #11
xano