Salesforce Suite - 7.x-2.x

Test status
StatusResult
Last receivedWed, 12/14/2011 - 11:23:38
Last requestedWed, 12/14/2011 - 11:24:03
Last testedWed, 12/14/2011 - 11:24:39
Test count2
Environment status
MySQLpass
Code reviewfail
Overall Resultpass
Branch information
Identifier7.x-2.x
ProjectSalesforce Suite
LinkProject information
SummaryPASSED: [[Coder]]: [Code review] 105 minor(s), 31 critical(s), and 663 normal(s); [[SimpleTest]]: [MySQL] 0 pass(es).
Details

MySQL

  1. Setup environment
  2. Detect an invalid patch URL
  3. Detect invalid repository information
  4. Detect invalid patch format
  5. Detect a non-applicable patch
  6. Detect invalid PHP syntax
  7. Detect a Drupal installation failure
  8. Detect a test run failure
  9. Detect a failing test
  10. Complete test suite with all tests passing

Code review

  1. Setup environment
  2. Detect an invalid patch URL
  3. Detect invalid repository information
  4. Detect invalid patch format
  5. Detect a non-applicable patch
  6. Detect invalid PHP syntax
  7. Detect a review run failure
  8. Detect coder flags
    Ensure that your code follows the Drupal standard and passes a coder review.
  9. Complete coder review with all passed
105 minor(s), 31 critical(s), and 663 normal(s)

Non-pass

