Completed
Push — fix/rest-api-url ( adfe79 )
by
unknown
33:25 queued 22:38
created

jetpack.php ➔ jetpack_index_permalinks_rest_api_url()   A

Complexity

Conditions 3
Paths 2

Size

Total Lines 8
Code Lines 5

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 3
eloc 5
nc 2
nop 1
dl 0
loc 8
rs 9.4285
c 0
b 0
f 0
1
<?php
2
3
/*
4
 * Plugin Name: Jetpack by WordPress.com
5
 * Plugin URI: http://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: 4.3.2
9
 * Author URI: http://jetpack.com
10
 * License: GPL2+
11
 * Text Domain: jetpack
12
 * Domain Path: /languages/
13
 */
14
15
define( 'JETPACK__MINIMUM_WP_VERSION', '4.5' );
16
17
define( 'JETPACK__VERSION',            '4.3.2' );
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
add_filter( 'rest_url_prefix', 'jetpack_index_permalinks_rest_api_url', 999 );
31
/**
32
 * Fix the REST API URL for sites using index permalinks
33
 *
34
 * @todo Remove when 4.7 is minimum version
0 ignored issues
show
Coding Style introduced by
Comment refers to a TODO task

This check looks TODO comments that have been left in the code.

``TODO``s show that something is left unfinished and should be attended to.

Loading history...
35
 * @see  https://core.trac.wordpress.org/ticket/38182
36
 * @see  https://github.com/Automattic/jetpack/issues/5216
37
 * @author kraftbj
38
 **/
39
function jetpack_index_permalinks_rest_api_url( $prefix ){
40
	global $wp_rewrite, $wp_version;
41
	if ( version_compare( $wp_version, '4.7-alpha-38790', '>=' ) && $wp_rewrite->using_index_permalinks() ){
42
		$prefix = $wp_rewrite->index . '/' . $prefix;
43
	}
44
45
	return $prefix;
46
}
47
48
/**
49
 * Returns the location of Jetpack's lib directory. This filter is applied
50
 * in require_lib().
51
 *
52
 * @since 4.0.2
53
 *
54
 * @return string Location of Jetpack library directory.
55
 *
56
 * @filter require_lib_dir
57
 */
58
function jetpack_require_lib_dir() {
59
	return JETPACK__PLUGIN_DIR . '_inc/lib';
60
}
61
add_filter( 'jetpack_require_lib_dir', 'jetpack_require_lib_dir' );
62
63
// @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...
64
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack.php'               );
65
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-network.php'       );
66
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-client.php'        );
67
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-data.php'          );
68
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-client-server.php' );
69
require_once( JETPACK__PLUGIN_DIR . 'sync/class.jetpack-sync-actions.php' );
70
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-options.php'       );
71
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-user-agent.php'    );
72
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-post-images.php'   );
73
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-error.php'         );
74
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-heartbeat.php'     );
75
require_once( JETPACK__PLUGIN_DIR . 'class.photon.php'                );
76
require_once( JETPACK__PLUGIN_DIR . 'functions.photon.php'            );
77
require_once( JETPACK__PLUGIN_DIR . 'functions.global.php'            );
78
require_once( JETPACK__PLUGIN_DIR . 'functions.compat.php'            );
79
require_once( JETPACK__PLUGIN_DIR . 'functions.gallery.php'           );
80
require_once( JETPACK__PLUGIN_DIR . 'require-lib.php'                 );
81
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-autoupdate.php'    );
82
require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-tracks.php'        );
83
require_once( JETPACK__PLUGIN_DIR . 'class.frame-nonce-preview.php'   );
84
require_once( JETPACK__PLUGIN_DIR . 'modules/module-headings.php');
85
86
if ( is_admin() ) {
87
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-admin.php'     );
88
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-jitm.php'      );
89
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-debugger.php'  );
90
}
91
92
// Play nice with http://wp-cli.org/
93
if ( defined( 'WP_CLI' ) && WP_CLI ) {
94
	require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-cli.php'       );
95
}
96
97
require_once( JETPACK__PLUGIN_DIR . '_inc/lib/class.core-rest-api-endpoints.php' );
98
99
register_activation_hook( __FILE__, array( 'Jetpack', 'plugin_activation' ) );
100
register_deactivation_hook( __FILE__, array( 'Jetpack', 'plugin_deactivation' ) );
101
add_action( 'updating_jetpack_version', array( 'Jetpack', 'do_version_bump' ), 10, 2 );
102
add_action( 'init', array( 'Jetpack', 'init' ) );
103
add_action( 'plugins_loaded', array( 'Jetpack', 'plugin_textdomain' ), 99 );
104
add_action( 'plugins_loaded', array( 'Jetpack', 'load_modules' ), 100 );
105
add_filter( 'jetpack_static_url', array( 'Jetpack', 'staticize_subdomain' ) );
106
add_filter( 'is_jetpack_site', '__return_true' );
107
108
/**
109
 * Add an easy way to photon-ize a URL that is safe to call even if Jetpack isn't active.
110
 *
111
 * See: http://jetpack.com/2013/07/11/photon-and-themes/
112
 */
113
if ( Jetpack::is_module_active( 'photon' ) ) {
114
	add_filter( 'jetpack_photon_url', 'jetpack_photon_url', 10, 3 );
115
}
116
117
/*
118
if ( is_admin() && ! Jetpack::check_identity_crisis() ) {
119
	Jetpack_Sync::sync_options( __FILE__, 'db_version', 'jetpack_active_modules', 'active_plugins' );
120
}
121
*/
122
123
require_once( JETPACK__PLUGIN_DIR . '3rd-party/3rd-party.php' );
124
125
Jetpack::init();
126