Hotel Booking System for Ubercart - 7.x-1.x

Latest changes

So Long and Thanks for all the Tests

1 week 2 days 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.

Hotel Booking System for Ubercart - 7.x-1.x

Test status

Status	Result
Last received	Fri, 12/09/2011 - 20:02:03
Last requested	Fri, 12/09/2011 - 20:02:04
Last tested	Fri, 12/09/2011 - 20:02:15
Test count	2

Environment status

MySQL	fail
Code review	fail

Overall Result	fail

Branch information

Identifier	7.x-1.x
Project	Hotel Booking System for Ubercart
Link	Project information

Event logView entire log

ID	Message	Timestamp
3132388	Result retrieved by project client.	4 years 6 days ago
2643443	Result retrieved by project client.	4 years 11 weeks ago
2643433	Result retrieved by project client.	4 years 11 weeks ago
2643418	Result received from test client #664.	4 years 11 weeks ago
2643408	Result received from test client #.	4 years 11 weeks ago
2643403	Requested by test client #664.	4 years 11 weeks ago
2643398	Requested by test client #.	4 years 11 weeks ago
2643393	Test reset by client request.	4 years 11 weeks ago
2643388	Requested by test client #.	4 years 11 weeks ago
2643378	Requested by test client #654.	4 years 11 weeks ago

SummaryFAILED: [[SimpleTest]]: [MySQL] Failed to run tests: @reason; [[Coder]]: [Code review] 172 minor(s), 8 critical(s), and 693 normal(s).

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

172 pass(es), 8 fail(s), and 693 exception(s)

Non-pass

Test name

Pass

Fail

Exception

hotel_booking/hotel-booking.itpl.php

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	5	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	7	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	8	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	9	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	60	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	77	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	80	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	85	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	88	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	99	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	107	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	116	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	123	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	153	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	163	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	244	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	262	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	263	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	272	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	hotel-booking.itpl.php	279	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	283	N/A

hotel_booking/hotel_booking.admin.inc

105

hotel_booking/hotel_booking.calendars.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.calendars.inc	4	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.calendars.inc	9	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	14	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	15	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	15	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	16	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	16	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	17	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	17	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	18	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	18	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	29	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	31	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	34	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	70	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	74	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	76	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	101	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	101	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	102	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	103	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	103	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	104	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	104	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	112	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	113	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	115	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	116	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	118	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.calendars.inc	140	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	157	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	162	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	172	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	178	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	232	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.calendars.inc	241	N/A
indent secondary line of comment one space	Other	hotel_booking.calendars.inc	242	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	252	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	259	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	275	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	275	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	276	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	276	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	277	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	277	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	278	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	278	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	279	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	279	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	282	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	283	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	292	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	295	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	298	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	300	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	300	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	337	N/A

hotel_booking/hotel_booking.install

hotel_booking/hotel_booking.module

108

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	7	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	14	N/A
indent secondary line of comment one space	Other	hotel_booking.module	20	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	21	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	22	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	23	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	24	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	25	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	28	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	29	N/A
indent secondary line of comment one space	Other	hotel_booking.module	30	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	32	N/A
indent secondary line of comment one space	Other	hotel_booking.module	33	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking.module	34	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	42	N/A
indent secondary line of comment one space	Other	hotel_booking.module	43	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	45	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	90	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	98	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	99	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	106	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	107	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	114	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	122	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	130	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	131	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	138	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	139	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	146	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	154	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	162	N/A

hotel_booking/hotel_booking.panes.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.panes.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.panes.inc	10	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	15	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	16	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	16	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	17	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	17	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	28	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	41	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	43	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	43	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	44	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	60	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	61	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	61	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	62	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	62	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	63	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	63	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	63	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	92	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	93	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	110	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	111	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	111	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	112	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	112	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	113	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	113	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	113	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	114	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	114	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	116	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.panes.inc	116	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	117	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	121	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	145	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.panes.inc	151	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	166	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	167	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	170	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	173	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	191	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	232	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	233	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	233	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	234	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	234	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	235	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	235	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	236	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	243	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	248	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.panes.inc	280	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	305	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	308	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	327	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	328	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	328	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	329	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	329	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	330	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	330	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	354	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	355	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	355	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	356	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	356	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	357	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	357	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	358	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	390	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	393	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	411	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	412	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	412	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	413	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	413	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	413	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	414	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.panes.inc	414	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	415	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.panes.inc	452	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	465	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	466	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	472	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	487	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	510	N/A

hotel_booking/hotel_booking.room_type.inc

hotel_booking/hotel_booking.rules.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.rules.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.rules.inc	8	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.rules.inc	43	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.rules.inc	45	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.rules.inc	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	hotel_booking.rules.inc	46	N/A
indent secondary line of comment one space	Other	hotel_booking.rules.inc	47	N/A
The $message argument to watchdog() should NOT be enclosed within t(), so that it can be properly translated at display time.	Other	hotel_booking.rules.inc	80	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.rules.inc	82	N/A

hotel_booking/hotel_booking.rules_defaults.inc

hotel_booking/hotel_booking.test

hotel_booking/hotel_booking.theme.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.theme.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.theme.inc	8	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	87	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	104	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	105	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.theme.inc	109	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	136	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	137	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	175	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	176	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	219	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	220	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	239	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	248	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	268	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	276	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	279	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	285	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	286	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	304	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	313	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	333	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	341	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	347	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	348	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	349	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	368	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	369	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	369	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	370	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	370	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.theme.inc	371	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	hotel_booking.theme.inc	371	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	373	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	389	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	390	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	390	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	391	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	391	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	392	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	392	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.theme.inc	393	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	hotel_booking.theme.inc	393	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	395	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	404	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	407	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	408	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	410	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	411	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	418	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	422	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.theme.inc	434	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	455	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	477	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	524	N/A

hotel_booking/hotel_booking.token.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.token.inc	3	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	8	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.token.inc	8	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	12	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	13	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	14	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	22	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	26	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	31	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	32	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	33	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	36	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	37	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	39	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	40	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	44	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	52	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	58	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.token.inc	60	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	61	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.token.inc	64	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	65	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	77	N/A

hotel_booking/hotel_booking.ubercart.inc

