GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Completed
Push — develop ( 4c5076...267df3 )
by Brad
04:54 queued 02:32
created

FooGallery_Cache::disable_html_cache()   A

Complexity

Conditions 2
Paths 2

Size

Total Lines 9
Code Lines 4

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 2
eloc 4
nc 2
nop 2
dl 0
loc 9
rs 9.6666
c 0
b 0
f 0
1
<?php
2
/**
3
 * Class used to cache gallery HTML output to save requests to the database
4
 * Date: 20/03/2017
5
 */
6
if ( ! class_exists( 'FooGallery_Cache' ) ) {
7
8
	class FooGallery_Cache {
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...
9
10
		function __construct() {
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...
11
			if ( is_admin() ) {
12
				//intercept the gallery save and save the html output to post meta
13
				add_action( 'foogallery_after_save_gallery', array( $this, 'cache_gallery_html_output_after_save' ), 10, 2 );
14
15
				//add some settings to allow the clearing and disabling of the cache
16
				add_filter( 'foogallery_admin_settings_override', array( $this, 'add_cache_settings' ) );
17
18
				//render the clear HTML cache button
19
				add_action( 'foogallery_admin_settings_custom_type_render_setting', array( $this, 'render_settings' ) );
20
21
				// Ajax call for clearing HTML cache
22
				add_action( 'wp_ajax_foogallery_clear_html_cache', array( $this, 'ajax_clear_all_caches' ) );
23
24
				add_action( 'foogallery_admin_new_version_detected', array( $this, 'clear_cache_on_update' ) );
25
			}
26
27
			add_filter( 'foogallery_load_gallery_template', array( $this, 'fetch_gallery_html_from_cache' ), 10, 3 );
28
29
			add_filter( 'foogallery_html_cache_disabled', array( $this, 'disable_html_cache' ), 10, 3 );
30
		}
31
32
		/**
33
		 * Override if the gallery html cache is disabled
34
		 *
35
		 * @param $disabled bool
36
		 * @param $gallery FooGallery
37
		 * @return bool
38
		 */
39
		function disable_html_cache( $disabled, $gallery ) {
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...
40
41
			//check if the gallery sorting is random
42
			if ( 'rand' === $gallery->sorting ) {
43
				$disabled = true;
44
			}
45
46
			return $disabled;
47
		}
48
49
		/**
50
		 * Save the HTML output of the gallery after the gallery has been saved
51
		 *
52
		 * @param $post_id
53
		 * @param $form_post
54
		 */
55
		function cache_gallery_html_output_after_save( $post_id, $form_post ) {
0 ignored issues
show
Unused Code introduced by
The parameter $form_post is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
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...
56
			$this->cache_gallery_html_output( $post_id );
57
		}
58
59
		/**
60
		 * Save the HTML output of the gallery to post meta so that it can be used in future requests
61
		 *
62
		 * @param $foogallery_id
63
		 */
64
		function cache_gallery_html_output( $foogallery_id ) {
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...
65
			//check if caching is disabled and quit early
66
			if ( 'on' === foogallery_get_setting( 'disable_html_cache' ) ) {
67
				return;
68
			}
69
70
			//we need a way to force the gallery to render it's output every time it is saved
71
			global $foogallery_force_gallery_cache;
0 ignored issues
show
Compatibility Best Practice introduced by
Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

Instead of relying on global state, we recommend one of these alternatives:

1. Pass all data via parameters

function myFunction($a, $b) {
    // Do something
}

2. Create a class that maintains your state

class MyClass {
    private $a;
    private $b;

    public function __construct($a, $b) {
        $this->a = $a;
        $this->b = $b;
    }

    public function myFunction() {
        // Do something
    }
}
Loading history...
72
			$foogallery_force_gallery_cache = true;
73
74
			//capture the html output
75
			ob_start();
76
			foogallery_render_gallery( $foogallery_id );
77
			$gallery_html = ob_get_contents();
78
			ob_end_clean();
79
80
			//save the output to post meta for later use
81
			update_post_meta( $foogallery_id, FOOGALLERY_META_CACHE, $gallery_html );
82
83
			$foogallery_force_gallery_cache = false;
84
		}
85
86
		/**
87
		 * Override the template output
88
		 *
89
		 * @param $override
90
		 * @param $gallery
91
		 * @param $template_location
92
		 *
93
		 * @return bool
94
		 */
95
		function fetch_gallery_html_from_cache( $override, $gallery, $template_location ) {
0 ignored issues
show
Unused Code introduced by
The parameter $template_location is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
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...
96
			global $foogallery_force_gallery_cache;
0 ignored issues
show
Compatibility Best Practice introduced by
Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

Instead of relying on global state, we recommend one of these alternatives:

1. Pass all data via parameters

function myFunction($a, $b) {
    // Do something
}

2. Create a class that maintains your state

class MyClass {
    private $a;
    private $b;

    public function __construct($a, $b) {
        $this->a = $a;
        $this->b = $b;
    }

    public function myFunction() {
        // Do something
    }
}
Loading history...
97
			if ( $foogallery_force_gallery_cache ) {
98
				return false;
99
			}
100
101
			//check if caching is disabled and quit early
102
			if ( 'on' === foogallery_get_setting( 'disable_html_cache' ) ) {
103
				return false;
104
			}
105
106
			//allow extensions of others disable the html cache
107
			if ( apply_filters( 'foogallery_html_cache_disabled', false, $gallery ) ) {
108
				return false;
109
			}
110
111
			$gallery_cache = get_post_meta( $gallery->ID, FOOGALLERY_META_CACHE, true );
112
113
			if ( !empty( $gallery_cache ) && is_string( $gallery_cache ) ) {
114
				//output the cached gallery html
115
				echo $gallery_cache;
116
				return true; //return that we will override
117
			} else {
118
				//we should cache the result for next time
119
				$this->cache_gallery_html_output( $gallery->ID );
120
			}
121
122
			return false;
123
		}
124
125
		/**
126
		 * Add some caching settings
127
		 * @param $settings
128
		 *
129
		 * @return array
130
		 */
131
		function add_cache_settings( $settings ) {
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...
132
133
			$cache_settings[] = array(
0 ignored issues
show
Coding Style Comprehensibility introduced by
$cache_settings was never initialized. Although not strictly required by PHP, it is generally a good practice to add $cache_settings = array(); before regardless.

Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code.

Let’s take a look at an example:

foreach ($collection as $item) {
    $myArray['foo'] = $item->getFoo();

    if ($item->hasBar()) {
        $myArray['bar'] = $item->getBar();
    }

    // do something with $myArray
}

As you can see in this example, the array $myArray is initialized the first time when the foreach loop is entered. You can also see that the value of the bar key is only written conditionally; thus, its value might result from a previous iteration.

This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization $myArray = array() either outside or inside the foreach loop.

Loading history...
134
				'id'      => 'disable_html_cache',
135
				'title'   => __( 'Disable HTML Cache', 'foogallery' ),
136
				'desc'    => __( 'The gallery HTML is cached by default. You can choose to disable the cache for debugging purposes. It is NOT recommended.', 'foogallery' ),
137
				'type'    => 'checkbox',
138
				'tab'     => 'general',
139
				'section' => __( 'Cache', 'foogallery' )
140
			);
141
142
			$cache_settings[] = array(
143
				'id'      => 'clear_html_cache',
144
				'title'   => __( 'Clear HTML Cache', 'foogallery' ),
145
				'desc'    => sprintf( __( '%s caches the gallery HTML output to improve page performance. Use this button to clear the gallery HTML that has been cached across all galleries.', 'foogallery' ), foogallery_plugin_name() ),
146
				'type'    => 'clear_gallery_cache_button',
147
				'tab'     => 'general',
148
				'section' => __( 'Cache', 'foogallery' )
149
			);
150
151
			$new_settings = array_merge( $cache_settings, $settings['settings'] );
152
153
			$settings['settings'] = $new_settings;
154
155
			return $settings;
156
		}
157
158
		/**
159
		 * Render any custom setting types to the settings page
160
		 */
161
		function render_settings( $args ) {
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...
162
			if ('clear_gallery_cache_button' === $args['type'] ) { ?>
163
				<div id="foogallery_clear_html_cache_container">
164
					<input type="button" data-nonce="<?php echo esc_attr( wp_create_nonce( 'foogallery_clear_html_cache' ) ); ?>" class="button-primary foogallery_clear_html_cache" value="<?php _e( 'Clear Gallery HTML Cache', 'foogallery' ); ?>">
165
					<span id="foogallery_clear_html_cache_spinner" style="position: absolute" class="spinner"></span>
166
				</div>
167
			<?php }
168
		}
169
170
		/**
171
		 * AJAX endpoint for clearing all gallery caches
172
		 */
173
		function ajax_clear_all_caches() {
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...
174
			if ( check_admin_referer( 'foogallery_clear_html_cache' ) ) {
175
176
				$this->clear_all_gallery_caches();
177
178
				_e('The cache for all galleries has been cleared!', 'foogallery' );
179
				die();
180
			}
181
		}
182
183
		/**
184
		 * Clears all caches for all galleries
185
		 */
186
		function clear_all_gallery_caches() {
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...
187
			delete_post_meta_by_key( FOOGALLERY_META_CACHE );
188
		}
189
190
		/**
191
		 * Clear all caches when the plugin has been updated. This is to account for changes in the HTML when a new version is released.
192
		 */
193
		function clear_cache_on_update() {
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...
194
			$this->clear_all_gallery_caches();
195
		}
196
	}
197
}