Examples for Developers - 8.x-1.x | Drupal Quality Assurance

Latest changes

So Long and Thanks for all the Tests

1 week 1 day ago

Support

In case of troubles

check the FAQ. Please make sure you've tried the test locally.
search known testbot issues and then create a new issue if yours isn't there already. Please give a link to the test.

Test client logs

No clients to display.

Examples for Developers - 8.x-1.x

Test status

Status	Result
Last received	Fri, 02/03/2012 - 07:11:06
Last requested	Fri, 02/03/2012 - 07:12:02
Last tested	Fri, 02/03/2012 - 07:12:26
Test count	44

Environment status

MySQL	fail
Code review	fail

Overall Result	fail

Branch information

Identifier	8.x-1.x
Project	Examples for Developers
Link	Project information

Event logView entire log

ID	Message	Timestamp
3152563	Result retrieved by project client.	4 years 6 days ago
2947228	Result retrieved by project client.	4 years 3 weeks ago
2947193	Result retrieved by project client.	4 years 3 weeks ago
2947173	Result received from test client #659.	4 years 3 weeks ago
2947153	Result received from test client #654.	4 years 3 weeks ago
2947143	Requested by test client #654.	4 years 3 weeks ago
2947138	Requested by test client #659.	4 years 3 weeks ago
2947123	Test request received.	4 years 3 weeks ago
2612838	Result retrieved by project client.	4 years 12 weeks ago
2612828	Result retrieved by project client.	4 years 12 weeks ago

SummaryFAILED: [[Coder]]: [Code review] 48 minor(s), 14 critical(s), and 327 normal(s); [[SimpleTest]]: [MySQL] Failed to run tests: failed during invocation of run-tests.sh.

Details

MySQL
Code review

MySQL

Setup environment
Detect an invalid patch URL
Detect invalid repository information
Detect invalid patch format
Detect a non-applicable patch
Detect invalid PHP syntax
Detect a Drupal installation failure
Detect a test run failure
Ensure that you can install SimpleTest locally and invoke tests using the command line script.
Detect a failing test
Complete test suite with all tests passing

Review log

Code review

Setup environment
Detect an invalid patch URL
Detect invalid repository information
Detect invalid patch format
Detect a non-applicable patch
Detect invalid PHP syntax
Detect a review run failure
Detect coder flags
Ensure that your code follows the Drupal standard and passes a coder review.
Complete coder review with all passed

48 minor(s), 14 critical(s), and 327 normal(s)

Non-pass

Test name Minor Critical Normal

action_example/action_example.module 3 0 4

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	action_example.module	64	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	action_example.module	66	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	action_example.module	67	N/A
Function documentation should be less than 80 characters per line.	Other	action_example.module	67	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	action_example.module	189	N/A
If you define a @param or @return, you should document it as well.	Other	action_example.module	281	N/A
Function summaries should be one line only. (Drupal Docs)	Other	action_example.module	311	N/A

ajax_example/ajax_example.module 3 0 34

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	ajax_example.module	29	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	ajax_example.module	29	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	35	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	43	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	209	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.module	232	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	260	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	260	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	269	N/A
Separate comments from comment syntax by a space.	Other	ajax_example.module	285	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	301	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	326	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	332	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	332	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	376	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	382	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	388	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	395	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	398	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	398	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	432	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	435	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	435	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example.module	442	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	448	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	465	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	507	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	507	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	514	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	517	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	521	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	525	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	531	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	535	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	536	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	537	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	538	N/A

ajax_example/ajax_example.test 0 0 12

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.test	34	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	35	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.test	35	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	36	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	37	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	40	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.test	40	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	41	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	42	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	45	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	46	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	47	N/A

ajax_example/ajax_example_advanced.inc 0 0 13

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_advanced.inc	212	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	238	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	249	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	263	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	277	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	296	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	311	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	327	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	341	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	353	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	372	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_advanced.inc	383	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	399	N/A

ajax_example/ajax_example_graceful_degradation.inc 0 1 15

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	ajax_example_graceful_degradation.inc	16	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	21	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	63	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	153	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_graceful_degradation.inc	184	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	230	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	269	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	291	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example_graceful_degradation.inc	303	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	321	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example_graceful_degradation.inc	327	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example_graceful_degradation.inc	328	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_graceful_degradation.inc	343	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	ajax_example_graceful_degradation.inc	485	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	496	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_graceful_degradation.inc	513	N/A

ajax_example/ajax_example_misc.inc 0 0 3

Message	Group	Filename	Line	Function
If you define a @param or @return, you should document it as well.	Other	ajax_example_misc.inc	17	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_misc.inc	42	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example_misc.inc	55	N/A

ajax_example/ajax_example_node_form_alter.inc 2 0 5

