acp_directory_info   A
last analyzed

Complexity

Total Complexity 3

Size/Duplication

Total Lines 26
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 0

Importance

Changes 2
Bugs 0 Features 0
Metric Value
c 2
b 0
f 0
dl 0
loc 26
rs 10
wmc 3
lcom 0
cbo 0

3 Methods

Rating   Name   Duplication   Size   Complexity  
A module() 0 15 1
A install() 0 3 1
A uninstall() 0 3 1
1
<?php
2
/**
3
*
4
* @author Erwan NADER (ErnadoO) [email protected]
5
* @package acp
6
* @version $Id$
7
* @copyright (c) 2008 http://www.phpbb-services.com
8
* @license http://opensource.org/licenses/gpl-license.php GNU Public License
9
*
10
*/
11
12
/**
13
* @package module_install
14
*/
15
class acp_directory_info
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...
16
{
17
    function module()
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
18
    {
19
        return array(
20
            'filename'		=> 'acp_directory',
21
            'title'			=> 'ACP_DIRECTORY',
22
            'version'		=> '1.0.1',
23
            'modes'			=> array(
24
            	''				=> array('title' => 'ACP_DIRECTORY',			'auth'	=> 'acl_a_board', 'cat' => array('')),
25
            	'main'			=> array('title' => 'ACP_DIRECTORY_MAIN',		'auth'	=> 'acl_a_board', 'cat' => array('ACP_DIRECTORY')),
26
				'settings'		=> array('title' => 'ACP_DIRECTORY_SETTINGS',	'auth'	=> 'acl_a_board', 'cat' => array('ACP_DIRECTORY')),
27
				'cat'			=> array('title' => 'ACP_DIRECTORY_CATS',		'auth'	=> 'acl_a_board', 'cat' => array('ACP_DIRECTORY')),
28
				'val'			=> array('title' => 'ACP_DIRECTORY_VAL',		'auth'	=> 'acl_a_board', 'cat' => array('ACP_DIRECTORY')),
29
            ),
30
        );
31
    }
32
33
    function install()
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
34
    {
35
    }
36
37
    function uninstall()
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
38
    {
39
    }
40
}