Completed
Push — sync/dbtlr/r159298-wpcom-15003... ( bc0eb2...c27aa0 )
by
unknown
12:20
created

jetpack.php ➔ jetpack_index_permalinks_rest_api_url()   B

Complexity

Conditions 6
Paths 2

Size

Total Lines 11
Code Lines 8

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 6
eloc 8
nc 2
nop 1
dl 0
loc 11
rs 8.8571
c 0
b 0
f 0
1
<?php
2
3
/*
4
 * Plugin Name: Jetpack by WordPress.com
5
 * Plugin URI: https://jetpack.com
6
 * Description: Bring the power of the WordPress.com cloud to your self-hosted WordPress. Jetpack enables you to connect your blog to a WordPress.com account to use the powerful features normally only available to WordPress.com users.
7
 * Author: Automattic
8
 * Version: 5.2-alpha
9
 * Author URI: https://jetpack.com
10
 * License: GPL2+
11
 * Text Domain: jetpack
12
 * Domain Path: /languages/
13
 */
14
15
define( 'JETPACK__MINIMUM_WP_VERSION', '4.7' );
16
17
define( 'JETPACK__VERSION',            '5.2-alpha' );
18
define( 'JETPACK_MASTER_USER',         true );
19
define( 'JETPACK__API_VERSION',        1 );
20
define( 'JETPACK__PLUGIN_DIR',         plugin_dir_path( __FILE__ ) );
21
define( 'JETPACK__PLUGIN_FILE',        __FILE__ );
22
23
defined( 'JETPACK_CLIENT__AUTH_LOCATION' )   or define( 'JETPACK_CLIENT__AUTH_LOCATION', 'header' );
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as or instead of || is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
24
defined( 'JETPACK_CLIENT__HTTPS' )           or define( 'JETPACK_CLIENT__HTTPS', 'AUTO' );
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as or instead of || is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
25
defined( 'JETPACK__GLOTPRESS_LOCALES_PATH' ) or define( 'JETPACK__GLOTPRESS_LOCALES_PATH', JETPACK__PLUGIN_DIR . 'locales.php' );
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as or instead of || is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
26
defined( 'JETPACK__API_BASE' )               or define( 'JETPACK__API_BASE', 'https://jetpack.wordpress.com/jetpack.' );
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as or instead of || is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
27
defined( 'JETPACK_PROTECT__API_HOST' )       or define( 'JETPACK_PROTECT__API_HOST', 'https://api.bruteprotect.com/' );
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as or instead of || is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
28
defined( 'JETPACK__WPCOM_JSON_API_HOST' )    or define( 'JETPACK__WPCOM_JSON_API_HOST', 'public-api.wordpress.com' );
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as or instead of || is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
29
30
/**
31
 * Returns the location of Jetpack's lib directory. This filter is applied
32
 * in require_lib().
33
 *
34
 * @since 4.0.2
35
 *
36
 * @return string Location of Jetpack library directory.
37
 *
38
 * @filter require_lib_dir
39
 */
40
function jetpack_require_lib_dir() {
41
	return JETPACK__PLUGIN_DIR . '_inc/lib';
42
}
43
add_filter( 'jetpack_require_lib_dir', 'jetpack_require_lib_dir' );
44
45
// @todo: Abstract out the admin functions, and only include them if is_admin()
0 ignored issues
show
Coding Style Best Practice introduced by
Comments for TODO tasks are often forgotten in the code; it might be better to use a dedicated issue tracker.
Loading history...
46
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack.php'               );
47
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-network.php'       );
48
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-client.php'        );
49
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-data.php'          );
50
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-client-server.php' );
51
require_once( JETPACK__PLUGIN_DIR . 'sync/class.jetpack-sync-actions.php' );
52
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-options.php'       );
53
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-user-agent.php'    );
54
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-post-images.php'   );
55
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-error.php'         );
56
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-heartbeat.php'     );
57
require_once( JETPACK__PLUGIN_DIR . 'class.photon.php'                );
58
require_once( JETPACK__PLUGIN_DIR . 'functions.photon.php'            );
59
require_once( JETPACK__PLUGIN_DIR . 'functions.global.php'            );
60
require_once( JETPACK__PLUGIN_DIR . 'functions.compat.php'            );
61
require_once( JETPACK__PLUGIN_DIR . 'functions.gallery.php'           );
62
require_once( JETPACK__PLUGIN_DIR . 'require-lib.php'                 );
63
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-autoupdate.php'    );
64
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-tracks.php'        );
65
require_once( JETPACK__PLUGIN_DIR . 'class.frame-nonce-preview.php'   );
66
require_once( JETPACK__PLUGIN_DIR . 'modules/module-headings.php');
67
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-constants.php');
68
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-idc.php'  );
69
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-connection-banner.php'  );
70
71
if ( is_admin() ) {
72
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-admin.php'     );
73
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-jitm.php'      );
74
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-debugger.php'  );
75
}
76
77
// Play nice with http://wp-cli.org/
78
if ( defined( 'WP_CLI' ) && WP_CLI ) {
79
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-cli.php'       );
80
}
81
82
require_once( JETPACK__PLUGIN_DIR . '_inc/lib/class.core-rest-api-endpoints.php' );
83
84
register_activation_hook( __FILE__, array( 'Jetpack', 'plugin_activation' ) );
85
register_deactivation_hook( __FILE__, array( 'Jetpack', 'plugin_deactivation' ) );
86
add_action( 'updating_jetpack_version', array( 'Jetpack', 'do_version_bump' ), 10, 2 );
87
add_action( 'init', array( 'Jetpack', 'init' ) );
88
add_action( 'plugins_loaded', array( 'Jetpack', 'plugin_textdomain' ), 99 );
89
add_action( 'plugins_loaded', array( 'Jetpack', 'load_modules' ), 100 );
90
add_filter( 'jetpack_static_url', array( 'Jetpack', 'staticize_subdomain' ) );
91
add_filter( 'is_jetpack_site', '__return_true' );
92
93
/**
94
 * Add an easy way to photon-ize a URL that is safe to call even if Jetpack isn't active.
95
 *
96
 * See: http://jetpack.com/2013/07/11/photon-and-themes/
97
 */
98
if ( Jetpack::is_module_active( 'photon' ) ) {
99
	add_filter( 'jetpack_photon_url', 'jetpack_photon_url', 10, 3 );
100
}
101
102
require_once( JETPACK__PLUGIN_DIR . '3rd-party/3rd-party.php' );
103
104
Jetpack::init();
105