Message	Group	Filename	Line	Function
If you define a @param or @return, you should document it as well.	Other	ajax_example_node_form_alter.inc	54	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	54	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	63	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example_node_form_alter.inc	97	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example_node_form_alter.inc	99	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	119	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	139	N/A

batch_example/batch_example.install 0 1 0

Message	Group	Filename	Line	Function	Status
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	batch_example.install	57	N/A

batch_example/batch_example.module 1 0 6

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	batch_example.module	27	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	89	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	122	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	165	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	237	N/A
If you define a @param or @return, you should document it as well.	Other	batch_example.module	238	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	batch_example.module	238	N/A

block_example/block_example.module 1 0 3

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	block_example.module	38	N/A
Separate comments from comment syntax by a space.	Other	block_example.module	126	N/A
Use Drupal's format_date(), not PHP's default date().	Other	block_example.module	156	N/A
Format should be `* Implementation of hook_foo().`	Other	block_example.module	201	N/A

cache_example/cache_example.module 0 0 2

Message	Group	Filename	Line	Function	Status
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	cache_example.module	37	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	cache_example.module	91	N/A

contextual_links_example/contextual-links-example-object.tpl.php 0 0 1

Message	Group	Filename	Line	Function	Status
Function documentation should be less than 80 characters per line.	Other	contextual-links-example-object.tpl.php	5	N/A

dbtng_example/dbtng_example.module 1 0 6

Message	Group	Filename	Line	Function
indent secondary line of comment one space	Other	dbtng_example.module	67	N/A
Function documentation should be less than 80 characters per line.	Other	dbtng_example.module	188	N/A
Function documentation should be less than 80 characters per line.	Other	dbtng_example.module	200	N/A
Remove the empty commented line in your function documentation.	Other	dbtng_example.module	244	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	dbtng_example.module	314	N/A
Separate comments from comment syntax by a space.	Other	dbtng_example.module	323	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	dbtng_example.module	359	N/A

dbtng_example/dbtng_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Separate comments from comment syntax by a space.	Other	dbtng_example.test	45	N/A

email_example/email_example.module 1 0 9

Message	Group	Filename	Line	Function
Format should be `* Implementation of hook_foo().`	Other	email_example.module	29	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	40	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	76	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	133	N/A
Separate comments from comment syntax by a space.	Other	email_example.module	150	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	157	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	171	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	196	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	205	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	206	N/A

email_example/email_example.test 0 0 12

Message	Group	Filename	Line	Function
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	12	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	41	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	45	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	52	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	53	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	60	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	62	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	66	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	67	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	73	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	81	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	90	N/A

examples.index.php 0 0 7

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	examples.index.php	13	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	19	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	20	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	23	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	24	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	31	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	32	N/A

examples.module 0 0 2

Message	Group	Filename	Line	Function	Status
Function documentation should be less than 80 characters per line.	Other	examples.module	6	N/A
Function documentation should be less than 80 characters per line.	Other	examples.module	17	N/A

field_example/field_example.module 6 1 3

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	field_example.module	14	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	field_example.module	45	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	field_example.module	46	N/A
put a space between the asterisk and the comment text	Other	field_example.module	51	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.module	275	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	field_example.module	300	N/A
Function summaries should be one line only. (Drupal Docs)	Other	field_example.module	317	N/A
Doxygen uses @todo and @bug to markup things to be done.	Other	field_example.module	321	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.module	329	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.module	334	N/A

file_example/file_example.module 3 4 13

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	file_example.module	16	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	24	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	69	N/A
Use Drupal's format_date(), not PHP's default date().	Other	file_example.module	91	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	file_example.module	240	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	file_example.module	278	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	file_example.module	281	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	file_example.module	290	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	file_example.module	332	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	393	N/A
Remove the empty commented line in your function documentation.	Other	file_example.module	420	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	436	N/A
If you define a @param or @return, you should document it as well.	Other	file_example.module	439	N/A
If you define a @param or @return, you should document it as well.	Other	file_example.module	440	N/A
The $message argument to drupal_set_message() should be enclosed within t() so that it is translatable.	Other	file_example.module	458	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized. (Drupal Docs)	Other	file_example.module	458	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	466	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	485	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	file_example.module	491	N/A
Use PHP's master function, not an alias. (List of PHP aliases)	Other	file_example.module	517	N/A

file_example/file_example_session_streams.inc 0 0 2

Message	Group	Filename	Line	Function	Status
Doxygen uses @todo and @bug to markup things to be done.	Other	file_example_session_streams.inc	442	N/A
Doxygen uses @todo and @bug to markup things to be done.	Other	file_example_session_streams.inc	547	N/A

filter_example/filter_example.module 0 0 2

Message	Group	Filename	Line	Function	Status
Function documentation should be less than 80 characters per line.	Other	filter_example.module	55	N/A
The $text argument to l() should be enclosed within t() so that it is translatable.	Other	filter_example.module	90	N/A