hotel_booking/hotel_booking.util.inc

159

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.util.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.util.inc	8	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	12	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	13	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	13	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	14	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	14	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	15	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	31	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	32	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	32	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	33	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	33	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	34	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	40	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	62	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	63	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	63	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	64	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	64	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	68	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	100	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	102	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	106	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	110	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	140	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	141	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	141	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	142	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	146	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	154	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	155	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	155	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	155	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	156	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	156	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	162	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	178	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	182	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	182	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	183	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	183	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	184	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	187	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	188	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	197	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	198	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	199	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	204	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	206	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	210	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	214	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	218	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	219	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	222	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	223	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	228	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	235	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	238	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	238	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	239	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	243	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	259	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	260	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	261	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	271	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	273	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	273	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	274	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	274	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.util.inc	275	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	276	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	307	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	308	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	308	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	309	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	309	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	310	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	310	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	311	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	311	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	312	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	312	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	313	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	313	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	314	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	328	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	332	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	332	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	333	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	333	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	334	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	340	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	344	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	345	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	345	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	346	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	346	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	347	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	347	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	348	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	348	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	349	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	349	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	350	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	350	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	351	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	351	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	352	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	352	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	354	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	362	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	374	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	379	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	381	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	382	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	393	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	394	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	394	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	395	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	395	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	396	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	396	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	397	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	397	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	398	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	398	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	399	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	399	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	400	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	400	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	401	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	401	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	401	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	404	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	406	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	414	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	425	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	426	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	432	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	439	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	444	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	446	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	460	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	474	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	475	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	475	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	476	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	476	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	477	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	477	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	477	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	478	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	478	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	479	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	492	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	495	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	495	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	496	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	496	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	497	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	515	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	535	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	536	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	536	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	537	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	540	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	549	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	551	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	551	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	552	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	552	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	553	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	572	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	573	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	hotel_booking.util.inc	583	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	602	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	603	N/A

hotel_booking/hotel_booking.views.inc

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.views.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.views.inc	8	N/A

hotel_booking/hotel_booking_availability_key.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_availability_key.tpl.php	3	N/A
indent secondary line of comment one space	Other	hotel_booking_availability_key.tpl.php	8	N/A
There should be no trailing spaces	Other	hotel_booking_availability_key.tpl.php	8	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	13	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	14	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	15	N/A

hotel_booking/hotel_booking_calendar_cell.tpl.php

hotel_booking/hotel_booking_calendar_cell_price.tpl.php

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_calendar_cell_price.tpl.php	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_calendar_cell_price.tpl.php	21	N/A

hotel_booking/hotel_booking_calendar_cell_tip.tpl.php

hotel_booking/hotel_booking_pane_help.tpl.php

hotel_booking/hotel_booking_search_form.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_form.tpl.php	3	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking_search_form.tpl.php	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_form.tpl.php	10	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking_search_form.tpl.php	14	N/A

hotel_booking/hotel_booking_search_results.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_results.tpl.php	3	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_search_results.tpl.php	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	hotel_booking_search_results.tpl.php	14	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_results.tpl.php	15	N/A
Control statements should have one space between the control keyword and opening parenthesis	Other	hotel_booking_search_results.tpl.php	36	N/A
the final ?> should be omitted from all code files	Other	hotel_booking_search_results.tpl.php	45	N/A

hotel_booking/hotel_booking_search_result_price.tpl.php

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_result_price.tpl.php	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_result_price.tpl.php	14	N/A

hotel_booking/views/hotel_booking_handler_field_from_price.inc

Message	Group	Filename	Line	Function
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	3	N/A
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_handler_field_from_price.inc	4	N/A
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_handler_field_from_price.inc	9	N/A

All

Test name

Pass

Fail

Exception

hotel_booking/hotel-booking.itpl.php

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	5	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	7	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	8	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	9	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	60	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	77	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	80	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	85	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	88	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	99	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	107	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	116	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	123	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	153	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	163	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	244	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	262	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	263	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	272	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	hotel-booking.itpl.php	279	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	283	N/A

hotel_booking/hotel_booking.admin.inc

105

hotel_booking/hotel_booking.calendars.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.calendars.inc	4	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.calendars.inc	9	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	14	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	15	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	15	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	16	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	16	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	17	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	17	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	18	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	18	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	29	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	31	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	34	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	70	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	74	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	76	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	101	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	101	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	102	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	103	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	103	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	104	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	104	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	112	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	113	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	115	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	116	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	118	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.calendars.inc	140	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	157	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	162	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	172	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	178	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	232	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.calendars.inc	241	N/A
indent secondary line of comment one space	Other	hotel_booking.calendars.inc	242	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	252	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	259	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	275	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	275	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	276	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	276	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	277	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	277	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	278	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	278	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	279	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	279	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	282	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	283	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	292	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	295	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	298	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	300	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	300	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	337	N/A

hotel_booking/hotel_booking.install

hotel_booking/hotel_booking.module

108

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	7	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	14	N/A
indent secondary line of comment one space	Other	hotel_booking.module	20	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	21	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	22	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	23	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	24	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	25	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	28	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	29	N/A
indent secondary line of comment one space	Other	hotel_booking.module	30	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	32	N/A
indent secondary line of comment one space	Other	hotel_booking.module	33	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking.module	34	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	42	N/A
indent secondary line of comment one space	Other	hotel_booking.module	43	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	45	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	90	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	98	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	99	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	106	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	107	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	114	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	122	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	130	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	131	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	138	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	139	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	146	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	154	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	162	N/A

hotel_booking/hotel_booking.panes.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.panes.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.panes.inc	10	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	15	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	16	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	16	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	17	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	17	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	28	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	41	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	43	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	43	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	44	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	60	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	61	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	61	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	62	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	62	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	63	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	63	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	63	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	92	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	93	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	110	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	111	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	111	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	112	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	112	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	113	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	113	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	113	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	114	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	114	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	116	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.panes.inc	116	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	117	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	121	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	145	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.panes.inc	151	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	166	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	167	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	170	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	173	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	191	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	232	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	233	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	233	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	234	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	234	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	235	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	235	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	236	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	243	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	248	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.panes.inc	280	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	305	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	308	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	327	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	328	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	328	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	329	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	329	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	330	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	330	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	354	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	355	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	355	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	356	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	356	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	357	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	357	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	358	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	390	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.panes.inc	393	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.panes.inc	411	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	412	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	412	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	413	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.panes.inc	413	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.panes.inc	413	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.panes.inc	414	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.panes.inc	414	N/A
indent secondary line of comment one space	Other	hotel_booking.panes.inc	415	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.panes.inc	452	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	465	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	466	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	472	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	487	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.panes.inc	510	N/A

