These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | /** |
||
3 | * Article management |
||
4 | * |
||
5 | * @copyright The XOOPS project http://www.xoops.org/ |
||
6 | * @license http://www.fsf.org/copyleft/gpl.html GNU public license |
||
7 | * @author Taiwen Jiang (phppp or D.J.) <[email protected]> |
||
8 | * @since 1.00 |
||
9 | * @version $Id$ |
||
10 | * @package module::article |
||
11 | */ |
||
12 | |||
13 | include_once '../../mainfile.php'; |
||
14 | |||
15 | /* |
||
0 ignored issues
–
show
|
|||
16 | if(!empty($GLOBALS["xoopsModuleConfig"]['theme_set'])){ |
||
17 | $GLOBALS["xoopsModuleConfig"]['theme_set'] = $GLOBALS["xoopsModuleConfig"]['theme_set']; |
||
18 | } |
||
19 | */ |
||
20 | require_once XOOPS_ROOT_PATH . "/class/module.textsanitizer.php"; |
||
21 | $myts =& MyTextSanitizerExtended::getInstance(); |
||
22 |
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.
The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.
This check looks for comments that seem to be mostly valid code and reports them.