form_example/form_example.module 0 0 4

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	form_example.module	17	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example.module	37	N/A
Doxygen uses @todo and @bug to markup things to be done.	Other	form_example.module	179	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	form_example.module	180	N/A

form_example/form_example_elements.inc 0 0 7

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	form_example_elements.inc	169	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	172	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	173	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	174	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	176	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_elements.inc	191	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_elements.inc	445	N/A

form_example/form_example_states.inc 0 0 8

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	form_example_states.inc	10	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_states.inc	38	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_states.inc	48	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_states.inc	56	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	70	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	126	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	210	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	243	N/A

form_example/form_example_tutorial.inc 0 0 14

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	form_example_tutorial.inc	32	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	35	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_tutorial.inc	38	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	63	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	91	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	134	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	175	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_tutorial.inc	185	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	224	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_tutorial.inc	278	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	298	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	370	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	537	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	681	N/A

form_example/form_example_wizard.inc 0 0 17

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	36	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	40	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	59	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	140	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	161	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	170	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	171	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	193	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	205	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_wizard.inc	215	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_wizard.inc	220	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	227	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	261	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	279	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_wizard.inc	283	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	286	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	287	N/A

menu_example/menu_example.module 2 0 18

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	menu_example.module	20	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	53	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	90	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	92	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	101	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	132	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	144	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	215	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	218	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	247	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	249	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	256	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	277	N/A
Function summaries should be one line only. (Drupal Docs)	Other	menu_example.module	309	N/A
Function summaries should be one line only. (Drupal Docs)	Other	menu_example.module	344	N/A
If you define a @param or @return, you should document it as well.	Other	menu_example.module	348	N/A
Function documentation should be less than 80 characters per line.	Other	menu_example.module	395	N/A
Use an indent of 2 spaces, with no tabs	Other	menu_example.module	459	N/A
If you define a @param or @return, you should document it as well.	Other	menu_example.module	469	N/A
Function summaries should be one line only. (Drupal Docs)	Other	menu_example.module	482	N/A

menu_example/menu_example.test 0 0 6

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	33	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	34	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	55	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	60	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	82	N/A

nodeapi_example/nodeapi_example.module 0 0 8

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	nodeapi_example.module	46	N/A
Function summaries should be one line only. (Drupal Docs)	Other	nodeapi_example.module	75	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	84	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	85	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	88	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	89	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	104	N/A
Remove the empty commented line in your function documentation.	Other	nodeapi_example.module	106	N/A

nodeapi_example/nodeapi_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Separate comments from comment syntax by a space.	Other	nodeapi_example.test	194	N/A

node_access_example/node_access_example.module 1 0 3

Message	Group	Filename	Line	Function
If you define a @param or @return, you should document it as well.	Other	node_access_example.module	116	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	node_access_example.module	116	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	node_access_example.module	118	N/A
Function summaries should be one line only. (Drupal Docs)	Other	node_access_example.module	226	N/A

node_access_example/node_access_example.test 0 1 1

Message	Group	Filename	Line	Function	Status
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	node_access_example.test	57	N/A
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	node_access_example.test	71	N/A

node_example/node_example.install 1 1 8

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	node_example.install	11	N/A
Use an indent of 2 spaces, with no tabs	Other	node_example.install	51	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	59	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	node_example.install	60	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	72	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	73	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	74	N/A
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	node_example.install	149	N/A
If you define a @param or @return, you should document it as well.	Other	node_example.install	157	N/A
If you define a @param or @return, you should document it as well.	Other	node_example.install	199	N/A

node_example/node_example.module 0 1 1

Message	Group	Filename	Line	Function	Status
Use the matching Drupal theme functions, not raw HTML.	Other	node_example.module	174	N/A
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	node_example.module	191	N/A

pager_example/pager_example.module 0 0 1

Message	Group	Filename	Line	Function	Status
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)	Other	pager_example.module	2	N/A

pager_example/pager_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)	Other	pager_example.test	2	N/A

page_example/page_example.module 2 0 3

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	page_example.module	17	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	page_example.module	100	N/A
Remove the empty commented line in your function documentation.	Other	page_example.module	142	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	page_example.module	145	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	page_example.module	197	N/A

page_example/page_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Remove the empty commented line in your function documentation.	Other	page_example.test	9	N/A

queue_example/queue_example.module 0 2 8

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	queue_example.module	29	N/A
Function documentation should be less than 80 characters per line.	Other	queue_example.module	30	N/A
Function summaries should be one line only. (Drupal Docs)	Other	queue_example.module	49	N/A
table names should be enclosed in {curly_brackets}	Other	queue_example.module	79	N/A
table names should be enclosed in {curly_brackets}	Other	queue_example.module	88	N/A
Function summaries should be one line only. (Drupal Docs)	Other	queue_example.module	158	N/A
If you define a @param or @return, you should document it as well.	Other	queue_example.module	246	N/A
Use Drupal's format_date(), not PHP's default date().	Other	queue_example.module	253	N/A
Use Drupal's format_date(), not PHP's default date().	Other	queue_example.module	258	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	queue_example.module	264	N/A

