Download & Extend

dblog_ext/dblog_filters TODO list

Project:Util
Version:6.x-3.x-dev
Component:Dblog_extension
Category:task
Priority:normal
Assigned:arhak
Status:active

Issue Summary

I will use this thread as a centralized TODO list of pending fixes to dblog_ext/dblog_filters suit

PS: please don't use "reply" on previous comments to keep them editable on time

Comments

#2

all the above issues with available patches will be bundled/altogether at #642200: review dblog_ext/dblog_filters updates

#3

One little thing that I would find helpful is to show the current date/time on the filter page so I can see what's recent in the log.

#4

@#3 do you mean showing the current date/time at admin/reports/dblog?
what if I don't have any date/time filter enabled?
what when the page gets old and the time gets outdated? a JS timer?
recent/aged filters are based on "within/beyond the last X minutes", what reference would make having the current time there?
a website could have an administrative tool for showing current time, even with JS updating it every minute, or even it might have a site-wide clock
could you extend on the exactly feature you would like?

#5

Just simply the current time when the page is generated; fancy updating is not important. It doesn't matter if a date/time filter is present.

Something like the attached (who needs sleep anyway).

AttachmentSize
dblog_ext.admin_.inc_.patch 714 bytes

#6

BTW, rather than sleeping, I also did this.

AttachmentSize
dblog_ext.module.patch 1002 bytes

#7

#5 & #6 are in the scope of dblog's enhancements, but not in the scope of dblog_filters

particularly #6 has a performance impact on a hook log_filters

those features might be useful, but I think they should be in a form_alter instead
they could be even in another sub-mod dblog_enhance totally independent from dblog_ext/dblog_filters

I might give them a try in the form of form_alter
do you agree with me on this?

#8

I just did them where it was convenient last night. As for the time patch, I have no issue with where it is.

I agree that the count patch could be far better somewhere else and done in a better way, such as a core patch to the original query. If you have time to create a core patch to do that, feel free; I do not and will forget by the time I do. You can take full credit for it.

If you would prefer these done differently and have the time, please go ahead.