Test nameMinorCriticalNormal
Leafsalesforce_api.api.php46173
Leafsalesforce_api/salesforce_api.admin.inc12359
Expandsalesforce_api/salesforce_api.drush.inc006
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersalesforce_api.drush.inc2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.drush.inc62N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.drush.inc76N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.drush.inc106N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.drush.inc111N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.drush.inc220N/A
Leafsalesforce_api/salesforce_api.features.inc001
Leafsalesforce_api/salesforce_api.install1222
Expandsalesforce_api/salesforce_api.module2012234
MessageGroupFilenameLineFunctionStatus
Remove the empty commented line in your function documentation.Othersalesforce_api.module6N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersalesforce_api.module57N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module65N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module66N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().Othersalesforce_api.module269N/A
Remove the empty commented line in your function documentation.Othersalesforce_api.module300N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module310N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module329N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.module381N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module397N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.module401N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module416N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module419N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module419N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module420N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module420N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module421N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module421N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module422N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module422N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module481N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module484N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module485N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module486N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module487N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module488N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module516N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module548N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module557N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module565N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module566N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module590N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module590N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module632N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module652N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module653N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module655N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module669N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module683N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module683N/A
Format should be * Implementation of hook_foo().Othersalesforce_api.module684N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module685N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module688N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module688N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module689N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module690N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module690N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module691N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module692N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module694N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module698N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module699N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module707N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersalesforce_api.module715N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersalesforce_api.module716N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersalesforce_api.module726N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersalesforce_api.module727N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module763N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module764N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module793N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module793N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module794N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module794N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module795N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module795N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module796N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module801N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module855N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module858N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module861N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module866N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module869N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module871N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module932N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module932N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module944N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module968N/A
Doxygen uses @todo and @bug to markup things to be done.Othersalesforce_api.module988N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1006N/A
Using eval() or drupal_eval() in your module's code could have a security risk if the PHP input provided to the function contains malicious code. (Drupal Docs)Othersalesforce_api.module1058N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1086N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersalesforce_api.module1199N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1209N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1210N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1229N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1257N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1267N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1271N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1273N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1275N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1277N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1279N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1281N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1282N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module1332N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1342N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1345N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1383N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1386N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1389N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1392N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1402N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1402N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1431N/A
@see should always be at the beginning of a line, never inline in other comments.Othersalesforce_api.module1461N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1461N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1461N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1462N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1462N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1464N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1464N/A
@see should always be at the beginning of a line, never inline in other comments.Othersalesforce_api.module1474N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1474N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1475N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1475N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1477N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1482N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1485N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1499N/A
The control statement should be on a separate line from the control conditionalOthersalesforce_api.module1500N/A
The control statement should be on a separate line from the control conditionalOthersalesforce_api.module1501N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1502N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1503N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1526N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1527N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1528N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1529N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1538N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1539N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1542N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1542N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1544N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1544N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1546N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1546N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1549N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1550N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1555N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1565N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1566N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1567N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1568N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1576N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1579N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1579N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1580N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1582N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1582N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1583N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1585N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1585N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1587N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1587N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1588N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1589N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1589N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1590N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1591N/A
indent secondary line of comment one space Othersalesforce_api.module1592N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.module1593N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1595N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1598N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1605N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1606N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1639N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1642N/A
Separate comments from comment syntax by a space.Othersalesforce_api.module1670N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1676N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersalesforce_api.module1693N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module1693N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1709N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1711N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1711N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1714N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1714N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1716N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1716N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1718N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1718N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1718N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module1727N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module1733N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1751N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1753N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1753N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1755N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1755N/A
Expandsalesforce_api/salesforce_api.views.inc002
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersalesforce_api.views.inc2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.views.inc41N/A
Expandsf_entity/sf_entity.module7769
MessageGroupFilenameLineFunctionStatus
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module9N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module33N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module38N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module101N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module177N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module184N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module189N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module197N/A
Use Drupal's format_date(), not PHP's default date().Othersf_entity.module200N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module205N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module208N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module208N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module209N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module209N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module214N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module221N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module239N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module242N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module242N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module249N/A
indent secondary line of comment one space Othersf_entity.module251N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module253N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module260N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module263N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module263N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module297N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module317N/A
Use an indent of 2 spaces, with no tabsOthersf_entity.module380N/A
Use an indent of 2 spaces, with no tabsOthersf_entity.module386N/A
Potential problem: confirm_form() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized. (Drupal Docs)Othersf_entity.module446N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module480N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module486N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_entity.module497N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module498N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_entity.module518N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module534N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module534N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module538N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module570N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module609N/A
Remove the empty commented line in your function documentation.Othersf_entity.module654N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module657N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module701N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module708N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_entity.module711N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module713N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module715N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module731N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module731N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module773N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module806N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module812N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module828N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module842N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module844N/A
Function documentation should be less than 80 characters per line.Othersf_entity.module845N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module846N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module855N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module859N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module859N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module885N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module944N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module956N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module961N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module1040N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_entity.module1042N/A
Function documentation should be less than 80 characters per line.Othersf_entity.module1043N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1044N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1046N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module1048N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1054N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1057N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module1114N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_entity.module1117N/A
Function documentation should be less than 80 characters per line.Othersf_entity.module1118N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1119N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1121N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module1123N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1157N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1173N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1231N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module1260N/A
Remove the empty commented line in your function documentation.Othersf_entity.module1361N/A
Expandsf_import/sf_import.admin.inc0112
MessageGroupFilenameLineFunctionStatus
Use Drupal's format_date(), not PHP's default date().Othersf_import.admin.inc23N/A
table names should be enclosed in {curly_brackets}Othersf_import.admin.inc52N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.admin.inc100N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.admin.inc152N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_import.admin.inc225N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.admin.inc252N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_import.admin.inc266N/A
If you define a @param or @return, you should document it as well.Othersf_import.admin.inc285N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.admin.inc285N/A
If you define a @param or @return, you should document it as well.Othersf_import.admin.inc286N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.admin.inc286N/A
If you define a @param or @return, you should document it as well.Othersf_import.admin.inc287N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.admin.inc287N/A
Expandsf_import/sf_import.batch.inc0113
MessageGroupFilenameLineFunctionStatus
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc11N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc13N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc33N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_import.batch.inc33N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc34N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc34N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc35N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc35N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized. (Drupal Docs)Othersf_import.batch.inc41N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc52N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc54N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc54N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc55N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc55N/A
Expandsf_import/sf_import.drush.inc008
MessageGroupFilenameLineFunctionStatus
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc78N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc89N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc109N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc144N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc157N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc172N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc179N/A
Function summaries should be one line only. (Drupal Docs)Othersf_import.drush.inc335N/A
Expandsf_import/sf_import.module2111
MessageGroupFilenameLineFunctionStatus
@file block missing (Drupal Docs)Othersf_import.module-1N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.module21N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.module31N/A
Function summaries should be one line only. (Drupal Docs)Othersf_import.module74N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_import.module76N/A
@see should always be at the beginning of a line, never inline in other comments.Othersf_import.module77N/A
@see references should be separated by "," followed by a single space and with no trailing punctuationOthersf_import.module77N/A
If you define a @param or @return, you should document it as well.Othersf_import.module78N/A
Function documentation should be less than 80 characters per line.Othersf_import.module78N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_import.module78N/A
table names should be enclosed in {curly_brackets}Othersf_import.module88N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.module91N/A
Function summaries should be one line only. (Drupal Docs)Othersf_import.module117N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_import.module142N/A
Expandsf_notifications/sf_notifications.admin.inc007
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othersf_notifications.admin.inc12N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.admin.inc13N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc19N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc35N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc44N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_notifications.admin.inc45N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc57N/A
Expandsf_notifications/sf_notifications.api.php006
MessageGroupFilenameLineFunctionStatus
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php25N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php27N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php38N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php40N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php62N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php64N/A
Expandsf_notifications/sf_notifications.install001
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_notifications.install2N/A
Expandsf_notifications/sf_notifications.module6045
MessageGroupFilenameLineFunctionStatus
@file block missing (Drupal Docs)Othersf_notifications.module-1N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module59N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module59N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module88N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module106N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module126N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module127N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module128N/A
Use an indent of 2 spaces, with no tabsOthersf_notifications.module134N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module172N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module175N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_notifications.module175N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module178N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module178N/A
Format should be * Implementation of hook_foo().Othersf_notifications.module205N/A
Format should be * Implementation of hook_foo().Othersf_notifications.module251N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module268N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_notifications.module277N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module339N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_notifications.module358N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module397N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module397N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module399N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module399N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module407N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module417N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module418N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module419N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module420N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module421N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_notifications.module421N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module424N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module425N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_notifications.module440N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module451N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module451N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module452N/A
put a space between the asterisk and the comment textOthersf_notifications.module453N/A
use lowercase html tags to comply with XHTMLOthersf_notifications.module461N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module471N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module471N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_notifications.module471N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module472N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module472N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module484N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module485N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module493N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module494N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module518N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module519N/A
Use Drupal's format_date(), not PHP's default date().Othersf_notifications.module524N/A
Expandsf_prematch/sf_prematch.admin.inc2012
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_prematch.admin.inc2N/A
Separate comments from comment syntax by a space.Othersf_prematch.admin.inc24N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.admin.inc25N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_prematch.admin.inc33N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.admin.inc109N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.admin.inc119N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.admin.inc126N/A
Use Drupal's format_date(), not PHP's default date().Othersf_prematch.admin.inc161N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.admin.inc174N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.admin.inc187N/A
Use Drupal's format_date(), not PHP's default date().Othersf_prematch.admin.inc189N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)Othersf_prematch.admin.inc229N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_prematch.admin.inc279N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_prematch.admin.inc280N/A
Expandsf_prematch/sf_prematch.install107
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_prematch.install2N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install13N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install21N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().Othersf_prematch.install74N/A
Remove the empty commented line in your function documentation.Othersf_prematch.install75N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install90N/A
Use Drupal's format_date(), not PHP's default date().Othersf_prematch.install92N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install104N/A
Expandsf_prematch/sf_prematch.main.inc1023
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_prematch.main.inc2N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc12N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc12N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc13N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_prematch.main.inc13N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc14N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc14N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc15N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc15N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc16N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc16N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.main.inc120N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc146N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc146N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc147N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_prematch.main.inc147N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc148N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc148N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc149N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc149N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc151N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc151N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_prematch.main.inc310N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.main.inc311N/A
Expandsf_prematch/sf_prematch.module0014
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othersf_prematch.module5N/A
Function summaries should be one line only. (Drupal Docs)Othersf_prematch.module54N/A
Function documentation should be less than 80 characters per line.Othersf_prematch.module92N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module94N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module94N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module95N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module95N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module136N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module147N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module147N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module148N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_prematch.module148N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module149N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module149N/A
Expandsf_queue/sf_queue.admin.inc326
MessageGroupFilenameLineFunctionStatus
Control statements should have one space between the control keyword and opening parenthesisOthersf_queue.admin.inc20N/A
Use Drupal's format_date(), not PHP's default date().Othersf_queue.admin.inc33N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_queue.admin.inc64N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.admin.inc68N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_queue.admin.inc112N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.admin.inc116N/A
Use an indent of 2 spaces, with no tabsOthersf_queue.admin.inc136N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.admin.inc145N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_queue.admin.inc148N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_queue.admin.inc151N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_queue.admin.inc160N/A
Expandsf_queue/sf_queue.install004
MessageGroupFilenameLineFunctionStatus
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.install13N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.install21N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.install23N/A
Remove the empty commented line in your function documentation.Othersf_queue.install39N/A
Expandsf_queue/sf_queue.module2128
MessageGroupFilenameLineFunctionStatus
@file description should be on the following line (Drupal Docs)Othersf_queue.module4N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module71N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module94N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module95N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_queue.module149N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module211N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module230N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module245N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module272N/A
Separate comments from comment syntax by a space.Othersf_queue.module285N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module307N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module319N/A
Separate comments from comment syntax by a space.Othersf_queue.module358N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module376N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module380N/A
use <br /> instead of <br>Othersf_queue.module408N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module414N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module419N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module426N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module431N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module442N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module448N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module455N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_queue.module461N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module468N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module509N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module534N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module541N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module548N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module559N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module575N/A

