Automattic /
jetpack
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
| 1 | <?php |
||
| 3889 | $from = isset( $_GET['from'] ) ? $_GET['from'] : false; |
||
| 3890 | |||
| 3891 | wp_redirect( $this->build_connect_url( true, false, $from ) ); |
||
| 3892 | exit; |
||
|
|
|||
| 3893 | case 'activate' : |
||
| 3894 | if ( ! current_user_can( 'jetpack_activate_modules' ) ) { |
||
| 3895 | $error = 'cheatin'; |
||
| 3902 | Jetpack::activate_module( $module ); |
||
| 3903 | // The following two lines will rarely happen, as Jetpack::activate_module normally exits at the end. |
||
| 3904 | wp_safe_redirect( Jetpack::admin_url( 'page=jetpack' ) ); |
||
| 3905 | exit; |
||
| 3906 | case 'activate_default_modules' : |
||
| 3907 | check_admin_referer( 'activate_default_modules' ); |
||
| 3908 | Jetpack::log( 'activate_default_modules' ); |
||
| 3923 | Jetpack::log( 'disconnect' ); |
||
| 3924 | Jetpack::disconnect(); |
||
| 3925 | wp_safe_redirect( Jetpack::admin_url( 'disconnected=true' ) ); |
||
| 3926 | exit; |
||
| 3927 | case 'reconnect' : |
||
| 3928 | if ( ! current_user_can( 'jetpack_reconnect' ) ) { |
||
| 3929 | $error = 'cheatin'; |
||
| 3950 | } |
||
| 3951 | Jetpack::state( 'module', $modules ); |
||
| 3952 | wp_safe_redirect( Jetpack::admin_url( 'page=jetpack' ) ); |
||
| 3953 | exit; |
||
| 3954 | case 'unlink' : |
||
| 3955 | $redirect = isset( $_GET['redirect'] ) ? $_GET['redirect'] : ''; |
||
| 3956 | check_admin_referer( 'jetpack-unlink' ); |
||
| 3962 | } else { |
||
| 3963 | wp_safe_redirect( Jetpack::admin_url( array( 'page' => $redirect ) ) ); |
||
| 3964 | } |
||
| 3965 | exit; |
||
| 3966 | default: |
||
| 3967 | /** |
||
| 3968 | * Fires when a Jetpack admin page is loaded with an unrecognized parameter. |
||
| 4049 | case 'token_http_request_failed' : |
||
| 4050 | $this->error = sprintf( __( 'Jetpack could not contact WordPress.com: %s. This usually means something is incorrectly configured on your web host.', 'jetpack' ), "<code>$error</code>" ); |
||
| 4051 | break; |
||
| 4052 | default : |
||
| 4053 | if ( empty( $error ) ) { |
||
| 4054 | break; |
||
| 4055 | } |
||
| 4129 | $titles[] = '<strong>' . preg_replace( '/\s+(?![^<>]++>)/', ' ', $mod_headers['name'] ) . '</strong>'; |
||
| 4130 | } |
||
| 4131 | } |
||
| 4132 | if ( $titles ) { |
||
| 4133 | $this->message .= '<br /><br />' . wp_sprintf( __( 'The following new modules have been activated: %l.', 'jetpack' ), $titles ); |
||
| 4134 | } |
||
| 4135 | } |
||
| 4141 | $titles[] = '<strong>' . preg_replace( '/\s+(?![^<>]++>)/', ' ', $mod_headers['name'] ) . '</strong>'; |
||
| 4142 | } |
||
| 4143 | } |
||
| 4144 | if ( $titles ) { |
||
| 4145 | $this->message .= '<br /><br />' . wp_sprintf( __( 'The following modules have been updated: %l.', 'jetpack' ), $titles ); |
||
| 4146 | } |
||
| 4147 | } |
||
| 7050 |
georgestephanis
Loading history...
An exit expression should only be used in rare cases. For example, if you write a short command line script.
In most cases however, using an
exitexpression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.