hotel_booking/hotel_booking.room_type.inc

hotel_booking/hotel_booking.rules.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.rules.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.rules.inc	8	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.rules.inc	43	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.rules.inc	45	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.rules.inc	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	hotel_booking.rules.inc	46	N/A
indent secondary line of comment one space	Other	hotel_booking.rules.inc	47	N/A
The $message argument to watchdog() should NOT be enclosed within t(), so that it can be properly translated at display time.	Other	hotel_booking.rules.inc	80	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.rules.inc	82	N/A

hotel_booking/hotel_booking.rules_defaults.inc

hotel_booking/hotel_booking.test

hotel_booking/hotel_booking.theme.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.theme.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.theme.inc	8	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	87	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	104	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	105	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.theme.inc	109	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	136	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	137	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	175	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	176	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	219	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	220	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	239	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	248	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	268	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	276	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	279	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	285	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	286	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	304	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	313	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	333	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	341	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	347	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	348	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	349	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	368	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	369	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	369	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	370	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	370	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.theme.inc	371	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	hotel_booking.theme.inc	371	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	373	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.theme.inc	389	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	390	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	390	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	391	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	391	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.theme.inc	392	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.theme.inc	392	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.theme.inc	393	N/A
@see references should be separated by "," followed by a single space and with no trailing punctuation	Other	hotel_booking.theme.inc	393	N/A
indent secondary line of comment one space	Other	hotel_booking.theme.inc	395	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	404	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	407	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	408	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	410	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.theme.inc	411	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	418	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	422	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.theme.inc	434	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	455	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	477	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.theme.inc	524	N/A

hotel_booking/hotel_booking.token.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.token.inc	3	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	8	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.token.inc	8	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	12	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	13	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	14	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	22	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	26	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	31	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	32	N/A
indent secondary line of comment one space	Other	hotel_booking.token.inc	33	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	36	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	37	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	39	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	40	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	44	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	52	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	58	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.token.inc	60	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	61	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.token.inc	64	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.token.inc	65	N/A
There should be no trailing spaces	Other	hotel_booking.token.inc	77	N/A

hotel_booking/hotel_booking.ubercart.inc

hotel_booking/hotel_booking.util.inc

159

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.util.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.util.inc	8	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	12	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	13	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	13	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	14	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	14	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	15	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	31	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	32	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	32	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	33	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	33	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	34	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	40	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	62	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	63	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	63	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	64	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	64	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	68	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	100	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	102	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	106	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	110	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	140	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	141	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	141	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	142	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	146	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	154	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	155	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	155	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	155	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	156	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	156	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	162	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	178	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	182	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	182	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	183	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	183	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	184	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	187	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	188	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	197	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	198	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	199	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	204	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	206	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	210	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	214	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	218	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	219	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	222	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	223	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	228	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	235	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	238	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	238	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	239	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	243	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	259	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	260	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	261	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	271	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	273	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	273	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	274	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	274	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.util.inc	275	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	276	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	307	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	308	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	308	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	309	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	309	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	310	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	310	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	311	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	311	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	312	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	312	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	313	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	313	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	314	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	328	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	332	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	332	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	333	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	333	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	334	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	340	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	344	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	345	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	345	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	346	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	346	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	347	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	347	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	348	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	348	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	349	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	349	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	350	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	350	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	351	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	351	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	352	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	352	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	354	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	362	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	374	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	379	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	381	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	382	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	393	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	394	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	394	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	395	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	395	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	396	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	396	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	397	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	397	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	398	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	398	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	399	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	399	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	400	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	400	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	401	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	401	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	401	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	404	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	406	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	414	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	425	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	426	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	432	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	439	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	444	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	446	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	460	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	474	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	475	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	475	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	476	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	476	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	477	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	477	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	477	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	478	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	478	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	479	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	492	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	495	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	495	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	496	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	496	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	497	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	515	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	535	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	536	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	536	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	537	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	540	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	549	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	551	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	551	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	552	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	552	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	553	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	572	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	573	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	hotel_booking.util.inc	583	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	602	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	603	N/A

hotel_booking/hotel_booking.views.inc

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.views.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.views.inc	8	N/A

hotel_booking/hotel_booking_availability_key.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_availability_key.tpl.php	3	N/A
indent secondary line of comment one space	Other	hotel_booking_availability_key.tpl.php	8	N/A
There should be no trailing spaces	Other	hotel_booking_availability_key.tpl.php	8	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	13	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	14	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	15	N/A

hotel_booking/hotel_booking_calendar_cell.tpl.php

hotel_booking/hotel_booking_calendar_cell_price.tpl.php

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_calendar_cell_price.tpl.php	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_calendar_cell_price.tpl.php	21	N/A

hotel_booking/hotel_booking_calendar_cell_tip.tpl.php

hotel_booking/hotel_booking_pane_help.tpl.php

hotel_booking/hotel_booking_search_form.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_form.tpl.php	3	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking_search_form.tpl.php	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_form.tpl.php	10	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking_search_form.tpl.php	14	N/A

hotel_booking/hotel_booking_search_results.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_results.tpl.php	3	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_search_results.tpl.php	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	hotel_booking_search_results.tpl.php	14	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_results.tpl.php	15	N/A
Control statements should have one space between the control keyword and opening parenthesis	Other	hotel_booking_search_results.tpl.php	36	N/A
the final ?> should be omitted from all code files	Other	hotel_booking_search_results.tpl.php	45	N/A

hotel_booking/hotel_booking_search_result_price.tpl.php

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_result_price.tpl.php	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_result_price.tpl.php	14	N/A

hotel_booking/views/hotel_booking_handler_field_from_price.inc

Message	Group	Filename	Line	Function
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	3	N/A
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_handler_field_from_price.inc	4	N/A
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_handler_field_from_price.inc	9	N/A

