Completed
Pull Request — master (#10)
by Michael
02:01
created

onupdate.php ➔ xoops_module_update_xfguestbook()   D

Complexity

Conditions 19
Paths 65

Size

Total Lines 85
Code Lines 43

Duplication

Lines 13
Ratio 15.29 %

Importance

Changes 0
Metric Value
cc 19
eloc 43
nc 65
nop 2
dl 13
loc 85
rs 4.7869
c 0
b 0
f 0

How to fix   Long Method    Complexity   

Long Method

Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.

For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.

Commonly applied refactorings include:

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 31 and the first side effect is on line 23.

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
/**
13
 * @copyright    XOOPS Project http://xoops.org/
14
 * @license      GNU GPL 2 or later (http://www.gnu.org/licenses/gpl-2.0.html)
15
 * @package
16
 * @since
17
 * @author       XOOPS Development Team
18
 */
19
20
if ((!defined('XOOPS_ROOT_PATH')) || !($GLOBALS['xoopsUser'] instanceof XoopsUser)
0 ignored issues
show
Bug introduced by
The class XoopsUser does not exist. Did you forget a USE statement, or did you not list all dependencies?

This error could be the result of:

1. Missing dependencies

PHP Analyzer uses your composer.json file (if available) to determine the dependencies of your project and to determine all the available classes and functions. It expects the composer.json to be in the root folder of your repository.

Are you sure this class is defined by one of your dependencies, or did you maybe not list a dependency in either the require or require-dev section?

2. Missing use statement

PHP does not complain about undefined classes in ìnstanceof checks. For example, the following PHP code will work perfectly fine:

if ($x instanceof DoesNotExist) {
    // Do something.
}

If you have not tested against this specific condition, such errors might go unnoticed.

Loading history...
21
    || !$GLOBALS['xoopsUser']->IsAdmin()
22
) {
23
    exit('Restricted access' . PHP_EOL);
24
}
25
26
/**
27
 * @param string $tablename
28
 *
29
 * @return bool
30
 */
31
function tableExists($tablename)
0 ignored issues
show
Coding Style introduced by
tableExists uses the super-global variable $GLOBALS which is generally not recommended.

Instead of super-globals, we recommend to explicitly inject the dependencies of your class. This makes your code less dependent on global state and it becomes generally more testable:

// Bad
class Router
{
    public function generate($path)
    {
        return $_SERVER['HOST'].$path;
    }
}

// Better
class Router
{
    private $host;

    public function __construct($host)
    {
        $this->host = $host;
    }

    public function generate($path)
    {
        return $this->host.$path;
    }
}

class Controller
{
    public function myAction(Request $request)
    {
        // Instead of
        $page = isset($_GET['page']) ? intval($_GET['page']) : 1;

        // Better (assuming you use the Symfony2 request)
        $page = $request->query->get('page', 1);
    }
}
Loading history...
32
{
33
    $result = $GLOBALS['xoopsDB']->queryF("SHOW TABLES LIKE '$tablename'");
34
35
    return ($GLOBALS['xoopsDB']->getRowsNum($result) > 0) ? true : false;
36
}
37
38
/**
39
 *
40
 * Prepares system prior to attempting to install module
41
 * @param XoopsModule $module {@link XoopsModule}
42
 *
43
 * @return bool true if ready to install, false if not
44
 */
45
function xoops_module_pre_update_xfguestbook(XoopsModule $module)
46
{
47
    $moduleDirName = basename(dirname(__DIR__));
48
    $className     = ucfirst($moduleDirName) . 'Util';
49
    if (!class_exists($className)) {
50
        xoops_load('util', $moduleDirName);
51
    }
52
    //check for minimum XOOPS version
53
    if (!$className::checkVerXoops($module)) {
54
        return false;
55
    }
56
57
    // check for minimum PHP version
58
    if (!$className::checkVerPhp($module)) {
59
        return false;
60
    }
61
    global $xoopsDB;
0 ignored issues
show
Compatibility Best Practice introduced by
Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

Instead of relying on global state, we recommend one of these alternatives:

1. Pass all data via parameters

function myFunction($a, $b) {
    // Do something
}

2. Create a class that maintains your state

class MyClass {
    private $a;
    private $b;

    public function __construct($a, $b) {
        $this->a = $a;
        $this->b = $b;
    }

    public function myFunction() {
        // Do something
    }
}
Loading history...
62
    //delete .html entries from the tpl table
63
64
//    $sql = 'DELETE FROM ' . $xoopsDB->prefix('tplfile') . " WHERE `tpl_module` = '" . $module->getVar('dirname', 'n') . '\' AND `tpl_file` LIKE \'%.tpl%\'';
65
//    $xoopsDB->queryF($sql);
66
//
67
//    $sql = 'DELETE FROM ' . $xoopsDB->prefix('newblocks') . " WHERE `dirname` = '" . $module->getVar('dirname', 'n') . "' AND `template` LIKE '%.tpl%'";
68
//    $xoopsDB->queryF($sql);
69
70
    return true;
71
}
72
73
/**
74
 *
75
 * Performs tasks required during update of the module
76
 * @param XoopsModule $module {@link XoopsModule}
77
 * @param null        $previousVersion
78
 *
79
 * @return bool true if update successful, false if not
80
 */
0 ignored issues
show
Documentation introduced by
Should the return type not be boolean|null?

This check compares the return type specified in the @return annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch.

Loading history...
81
82
function xoops_module_update_xfguestbook(XoopsModule $module, $previousVersion = null)
0 ignored issues
show
Coding Style introduced by
xoops_module_update_xfguestbook uses the super-global variable $GLOBALS which is generally not recommended.

Instead of super-globals, we recommend to explicitly inject the dependencies of your class. This makes your code less dependent on global state and it becomes generally more testable:

// Bad
class Router
{
    public function generate($path)
    {
        return $_SERVER['HOST'].$path;
    }
}

// Better
class Router
{
    private $host;

    public function __construct($host)
    {
        $this->host = $host;
    }

    public function generate($path)
    {
        return $this->host.$path;
    }
}

class Controller
{
    public function myAction(Request $request)
    {
        // Instead of
        $page = isset($_GET['page']) ? intval($_GET['page']) : 1;

        // Better (assuming you use the Symfony2 request)
        $page = $request->query->get('page', 1);
    }
}
Loading history...
83
{
84
    global $xoopsDB;
0 ignored issues
show
Compatibility Best Practice introduced by
Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

Instead of relying on global state, we recommend one of these alternatives:

1. Pass all data via parameters

function myFunction($a, $b) {
    // Do something
}

2. Create a class that maintains your state

class MyClass {
    private $a;
    private $b;

    public function __construct($a, $b) {
        $this->a = $a;
        $this->b = $b;
    }

    public function myFunction() {
        // Do something
    }
}
Loading history...
85
    $moduleDirName = basename(dirname(__DIR__));
86
    $capsDirName   = strtoupper($moduleDirName);
0 ignored issues
show
Unused Code introduced by
$capsDirName is not used, you could remove the assignment.

This check looks for variable assignements that are either overwritten by other assignments or where the variable is not used subsequently.

$myVar = 'Value';
$higher = false;

if (rand(1, 6) > 3) {
    $higher = true;
} else {
    $higher = false;
}

Both the $myVar assignment in line 1 and the $higher assignment in line 2 are dead. The first because $myVar is never used and the second because $higher is always overwritten for every possible time line.

Loading history...
87
88
    if ($previousVersion < 330) {
89
90
        include_once __DIR__ . '/config.php';
91
        $configurator = new ModuleConfigurator();
92
        $classUtil    = ucfirst($moduleDirName) . 'Util';
93
        if (!class_exists($classUtil)) {
94
            xoops_load('util', $moduleDirName);
95
        }
96
97
        //delete old HTML templates
98
        if (count($configurator->templateFolders) > 0) {
99
            foreach ($configurator->templateFolders as $folder) {
100
                $templateFolder = $GLOBALS['xoops']->path('modules/' . $moduleDirName . $folder);
101
                if (is_dir($templateFolder)) {
102
                    $templateList = array_diff(scandir($templateFolder), array('..', '.'));
103
                    foreach ($templateList as $k => $v) {
104
                        $fileInfo = new SplFileInfo($templateFolder . $v);
105
                        if ($fileInfo->getExtension() === 'html' && $fileInfo->getFilename() !== 'index.html') {
106
                            if (file_exists($templateFolder . $v)) {
107
                                unlink($templateFolder . $v);
108
                            }
109
                        }
110
                    }
111
                }
112
            }
113
        }
114
115
        //  ---  DELETE OLD FILES ---------------
116
        if (count($configurator->oldFiles) > 0) {
117
            //    foreach (array_keys($GLOBALS['uploadFolders']) as $i) {
0 ignored issues
show
Unused Code Comprehensibility introduced by
67% 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...
118
            foreach (array_keys($configurator->oldFiles) as $i) {
119
                $tempFile = $GLOBALS['xoops']->path('modules/' . $moduleDirName . $configurator->oldFiles[$i]);
120
                if (is_file($tempFile)) {
121
                    unlink($tempFile);
122
                }
123
            }
124
        }
125
126
        //  ---  DELETE OLD FOLDERS ---------------
127
        xoops_load('XoopsFile');
128
        if (count($configurator->oldFolders) > 0) {
129
            //    foreach (array_keys($GLOBALS['uploadFolders']) as $i) {
0 ignored issues
show
Unused Code Comprehensibility introduced by
67% 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...
130
            foreach (array_keys($configurator->oldFolders) as $i) {
131
                $tempFolder = $GLOBALS['xoops']->path('modules/' . $moduleDirName . $configurator->oldFolders[$i]);
132
                /** @var XoopsObjectHandler $folderHandler */
133
                $folderHandler = XoopsFile::getHandler('folder', $tempFolder);
134
                $folderHandler->delete($tempFolder);
135
            }
136
        }
137
138
        //  ---  CREATE FOLDERS ---------------
139 View Code Duplication
        if (count($configurator->uploadFolders) > 0) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
140
            //    foreach (array_keys($GLOBALS['uploadFolders']) as $i) {
0 ignored issues
show
Unused Code Comprehensibility introduced by
67% 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...
141
            foreach (array_keys($configurator->uploadFolders) as $i) {
142
                $classUtil::createFolder($configurator->uploadFolders[$i]);
143
            }
144
        }
145
146
        //  ---  COPY blank.png FILES ---------------
147 View Code Duplication
        if (count($configurator->blankFiles) > 0) {
0 ignored issues
show
Duplication introduced by
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
148
            $file = __DIR__ . '/../assets/images/blank.png';
149
            foreach (array_keys($configurator->blankFiles) as $i) {
150
                $dest = $configurator->blankFiles[$i] . '/blank.png';
151
                $classUtil::copyFile($file, $dest);
152
            }
153
        }
154
155
        //delete .html entries from the tpl table
156
        $sql = 'DELETE FROM ' . $xoopsDB->prefix('tplfile') . " WHERE `tpl_module` = '" . $module->getVar('dirname', 'n') . '\' AND `tpl_file` LIKE \'%.html%\'';
157
        $xoopsDB->queryF($sql);
158
        $sql = 'DELETE FROM ' . $xoopsDB->prefix('newblocks') . " WHERE `dirname` = '" . $module->getVar('dirname', 'n') . "' AND `template` LIKE '%.html%'";
159
        $xoopsDB->queryF($sql);
160
161
        /** @var XoopsGroupPermHandler $gpermHandler */
162
        //        $gpermHandler = xoops_getHandler('groupperm');
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% 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...
163
        //        return $gpermHandler->deleteByModule($module->getVar('mid'), 'item_read');
0 ignored issues
show
Unused Code Comprehensibility introduced by
73% 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...
164
165
    }
166
}
167