queue_example/queue_example.test 0 1 1

Message	Group	Filename	Line	Function	Status
table names should be enclosed in {curly_brackets}	Other	queue_example.test	32	N/A
Separate comments from comment syntax by a space.	Other	queue_example.test	47	N/A

render_example/render_example.module 0 0 5

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	render_example.module	51	N/A
Use Drupal's format_date(), not PHP's default date().	Other	render_example.module	206	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	render_example.module	355	N/A
Function summaries should be one line only. (Drupal Docs)	Other	render_example.module	522	N/A
Function summaries should be one line only. (Drupal Docs)	Other	render_example.module	537	N/A

simpletest_example/simpletest_example.module 1 0 3

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	simpletest_example.module	114	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.module	121	N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSE	Other	simpletest_example.module	125	N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSE	Other	simpletest_example.module	127	N/A

simpletest_example/simpletest_example.test 3 0 3

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	simpletest_example.test	10	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.test	19	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.test	20	N/A
Function summaries should be one line only. (Drupal Docs)	Other	simpletest_example.test	97	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.test	103	N/A
Use Drupal's format_date(), not PHP's default date().	Other	simpletest_example.test	140	N/A

tablesort_example/tablesort_example.install 0 0 1

Message	Group	Filename	Line	Function	Status
Remove the empty commented line in your function documentation.	Other	tablesort_example.install	9	N/A

tablesort_example/tablesort_example.test 0 0 2

Message	Group	Filename	Line	Function	Status
Separate comments from comment syntax by a space.	Other	tablesort_example.test	38	N/A
Separate comments from comment syntax by a space.	Other	tablesort_example.test	47	N/A

theming_example/theming_example.module 0 0 2

Message	Group	Filename	Line	Function	Status
Function summaries should be one line only. (Drupal Docs)	Other	theming_example.module	106	N/A
Function summaries should be one line only. (Drupal Docs)	Other	theming_example.module	272	N/A

theming_example/theming_example_text_form.tpl.php 0 0 1

Message	Group	Filename	Line	Function	Status
Remove the empty commented line in your function documentation.	Other	theming_example_text_form.tpl.php	10	N/A

token_example/token_example.module 0 1 1

Message	Group	Filename	Line	Function	Status
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	token_example.module	68	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	token_example.module	122	N/A

trigger_example/trigger_example.module 1 0 6

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	trigger_example.module	106	N/A
Remove the empty commented line in your function documentation.	Other	trigger_example.module	109	N/A
Function summaries should be one line only. (Drupal Docs)	Other	trigger_example.module	143	N/A
Function documentation should be less than 80 characters per line.	Other	trigger_example.module	221	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	trigger_example.module	234	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	trigger_example.module	236	N/A
Format should be `* Implementation of hook_foo().`	Other	trigger_example.module	293	N/A

vertical_tabs_example/vertical_tabs_example.module 0 0 1

Message	Group	Filename	Line	Function	Status
Use the matching Drupal theme functions, not raw HTML.	Other	vertical_tabs_example.module	97	N/A

xmlrpc_example/xmlrpc_example.module 2 0 36

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	21	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	98	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	198	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	228	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	232	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	232	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	233	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	233	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	235	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	261	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	287	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	292	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	311	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	xmlrpc_example.module	356	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	362	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	369	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	376	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	377	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	411	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	414	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	415	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	452	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	455	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	456	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	489	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	494	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	495	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	608	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	609	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	620	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	622	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	622	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	623	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	623	N/A
Format should be `* Implementation of hook_foo().`	Other	xmlrpc_example.module	632	N/A
'Implementation' should be at the start of the sentence and begin with a capitialized letter	Other	xmlrpc_example.module	632	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	638	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	652	N/A

All

Test name Minor Critical Normal

action_example/action_example.module 3 0 4

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	action_example.module	64	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	action_example.module	66	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	action_example.module	67	N/A
Function documentation should be less than 80 characters per line.	Other	action_example.module	67	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	action_example.module	189	N/A
If you define a @param or @return, you should document it as well.	Other	action_example.module	281	N/A
Function summaries should be one line only. (Drupal Docs)	Other	action_example.module	311	N/A

action_example/action_example.test 0 0 0

ajax_example/ajax_example.install 0 0 0

ajax_example/ajax_example.module 3 0 34

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	ajax_example.module	29	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	ajax_example.module	29	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	35	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	43	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	209	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.module	232	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	260	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	260	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	269	N/A
Separate comments from comment syntax by a space.	Other	ajax_example.module	285	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	301	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	326	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	332	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	332	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	376	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	382	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	388	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	395	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	398	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	398	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	432	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	435	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	435	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example.module	442	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	448	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	465	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	507	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example.module	507	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	514	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	517	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	521	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example.module	525	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example.module	531	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	535	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	536	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	537	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.module	538	N/A