Review log

[13:02:01] Log initialized (/var/lib/drupaltestbot/sites/default/files/review.test_201968.pifr_coder.1323460921.log)
[13:02:01] Environment variables and review information initialized.
[13:02:01] core_url = [git://git.drupal.org/project/drupal.git];  Test repository = [git://git.drupal.org/project/uc_hotel.git]
[13:02:01] Review started.
[13:02:01] Invoking operation [setup]...
[13:02:01] Command [rm -rf sites/default/files/checkout 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot]
  Completion status: [0]
  Output: no output.
[13:02:01] Command [rm -rf sites/default/files/review 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot]
  Completion status: [0]
  Output: no output.
[13:02:01] Database backend [mysql] loaded.
[13:02:01] Invoking operation [fetch]...
[13:02:01] Invoking operation [checkout]...
[13:02:01] Version control system backend [git] loaded.
[13:02:07] Command [git clone 'git://git.drupal.org/project/uc_hotel.git' 'checkout' --reference /var/cache/git/reference 2>&1] succeeded
  Duration: 6 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files]
  Completion status: [0]
  Output: [Cloning into checkout...].
[13:02:07] Command [git --work-tree='checkout' --git-dir='checkout/.git' checkout '7.x-1.x' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files]
  Completion status: [0]
  Output: [Switched to a new branch '7.x-1.x'
Branch 7.x-1.x set up to track remote branch 7.x-1.x from origin.].
[13:02:07] Command [git --work-tree='checkout' --git-dir='checkout/.git' status 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files]
  Completion status: [0]
  Output: [# On branch 7.x-1.x
nothing to commit (working directory clean)].
[13:02:07] Main branch [7.x-1.x] checkout [complete].
[13:02:07] Invoking operation [check]...
[13:02:07] Ignoring operation [check].
[13:02:07] Invoking operation [apply]...
[13:02:07] Ignoring operation [apply].
[13:02:07] Invoking operation [syntax]...
[13:02:07] Command [php -l -f './hotel_booking/views/hotel_booking_handler_field_from_price.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/views/hotel_booking_handler_field_from_price.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel-booking.itpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel-booking.itpl.php].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.util.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.util.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.theme.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.theme.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.views.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.views.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking_availability_key.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_availability_key.tpl.php].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.calendars.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.calendars.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.rules.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.rules.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking_search_result_price.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_search_result_price.tpl.php].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking_search_form.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_search_form.tpl.php].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking_search_results.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_search_results.tpl.php].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking_calendar_cell_price.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_calendar_cell_price.tpl.php].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.panes.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.panes.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.token.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.token.inc].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.module' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.module].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking.test' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.test].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking_calendar_cell_tip.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_calendar_cell_tip.tpl.php].
[13:02:07] Command [php -l -f './hotel_booking/hotel_booking_pane_help.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_pane_help.tpl.php].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.ubercart.inc' 2>&1] succeeded
  Duration: 1 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.ubercart.inc].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.rules_defaults.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.rules_defaults.inc].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking_calendar_cell.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_calendar_cell.tpl.php].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.admin.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.admin.inc].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.install' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.install].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.room_type.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.room_type.inc].
[13:02:08] Checked [24 of 24] relevant file(s) for syntax.
[13:02:08] Invoking operation [review]...
[13:02:12] Reviewed [24 of 24] relevant file(s).
[13:02:12] Review complete. test_id=201968 result code=8 details=Array
(
    [@pass] => 172
    [@fail] => 8
    [@exception] => 693
)

[13:02:12] Static variables reset.

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

172 minor(s), 8 critical(s), and 693 normal(s)

Non-pass

Test name

Minor

Critical

Normal

hotel_booking/hotel-booking.itpl.php

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	5	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	7	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	8	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	9	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	60	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	77	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	80	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	85	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	88	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	99	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	107	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	116	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	123	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	153	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	163	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	244	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	262	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	263	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	272	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	hotel-booking.itpl.php	279	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	283	N/A

hotel_booking/hotel_booking.admin.inc

105

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.admin.inc	3	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.admin.inc	12	N/A
indent secondary line of comment one space	Other	hotel_booking.admin.inc	13	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.admin.inc	14	N/A
There should be no trailing spaces	Other	hotel_booking.admin.inc	23	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	39	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	42	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	90	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	120	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	123	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	144	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	147	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	173	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	181	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	187	N/A

hotel_booking/hotel_booking.calendars.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.calendars.inc	4	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.calendars.inc	9	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	14	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	15	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	15	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	16	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	16	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	17	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	17	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	18	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	18	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	29	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	31	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	34	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	70	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	74	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	76	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	101	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	101	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	102	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	103	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	103	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	104	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	104	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	112	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	113	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	115	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	116	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	118	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.calendars.inc	140	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	157	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	162	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	172	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	178	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	232	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.calendars.inc	241	N/A
indent secondary line of comment one space	Other	hotel_booking.calendars.inc	242	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	252	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	259	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	275	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	275	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	276	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	276	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	277	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	277	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	278	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	278	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	279	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	279	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	282	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	283	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	292	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	295	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	298	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	300	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	300	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	337	N/A

hotel_booking/hotel_booking.install

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.install	244	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.install	357	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	hotel_booking.install	413	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	416	N/A
indent secondary line of comment one space	Other	hotel_booking.install	417	N/A
Missing parenthesis after function name	Other	hotel_booking.install	472	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	472	N/A
indent secondary line of comment one space	Other	hotel_booking.install	475	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.install	506	N/A
Missing parenthesis after function name	Other	hotel_booking.install	522	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	522	N/A
indent secondary line of comment one space	Other	hotel_booking.install	524	N/A
Missing parenthesis after function name	Other	hotel_booking.install	534	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	534	N/A
indent secondary line of comment one space	Other	hotel_booking.install	536	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.install	541	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	556	N/A
indent secondary line of comment one space	Other	hotel_booking.install	558	N/A

hotel_booking/hotel_booking.module

