Closed (fixed)
Project:
Drupal.org customizations
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
13 Apr 2007 at 15:23 UTC
Updated:
21 Aug 2014 at 21:00 UTC
Jump to comment: Most recent
Now that watchdog.module is history, we need to rename it in project module to be dblog.module.
Also, we need a new component called syslog.module.
(Thinking loud: or should we lump them all under "logging"?)
Comments
Comment #1
dwwnot sure what i think about "logging" vs. the 2 separate module components... i could argue in favor of either approach. so, i'll leave that for someone with stronger opinions to decide. ;)
however, a word of warning from the internals of project_issue.module. it's easy to add new components, but renaming existing ones doesn't necessarily do what you'd expect. all the existing issues about watchdog would still be listed as "watchdog", and if you tried to follow-up to them, you'd get a validation error on the form and you'd have to assign it to dblog.module or logging yourself. perhaps that's not the end of the world, but i wanted to mention it.
if you wanted to avoid this behavior, we'd need a db query to run on d.o to automatically rename the component for all current issues, in addition to changing the settings in the UI on the drupal project node.
hope that makes sense,
-derek
Comment #2
kbahey commentedI guess having two (syslog.module, and dblog.module) is more consistent with the way we do things now.
As for renaming, can this be done per release? For example leave issues as "watchdog.module" up to 5.x, and make 6.x and beyond "dblog.module"? Is this viable?
This would be best, since someone reporting an issue on 4.7 or 5.x would be really confused if they can't find watchdog.module.
Even renaming via a one time query will get us into that situation if it is global.
Comment #3
gábor hojtsyI added the syslog.module and dblog.module components with consistency (as stated) with other components. As components are global and not tied to versions, I don't see any way to remove the watchdog.module component any time soon (ie. at least until Drupal 5 becomes unsupported, but even then closed issues might be interesting to have this component assigned for future data mining or whatever). So keep history.
Comment #4
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.