src/content-helper/dashboard-page/pages/traffic-boost/preview/components/preview-iframe.tsx (1)

89-94: Avoid hard-coding the UUID in JS; source it from PHP and fix comment/doc.

• Use a single source of truth: expose the UUID from PHP (localized/inline script) and read it here to prevent drift with wp-parsely.php.
• The nearby JSDoc still says “random UUID”; update it to “predefined UUID.”
• Add a period to the first inline comment to satisfy the guideline.

Apply within this range:

-		// Needs to match the UUID in create_engagement_boost_changeset_post()
+		// Needs to match the UUID in create_engagement_boost_changeset_post().
 		// in wp-parsely.php.
-		const uuid = '905b130b-4129-4416-919c-9e31433a6f65';
+		const uuid =
+			// Prefer server-provided value to avoid drift with PHP.
+			((window as any)?.wpParsely?.engagementBoostChangesetUuid as string) ??
+			'905b130b-4129-4416-919c-9e31433a6f65';
 		const url = new URL( previewUrl );
 		url.searchParams.set( 'customize_changeset_uuid', uuid );

Outside this range, update the JSDoc above iFrameSrc to reflect that we use a predefined UUID rather than a random one, and include an @SInCE 3.21.0 tag.

wp-parsely.php (3)

119-135: Tighten the docblock and future-proof references.

• Referencing a specific line number in core (class-wp-customize-manager.php) is brittle; consider removing it.
• Keep the excellent rationale but trim incidental implementation details.

---

149-158: Handle insertion errors and avoid silent failures.

Check for WP_Error from wp_insert_post to prevent unnoticed failures; request an error object via the $wp_error flag.

Apply within this range:

-	if ( 0 === $post_id ) {
-		wp_insert_post(
-			array(
-				'post_type'   => 'customize_changeset',
-				'post_name'   => $uuid,
-				'post_title'  => "wp-parsely-$uuid",
-				'post_status' => 'private',
-			)
-		);
-	}
+	if ( 0 === $post_id ) {
+		$result = wp_insert_post(
+			array(
+				'post_type'   => 'customize_changeset',
+				'post_name'   => $uuid,
+				'post_title'  => "wp-parsely-$uuid",
+				'post_status' => 'private',
+			),
+			true // Return WP_Error on failure.
+		);
+		if ( is_wp_error( $result ) ) {
+			// Optional: log via your plugin's logging mechanism.
+			return;
+		}
+	}

---

117-159: Centralize the UUID and pass it to JS.

Define a plugin-level constant for the changeset UUID and expose it to the admin script to remove duplication and drift risk with TS.

Example (outside this range):

• Define a constant near other plugin constants:
  • define( NAMESPACE . '\EB_CHANGESET_UUID', '905b130b-4129-4416-919c-9e31433a6f65' );
• When registering/enqueueing the Content Helper scripts, add:
  • wp_add_inline_script( 'wp-parsely-admin', 'window.wpParsely = window.wpParsely || {}; window.wpParsely.engagementBoostChangesetUuid = ' . wp_json_encode( EB_CHANGESET_UUID ) . ';', 'before' );
• Use EB_CHANGESET_UUID in create_engagement_boost_changeset_post().

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

wp-parsely.php (2)

149-151: Filename fixed in the comment—thanks for addressing.

“preview-iframe.tsx” reference is now correct and ends with a period.

---

136-152: Load post_exists() instead of bailing; call the global function explicitly.

Early-returning when post_exists() isn’t loaded makes the fix a no-op on admin requests where that file isn’t included. Require the file and use the global function to avoid namespace lookup and ensure execution.

-	if ( ! function_exists( 'post_exists' ) ) {
-		return;
-	}
+	if ( ! function_exists( '\post_exists' ) ) {
+		require_once ABSPATH . 'wp-admin/includes/post.php';
+	}
@@
-	$post_id = post_exists( "wp-parsely-$uuid", '', '', 'customize_changeset', 'private' );
+	$post_id = \post_exists( "wp-parsely-$uuid", '', '', 'customize_changeset', 'private' );

wp-parsely.php (2)

126-128: Avoid brittle core line-number reference in docs.

Referencing specific core line numbers will drift across WP versions.

- * it fails with -1 ("Non-existent changeset UUID") around line 561 in
- * `class-wp-customize-manager.php` and prevents preview, displaying "-1".
+ * it fails with -1 ("Non-existent changeset UUID") in `class-wp-customize-manager.php` and prevents preview, displaying "-1".

---

151-154: Use slug-based lookup to avoid duplicate changesets across statuses.

post_exists() with a strict 'private' status can miss an existing changeset (e.g., trashed/draft), causing a new post with a suffixed slug. Look up by slug across any status.

-	$post_id = \post_exists( "wp-parsely-$uuid", '', '', 'customize_changeset', 'private' );
+	$existing = get_posts(
+		array(
+			'name'           => $uuid,
+			'post_type'      => 'customize_changeset',
+			'post_status'    => 'any',
+			'fields'         => 'ids',
+			'posts_per_page' => 1,
+			'no_found_rows'  => true,
+		)
+	);
+	$post_id = $existing ? (int) $existing[0] : 0;

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.