108

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	7	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	14	N/A
indent secondary line of comment one space	Other	hotel_booking.module	20	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	21	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	22	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	23	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	24	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	25	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	28	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	29	N/A
indent secondary line of comment one space	Other	hotel_booking.module	30	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	32	N/A
indent secondary line of comment one space	Other	hotel_booking.module	33	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking.module	34	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	42	N/A
indent secondary line of comment one space	Other	hotel_booking.module	43	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	45	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	90	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	98	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	99	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	106	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	107	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	114	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	122	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	130	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	131	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	138	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	139	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	146	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	154	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	162	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	163	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	170	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	171	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	178	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	195	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	244	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	245	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	246	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	247	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	371	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	379	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	409	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.module	424	N/A
Arrays should be formatted with a space separating each element and assignment operator	Other	hotel_booking.module	429	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	437	N/A
indent secondary line of comment one space	Other	hotel_booking.module	438	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	440	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	457	N/A
indent secondary line of comment one space	Other	hotel_booking.module	458	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	484	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	485	N/A
indent secondary line of comment one space	Other	hotel_booking.module	486	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	488	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	489	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	489	N/A
indent secondary line of comment one space	Other	hotel_booking.module	490	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.module	495	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	498	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	499	N/A
indent secondary line of comment one space	Other	hotel_booking.module	500	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	503	N/A
indent secondary line of comment one space	Other	hotel_booking.module	504	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	508	N/A
Arrays should be formatted with a space separating each element and assignment operator	Other	hotel_booking.module	516	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	519	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	526	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	535	N/A
Arrays should be formatted with a space separating each element and assignment operator	Other	hotel_booking.module	540	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.module	547	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	557	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	558	N/A
indent secondary line of comment one space	Other	hotel_booking.module	559	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	562	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	563	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	563	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	564	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	564	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	571	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	580	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	650	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	657	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	667	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	668	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	668	N/A
indent secondary line of comment one space	Other	hotel_booking.module	669	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	671	N/A
There should be no trailing spaces	Other	hotel_booking.module	701	N/A
There should be no trailing spaces	Other	hotel_booking.module	711	N/A
There should be no trailing spaces	Other	hotel_booking.module	713	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.module	745	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	756	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	769	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	815	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	822	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	841	N/A
indent secondary line of comment one space	Other	hotel_booking.module	842	N/A
There should be no trailing spaces	Other	hotel_booking.module	873	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	hotel_booking.module	884	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	885	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	907	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	908	N/A
indent secondary line of comment one space	Other	hotel_booking.module	909	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	911	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	912	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	912	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	912	N/A
indent secondary line of comment one space	Other	hotel_booking.module	913	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	919	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	920	N/A
indent secondary line of comment one space	Other	hotel_booking.module	921	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	924	N/A
indent secondary line of comment one space	Other	hotel_booking.module	925	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	953	N/A
indent secondary line of comment one space	Other	hotel_booking.module	954	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	988	N/A
indent secondary line of comment one space	Other	hotel_booking.module	989	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	995	N/A
indent secondary line of comment one space	Other	hotel_booking.module	996	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1002	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1003	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1009	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1010	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1017	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1018	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1026	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1028	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1030	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	1031	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	1031	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1032	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	1037	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.module	1037	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.module	1043	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1055	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	1056	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	1056	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1057	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1066	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	1067	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	1067	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1068	N/A

hotel_booking/hotel_booking.panes.inc

hotel_booking/hotel_booking.room_type.inc

hotel_booking/hotel_booking.rules.inc

hotel_booking/hotel_booking.rules_defaults.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.rules_defaults.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.rules_defaults.inc	8	N/A
indent secondary line of comment one space	Other	hotel_booking.rules_defaults.inc	13	N/A
indent secondary line of comment one space	Other	hotel_booking.rules_defaults.inc	14	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.rules_defaults.inc	34	N/A

hotel_booking/hotel_booking.test

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	hotel_booking.test	-1	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	40	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	42	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	44	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	46	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	59	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	61	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	63	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	66	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	78	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	80	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	83	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	88	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	100	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	102	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	105	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	109	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	146	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	153	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	155	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.test	156	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	168	N/A

hotel_booking/hotel_booking.theme.inc

hotel_booking/hotel_booking.token.inc

hotel_booking/hotel_booking.ubercart.inc

hotel_booking/hotel_booking.util.inc

159

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.util.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.util.inc	8	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	12	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	13	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	13	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	14	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	14	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	15	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	31	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	32	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	32	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	33	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	33	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	34	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	40	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	62	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	63	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	63	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	64	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	64	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	68	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	100	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	102	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	106	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	110	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	140	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	141	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	141	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	142	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	146	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	154	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	155	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	155	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	155	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	156	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	156	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	162	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	178	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	182	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	182	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	183	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	183	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	184	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	187	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	188	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	197	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	198	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	199	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	204	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	206	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	210	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	214	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	218	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	219	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	222	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	223	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	228	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	235	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	238	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	238	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	239	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	243	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	259	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	260	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	261	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	271	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	273	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	273	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	274	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	274	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.util.inc	275	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	276	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	307	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	308	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	308	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	309	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	309	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	310	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	310	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	311	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	311	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	312	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	312	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	313	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	313	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	314	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	328	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	332	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	332	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	333	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	333	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	334	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	340	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	344	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	345	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	345	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	346	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	346	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	347	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	347	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	348	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	348	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	349	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	349	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	350	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	350	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	351	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	351	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	352	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	352	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	354	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	362	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	374	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	379	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	381	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	382	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	393	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	394	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	394	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	395	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	395	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	396	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	396	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	397	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	397	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	398	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	398	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	399	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	399	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	400	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	400	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	401	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	401	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	401	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	404	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	406	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	414	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	425	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	426	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	432	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	439	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	444	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	446	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	460	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	474	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	475	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	475	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	476	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	476	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	477	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	477	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	477	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	478	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	478	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	479	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	492	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	495	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	495	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	496	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	496	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	497	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	515	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	535	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	536	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	536	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	537	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	540	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	549	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	551	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	551	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	552	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	552	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	553	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	572	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	573	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	hotel_booking.util.inc	583	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	602	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	603	N/A

hotel_booking/hotel_booking.views.inc

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.views.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.views.inc	8	N/A

