Enable the "Preview & Customize" button for Premium and WooCommerce themes (on horizon)

[okmttdhr]

Related to #79223
#84483

Proposed Changes

This PR enables the "Preview & Customize" button for Premium and WooCommerce themes on the Horizon environment.

Note that the whole "Live Preview in Premium and Woo themes" feature is under development. See #79223.

before	after

Testing Instructions

• Go to the Theme Showcase page.
• Click the three-dot menu on a Premium (e.g., Hevor) or WooCommerce (e.g., Amulet) theme.
  • Click the Preview & Customize button.
    
  • Verify it redirects to the Site Editor and you're live-previewing the theme.

Regression testing for Simple sites;

• Click the three-dots menu on a Free (e.g., Epi) theme.
  • Click the Preview & Customize button.
  • Verify it redirects to the Site Editor and you're live-previewing the theme.
• Click the three-dots menu on a Partner (e.g., Eben) / wporg (e.g., Classified Listings) theme.
  • Verify you don't see the Preview & Customize button.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• https://wpcalypso.wordpress.com/devdocs/docs/testing/index.md for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-90860

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-90860&env=jetpack

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• blaze-dashboard
• odyssey-stats

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/live-preview-in-premium-woo-themes on your sandbox.

[taipeicoder]

Tested:

• Go to the Theme Showcase page.
• Click the three-dot menu on a Premium (e.g., Hevor) or WooCommerce (e.g., Amulet) theme.
• Click the Preview & Customize button.
• ✅ Verify it redirects to the Site Editor and you're live-previewing the theme.

Regression testing for Simple sites;

• Click the three-dots menu on a Free (e.g., Epi) theme.
• Click the Preview & Customize button.
• ✅ Verify it redirects to the Site Editor and you're live-previewing the theme.
• Click the three-dots menu on a Partner (e.g., Eben) / wporg (e.g., Classified Listings) theme.
• ✅ Verify you don't see the Preview & Customize button.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~67 bytes added 📈 [gzipped])

name    parsed_size           gzip_size
themes       +206 B  (+0.0%)      +67 B  (+0.0%)
theme        +206 B  (+0.0%)      +67 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[renatho]

Hi @okmttdhr!

Me again. While working on the Sensei bundle themes, I'm comparing it with WooCommerce themes. So I just noticed this difference and I'd like to ask you if it should really be specific for WooCommerce, or for any bundle.

If for any bundle, I could change it as part of #84886. Probably using doesThemeBundleSoftwareSet instead of isThemeWooCommerce. Or if it's really only for WooCommerce, I'll leave it as it is.

[okmttdhr]

Thanks for reaching out, @renatho!

This feature should be compatible with all Bundle themes in the future (CC: @Automattic/lego). However, several changes are needed to transition it from being Woo themes-specific to being applicable to Bundle themes. For example;

• The logic to decide if the site has the feature to use the theme:

  • wp-calypso/apps/wpcom-block-editor/src/wpcom/features/live-preview/hooks/use-can-preview-but-need-upgrade.ts

    Lines 30 to 34 in c228880

    	const canUseWooCommerceTheme =
    	previewingThemeType === WOOCOMMERCE_THEME &&
    	[ WPCOM_FEATURES_PREMIUM_THEMES, FEATURE_WOOP, WPCOM_FEATURES_ATOMIC ].every( ( feature ) =>
    	activeFeatures.includes( feature )
    	);

  • Is this condition the same for all Bundle themes?
• The plan they need:

  • wp-calypso/apps/wpcom-block-editor/src/wpcom/features/live-preview/hooks/use-can-preview-but-need-upgrade.ts

    Lines 119 to 126 in c228880

    	previewingTheme.type === WOOCOMMERCE_THEME
    	? /**
    	* For a WooCommerce theme, the users should have the Business plan or higher,
    	* AND the WooCommerce plugin has to be installed.
    	*/
    	generateCheckoutUrl( PLAN_BUSINESS )
    	: // For a Premium theme, the users should have the Premium plan or higher.
    	generateCheckoutUrl( PLAN_PREMIUM );

  • Is this condition the same for all Bundle themes?
• The display name of a theme type:

  • wp-calypso/apps/wpcom-block-editor/src/wpcom/features/live-preview/hooks/use-previewing-theme.ts

    Line 47 in c228880

    previewingThemeType === WOOCOMMERCE_THEME ? 'WooCommerce' : 'Premium';

  • Can this be retrieved by useBundleSettings?

I would greatly appreciate it if you could implement all the changes simultaneously. But, if this isn't feasible, please leave it as it is, and I will file an issue to address it later. 🙂

For functionality testing: pekYwv-3xz-p2

[renatho]

Hi @okmttdhr! 👋

please leave it as it is, and I will file an issue to address it later

After checking this a little, I think it would be the best approach. And if you want to reference me in the issue, I can help with what is needed regarding the bundle feature.

I think the conclusion (not concluded yet) of the thread #84886 (comment) will be a good reference for the needs here.

[okmttdhr]

📝

• Live Preview with Bundle Themes #86274