These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
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: 6.5-beta |
|||||||||||
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', '6.5-beta' ); |
|||||||||||
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
|
||||||||||||
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):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like 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-FlowOne 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 // 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. ![]() |
||||||||||||
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):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like 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-FlowOne 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 // 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. ![]() |
||||||||||||
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):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like 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-FlowOne 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 // 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. ![]() |
||||||||||||
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):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like 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-FlowOne 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 // 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. ![]() |
||||||||||||
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):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like 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-FlowOne 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 // 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. ![]() |
||||||||||||
29 | ||||||||||||
30 | defined( 'JETPACK__SANDBOX_DOMAIN' ) or define( 'JETPACK__SANDBOX_DOMAIN', '' ); |
|||||||||||
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):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like 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-FlowOne 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 // 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. ![]() |
||||||||||||
31 | ||||||||||||
32 | /** |
|||||||||||
33 | * Returns the location of Jetpack's lib directory. This filter is applied |
|||||||||||
34 | * in require_lib(). |
|||||||||||
35 | * |
|||||||||||
36 | * @since 4.0.2 |
|||||||||||
37 | * |
|||||||||||
38 | * @return string Location of Jetpack library directory. |
|||||||||||
39 | * |
|||||||||||
40 | * @filter require_lib_dir |
|||||||||||
41 | */ |
|||||||||||
42 | function jetpack_require_lib_dir() { |
|||||||||||
43 | return JETPACK__PLUGIN_DIR . '_inc/lib'; |
|||||||||||
44 | } |
|||||||||||
45 | add_filter( 'jetpack_require_lib_dir', 'jetpack_require_lib_dir' ); |
|||||||||||
46 | ||||||||||||
47 | /** |
|||||||||||
48 | * Checks if the code debug mode turned on, and returns false if it is. When Jetpack is in |
|||||||||||
49 | * code debug mode, it shouldn't use minified assets. Note that this filter is not being used |
|||||||||||
50 | * in every place where assets are enqueued. The filter is added at priority 9 to be overridden |
|||||||||||
51 | * by any default priority filter that runs after it. |
|||||||||||
52 | * |
|||||||||||
53 | * @since 6.2.0 |
|||||||||||
54 | * |
|||||||||||
55 | * @return boolean |
|||||||||||
56 | * |
|||||||||||
57 | * @filter jetpack_should_use_minified_assets |
|||||||||||
58 | */ |
|||||||||||
59 | function jetpack_should_use_minified_assets() { |
|||||||||||
60 | if ( defined( 'SCRIPT_DEBUG' ) && SCRIPT_DEBUG ) { |
|||||||||||
61 | return false; |
|||||||||||
62 | } |
|||||||||||
63 | return true; |
|||||||||||
64 | } |
|||||||||||
65 | add_filter( 'jetpack_should_use_minified_assets', 'jetpack_should_use_minified_assets', 9 ); |
|||||||||||
66 | ||||||||||||
67 | // @todo: Abstract out the admin functions, and only include them if is_admin() |
|||||||||||
0 ignored issues
–
show
|
||||||||||||
68 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack.php' ); |
|||||||||||
69 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-network.php' ); |
|||||||||||
70 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-client.php' ); |
|||||||||||
71 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-data.php' ); |
|||||||||||
72 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-client-server.php' ); |
|||||||||||
73 | require_once( JETPACK__PLUGIN_DIR . 'sync/class.jetpack-sync-actions.php' ); |
|||||||||||
74 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-options.php' ); |
|||||||||||
75 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-user-agent.php' ); |
|||||||||||
76 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-post-images.php' ); |
|||||||||||
77 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-error.php' ); |
|||||||||||
78 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-heartbeat.php' ); |
|||||||||||
79 | require_once( JETPACK__PLUGIN_DIR . 'class.photon.php' ); |
|||||||||||
80 | require_once( JETPACK__PLUGIN_DIR . 'functions.photon.php' ); |
|||||||||||
81 | require_once( JETPACK__PLUGIN_DIR . 'functions.global.php' ); |
|||||||||||
82 | require_once( JETPACK__PLUGIN_DIR . 'functions.compat.php' ); |
|||||||||||
83 | require_once( JETPACK__PLUGIN_DIR . 'functions.gallery.php' ); |
|||||||||||
84 | require_once( JETPACK__PLUGIN_DIR . 'require-lib.php' ); |
|||||||||||
85 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-autoupdate.php' ); |
|||||||||||
86 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-tracks.php' ); |
|||||||||||
87 | require_once( JETPACK__PLUGIN_DIR . 'class.frame-nonce-preview.php' ); |
|||||||||||
88 | require_once( JETPACK__PLUGIN_DIR . 'modules/module-headings.php'); |
|||||||||||
89 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-constants.php'); |
|||||||||||
90 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-idc.php' ); |
|||||||||||
91 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-connection-banner.php' ); |
|||||||||||
92 | ||||||||||||
93 | if ( is_admin() ) { |
|||||||||||
94 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-admin.php' ); |
|||||||||||
95 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-jitm.php' ); |
|||||||||||
96 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-debugger.php' ); |
|||||||||||
97 | } |
|||||||||||
98 | ||||||||||||
99 | // Play nice with http://wp-cli.org/ |
|||||||||||
100 | if ( defined( 'WP_CLI' ) && WP_CLI ) { |
|||||||||||
101 | require_once( JETPACK__PLUGIN_DIR . 'class.jetpack-cli.php' ); |
|||||||||||
102 | } |
|||||||||||
103 | ||||||||||||
104 | require_once( JETPACK__PLUGIN_DIR . '_inc/lib/class.core-rest-api-endpoints.php' ); |
|||||||||||
105 | ||||||||||||
106 | register_activation_hook( __FILE__, array( 'Jetpack', 'plugin_activation' ) ); |
|||||||||||
107 | register_deactivation_hook( __FILE__, array( 'Jetpack', 'plugin_deactivation' ) ); |
|||||||||||
108 | add_action( 'updating_jetpack_version', array( 'Jetpack', 'do_version_bump' ), 10, 2 ); |
|||||||||||
109 | add_action( 'init', array( 'Jetpack', 'init' ) ); |
|||||||||||
110 | add_action( 'plugins_loaded', array( 'Jetpack', 'plugin_textdomain' ), 99 ); |
|||||||||||
111 | add_action( 'plugins_loaded', array( 'Jetpack', 'load_modules' ), 100 ); |
|||||||||||
112 | add_filter( 'jetpack_static_url', array( 'Jetpack', 'staticize_subdomain' ) ); |
|||||||||||
113 | add_filter( 'is_jetpack_site', '__return_true' ); |
|||||||||||
114 | ||||||||||||
115 | /** |
|||||||||||
116 | * Add an easy way to photon-ize a URL that is safe to call even if Jetpack isn't active. |
|||||||||||
117 | * |
|||||||||||
118 | * See: http://jetpack.com/2013/07/11/photon-and-themes/ |
|||||||||||
119 | */ |
|||||||||||
120 | if ( Jetpack::is_module_active( 'photon' ) ) { |
|||||||||||
121 | add_filter( 'jetpack_photon_url', 'jetpack_photon_url', 10, 3 ); |
|||||||||||
122 | } |
|||||||||||
123 | ||||||||||||
124 | if ( JETPACK__SANDBOX_DOMAIN ) { |
|||||||||||
125 | require_once( JETPACK__PLUGIN_DIR . '_inc/jetpack-server-sandbox.php' ); |
|||||||||||
126 | } |
|||||||||||
127 | ||||||||||||
128 | require_once( JETPACK__PLUGIN_DIR . '3rd-party/3rd-party.php' ); |
|||||||||||
129 | ||||||||||||
130 | Jetpack::init(); |
|||||||||||
131 |
PHP has two types of connecting operators (logical operators, and boolean operators):
and
&&
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 are used for Control-Flow
One case where you explicitly want to use logical operators is for control-flow such as this:
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 withthrow
at this point:These limitations lead to logical operators rarely being of use in current PHP code.