ajax_example/ajax_example.test 0 0 12

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.test	34	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	35	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.test	35	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	36	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	37	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	40	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example.test	40	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	41	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	42	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	45	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	46	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example.test	47	N/A

ajax_example/ajax_example_advanced.inc 0 0 13

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_advanced.inc	212	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	238	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	249	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	263	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	277	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	296	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	311	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	327	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	341	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	353	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	372	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_advanced.inc	383	N/A
Use Drupal's format_date(), not PHP's default date().	Other	ajax_example_advanced.inc	399	N/A

ajax_example/ajax_example_graceful_degradation.inc 0 1 15

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	ajax_example_graceful_degradation.inc	16	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	21	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	63	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	153	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_graceful_degradation.inc	184	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	230	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	269	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	ajax_example_graceful_degradation.inc	291	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example_graceful_degradation.inc	303	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	321	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example_graceful_degradation.inc	327	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example_graceful_degradation.inc	328	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_graceful_degradation.inc	343	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	ajax_example_graceful_degradation.inc	485	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_graceful_degradation.inc	496	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	ajax_example_graceful_degradation.inc	513	N/A

ajax_example/ajax_example_misc.inc 0 0 3

Message	Group	Filename	Line	Function
If you define a @param or @return, you should document it as well.	Other	ajax_example_misc.inc	17	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_misc.inc	42	N/A
If you define a @param or @return, you should document it as well.	Other	ajax_example_misc.inc	55	N/A

ajax_example/ajax_example_node_form_alter.inc 2 0 5

Message	Group	Filename	Line	Function
If you define a @param or @return, you should document it as well.	Other	ajax_example_node_form_alter.inc	54	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	54	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	63	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example_node_form_alter.inc	97	N/A
Use an indent of 2 spaces, with no tabs	Other	ajax_example_node_form_alter.inc	99	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	119	N/A
Function summaries should be one line only. (Drupal Docs)	Other	ajax_example_node_form_alter.inc	139	N/A

batch_example/batch_example.install 0 1 0

Message	Group	Filename	Line	Function	Status
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	batch_example.install	57	N/A

batch_example/batch_example.module 1 0 6

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	batch_example.module	27	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	89	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	122	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	165	N/A
Function summaries should be one line only. (Drupal Docs)	Other	batch_example.module	237	N/A
If you define a @param or @return, you should document it as well.	Other	batch_example.module	238	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	batch_example.module	238	N/A

batch_example/batch_example.test 0 0 0

block_example/block_example.install 0 0 0

block_example/block_example.module 1 0 3

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	block_example.module	38	N/A
Separate comments from comment syntax by a space.	Other	block_example.module	126	N/A
Use Drupal's format_date(), not PHP's default date().	Other	block_example.module	156	N/A
Format should be `* Implementation of hook_foo().`	Other	block_example.module	201	N/A

block_example/block_example.test 0 0 0

cache_example/cache_example.module 0 0 2

Message	Group	Filename	Line	Function	Status
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	cache_example.module	37	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	cache_example.module	91	N/A

cache_example/cache_example.test 0 0 0

contextual_links_example/contextual-links-example-object.tpl.php 0 0 1

Message	Group	Filename	Line	Function	Status
Function documentation should be less than 80 characters per line.	Other	contextual-links-example-object.tpl.php	5	N/A

contextual_links_example/contextual_links_example.module 0 0 0

contextual_links_example/contextual_links_example.test 0 0 0

cron_example/cron_example.module 0 0 0

cron_example/cron_example.test 0 0 0

dbtng_example/dbtng_example.install 0 0 0

dbtng_example/dbtng_example.module 1 0 6

Message	Group	Filename	Line	Function
indent secondary line of comment one space	Other	dbtng_example.module	67	N/A
Function documentation should be less than 80 characters per line.	Other	dbtng_example.module	188	N/A
Function documentation should be less than 80 characters per line.	Other	dbtng_example.module	200	N/A
Remove the empty commented line in your function documentation.	Other	dbtng_example.module	244	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	dbtng_example.module	314	N/A
Separate comments from comment syntax by a space.	Other	dbtng_example.module	323	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	dbtng_example.module	359	N/A

dbtng_example/dbtng_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Separate comments from comment syntax by a space.	Other	dbtng_example.test	45	N/A

email_example/email_example.module 1 0 9

Message	Group	Filename	Line	Function
Format should be `* Implementation of hook_foo().`	Other	email_example.module	29	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	40	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	76	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	133	N/A
Separate comments from comment syntax by a space.	Other	email_example.module	150	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	157	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	171	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	196	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	205	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.module	206	N/A

email_example/email_example.test 0 0 12

