← All changes | _inc/lib/class-jetpack-ai-helper.php +113 -14 13.6.2 → 16.3-a.1 View file →

		@@ -11,8 +11,13 @@
11	11	use Automattic\Jetpack\Search\Plan as Search_Plan;
12	12	use Automattic\Jetpack\Status;
13	13	use Automattic\Jetpack\Status\Visitor;
14	14
	15	+// Required directly rather than relying on the plugin bootstrap: on
	16	+// WordPress.com Simple this helper is loaded outside load-jetpack.php
	17	+// (see the GUIDELINES_BANNER_DISMISSED_META_KEY note below).
	18	+require_once __DIR__ . '/class-jetpack-ai-settings.php';
	19	+
15	20	/**
16	21	* Class Jetpack_AI_Helper
17	22	*
18	23	* @since 11.8
		@@ -18,8 +23,23 @@
18	23	* @since 11.8
19	24	*/
20	25	class Jetpack_AI_Helper {
21	26	/**
	27	+ * User meta key storing whether the user dismissed the Content Guidelines
	28	+ * AI empty-state banner. Written by the guidelines-banner-dismissed REST
	29	+ * endpoint and read by the Content Guidelines admin-page preload.
	30	+ *
	31	+ * Lives here rather than on the endpoint class because on WordPress.com
	32	+ * Simple the wpcom-endpoints classes are only loaded in REST requests,
	33	+ * while the preload needs the key during admin page loads.
	34	+ *
	35	+ * @since 16.1
	36	+ *
	37	+ * @var string
	38	+ */
	39	+ const GUIDELINES_BANNER_DISMISSED_META_KEY = 'jetpack_content_guidelines_ai_banner_dismissed';
	40	+
	41	+ /**
22	42	* Allow new completion every X seconds. Will return cached result otherwise.
23	43	*
24	44	* @var int
25	45	*/
		@@ -32,15 +52,22 @@
32	52	*/
33	53	public static $image_generation_cache_timeout = MONTH_IN_SECONDS;
34	54
35	55	/**
36		- * Cache AI-assistant feature for ten seconds.
	56	+ * Cache AI-assistant feature for 60 seconds.
37	57	*
38	58	* @var int
39	59	*/
40		- public static $ai_assistant_feature_cache_timeout = 10;
	60	+ public static $ai_assistant_feature_cache_timeout = 60;
41	61
42	62	/**
	63	+ * Cache AI-assistant errors for ten seconds.
	64	+ *
	65	+ * @var int
	66	+ */
	67	+ public static $ai_assistant_feature_error_cache_timeout = 10;
	68	+
	69	+ /**
43	70	* Stores the number of JetpackAI calls in case we want to mark AI-assisted posts some way.
44	71	*
45	72	* @var int
46	73	*/
		@@ -46,8 +73,15 @@
46	73	*/
47	74	public static $post_meta_with_ai_generation_number = '_jetpack_ai_calls';
48	75
49	76	/**
	77	+ * Storing the error to prevent repeated requests to WPCOM after failure.
	78	+ *
	79	+ * @var null|WP_Error
	80	+ */
	81	+ private static $ai_assistant_failed_request = null;
	82	+
	83	+ /**
50	84	* Checks if a given request is allowed to get AI data from WordPress.com.
51	85	*
52	86	* @param WP_REST_Request $request Full details about the request.
53	87	*
		@@ -83,19 +117,55 @@
83	117	} elseif ( ( new Automattic\Jetpack\Status\Host() )->is_woa_site() ) {
84	118	$default = true;
85	119	}
86	120
87		- /**
88		- * Filter whether the AI features are enabled in the Jetpack plugin.
89		- *
90		- * @since 11.8
91		- *
92		- * @param bool $default Are AI features enabled? Defaults to false.
93		- */
94		- return apply_filters( 'jetpack_ai_enabled', $default );
	121	+ // The jetpack_ai_enabled filter runs inside the helper; the host and
	122	+ // master gates apply after the chain and cannot be filtered back on.
	123	+ return Jetpack_AI_Settings::is_ai_enabled( $default );
95	124	}
96	125
97	126	/**
	127	+ * Return true if the Content Guidelines AI surfaces should be active on the
	128	+ * current site.
	129	+ *
	130	+ * Same platforms as is_enabled() (WPCOM Simple and Atomic), plus WordPress
	131	+ * VIP sites. Kept separate from is_enabled() so widening Content Guidelines
	132	+ * to VIP does not also open the general AI proxy endpoint there.
	133	+ *
	134	+ * @since 16.2
	135	+ *
	136	+ * @return bool
	137	+ */
	138	+ public static function is_enabled_for_content_guidelines() {
	139	+ $default = false;
	140	+
	141	+ if ( defined( 'IS_WPCOM' ) && IS_WPCOM ) {
	142	+ $default = true;
	143	+ } else {
	144	+ $host = new Automattic\Jetpack\Status\Host();
	145	+ if ( $host->is_woa_site() || $host->is_vip_site() ) {
	146	+ $default = true;
	147	+ }
	148	+ }
	149	+
	150	+ // The jetpack_ai_enabled filter runs inside the helper; the host and
	151	+ // master gates apply after the chain and cannot be filtered back on.
	152	+ return Jetpack_AI_Settings::is_ai_enabled( $default );
	153	+ }
	154	+
	155	+ /**
	156	+ * Whether the current user has dismissed the Content Guidelines AI
	157	+ * empty-state banner.
	158	+ *
	159	+ * @since 16.1
	160	+ *
	161	+ * @return bool
	162	+ */
	163	+ public static function is_guidelines_banner_dismissed() {
	164	+ return (bool) get_user_meta( get_current_user_id(), self::GUIDELINES_BANNER_DISMISSED_META_KEY, true );
	165	+ }
	166	+
	167	+ /**
98	168	* Return true if the AI chat feature should be active on the current site.
99	169	*
100	170	* @todo IS_WPCOM (the endpoints need to be updated too).
101	171	*
		@@ -249,9 +319,10 @@
249	319	),
250	320	wp_json_encode(
251	321	array(
252	322	'content' => $content,
253		- )
	323	+ ),
	324	+ JSON_UNESCAPED_SLASHES
254	325	),
255	326	'wpcom'
256	327	);
257	328
		@@ -323,9 +394,10 @@
323	394	),
324	395	wp_json_encode(
325	396	array(
326	397	'prompt' => $prompt,
327		- )
	398	+ ),
	399	+ JSON_UNESCAPED_SLASHES
328	400	),
329	401	'wpcom'
330	402	);
331	403
		@@ -365,8 +437,19 @@
365	437	);
366	438	}
367	439	}
368	440
	441	+ if ( ! class_exists( 'WPCOM\Jetpack_AI\Feature_Control' ) ) {
	442	+ if ( is_readable( WP_CONTENT_DIR . '/lib/jetpack-ai/feature-control.php' ) ) {
	443	+ require_once WP_CONTENT_DIR . '/lib/jetpack-ai/feature-control.php';
	444	+ } else {
	445	+ return new WP_Error(
	446	+ 'jetpack_ai_feature_control_not_found',
	447	+ __( 'WPCOM\Jetpack_AI\Feature_Control class not found.', 'jetpack' )
	448	+ );
	449	+ }
	450	+ }
	451	+
369	452	// Determine the upgrade type
370	453	$upgrade_type = wpcom_is_vip( $blog_id ) ? 'vip' : 'default';
371	454
372	455	return array(
		@@ -382,8 +465,9 @@
382	465	'next-tier' => WPCOM\Jetpack_AI\Usage\Helper::get_next_tier( $blog_id ),
383	466	'tier-plans' => WPCOM\Jetpack_AI\Usage\Helper::get_tier_plans_list(),
384	467	'tier-plans-enabled' => WPCOM\Jetpack_AI\Usage\Helper::ai_tier_plans_enabled(),
385	468	'costs' => WPCOM\Jetpack_AI\Usage\Helper::get_costs(),
	469	+ 'features-control' => WPCOM\Jetpack_AI\Feature_Control::get_features(),
386	470	);
387	471	}
388	472
389	473	// Outside of WPCOM, we need to fetch the data from the site.
		@@ -395,8 +479,12 @@
395	479	if ( $cache ) {
396	480	return $cache;
397	481	}
398	482
	483	+ if ( null !== static::$ai_assistant_failed_request ) {
	484	+ return static::$ai_assistant_failed_request;
	485	+ }
	486	+
399	487	$request_path = sprintf( '/sites/%d/jetpack-ai/ai-assistant-feature', $blog_id );
400	488
401	489	$wpcom_request = Client::wpcom_json_api_request_as_user(
402	490	$request_path,
		@@ -405,8 +493,9 @@
405	493	'method' => 'GET',
406	494	'headers' => array(
407	495	'X-Forwarded-For' => ( new Visitor() )->get_ip( true ),
408	496	),
	497	+ 'timeout' => 30,
409	498	),
410	499	null,
411	500	'wpcom'
412	501	);
		@@ -419,12 +508,22 @@
419	508	set_transient( $transient_name, $ai_assistant_feature_data, self::$ai_assistant_feature_cache_timeout );
420	509
421	510	return $ai_assistant_feature_data;
422	511	} else {
423		- return new WP_Error(
	512	+ $error = new WP_Error(
424	513	'failed_to_fetch_data',
425	514	esc_html__( 'Unable to fetch the requested data.', 'jetpack' ),
426		- array( 'status' => $response_code )
	515	+ array(
	516	+ 'status' => $response_code,
	517	+ 'ts' => time(),
	518	+ )
427	519	);
	520	+
	521	+ // Cache the AI Assistant feature error, for Jetpack sites, avoid API hammering.
	522	+ set_transient( $transient_name, $error, self::$ai_assistant_feature_error_cache_timeout );
	523	+
	524	+ static::$ai_assistant_failed_request = $error;
	525	+
	526	+ return $error;
428	527	}
429	528	}
430	529	}