| Function summaries should be one line only. (Drupal Docs) | Other | epublish.module | 17 | N/A |  |
| Administrative menu items should have a description. | Other | epublish.module | 200 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 206 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 211 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 218 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 225 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 232 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 239 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 240 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 246 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 253 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 260 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 267 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 274 | N/A | |
| Administrative menu items should have a description. | Other | epublish.module | 281 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 315 | N/A | |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | epublish.module | 516 | N/A |  |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | epublish.module | 517 | N/A | |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | epublish.module | 534 | N/A | |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | epublish.module | 535 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 579 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 584 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 587 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 588 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 626 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 628 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 632 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 633 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 639 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 640 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 680 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 684 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 691 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 693 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 695 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 697 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 699 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 704 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 720 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 722 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 724 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 727 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 742 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 744 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 747 | N/A | |
| Separate comments from comment syntax by a space. | Other | epublish.module | 795 | N/A | |
| Doxygen uses @todo and @bug to markup things to be done. | Other | epublish.module | 797 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 798 | N/A |  |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 799 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 811 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 832 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 834 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 836 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 838 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 889 | N/A | |
| Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n) | Other | epublish.module | 889 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 893 | N/A | |
| Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n) | Other | epublish.module | 893 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 897 | N/A | |
| Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n) | Other | epublish.module | 897 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 901 | N/A | |
| Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n) | Other | epublish.module | 901 | N/A | |
| Function summaries should be one line only. (Drupal Docs) | Other | epublish.module | 918 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 921 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 923 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 925 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 928 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 929 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 940 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 942 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 945 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 946 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 962 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 964 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 965 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 983 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 986 | N/A | |
| Function summaries should be one line only. (Drupal Docs) | Other | epublish.module | 986 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 987 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 994 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 996 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 998 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 999 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1003 | N/A | |
| else statements should begin on a new line | Other | epublish.module | 1023 | N/A | |
| else statements should begin on a new line | Other | epublish.module | 1025 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1031 | N/A | |
| Function summaries should be one line only. (Drupal Docs) | Other | epublish.module | 1031 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1032 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1033 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1038 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1041 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1067 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1069 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1072 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1073 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 1096 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1101 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1104 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1113 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1115 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1118 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1119 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1128 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1130 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1157 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1158 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1159 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1160 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1161 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 1165 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1171 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1172 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1179 | N/A | |
| Missing period | Other | epublish.module | 1179 | N/A | |
Format should be * Implementation of hook_foo(). | Other | epublish.module | 1179 | N/A | |
| indent secondary line of comment one space | Other | epublish.module | 1180 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1207 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1210 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1390 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1393 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1440 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1443 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 1485 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1490 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1492 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1493 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1495 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1525 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1528 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 1594 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1670 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1673 | N/A | |
| Use an indent of 2 spaces, with no tabs | Other | epublish.module | 1701 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1707 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1709 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1710 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1712 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1742 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1744 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1746 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1747 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1749 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1750 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1751 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1752 | N/A | |
| Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n) | Other | epublish.module | 1757 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 1788 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1793 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1796 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 1805 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1807 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1810 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1822 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 1842 | N/A | |
| The $string argument to t() should not begin or end with a space. (Drupal Docs) | Other | epublish.module | 1848 | N/A | |
| The $string argument to t() should not begin or end with a space. (Drupal Docs) | Other | epublish.module | 1856 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1883 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 1886 | N/A | |
| In SQL strings, Use db_query() placeholders in place of variables. This is a potential source of SQL injection attacks when the variable can come from user data. (Drupal Docs) | Other | epublish.module | 1921 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2011 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2014 | N/A | |
| else statements should begin on a new line | Other | epublish.module | 2023 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2035 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2038 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 2065 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2070 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2073 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 2082 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2084 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2087 | N/A | |
| Use db_query_range() instead of the SQL LIMIT clause (Drupal Docs) | Other | epublish.module | 2095 | N/A | |
| Use db_query_range() instead of the SQL LIMIT clause (Drupal Docs) | Other | epublish.module | 2099 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2129 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2132 | N/A | |
| The $string argument to t() should not begin or end with a space. (Drupal Docs) | Other | epublish.module | 2143 | N/A | |
| Use Drupal's format_date(), not PHP's default date(). | Other | epublish.module | 2209 | N/A | |
| Use Drupal's format_date(), not PHP's default date(). | Other | epublish.module | 2210 | N/A | |
| Use Drupal's format_date(), not PHP's default date(). | Other | epublish.module | 2211 | N/A | |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | epublish.module | 2214 | N/A | |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | epublish.module | 2215 | N/A | |
| in most cases, replace the string function with the drupal_ equivalent string functions | Other | epublish.module | 2216 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 2218 | N/A | |
| Use Drupal's format_date(), not PHP's default date(). | Other | epublish.module | 2218 | N/A | |
| Use the matching Drupal theme functions, not raw HTML. | Other | epublish.module | 2326 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 2342 | N/A | |
| Doxygen uses @todo and @bug to markup things to be done. | Other | epublish.module | 2350 | N/A | |
| Separate comments from comment syntax by a space. | Other | epublish.module | 2357 | N/A | |
| The $string argument to t() should not begin or end with a space. (Drupal Docs) | Other | epublish.module | 2360 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 2411 | N/A | |
| Separate comments from comment syntax by a space. | Other | epublish.module | 2413 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2426 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 2429 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2431 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2490 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2493 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 2517 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2522 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2524 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2527 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2557 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2560 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2602 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2605 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2625 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2628 | N/A | |
| put a space between the asterisk and the comment text | Other | epublish.module | 2652 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2657 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2660 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2674 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2676 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2687 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2689 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2699 | N/A | |
| Doxygen uses @todo and @bug to markup things to be done. | Other | epublish.module | 2714 | N/A | |
| Doxygen uses @todo and @bug to markup things to be done. | Other | epublish.module | 2717 | N/A | |
| Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n) | Other | epublish.module | 2753 | N/A | |
| Potential problem: "SELECT FROM {node}" statements should probably be wrapped in db_rewrite_sql() and with the alias for {node} table defined (e.g. {node} n) | Other | epublish.module | 2754 | N/A | |
| Use sentence case, not title case, for end-user strings. (Wikipedia) | Other | epublish.module | 2804 | N/A | |
| Potential problem: use the Form API to prevent against CSRF attacks. If you need to use $_POST variables, ensure they are fully sanitized if displayed by using check_plain(), filter_xss() or similar. (Drupal Docs) | Other | epublish.module | 2816 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 2838 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2840 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2842 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2845 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 2871 | N/A | |
| Function summaries should be one line only. (Drupal Docs) | Other | epublish.module | 2871 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2874 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2877 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 2878 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 2890 | N/A | |
| Function summaries should be one line only. (Drupal Docs) | Other | epublish.module | 2890 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2893 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2896 | N/A | |
| Function documentation should be less than 80 characters per line. | Other | epublish.module | 2897 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2911 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2913 | N/A | |
| If you define a @param or @return, you should document it as well. | Other | epublish.module | 2916 | N/A | |
| Function summaries should be one line only. (Drupal Docs) | Other | epublish.module | 2943 | N/A | |
| The $string argument to t() should not begin or end with a space. (Drupal Docs) | Other | epublish.module | 2973 | N/A | |
| The $string argument to t() should not begin or end with a space. (Drupal Docs) | Other | epublish.module | 2976 | N/A | |
| The $text argument to l() should be enclosed within t() so that it is translatable. | Other | epublish.module | 2978 | N/A | |
| The $string argument to t() should not begin or end with a space. (Drupal Docs) | Other | epublish.module | 2978 | N/A | |