Message	Group	Filename	Line	Function
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	12	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	41	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	45	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	52	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	53	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	60	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	62	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	66	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	67	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	73	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	81	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	email_example.test	90	N/A

examples.index.php 0 0 7

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	examples.index.php	13	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	19	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	20	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	23	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	24	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	31	N/A
Function documentation should be less than 80 characters per line.	Other	examples.index.php	32	N/A

examples.module 0 0 2

Message	Group	Filename	Line	Function	Status
Function documentation should be less than 80 characters per line.	Other	examples.module	6	N/A
Function documentation should be less than 80 characters per line.	Other	examples.module	17	N/A

field_example/field_example.install 2 0 0

Message	Group	Filename	Line	Function	Status
Format should be `* Implementation of hook_foo().`	Other	field_example.install	16	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	field_example.install	20	N/A

field_example/field_example.module 6 1 3

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	field_example.module	14	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	field_example.module	45	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	field_example.module	46	N/A
put a space between the asterisk and the comment text	Other	field_example.module	51	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.module	275	N/A
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	field_example.module	300	N/A
Function summaries should be one line only. (Drupal Docs)	Other	field_example.module	317	N/A
Doxygen uses @todo and @bug to markup things to be done.	Other	field_example.module	321	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.module	329	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.module	334	N/A

field_example/field_example.test 5 0 0

Message	Group	Filename	Line	Function
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.test	33	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.test	52	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.test	53	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.test	54	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	field_example.test	55	N/A

file_example/file_example.module 3 4 13

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	file_example.module	16	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	24	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	69	N/A
Use Drupal's format_date(), not PHP's default date().	Other	file_example.module	91	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	file_example.module	240	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	file_example.module	278	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	file_example.module	281	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	file_example.module	290	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)	Other	file_example.module	332	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	393	N/A
Remove the empty commented line in your function documentation.	Other	file_example.module	420	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	436	N/A
If you define a @param or @return, you should document it as well.	Other	file_example.module	439	N/A
If you define a @param or @return, you should document it as well.	Other	file_example.module	440	N/A
The $message argument to drupal_set_message() should be enclosed within t() so that it is translatable.	Other	file_example.module	458	N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized. (Drupal Docs)	Other	file_example.module	458	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	466	N/A
Function summaries should be one line only. (Drupal Docs)	Other	file_example.module	485	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	file_example.module	491	N/A
Use PHP's master function, not an alias. (List of PHP aliases)	Other	file_example.module	517	N/A

file_example/file_example.test 0 0 0

file_example/file_example_session_streams.inc 0 0 2

Message	Group	Filename	Line	Function	Status
Doxygen uses @todo and @bug to markup things to be done.	Other	file_example_session_streams.inc	442	N/A
Doxygen uses @todo and @bug to markup things to be done.	Other	file_example_session_streams.inc	547	N/A

filter_example/filter_example.module 0 0 2

Message	Group	Filename	Line	Function	Status
Function documentation should be less than 80 characters per line.	Other	filter_example.module	55	N/A
The $text argument to l() should be enclosed within t() so that it is translatable.	Other	filter_example.module	90	N/A

filter_example/filter_example.test 0 0 0

form_example/form_example.module 0 0 4

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	form_example.module	17	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example.module	37	N/A
Doxygen uses @todo and @bug to markup things to be done.	Other	form_example.module	179	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	form_example.module	180	N/A

form_example/form_example.test 0 0 0

form_example/form_example_elements.inc 0 0 7

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	form_example_elements.inc	169	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	172	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	173	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	174	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_elements.inc	176	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_elements.inc	191	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_elements.inc	445	N/A

form_example/form_example_states.inc 0 0 8

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	form_example_states.inc	10	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_states.inc	38	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_states.inc	48	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_states.inc	56	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	70	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	126	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	210	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_states.inc	243	N/A

form_example/form_example_tutorial.inc 0 0 14

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	form_example_tutorial.inc	32	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	35	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_tutorial.inc	38	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	63	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	91	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	134	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	175	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_tutorial.inc	185	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	224	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_tutorial.inc	278	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	298	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	370	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	537	N/A
Separate comments from comment syntax by a space.	Other	form_example_tutorial.inc	681	N/A

form_example/form_example_wizard.inc 0 0 17

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	36	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	40	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	59	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	140	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	161	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	170	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	171	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	193	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	205	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_wizard.inc	215	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	form_example_wizard.inc	220	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	227	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	261	N/A
Function summaries should be one line only. (Drupal Docs)	Other	form_example_wizard.inc	279	N/A
Function documentation should be less than 80 characters per line.	Other	form_example_wizard.inc	283	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	286	N/A
If you define a @param or @return, you should document it as well.	Other	form_example_wizard.inc	287	N/A

image_example/image_example.install 0 0 0

image_example/image_example.module 7 0 0

