Admin Notice Prompting Jetpack Install Even Though It's Already Active

[katiebethbrown]

Quick summary

We're seeing an admin notice prompting for Jetpack to be installed, even though it's already installed and active on the site:

We're running a child theme of Dara. Dara appears to be prompting for Jetpack install for feature dependencies, via pluginenhancements.php.

I think this is happening because we're pulling a list of plugin names into an array, and then looking for the name Jetpack by WordPress.com. But I think the plugin is just named Jetpack now, so there’s not match detected and the error shows.

Related Slack Discussion: p1698949619753949-slack-C029FM1EH

[cuemarie]

📌 REPRODUCTION RESULTS

• Tested on Atomic – Replicated
• Replicable outside of Dotcom – Yes

📌 FINDINGS/SCREENSHOTS/VIDEO I am able to replicate this, but only with the non-wpcom version of the theme, v1.2.1, available in the WordPress.org themes catalog: https://wordpress.org/themes/dara/

WordPress.com Atomic site

• installed Dara v1.2.10-wpcom - no warning
• installed Dara v1.2.1 – Replicated

Self-Hosted (Pressable) site

• installed Dara v1.2.8 (downloaded from https://wordpress.com/theme/dara/ ) - No warning
• installed Dara v1.2.1 - Replicated

📌 ACTIONS

• Triaged
• Lowered priority
• left a note of my findings here: p1699295460268399/1698949619.753949-slack-C029FM1EH

[dsas]

Looks like the difference isn't because of the versions, but because we don't add the plugin-enhancements.php file for wpcom, it's added for wporg by the org-submitter

The fix would be to change the org-submitter, then regenerate all of the relevant theme zips so the new plugin-enhancements.php gets bundled with it.