hotel_booking/hotel_booking_availability_key.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_availability_key.tpl.php	3	N/A
indent secondary line of comment one space	Other	hotel_booking_availability_key.tpl.php	8	N/A
There should be no trailing spaces	Other	hotel_booking_availability_key.tpl.php	8	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	13	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	14	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	15	N/A

hotel_booking/hotel_booking_calendar_cell.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_calendar_cell.tpl.php	3	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_calendar_cell.tpl.php	14	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_calendar_cell.tpl.php	25	N/A

hotel_booking/hotel_booking_calendar_cell_price.tpl.php

hotel_booking/hotel_booking_calendar_cell_tip.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_calendar_cell_tip.tpl.php	4	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_calendar_cell_tip.tpl.php	20	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_calendar_cell_tip.tpl.php	36	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_calendar_cell_tip.tpl.php	41	N/A

hotel_booking/hotel_booking_pane_help.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_pane_help.tpl.php	3	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_pane_help.tpl.php	11	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_pane_help.tpl.php	12	N/A
missing space after comma	Other	hotel_booking_pane_help.tpl.php	15	N/A
The $text argument to l() should be enclosed within t() so that it is translatable.	Other	hotel_booking_pane_help.tpl.php	32	N/A

hotel_booking/hotel_booking_search_form.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_form.tpl.php	3	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking_search_form.tpl.php	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_form.tpl.php	10	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking_search_form.tpl.php	14	N/A

hotel_booking/hotel_booking_search_results.tpl.php

hotel_booking/hotel_booking_search_result_price.tpl.php

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_result_price.tpl.php	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_result_price.tpl.php	14	N/A

hotel_booking/views/hotel_booking_handler_field_from_price.inc

Message	Group	Filename	Line	Function
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	3	N/A
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_handler_field_from_price.inc	4	N/A
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_handler_field_from_price.inc	9	N/A

All

Test name

Minor

Critical

Normal

hotel_booking/hotel-booking.itpl.php

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	5	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	7	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	8	N/A
Function documentation should be less than 80 characters per line.	Other	hotel-booking.itpl.php	9	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	60	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	77	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	80	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	85	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	88	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	99	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	107	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	116	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	123	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	143	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	153	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel-booking.itpl.php	163	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	244	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	262	N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)	Other	hotel-booking.itpl.php	263	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	272	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	hotel-booking.itpl.php	279	N/A
Core uses "e-mail" in end-user text and "mail" elsewhere (database, function names, etc.)	Other	hotel-booking.itpl.php	283	N/A

hotel_booking/hotel_booking.admin.inc

105

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.admin.inc	3	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.admin.inc	12	N/A
indent secondary line of comment one space	Other	hotel_booking.admin.inc	13	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.admin.inc	14	N/A
There should be no trailing spaces	Other	hotel_booking.admin.inc	23	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	39	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	42	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	90	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	120	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	123	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	144	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	147	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	173	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.admin.inc	181	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.admin.inc	187	N/A

hotel_booking/hotel_booking.calendars.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.calendars.inc	4	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.calendars.inc	9	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	14	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	15	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	15	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	16	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	16	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	17	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	17	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	18	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	18	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	29	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	31	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	34	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	70	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	74	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	75	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	76	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.calendars.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	101	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	101	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	102	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	103	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	103	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	104	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	104	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	112	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	113	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	115	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	116	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	118	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.calendars.inc	140	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	157	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	162	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	172	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	178	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	232	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.calendars.inc	241	N/A
indent secondary line of comment one space	Other	hotel_booking.calendars.inc	242	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	252	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	259	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	275	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	275	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	276	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	276	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	277	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	277	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	278	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	278	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.calendars.inc	279	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.calendars.inc	279	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	282	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	283	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	292	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	295	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	298	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	300	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.calendars.inc	300	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.calendars.inc	337	N/A

hotel_booking/hotel_booking.install

Message	Group	Filename	Line	Function
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.install	244	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.install	357	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	hotel_booking.install	413	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	416	N/A
indent secondary line of comment one space	Other	hotel_booking.install	417	N/A
Missing parenthesis after function name	Other	hotel_booking.install	472	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	472	N/A
indent secondary line of comment one space	Other	hotel_booking.install	475	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.install	506	N/A
Missing parenthesis after function name	Other	hotel_booking.install	522	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	522	N/A
indent secondary line of comment one space	Other	hotel_booking.install	524	N/A
Missing parenthesis after function name	Other	hotel_booking.install	534	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	534	N/A
indent secondary line of comment one space	Other	hotel_booking.install	536	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.install	541	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.install	556	N/A
indent secondary line of comment one space	Other	hotel_booking.install	558	N/A

hotel_booking/hotel_booking.module

108