Message	Group	Filename	Line	Function
Format should be `* Implementation of hook_foo().`	Other	image_example.module	27	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	image_example.module	35	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	image_example.module	36	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	image_example.module	37	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	image_example.module	38	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	image_example.module	39	N/A
in most cases, replace the string function with the drupal_ equivalent string functions	Other	image_example.module	331	N/A

image_example/image_example.pages.inc 0 0 0

image_example/image_example.test 0 0 0

js_example/accordion.tpl.php 0 0 0

js_example/js_example.module 0 0 0

menu_example/menu_example.module 2 0 18

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	menu_example.module	20	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	53	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	90	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	92	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	101	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	132	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	144	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	215	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	218	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	247	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	menu_example.module	249	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	256	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.module	277	N/A
Function summaries should be one line only. (Drupal Docs)	Other	menu_example.module	309	N/A
Function summaries should be one line only. (Drupal Docs)	Other	menu_example.module	344	N/A
If you define a @param or @return, you should document it as well.	Other	menu_example.module	348	N/A
Function documentation should be less than 80 characters per line.	Other	menu_example.module	395	N/A
Use an indent of 2 spaces, with no tabs	Other	menu_example.module	459	N/A
If you define a @param or @return, you should document it as well.	Other	menu_example.module	469	N/A
Function summaries should be one line only. (Drupal Docs)	Other	menu_example.module	482	N/A

menu_example/menu_example.test 0 0 6

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	33	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	34	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	55	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	60	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	menu_example.test	82	N/A

nodeapi_example/nodeapi_example.install 0 0 0

nodeapi_example/nodeapi_example.module 0 0 8

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	nodeapi_example.module	46	N/A
Function summaries should be one line only. (Drupal Docs)	Other	nodeapi_example.module	75	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	84	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	85	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	88	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	89	N/A
Function documentation should be less than 80 characters per line.	Other	nodeapi_example.module	104	N/A
Remove the empty commented line in your function documentation.	Other	nodeapi_example.module	106	N/A

nodeapi_example/nodeapi_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Separate comments from comment syntax by a space.	Other	nodeapi_example.test	194	N/A

node_access_example/node_access_example.install 0 0 0

node_access_example/node_access_example.module 1 0 3

Message	Group	Filename	Line	Function
If you define a @param or @return, you should document it as well.	Other	node_access_example.module	116	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	node_access_example.module	116	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	node_access_example.module	118	N/A
Function summaries should be one line only. (Drupal Docs)	Other	node_access_example.module	226	N/A

node_access_example/node_access_example.test 0 1 1

Message	Group	Filename	Line	Function	Status
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	node_access_example.test	57	N/A
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	node_access_example.test	71	N/A

node_example/node_example.install 1 1 8

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	node_example.install	11	N/A
Use an indent of 2 spaces, with no tabs	Other	node_example.install	51	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	59	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	node_example.install	60	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	72	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	73	N/A
Separate comments from comment syntax by a space.	Other	node_example.install	74	N/A
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	node_example.install	149	N/A
If you define a @param or @return, you should document it as well.	Other	node_example.install	157	N/A
If you define a @param or @return, you should document it as well.	Other	node_example.install	199	N/A

node_example/node_example.module 0 1 1

Message	Group	Filename	Line	Function	Status
Use the matching Drupal theme functions, not raw HTML.	Other	node_example.module	174	N/A
Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n)	Other	node_example.module	191	N/A

node_example/node_example.test 0 0 0

pager_example/pager_example.module 0 0 1

Message	Group	Filename	Line	Function	Status
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)	Other	pager_example.module	2	N/A

pager_example/pager_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)	Other	pager_example.test	2	N/A

page_example/page_example.module 2 0 3

Message	Group	Filename	Line	Function
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	page_example.module	17	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	page_example.module	100	N/A
Remove the empty commented line in your function documentation.	Other	page_example.module	142	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	page_example.module	145	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	page_example.module	197	N/A

page_example/page_example.test 0 0 1

Message	Group	Filename	Line	Function	Status
Remove the empty commented line in your function documentation.	Other	page_example.test	9	N/A

queue_example/queue_example.module 0 2 8

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	queue_example.module	29	N/A
Function documentation should be less than 80 characters per line.	Other	queue_example.module	30	N/A
Function summaries should be one line only. (Drupal Docs)	Other	queue_example.module	49	N/A
table names should be enclosed in {curly_brackets}	Other	queue_example.module	79	N/A
table names should be enclosed in {curly_brackets}	Other	queue_example.module	88	N/A
Function summaries should be one line only. (Drupal Docs)	Other	queue_example.module	158	N/A
If you define a @param or @return, you should document it as well.	Other	queue_example.module	246	N/A
Use Drupal's format_date(), not PHP's default date().	Other	queue_example.module	253	N/A
Use Drupal's format_date(), not PHP's default date().	Other	queue_example.module	258	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	queue_example.module	264	N/A

