WfLinksUtility::checkVerXoops() - Code Metrics - Inspection of "updates" - mambax7/wflinks - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 2b2520...e78a73 )

by Michael

created 2017-09-04 00:34 UTC

WfLinksUtility::checkVerXoops() D

↳ Parent: Project

Complexity

Conditions	9
Paths	40

Size

Total Lines	39
Code Lines	27

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	9
eloc	27
nc	40
nop	2
dl	0
loc	39
rs	4.909
c	0
b	0
f	0

<?php



use Xmf\Request;

require_once __DIR__ . '/common/traitversionchecks.php';
require_once __DIR__ . '/common/traitserverstats.php';

/**
 * Class MyalbumUtil
 */
class WfLinksUtility extends XoopsObject
namespace YourVendor;

class YourClass { }
{
    use VersionChecks; //checkVerXoops, checkVerPhp Traits

    use ServerStats; // getServerStats Trait

    /**
     * Function responsible for checking if a directory exists, we can also write in and create an index.html file
     *
     * @param string $folder The full path of the directory to check
     *
     * @return void
     */
    public static function createFolder($folder)
    {
        //        try {
        //            if (!mkdir($folder) && !is_dir($folder)) {

        //                throw new \RuntimeException(sprintf('Unable to create the %s directory', $folder));

        //            } else {

        //                file_put_contents($folder . '/index.html', '<script>history.go(-1);</script>');

        //            }
        //        }
        //        catch (Exception $e) {

        //            echo 'Caught exception: ', $e->getMessage(), "\n", '<br>';

        //        }
        try {
            if (!file_exists($folder)) {
                if (!mkdir($folder) && !is_dir($folder)) {
                    throw new \RuntimeException(sprintf('Unable to create the %s directory', $folder));
                }

                file_put_contents($folder . '/index.html', '<script>history.go(-1);</script>');
            }
        }
        catch (Exception $e) {
            echo 'Caught exception: ', $e->getMessage(), "\n", '<br>';
        }
    }

    /**
     * @param $file
     * @param $folder
     * @return bool
     */
    public static function copyFile($file, $folder)
    {
        return copy($file, $folder);
        //        try {
        //            if (!is_dir($folder)) {

        //                throw new \RuntimeException(sprintf('Unable to copy file as: %s ', $folder));

        //            } else {

        //                return copy($file, $folder);

        //            }
        //        } catch (Exception $e) {

        //            echo 'Caught exception: ', $e->getMessage(), "\n", "<br>";

        //        }
        //        return false;
    }

    /**
     * @param $src
     * @param $dst
     */
    public static function recurseCopy($src, $dst)
    {
        $dir = opendir($src);
        //    @mkdir($dst);
        while (false !== ($file = readdir($dir))) {
            if (($file !== '.') && ($file !== '..')) {
                if (is_dir($src . '/' . $file)) {
                    self::recurseCopy($src . '/' . $file, $dst . '/' . $file);
                } else {
                    copy($src . '/' . $file, $dst . '/' . $file);
                }
            }
        }
        closedir($dir);
    }
}


1			<?php
			0 ignored issues – show Coding Style Compatibility introduced 2017-09-04 00:35 UTC by Report Bug Copy Issue Report 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 12 and the first side effect is on line 6. 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
4			use Xmf\Request;
5
6			require_once __DIR__ . '/common/traitversionchecks.php';
7			require_once __DIR__ . '/common/traitserverstats.php';
8
9			/**
10			* Class MyalbumUtil
11			*/
12			class WfLinksUtility extends XoopsObject
			0 ignored issues – show Coding Style Compatibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report 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...
13			{
14			use VersionChecks; //checkVerXoops, checkVerPhp Traits
15
16			use ServerStats; // getServerStats Trait
17
18			/**
19			* Function responsible for checking if a directory exists, we can also write in and create an index.html file
20			*
21			* @param string $folder The full path of the directory to check
22			*
23			* @return void
24			*/
25			public static function createFolder($folder)
26			{
27			// try {
28			// if (!mkdir($folder) && !is_dir($folder)) {
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `65%` 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...
29			// throw new \RuntimeException(sprintf('Unable to create the %s directory', $folder));
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `63%` 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...
30			// } else {
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `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...
31			// file_put_contents($folder . '/index.html', '<script>history.go(-1);</script>');
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `54%` 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...
32			// }
33			// }
34			// catch (Exception $e) {
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `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...
35			// echo 'Caught exception: ', $e->getMessage(), "\n", '<br>';
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `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...
36			// }
37			try {
38			if (!file_exists($folder)) {
39			if (!mkdir($folder) && !is_dir($folder)) {
40			throw new \RuntimeException(sprintf('Unable to create the %s directory', $folder));
41			}
42
43			file_put_contents($folder . '/index.html', '<script>history.go(-1);</script>');
44			}
45			}
46			catch (Exception $e) {
47			echo 'Caught exception: ', $e->getMessage(), "\n", '<br>';
48			}
49			}
50
51			/**
52			* @param $file
53			* @param $folder
54			* @return bool
55			*/
56			public static function copyFile($file, $folder)
57			{
58			return copy($file, $folder);
59			// try {
60			// if (!is_dir($folder)) {
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `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...
61			// throw new \RuntimeException(sprintf('Unable to copy file as: %s ', $folder));
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `63%` 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...
62			// } else {
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `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...
63			// return copy($file, $folder);
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `64%` 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...
64			// }
65			// } catch (Exception $e) {
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `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...
66			// echo 'Caught exception: ', $e->getMessage(), "\n", "<br>";
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-09-02 13:58 UTC by Report Bug Copy Issue Report `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...
67			// }
68			// return false;
69			}
70
71			/**
72			* @param $src
73			* @param $dst
74			*/
75			public static function recurseCopy($src, $dst)
76			{
77			$dir = opendir($src);
78			// @mkdir($dst);
79			while (false !== ($file = readdir($dir))) {
80			if (($file !== '.') && ($file !== '..')) {
81			if (is_dir($src . '/' . $file)) {
82			self::recurseCopy($src . '/' . $file, $dst . '/' . $file);
83			} else {
84			copy($src . '/' . $file, $dst . '/' . $file);
85			}
86			}
87			}
88			closedir($dir);
89			}
90			}
91

mambax7 / wflinks

Push — master ( 2b2520...e78a73 )

WfLinksUtility::checkVerXoops() D

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like