Message	Group	Filename	Line	Function
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	7	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	14	N/A
indent secondary line of comment one space	Other	hotel_booking.module	20	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	21	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	22	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	23	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	24	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	25	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	28	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	29	N/A
indent secondary line of comment one space	Other	hotel_booking.module	30	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	32	N/A
indent secondary line of comment one space	Other	hotel_booking.module	33	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking.module	34	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	42	N/A
indent secondary line of comment one space	Other	hotel_booking.module	43	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	45	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	90	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	98	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	99	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	106	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	107	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	114	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	122	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	130	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	131	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	138	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	139	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	146	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	154	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	162	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	163	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	170	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	171	N/A
Administrative menu items should have a description.	Other	hotel_booking.module	178	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	195	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	244	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	245	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	246	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	247	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	371	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	379	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	409	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.module	424	N/A
Arrays should be formatted with a space separating each element and assignment operator	Other	hotel_booking.module	429	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	437	N/A
indent secondary line of comment one space	Other	hotel_booking.module	438	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	440	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	457	N/A
indent secondary line of comment one space	Other	hotel_booking.module	458	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	484	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	485	N/A
indent secondary line of comment one space	Other	hotel_booking.module	486	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	488	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	489	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	489	N/A
indent secondary line of comment one space	Other	hotel_booking.module	490	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.module	495	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	498	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	499	N/A
indent secondary line of comment one space	Other	hotel_booking.module	500	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	503	N/A
indent secondary line of comment one space	Other	hotel_booking.module	504	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	508	N/A
Arrays should be formatted with a space separating each element and assignment operator	Other	hotel_booking.module	516	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	519	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	526	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	535	N/A
Arrays should be formatted with a space separating each element and assignment operator	Other	hotel_booking.module	540	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.module	547	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	557	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	558	N/A
indent secondary line of comment one space	Other	hotel_booking.module	559	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	562	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	563	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	563	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	564	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	564	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	571	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	580	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	650	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	657	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	667	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	668	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	668	N/A
indent secondary line of comment one space	Other	hotel_booking.module	669	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	671	N/A
There should be no trailing spaces	Other	hotel_booking.module	701	N/A
There should be no trailing spaces	Other	hotel_booking.module	711	N/A
There should be no trailing spaces	Other	hotel_booking.module	713	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.module	745	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	756	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	769	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	815	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	822	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	841	N/A
indent secondary line of comment one space	Other	hotel_booking.module	842	N/A
There should be no trailing spaces	Other	hotel_booking.module	873	N/A
Use the matching Drupal theme functions, not raw HTML.	Other	hotel_booking.module	884	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.module	885	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	907	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	908	N/A
indent secondary line of comment one space	Other	hotel_booking.module	909	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	911	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	912	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	912	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	912	N/A
indent secondary line of comment one space	Other	hotel_booking.module	913	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	919	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.module	920	N/A
indent secondary line of comment one space	Other	hotel_booking.module	921	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	924	N/A
indent secondary line of comment one space	Other	hotel_booking.module	925	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	953	N/A
indent secondary line of comment one space	Other	hotel_booking.module	954	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	988	N/A
indent secondary line of comment one space	Other	hotel_booking.module	989	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	995	N/A
indent secondary line of comment one space	Other	hotel_booking.module	996	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1002	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1003	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1009	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1010	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1017	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1018	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1026	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1028	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1030	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	1031	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	1031	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1032	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.module	1037	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.module	1037	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.module	1043	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1055	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	1056	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	1056	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1057	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.module	1066	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.module	1067	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.module	1067	N/A
indent secondary line of comment one space	Other	hotel_booking.module	1068	N/A

hotel_booking/hotel_booking.panes.inc

hotel_booking/hotel_booking.room_type.inc

hotel_booking/hotel_booking.rules.inc

hotel_booking/hotel_booking.rules_defaults.inc

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.rules_defaults.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.rules_defaults.inc	8	N/A
indent secondary line of comment one space	Other	hotel_booking.rules_defaults.inc	13	N/A
indent secondary line of comment one space	Other	hotel_booking.rules_defaults.inc	14	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.rules_defaults.inc	34	N/A

hotel_booking/hotel_booking.test

Message	Group	Filename	Line	Function
@file block missing (Drupal Docs)	Other	hotel_booking.test	-1	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	40	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	42	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	44	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	46	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	59	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	61	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	63	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	66	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	78	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	80	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	83	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	88	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	100	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	102	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	105	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	109	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	146	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	153	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	155	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.test	156	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.test	168	N/A

hotel_booking/hotel_booking.theme.inc

hotel_booking/hotel_booking.token.inc

hotel_booking/hotel_booking.ubercart.inc

hotel_booking/hotel_booking.util.inc

159

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.util.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.util.inc	8	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	12	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	13	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	13	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	14	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	14	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	15	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	31	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	32	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	32	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	33	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	33	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	34	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	40	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	62	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	63	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	63	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	64	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	64	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	65	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	68	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	100	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	100	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	102	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	102	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	106	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	110	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	140	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	141	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	141	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	142	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	146	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	154	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	155	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	155	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	155	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	156	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	156	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	158	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	162	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	178	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	182	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	182	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	183	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	183	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	184	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	187	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	188	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	197	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	198	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	199	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	204	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	206	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	210	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	214	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	218	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	219	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	222	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	223	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	228	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	235	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	238	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	238	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	239	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	243	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	259	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	260	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	261	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	271	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	273	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	273	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	274	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	274	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking.util.inc	275	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	276	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	307	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	308	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	308	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	309	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	309	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	310	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	310	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	311	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	311	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	312	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	312	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	313	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	313	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	314	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	328	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	332	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	332	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	333	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	333	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	334	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	340	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	344	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	345	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	345	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	346	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	346	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	347	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	347	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	348	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	348	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	349	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	349	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	350	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	350	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	351	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	351	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	352	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	352	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	354	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	362	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	374	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	379	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	381	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	382	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	393	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	394	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	394	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	395	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	395	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	396	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	396	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	397	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	397	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	398	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	398	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	399	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	399	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	400	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	400	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	401	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	401	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	401	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	404	N/A
Use an indent of 2 spaces, with no tabs	Other	hotel_booking.util.inc	406	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	414	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	425	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	426	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	432	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	439	N/A
put a space between the asterisk and the comment text	Other	hotel_booking.util.inc	444	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	446	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	460	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	474	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	475	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	475	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	476	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	476	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	477	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking.util.inc	477	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	477	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	478	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	478	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	479	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	492	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	495	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	495	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	496	N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)	Other	hotel_booking.util.inc	496	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	497	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	515	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	535	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	536	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	536	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	537	N/A
Use Drupal's format_date(), not PHP's default date().	Other	hotel_booking.util.inc	540	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	549	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	551	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	551	N/A
If you define a @param or @return, you should document it as well.	Other	hotel_booking.util.inc	552	N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)	Other	hotel_booking.util.inc	552	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	553	N/A
Function summaries should be one line only. (Drupal Docs)	Other	hotel_booking.util.inc	572	N/A
indent secondary line of comment one space	Other	hotel_booking.util.inc	573	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	hotel_booking.util.inc	583	N/A
Separate comments from comment syntax by a space.	Other	hotel_booking.util.inc	602	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking.util.inc	603	N/A

hotel_booking/hotel_booking.views.inc

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking.views.inc	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking.views.inc	8	N/A

hotel_booking/hotel_booking_availability_key.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_availability_key.tpl.php	3	N/A
indent secondary line of comment one space	Other	hotel_booking_availability_key.tpl.php	8	N/A
There should be no trailing spaces	Other	hotel_booking_availability_key.tpl.php	8	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	13	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	14	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_availability_key.tpl.php	15	N/A

