UserlogCorePreload   A
last analyzed

Complexity

Total Complexity 4

Size/Duplication

Total Lines 44
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 0

Importance

Changes 0
Metric Value
dl 0
loc 44
rs 10
c 0
b 0
f 0
wmc 4
lcom 0
cbo 0

4 Methods

Rating   Name   Duplication   Size   Complexity  
A eventCoreFooterStart() 0 4 1
A eventCoreIncludeFunctionsRedirectheader() 0 4 1
A eventCoreIncludeCommonEnd() 0 4 1
A eventSystemClassGuiHeader() 0 4 1
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 27 and the first side effect is on line 22.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
/*
3
 You may not change or alter any portion of this comment or credits
4
 of supporting developers from this source code or any supporting source code
5
 which is considered copyrighted (c) material of the original comment or credit authors.
6
7
 This program is distributed in the hope that it will be useful,
8
 but WITHOUT ANY WARRANTY; without even the implied warranty of
9
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
10
*/
11
/**
12
 *  userlog module
13
 *
14
 * @copyright       XOOPS Project (https://xoops.org)
15
 * @license         GNU GPL 2 (http://www.gnu.org/licenses/old-licenses/gpl-2.0.html)
16
 * @package         userlog preloads
17
 * @since           1
18
 * @author          irmtfan ([email protected])
19
 * @author          XOOPS Project <www.xoops.org> <www.xoops.ir>
20
 */
21
22
defined('XOOPS_ROOT_PATH') || exit('Restricted access.');
23
24
/**
25
 * Class UserlogCorePreload
26
 */
27
class UserlogCorePreload extends XoopsPreloadItem
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
28
{
29
    // to log main part of modules
30
    /**
31
     * @param $args
32
     */
33
    public static function eventCoreFooterStart($args)
34
    {
35
        include __DIR__ . '/../include/log.php';
36
    }
37
38
    // to log redirects because usually prorammers use exit() after redirect_header function.
39
40
    /**
41
     * @param $args
42
     */
43
    public static function eventCoreIncludeFunctionsRedirectheader($args)
44
    {
45
        include __DIR__ . '/../include/log.php';
46
    }
47
48
    /**
49
     * @param $args
50
     */
51
    public static function eventCoreIncludeCommonEnd($args)
52
    {
53
        include __DIR__ . '/../include/postlog.php';
54
    }
55
    // in XOOPS255/index.php (homepage) when no module is set for start page there is a bug in XOOPS255/header.php exit() should be commented
56
    /*$xoopsPreload->triggerEvent('core.header.checkcache');
0 ignored issues
show
Unused Code Comprehensibility introduced by
74% of this comment could be valid code. Did you maybe forget this after debugging?

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.

Loading history...
57
    if ($xoTheme->checkCache()) {
58
        $xoopsPreload->triggerEvent('core.header.cacheend');
59
        //exit();
60
    } */
61
62
    // to log admin part of modules (must use moduleadmin class)
63
    /**
64
     * @param $args
65
     */
66
    public static function eventSystemClassGuiHeader($args)
67
    {
68
        include __DIR__ . '/../include/log.php';
69
    }
70
}
71