Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
documentation
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Jan 2010 at 12:15 UTC
Updated:
3 Jan 2014 at 01:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
confiz commentedThe documentation is completed for Drupal 6
Comment #2
confiz commentedComment #3
jhodgdonIt looks like these are already documented in Drupal 7.
Your patch for Drupal 6 is OK, except the part at the top:
I think this should be removed, because this doc header isn't attached to any file or function or constant.
Comment #4
jhodgdonActually, I misread this -- it is on EMERG. Duh.
Comment #5
gábor hojtsyNo mention of the RFC anymore?
Comment #6
jhodgdonAgreed, we should have the reference to the RFC in there. This is also missing in Drupal 7.
So for Drupal 7, the issue is that all of these WATCHDOG_* need to have a reference put in to the RFC (see the patch above - the line that was removed).
Then for Drupal 6 we need a patch that is just like the above but leaving in or adding the reference to the RFC.
Should be a good project for a novice doc contributor.
Comment #7
qasimzee commentedsubscribe
Comment #8
qasimzee commentedThe updated patch is attached.
Comment #10
qasimzee commentedupdated patch is attached
Comment #11
jhodgdonYou have to set the status back to "needs review" to launch the test bot. :)
Comment #12
jhodgdonThe patch isn't correct though. We are looking for a Drupal 7 patch that puts back in the line that said
Severity levels, as defined in RFC 3164 http://www.faqs.org/rfcs/rfc3164.html
Comment #13
Garrett Albright commentedIt looks like each declaration is now commented properly, but the bit about the RFC is still missing.
Comment #14
jhodgdonI don't think this patch really fixes the D7 issue. All of the individual WATCHDOG_* constants need a reference to the RFC.
Comment #15
Garrett Albright commentedEach individual one?
Comment #16
Garrett Albright commentedGrammar fix.
Comment #17
jhodgdonHmmm...
So think about where this will be displayed, a page like:
http://api.drupal.org/api/constant/WATCHDOG_ERROR/7
I don't think saying "These constant definitions..." makes sense in that context, because you are just documenting a single constant.
Come to think of it, the summary line is also not very good:
Log message severity -- Error: error conditions.
I don't think it should be plural, and it seems very awkward to me. Maybe we should make all of these something like this:
Watchdog log message severity constant indicating an error condition.
Thoughts?
Comment #18
Garrett Albright commentedPick those nits, dawg.
The text describing the severities are just copy-and-pasted from the RFC. I think they're fine, and (as seen in #15 and #16) I tend to be picky about such things.
Comment #19
Garrett Albright commentedComment #21
qasimzee commented#18: 696696-watchdog-constants-4-D7.patch queued for re-testing.
Comment #23
jhodgdonI'm happy with the patch in #18. Thanks!
I think the test bot is broken. This is a doc-only patch and obviously didn't affect the database being dropped (whatever that means).
Comment #24
jhodgdon#18: 696696-watchdog-constants-4-D7.patch queued for re-testing.
Comment #25
dries commentedCommitted to CVS HEAD. Thanks!
Comment #26
jhodgdonNeeds port to Drupal 6. It won't be the patch above exactly, but the resulting sections of doc should be the same.
Comment #27
Garrett Albright commentedD6 patch.
Comment #28
jhodgdonLooks good to me, thanks again!
Comment #29
gábor hojtsyThanks, committed.
Comment #30
asimmonds commentedThe D6 commit accidentally renamed the constant WATCHDOG_EMERG to WATCHDOG_EMERGENCY.
Follow-up patch to revert this.
Comment #31
Garrett Albright commentedOops. Sorry about that.
Comment #32
gábor hojtsyCommitted, thank you.