All

Test nameMinorCriticalNormal
Leafsalesforce_api.api.php46173
Leafsalesforce_api/salesforce_api.admin.inc12359
Expandsalesforce_api/salesforce_api.drush.inc006
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersalesforce_api.drush.inc2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.drush.inc62N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.drush.inc76N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.drush.inc106N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.drush.inc111N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.drush.inc220N/A
Leafsalesforce_api/salesforce_api.features.inc001
Leafsalesforce_api/salesforce_api.install1222
Expandsalesforce_api/salesforce_api.module2012234
MessageGroupFilenameLineFunctionStatus
Remove the empty commented line in your function documentation.Othersalesforce_api.module6N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersalesforce_api.module57N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module65N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module66N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().Othersalesforce_api.module269N/A
Remove the empty commented line in your function documentation.Othersalesforce_api.module300N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module310N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module329N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.module381N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module397N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.module401N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module416N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module419N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module419N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module420N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module420N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module421N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module421N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module422N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module422N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module481N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module484N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module485N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module486N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module487N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module488N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module516N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module548N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module557N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module565N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module566N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module590N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module590N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module632N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module652N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module653N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module655N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module669N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module683N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module683N/A
Format should be * Implementation of hook_foo().Othersalesforce_api.module684N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module685N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module688N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module688N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module689N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module690N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module690N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module691N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module692N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module694N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module698N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module699N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module707N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersalesforce_api.module715N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersalesforce_api.module716N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersalesforce_api.module726N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersalesforce_api.module727N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module763N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module764N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module793N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module793N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module794N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module794N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module795N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module795N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module796N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module801N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module855N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module858N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module861N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module866N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module869N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module871N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module932N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module932N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module944N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module968N/A
Doxygen uses @todo and @bug to markup things to be done.Othersalesforce_api.module988N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1006N/A
Using eval() or drupal_eval() in your module's code could have a security risk if the PHP input provided to the function contains malicious code. (Drupal Docs)Othersalesforce_api.module1058N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1086N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersalesforce_api.module1199N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1209N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1210N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1229N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1257N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1267N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1271N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1273N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1275N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1277N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1279N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1281N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1282N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module1332N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1342N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1345N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1383N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1386N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1389N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1392N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1402N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1402N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1431N/A
@see should always be at the beginning of a line, never inline in other comments.Othersalesforce_api.module1461N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1461N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1461N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1462N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1462N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1464N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1464N/A
@see should always be at the beginning of a line, never inline in other comments.Othersalesforce_api.module1474N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1474N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1475N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1475N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1477N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1482N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1485N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1499N/A
The control statement should be on a separate line from the control conditionalOthersalesforce_api.module1500N/A
The control statement should be on a separate line from the control conditionalOthersalesforce_api.module1501N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1502N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1503N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1526N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1527N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1528N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1529N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1538N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1539N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1542N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1542N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1544N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1544N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1546N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1546N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1549N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1550N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1555N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1565N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1566N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1567N/A
do not use mixed case (camelCase), use lower case and _Othersalesforce_api.module1568N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1576N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1579N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1579N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1580N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1582N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1582N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1583N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1585N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1585N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1587N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1587N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1588N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1589N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1589N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1590N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1591N/A
indent secondary line of comment one space Othersalesforce_api.module1592N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.module1593N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1595N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1598N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1605N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1606N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1639N/A
Control statements should have one space between the control keyword and opening parenthesisOthersalesforce_api.module1642N/A
Separate comments from comment syntax by a space.Othersalesforce_api.module1670N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1676N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersalesforce_api.module1693N/A
Use the matching Drupal theme functions, not raw HTML.Othersalesforce_api.module1693N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1709N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1711N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1711N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1714N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1714N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1716N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1716N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1718N/A
Function documentation should be less than 80 characters per line.Othersalesforce_api.module1718N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersalesforce_api.module1718N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module1727N/A
Use an indent of 2 spaces, with no tabsOthersalesforce_api.module1733N/A
Function summaries should be one line only. (Drupal Docs)Othersalesforce_api.module1751N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1753N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1753N/A
If you define a @param or @return, you should document it as well.Othersalesforce_api.module1755N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersalesforce_api.module1755N/A
Expandsalesforce_api/salesforce_api.views.inc002
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersalesforce_api.views.inc2N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersalesforce_api.views.inc41N/A
Expandsf_entity/sf_entity.module7769
MessageGroupFilenameLineFunctionStatus
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module9N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module33N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module38N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module101N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module177N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module184N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module189N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module197N/A
Use Drupal's format_date(), not PHP's default date().Othersf_entity.module200N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module205N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module208N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module208N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module209N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module209N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module214N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module221N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module239N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module242N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module242N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module249N/A
indent secondary line of comment one space Othersf_entity.module251N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module253N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module260N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module263N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module263N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module297N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module317N/A
Use an indent of 2 spaces, with no tabsOthersf_entity.module380N/A
Use an indent of 2 spaces, with no tabsOthersf_entity.module386N/A
Potential problem: confirm_form() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized. (Drupal Docs)Othersf_entity.module446N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module480N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module486N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_entity.module497N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module498N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_entity.module518N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module534N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module534N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module538N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module570N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module609N/A
Remove the empty commented line in your function documentation.Othersf_entity.module654N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module657N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module701N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module708N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_entity.module711N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module713N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module715N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module731N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module731N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module773N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module806N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module812N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_entity.module828N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module842N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module844N/A
Function documentation should be less than 80 characters per line.Othersf_entity.module845N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module846N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module855N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_entity.module859N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_entity.module859N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module885N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module944N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module956N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module961N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module1040N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_entity.module1042N/A
Function documentation should be less than 80 characters per line.Othersf_entity.module1043N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1044N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1046N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module1048N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1054N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1057N/A
Function summaries should be one line only. (Drupal Docs)Othersf_entity.module1114N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_entity.module1117N/A
Function documentation should be less than 80 characters per line.Othersf_entity.module1118N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1119N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_entity.module1121N/A
If you define a @param or @return, you should document it as well.Othersf_entity.module1123N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1157N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1173N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_entity.module1231N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_entity.module1260N/A
Remove the empty commented line in your function documentation.Othersf_entity.module1361N/A
Expandsf_import/sf_import.admin.inc0112
MessageGroupFilenameLineFunctionStatus
Use Drupal's format_date(), not PHP's default date().Othersf_import.admin.inc23N/A
table names should be enclosed in {curly_brackets}Othersf_import.admin.inc52N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.admin.inc100N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.admin.inc152N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_import.admin.inc225N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.admin.inc252N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_import.admin.inc266N/A
If you define a @param or @return, you should document it as well.Othersf_import.admin.inc285N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.admin.inc285N/A
If you define a @param or @return, you should document it as well.Othersf_import.admin.inc286N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.admin.inc286N/A
If you define a @param or @return, you should document it as well.Othersf_import.admin.inc287N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.admin.inc287N/A
Expandsf_import/sf_import.batch.inc0113
MessageGroupFilenameLineFunctionStatus
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc11N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc13N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc33N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_import.batch.inc33N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc34N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc34N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc35N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc35N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure to use check_plain(), filter_xss() or similar to ensure your $variable is fully sanitized. (Drupal Docs)Othersf_import.batch.inc41N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc52N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc54N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc54N/A
If you define a @param or @return, you should document it as well.Othersf_import.batch.inc55N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_import.batch.inc55N/A
Expandsf_import/sf_import.drush.inc008
MessageGroupFilenameLineFunctionStatus
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc78N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc89N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc109N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc144N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc157N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc172N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.drush.inc179N/A
Function summaries should be one line only. (Drupal Docs)Othersf_import.drush.inc335N/A
Leafsf_import/sf_import.install000
Expandsf_import/sf_import.module2111
MessageGroupFilenameLineFunctionStatus
@file block missing (Drupal Docs)Othersf_import.module-1N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.module21N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.module31N/A
Function summaries should be one line only. (Drupal Docs)Othersf_import.module74N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_import.module76N/A
@see should always be at the beginning of a line, never inline in other comments.Othersf_import.module77N/A
@see references should be separated by "," followed by a single space and with no trailing punctuationOthersf_import.module77N/A
If you define a @param or @return, you should document it as well.Othersf_import.module78N/A
Function documentation should be less than 80 characters per line.Othersf_import.module78N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_import.module78N/A
table names should be enclosed in {curly_brackets}Othersf_import.module88N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_import.module91N/A
Function summaries should be one line only. (Drupal Docs)Othersf_import.module117N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_import.module142N/A
Expandsf_notifications/sf_notifications.admin.inc007
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othersf_notifications.admin.inc12N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.admin.inc13N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc19N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc35N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc44N/A
Use the matching Drupal theme functions, not raw HTML.Othersf_notifications.admin.inc45N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_notifications.admin.inc57N/A
Expandsf_notifications/sf_notifications.api.php006
MessageGroupFilenameLineFunctionStatus
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php25N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php27N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php38N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php40N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php62N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.api.php64N/A
Expandsf_notifications/sf_notifications.drush.inc200
MessageGroupFilenameLineFunctionStatus
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().Othersf_notifications.drush.inc18N/A
@see references should be separated by "," followed by a single space and with no trailing punctuationOthersf_notifications.drush.inc18N/A
Expandsf_notifications/sf_notifications.install001
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_notifications.install2N/A
Expandsf_notifications/sf_notifications.module6045
MessageGroupFilenameLineFunctionStatus
@file block missing (Drupal Docs)Othersf_notifications.module-1N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module59N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module59N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module88N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module106N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module126N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module127N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module128N/A
Use an indent of 2 spaces, with no tabsOthersf_notifications.module134N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module172N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module175N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_notifications.module175N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module178N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module178N/A
Format should be * Implementation of hook_foo().Othersf_notifications.module205N/A
Format should be * Implementation of hook_foo().Othersf_notifications.module251N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module268N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_notifications.module277N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module339N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_notifications.module358N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module397N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module397N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module399N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module399N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module407N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module417N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module418N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module419N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module420N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module421N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_notifications.module421N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module424N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module425N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_notifications.module440N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module451N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module451N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module452N/A
put a space between the asterisk and the comment textOthersf_notifications.module453N/A
use lowercase html tags to comply with XHTMLOthersf_notifications.module461N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module471N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module471N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_notifications.module471N/A
If you define a @param or @return, you should document it as well.Othersf_notifications.module472N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_notifications.module472N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module484N/A
do not use mixed case (camelCase), use lower case and _Othersf_notifications.module485N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module493N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module494N/A
Function summaries should be one line only. (Drupal Docs)Othersf_notifications.module518N/A
Function documentation should be less than 80 characters per line.Othersf_notifications.module519N/A
Use Drupal's format_date(), not PHP's default date().Othersf_notifications.module524N/A
Expandsf_prematch/sf_prematch.admin.inc2012
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_prematch.admin.inc2N/A
Separate comments from comment syntax by a space.Othersf_prematch.admin.inc24N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.admin.inc25N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_prematch.admin.inc33N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.admin.inc109N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.admin.inc119N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.admin.inc126N/A
Use Drupal's format_date(), not PHP's default date().Othersf_prematch.admin.inc161N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.admin.inc174N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.admin.inc187N/A
Use Drupal's format_date(), not PHP's default date().Othersf_prematch.admin.inc189N/A
The $string argument to t() should not begin or end with a space. (Drupal Docs)Othersf_prematch.admin.inc229N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_prematch.admin.inc279N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_prematch.admin.inc280N/A
Expandsf_prematch/sf_prematch.install107
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_prematch.install2N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install13N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install21N/A
@see should always be followed by a filename, a URL, class/interface name (optionally including method), or a function name including ().Othersf_prematch.install74N/A
Remove the empty commented line in your function documentation.Othersf_prematch.install75N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install90N/A
Use Drupal's format_date(), not PHP's default date().Othersf_prematch.install92N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.install104N/A
Expandsf_prematch/sf_prematch.main.inc1023
MessageGroupFilenameLineFunctionStatus
Commits to the Git repository do not require the CVS $Id$ keyword in each file. (Drupal Docs)Othersf_prematch.main.inc2N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc12N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc12N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc13N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_prematch.main.inc13N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc14N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc14N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc15N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc15N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc16N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc16N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_prematch.main.inc120N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc146N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc146N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc147N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_prematch.main.inc147N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc148N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc148N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc149N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc149N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.main.inc151N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.main.inc151N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_prematch.main.inc310N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_prematch.main.inc311N/A
Expandsf_prematch/sf_prematch.module0014
MessageGroupFilenameLineFunctionStatus
Function documentation should be less than 80 characters per line.Othersf_prematch.module5N/A
Function summaries should be one line only. (Drupal Docs)Othersf_prematch.module54N/A
Function documentation should be less than 80 characters per line.Othersf_prematch.module92N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module94N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module94N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module95N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module95N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module136N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module147N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module147N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module148N/A
@param and @return descriptions begin indented on the next line. (Drupal Docs)Othersf_prematch.module148N/A
If you define a @param or @return, you should document it as well.Othersf_prematch.module149N/A
@param and @return syntax does not indicate the data type. (Drupal Docs)Othersf_prematch.module149N/A
Expandsf_queue/sf_queue.admin.inc326
MessageGroupFilenameLineFunctionStatus
Control statements should have one space between the control keyword and opening parenthesisOthersf_queue.admin.inc20N/A
Use Drupal's format_date(), not PHP's default date().Othersf_queue.admin.inc33N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_queue.admin.inc64N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.admin.inc68N/A
in most cases, replace the string function with the drupal_ equivalent string functionsOthersf_queue.admin.inc112N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.admin.inc116N/A
Use an indent of 2 spaces, with no tabsOthersf_queue.admin.inc136N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.admin.inc145N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_queue.admin.inc148N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_queue.admin.inc151N/A
Control statements should have one space between the control keyword and opening parenthesisOthersf_queue.admin.inc160N/A
Expandsf_queue/sf_queue.install004
MessageGroupFilenameLineFunctionStatus
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.install13N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.install21N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.install23N/A
Remove the empty commented line in your function documentation.Othersf_queue.install39N/A
Expandsf_queue/sf_queue.module2128
MessageGroupFilenameLineFunctionStatus
@file description should be on the following line (Drupal Docs)Othersf_queue.module4N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module71N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module94N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module95N/A
Potential problem: drupal_set_message() only accepts filtered text, be sure all !placeholders for $variables in t() are fully sanitized using check_plain(), filter_xss() or similar. (Drupal Docs)Othersf_queue.module149N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module211N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module230N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module245N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module272N/A
Separate comments from comment syntax by a space.Othersf_queue.module285N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module307N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module319N/A
Separate comments from comment syntax by a space.Othersf_queue.module358N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module376N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module380N/A
use <br /> instead of <br>Othersf_queue.module408N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module414N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module419N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module426N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module431N/A
Doxygen uses @todo and @bug to markup things to be done.Othersf_queue.module442N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module448N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module455N/A
The $text argument to l() should be enclosed within t() so that it is translatable.Othersf_queue.module461N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module468N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module509N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module534N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module541N/A
Use sentence case, not title case, for end-user strings. (Wikipedia)Othersf_queue.module548N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module559N/A
Function summaries should be one line only. (Drupal Docs)Othersf_queue.module575N/A