hotel_booking/hotel_booking_calendar_cell.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_calendar_cell.tpl.php	3	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_calendar_cell.tpl.php	14	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_calendar_cell.tpl.php	25	N/A

hotel_booking/hotel_booking_calendar_cell_price.tpl.php

hotel_booking/hotel_booking_calendar_cell_tip.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_calendar_cell_tip.tpl.php	4	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_calendar_cell_tip.tpl.php	20	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_calendar_cell_tip.tpl.php	36	N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)	Other	hotel_booking_calendar_cell_tip.tpl.php	41	N/A

hotel_booking/hotel_booking_pane_help.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_pane_help.tpl.php	3	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_pane_help.tpl.php	11	N/A
Function documentation should be less than 80 characters per line.	Other	hotel_booking_pane_help.tpl.php	12	N/A
missing space after comma	Other	hotel_booking_pane_help.tpl.php	15	N/A
The $text argument to l() should be enclosed within t() so that it is translatable.	Other	hotel_booking_pane_help.tpl.php	32	N/A

hotel_booking/hotel_booking_search_form.tpl.php

Message	Group	Filename	Line	Function
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_form.tpl.php	3	N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().	Other	hotel_booking_search_form.tpl.php	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_form.tpl.php	10	N/A
Functions should be called with no spaces between the function name and opening parentheses	Other	hotel_booking_search_form.tpl.php	14	N/A

hotel_booking/hotel_booking_search_results.tpl.php

hotel_booking/hotel_booking_search_result_price.tpl.php

Message	Group	Filename	Line	Function	Status
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_search_result_price.tpl.php	3	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_search_result_price.tpl.php	14	N/A

hotel_booking/views/hotel_booking_handler_field_from_price.inc

Message	Group	Filename	Line	Function
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	3	N/A
@file description should be on the following line (Drupal Docs)	Other	hotel_booking_handler_field_from_price.inc	4	N/A
There should be no trailing spaces	Other	hotel_booking_handler_field_from_price.inc	9	N/A
Remove the empty commented line in your function documentation.	Other	hotel_booking_handler_field_from_price.inc	9	N/A

Review log

[13:02:02] Log initialized (/var/lib/drupaltestbot/sites/default/files/review.test_201968.pifr_coder.1323460922.log)
[13:02:02] Environment variables and review information initialized.
[13:02:02] core_url = [git://git.drupal.org/project/drupal.git];  Test repository = [git://git.drupal.org/project/uc_hotel.git]
[13:02:02] Review started.
[13:02:02] Invoking operation [setup]...
[13:02:02] Command [rm -rf sites/default/files/checkout 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot]
  Completion status: [0]
  Output: no output.
[13:02:02] Command [rm -rf sites/default/files/review 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot]
  Completion status: [0]
  Output: no output.
[13:02:02] Database backend [mysql] loaded.
[13:02:02] Invoking operation [fetch]...
[13:02:02] Invoking operation [checkout]...
[13:02:02] Version control system backend [git] loaded.
[13:02:08] Command [git clone 'git://git.drupal.org/project/uc_hotel.git' 'checkout' --reference /var/cache/git/reference 2>&1] succeeded
  Duration: 6 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files]
  Completion status: [0]
  Output: [Cloning into checkout...].
[13:02:08] Command [git --work-tree='checkout' --git-dir='checkout/.git' checkout '7.x-1.x' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files]
  Completion status: [0]
  Output: [Switched to a new branch '7.x-1.x'
Branch 7.x-1.x set up to track remote branch 7.x-1.x from origin.].
[13:02:08] Command [git --work-tree='checkout' --git-dir='checkout/.git' status 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files]
  Completion status: [0]
  Output: [# On branch 7.x-1.x
nothing to commit (working directory clean)].
[13:02:08] Main branch [7.x-1.x] checkout [complete].
[13:02:08] Invoking operation [check]...
[13:02:08] Ignoring operation [check].
[13:02:08] Invoking operation [apply]...
[13:02:08] Ignoring operation [apply].
[13:02:08] Invoking operation [syntax]...
[13:02:08] Command [php -l -f './hotel_booking/views/hotel_booking_handler_field_from_price.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/views/hotel_booking_handler_field_from_price.inc].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking_pane_help.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_pane_help.tpl.php].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.install' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.install].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.rules_defaults.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.rules_defaults.inc].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking_search_form.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_search_form.tpl.php].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.module' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.module].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.util.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.util.inc].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking_calendar_cell.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_calendar_cell.tpl.php].
[13:02:08] Command [php -l -f './hotel_booking/hotel-booking.itpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel-booking.itpl.php].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.views.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.views.inc].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking.test' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.test].
[13:02:08] Command [php -l -f './hotel_booking/hotel_booking_search_result_price.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_search_result_price.tpl.php].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.calendars.inc' 2>&1] succeeded
  Duration: 1 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.calendars.inc].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking_availability_key.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_availability_key.tpl.php].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking_calendar_cell_tip.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_calendar_cell_tip.tpl.php].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.admin.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.admin.inc].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.ubercart.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.ubercart.inc].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking_search_results.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_search_results.tpl.php].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.theme.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.theme.inc].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.rules.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.rules.inc].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.token.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.token.inc].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.room_type.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.room_type.inc].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking_calendar_cell_price.tpl.php' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking_calendar_cell_price.tpl.php].
[13:02:09] Command [php -l -f './hotel_booking/hotel_booking.panes.inc' 2>&1] succeeded
  Duration: 0 seconds
  Directory: [/var/lib/drupaltestbot/sites/default/files/checkout]
  Completion status: [0]
  Output: [No syntax errors detected in ./hotel_booking/hotel_booking.panes.inc].
[13:02:09] Checked [24 of 24] relevant file(s) for syntax.
[13:02:09] Invoking operation [review]...
[13:02:13] Reviewed [24 of 24] relevant file(s).
[13:02:13] Review complete. test_id=201968 result code=8 details=Array
(
    [@pass] => 172
    [@fail] => 8
    [@exception] => 693
)

[13:02:13] Static variables reset.

Drupal Quality Assurance

Latest changes

Support

Test client logs

Hotel Booking System for Ubercart - 7.x-1.x

MySQL

Non-pass

All

Code review

Non-pass

All