Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Untangle theme screens #41374

Draft
wants to merge 30 commits into
base: trunk
Choose a base branch
from
Draft

Untangle theme screens #41374

wants to merge 30 commits into from

Conversation

scruffian
Copy link
Member

Fixes #

Proposed changes:

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

  • Go to '..'

Copy link
Contributor

github-actions bot commented Jan 28, 2025

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  • 🔴 Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Choose a review path based on your changes:
    • A. Team Review: add the "[Status] Needs Team Review" label
      • For most changes, including minor cross-team impacts.
      • Example: Updating a team-specific component or a small change to a shared library.
    • B. Crew Review: add the "[Status] Needs Review" label
      • For significant changes to core functionality.
      • Example: Major updates to a shared library or complex features.
    • C. Both: Start with Team, then request Crew
      • For complex changes or when you need extra confidence.
      • Example: Refactor affecting multiple systems.
  3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

@github-actions github-actions bot added the [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! label Jan 28, 2025
Copy link
Contributor

github-actions bot commented Jan 28, 2025

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the add/theme-install branch.

    • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.
  • To test on Simple, run the following command on your sandbox:

    bin/jetpack-downloader test jetpack add/theme-install
    
    bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/theme-install
    

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

Copy link
Contributor

github-actions bot commented Jan 28, 2025

Code Coverage Summary

Cannot generate coverage summary while tests are failing. 🤐

Please fix the tests, or re-run the Code coverage job if it was something being flaky.

Full summary · PHP report · JS report

@draganescu draganescu changed the title Add/theme install Untangle theme screens Jan 29, 2025
@github-actions github-actions bot added [Feature] Masterbar WordPress.com Toolbar and Dashboard customizations [Package] Masterbar labels Jan 29, 2025
/**
* Displays a banner before the theme browser that links to the WP.com Theme Showcase.
*/
function wpcom_themes_show_banner() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't remove this function until it's removed from being called on WPCOM: fbhepr%2Skers%2Sjcpbz%2Sjc%2Qpbagrag%2Snqzva%2Qcyhtvaf%2Sjcpbz%2Qgurzrf.cuc%3Se%3Q04155113%23176%2Q179-og

@ryelle
Copy link
Member

ryelle commented Jan 29, 2025

In 02fe4c2 I copied over the files from wpcomsh (the code used for Atomic themes), but this doesn't remove those original files yet. Then in 32b4963, I forked the core wp_ajax_query_themes handler, because it first checks for install_themes permissions. I don't like this approach, copying more core code, so I'm open to better solutions — but this at least lets the existing wpcom API functions hook into the correct results.

@ryelle
Copy link
Member

ryelle commented Jan 31, 2025

There are now wrapper filters on the template code — wpcom_themes_tmpl_theme for the card template & wpcom_themes_tmpl_theme_preview for the full-screen customizer preview. I've then added in the theme tier, passed back from the wpcom endpoint, and added it next to the theme name. It's not styled, probably needs to go somewhere else, but it's starting point.

Screenshot:

Screenshot 2025-01-31 at 12 26 03 PM

Maybe this should replace the "Installed" banner?

@ryelle ryelle force-pushed the add/theme-install branch from 32e9c8e to 563f07a Compare February 4, 2025 20:28
@ryelle
Copy link
Member

ryelle commented Feb 4, 2025

I'm not sure the best place for this, but just to note this down somewhere, here's how I'm thinking about the work breakdown for the theme-install.php portion of the work (this does cross over a few of the other open issues). Unchecked checkboxes are tasks anyone can pick up, so we can work on this in parallel.

  • Add a custom theme-install page for Simple sites
    • New page on simple sites, should show themes & core filters
    • Add DIFM banner (IIRC this should support JiTM in general, which is in progress by @getdave)
    • Add “Upload theme” button to header, should reveal Atomic upsell
  • Display wpcom, partner, and community themes
    • Community themes that are available on wpcom should be hidden, priority given to the wpcom theme (for example, searching "Layover" should only return the wpcom version) — probably not working due to the prefixed stylesheet value.
    • Themes should display plan label (reference PR for text and conditions), buttons should change to “Upgrade to…” (in progress by @matiasbenedetto)
    • “Install" button tries to run behind the scenes with install ajax request, but fails (of course). This applies to community & partner themes.
    • Add partner themes to Atomic results.
  • Users should be able to upgrade and activate paid themes/plans, including community and partner
    • Personal & Premium are working great
    • Atomic conversion currently requires a visit to the Theme Showcase page (see these notes). We talked about moving this screen to wp-admin; also simply redirecting back to wp-admin after theme activation.
    • Some partner themes (Drinkify) don't populate product_details, so they’re not purchasable.
  • Direct links to theme should show wpcom theme info. For example, /wp-admin/themes.php?page=wpcom-install-theme&theme=pub%2Fconference. Not working on Atomic either (/wp-admin/theme-install.php?theme=timestream).

@ryelle ryelle force-pushed the add/theme-install branch from 30611da to f5f6f49 Compare February 7, 2025 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Masterbar WordPress.com Toolbar and Dashboard customizations [mu wpcom Feature] Wpcom Themes [Package] Jetpack mu wpcom WordPress.com Features [Package] Masterbar [Status] In Progress [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants