← All changes | includes/class-activator.php +0 -30 3.0.0 → 2.11.8 View file →

		@@ -106,11 +106,8 @@
106	106
107	107	// Schedule cron events
108	108	self::schedule_events();
109	109
110		- // Capture the self-integrity anchor (A3: manifest fingerprint in DB).
111		- self::anchor_self_integrity( $settings );
112		-
113	110	// Set activation transient for admin notice
114	111	set_transient( 'vigilante_activated', true, 30 );
115	112
116	113	// Store activation time
		@@ -123,35 +120,8 @@
123	120	flush_rewrite_rules();
124	121
125	122	// Clean any output that may have been generated
126	123	ob_end_clean();
127		- }
128		-
129		- /**
130		- * Anchor the self-integrity check on activation
131		- *
132		- * The first activation captures the fingerprint of the shipped manifest,
133		- * unless WordPress.org distributes something else for that version, so
134		- * the self-check has a baseline from the very first run. A
135		- * reactivation keeps the anchor it already has and checks against it:
136		- * capturing again adopted whatever manifest the folder held at that
137		- * moment, a regenerated one included, the same reason the critical files
138		- * baseline is not thrown away on reactivation.
139		- *
140		- * @since 3.0.0
141		- *
142		- * @param Vigilante_Settings $settings Settings instance.
143		- * @return void
144		- */
145		- public static function anchor_self_integrity( $settings ) {
146		- if ( ! class_exists( 'Vigilante_Self_Integrity' ) ) {
147		- require_once VIGILANTE_INCLUDES_DIR . 'class-self-integrity.php';
148		- }
149		- // run_check() captures on the first run itself, but only when
150		- // WordPress.org does not contradict the manifest; with an anchor already
151		- // there it checks against it.
152		- $self_integrity = new Vigilante_Self_Integrity( $settings );
153		- $self_integrity->run_check( 'activation' );
154	124	}
155	125
156	126	/**
157	127	* Idempotent migrations for existing installations.