queue_example/queue_example.test 0 1 1

Message	Group	Filename	Line	Function	Status
table names should be enclosed in {curly_brackets}	Other	queue_example.test	32	N/A
Separate comments from comment syntax by a space.	Other	queue_example.test	47	N/A

render_example/render_example.install 0 0 0

render_example/render_example.module 0 0 5

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	render_example.module	51	N/A
Use Drupal's format_date(), not PHP's default date().	Other	render_example.module	206	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	render_example.module	355	N/A
Function summaries should be one line only. (Drupal Docs)	Other	render_example.module	522	N/A
Function summaries should be one line only. (Drupal Docs)	Other	render_example.module	537	N/A

render_example/render_example.test 0 0 0

simpletest_example/simpletest_example.install 0 0 0

simpletest_example/simpletest_example.module 1 0 3

Message	Group	Filename	Line	Function
Use the matching Drupal theme functions, not raw HTML.	Other	simpletest_example.module	114	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.module	121	N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSE	Other	simpletest_example.module	125	N/A
Use uppercase for PHP constants, e.g. NULL, TRUE, FALSE	Other	simpletest_example.module	127	N/A

simpletest_example/simpletest_example.test 3 0 3

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	simpletest_example.test	10	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.test	19	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.test	20	N/A
Function summaries should be one line only. (Drupal Docs)	Other	simpletest_example.test	97	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	simpletest_example.test	103	N/A
Use Drupal's format_date(), not PHP's default date().	Other	simpletest_example.test	140	N/A

tablesort_example/tablesort_example.install 0 0 1

Message	Group	Filename	Line	Function	Status
Remove the empty commented line in your function documentation.	Other	tablesort_example.install	9	N/A

tablesort_example/tablesort_example.module 0 0 0

tablesort_example/tablesort_example.test 0 0 2

Message	Group	Filename	Line	Function	Status
Separate comments from comment syntax by a space.	Other	tablesort_example.test	38	N/A
Separate comments from comment syntax by a space.	Other	tablesort_example.test	47	N/A

theming_example/theming_example.module 0 0 2

Message	Group	Filename	Line	Function	Status
Function summaries should be one line only. (Drupal Docs)	Other	theming_example.module	106	N/A
Function summaries should be one line only. (Drupal Docs)	Other	theming_example.module	272	N/A

theming_example/theming_example.test 0 0 0

theming_example/theming_example_text_form.tpl.php 0 0 1

Message	Group	Filename	Line	Function	Status
Remove the empty commented line in your function documentation.	Other	theming_example_text_form.tpl.php	10	N/A

token_example/token_example.module 0 1 1

Message	Group	Filename	Line	Function	Status
Potential problem: FAPI elements '#title' and '#description' only accept filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized.	Other	token_example.module	68	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	token_example.module	122	N/A

token_example/token_example.test 0 0 0

token_example/token_example.tokens.inc 0 0 0

trigger_example/trigger_example.module 1 0 6

Message	Group	Filename	Line	Function
Function summaries should be one line only. (Drupal Docs)	Other	trigger_example.module	106	N/A
Remove the empty commented line in your function documentation.	Other	trigger_example.module	109	N/A
Function summaries should be one line only. (Drupal Docs)	Other	trigger_example.module	143	N/A
Function documentation should be less than 80 characters per line.	Other	trigger_example.module	221	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	trigger_example.module	234	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	trigger_example.module	236	N/A
Format should be `* Implementation of hook_foo().`	Other	trigger_example.module	293	N/A

trigger_example/trigger_example.test 0 0 0

vertical_tabs_example/vertical_tabs_example.module 0 0 1

Message	Group	Filename	Line	Function	Status
Use the matching Drupal theme functions, not raw HTML.	Other	vertical_tabs_example.module	97	N/A

xmlrpc_example/xmlrpc_example.module 2 0 36

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	21	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	98	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	198	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	228	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	232	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	232	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	233	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	233	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	235	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	261	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	287	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	292	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	311	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	xmlrpc_example.module	356	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	362	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	369	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	376	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	377	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	411	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	414	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	415	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	452	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	455	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	456	N/A
Function summaries should be one line only. (Drupal Docs)	Other	xmlrpc_example.module	489	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	494	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	495	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	608	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	609	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	620	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	622	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	622	N/A
If you define a @param or @return, you should document it as well.	Other	xmlrpc_example.module	623	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	xmlrpc_example.module	623	N/A
Format should be `* Implementation of hook_foo().`	Other	xmlrpc_example.module	632	N/A
'Implementation' should be at the start of the sentence and begin with a capitialized letter	Other	xmlrpc_example.module	632	N/A
Function documentation should be less than 80 characters per line.	Other	xmlrpc_example.module	638	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	xmlrpc_example.module	652	N/A

xmlrpc_example/xmlrpc_example.test 0 0 0

Review log