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

Purchasing the Commerce plan and DIFM Express breaks the connection to DIFM Express tools #94517

Open
dcoleonline opened this issue Sep 13, 2024 · 17 comments
Assignees
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Default business plan to atomic DIFM Express Built By Express Onboarding Pipeline related tasks [Feature Group] Signup & Site Onboarding Tools for user registration and onboarding new users to the site. [Feature] Site Goals & Onboarding Paths The onboarding flows for all new sites. Groundskeeping Issues handled through Dotcom Groundskeeping rotations [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@dcoleonline
Copy link
Contributor

dcoleonline commented Sep 13, 2024

Quick summary

There is currently an issue that occurs when a customer purchases DIFM Express with the Commerce plan. The Commerce plan pushes the site AT, breaking the connection needed for our content submission form and other DIFM Express automation tools. Discussed here p58i-icz-p2#comment-64349

Steps to reproduce

1. Add $1,039 free credits to your WP account

2. Add a new site with the Commerce plan to your cart

  • Go to https://wordpress.com/sites and click “Add new site”
  • Add a free domain and click “Continue”
  • Select the “Get Commerce” to add the Commerce plan to your cart

3. Add DIFM Express to the cart

4. Checkout using your free credits
difm-express-checkout

5. If you see the content form after checkout, try submitting content. You will see an error and will not be able to submit content
content-form-error

If you paste the URL in a new tab, we see this error:
direct-link

6. Check the DIFM tools in the Blog RC

  • Go to the Blog RC for the new site
  • Scroll down to the DIFM Tools section and see the note `No Built By Express options found.’
    DIFM-tools
  • Connection is broken.

7. Review the audit trail to see when the connection breaks in the sequence
blog-audit

What you expected to happen

The site should stay connected to the DIFM Tools and the form should work for the customer to submit content.

When the connection is working, we should see the link to their content form under DIFM Tools like this:
working-tools

What actually happened

The Commerce plan pushes the site atomic right after purchase, which breaks the connection to the DIFM Tools. The customer is not able to submit their content in the form.

Impact

Some (< 50%)

Available workarounds?

Yes, difficult to implement

If the above answer is "Yes...", outline the workaround.

We have a time-consuming workaround outlined here → Process: Fixing Content Form on AT Sites (Pdh1Xd-2Ni-p2)

That being said, there are plans (p58i-icz-p2#comment-64349) to start pushing all new WP.com Business plan sites atomic after purchase. If this happens, this form issue will start to greatly affect the efficiency of our team.

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

@dcoleonline dcoleonline added [Type] Bug When a feature is broken and / or not performing as intended [Pri] Normal Schedule for the next available opportuinity. [Feature Group] Signup & Site Onboarding Tools for user registration and onboarding new users to the site. Needs triage Ticket needs to be triaged DIFM Express Built By Express Onboarding Pipeline related tasks Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Site Goals & Onboarding Paths The onboarding flows for all new sites. [Product] WordPress.com All features accessible on and related to WordPress.com. labels Sep 13, 2024
Copy link

github-actions bot commented Sep 13, 2024

Support References

This comment is automatically generated. Please do not edit it.

  • p58i-icz-p2#comment-64349
  • p58i-icz-p2#comment-64402
  • p58i-icz-p2#comment-6434
  • pet6gk-1yJ-p2#comment-1371

@retnonindya
Copy link

retnonindya commented Sep 18, 2024

📌 REPRODUCTION RESULTS
Replicated

📌 FINDINGS/SCREENSHOTS/VIDEO
Not only user can't submit content, I also found the warning confusing:

Screenshot 2024-09-18 at 4 27 30 PM

The warning about "please check your Internet connection" implies that the issue is on the user's Internet connection, while it's more on website/Jetpack connection.

📌 ACTIONS

  • Triaged
  • I noticed we had informed folks here: p58i-icz-p2#comment-64349
  • Considering the severity of the issue, I'm raising this issue's priority to Blocker since the workaround itself is time-consuming for the team

Thanks heaps for reporting this, @dcoleonline!

@retnonindya retnonindya added [Pri] BLOCKER Requires immediate attention. and removed [Pri] Normal Schedule for the next available opportuinity. Needs triage Ticket needs to be triaged labels Sep 18, 2024
@retnonindya retnonindya moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Sep 18, 2024
@github-actions github-actions bot added the [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts label Sep 18, 2024
@candy02058912 candy02058912 added the Groundskeeping Issues handled through Dotcom Groundskeeping rotations label Sep 19, 2024
@candy02058912
Copy link
Contributor

@Automattic/quake will be moving this project forward: p58i-icz-p2#comment-64402

@p-jackson p-jackson self-assigned this Sep 23, 2024
@p-jackson
Copy link
Member

The same problem existed when the site was originally created using the DIFM flow, which is now fixed by D162026-code.
Still working on the case described in this issue's steps to reproduced, where the DIFM flow is used to add the DIFM product to an existing site. It's a bit trickier.

@autumnfjeld
Copy link
Contributor

autumnfjeld commented Sep 23, 2024

Discussed here: p58i-icz-p2#comment-6434

@p-jackson
Copy link
Member

p-jackson commented Sep 24, 2024

The same issue exists with a new flow I discovered: do-it-for-me-store
Fix: D162188-code

@paulopmt1
Copy link
Contributor

paulopmt1 commented Sep 25, 2024

@autumnfjeld Although we're pausing the project (pet6gk-1yJ-p2#comment-1371), fixing the root issue seems to be a good maintenance task to prioritize. Thoughts?

@autumnfjeld
Copy link
Contributor

Yes, I agree. It's a good maintenance task and it would be great if we continue work and fix this issue.

@obenland
Copy link
Member

It's a good maintenance task

That doesn't sound like this should be a Blocker level issue then.

@retnonindya I'll lower the priority on this. Blockers should be something that needs our immediate attention and be solved as quickly as possible.

@obenland obenland added [Pri] High Address as soon as possible after BLOCKER issues and removed [Pri] BLOCKER Requires immediate attention. labels Sep 27, 2024
@taipeicoder taipeicoder moved this from Triaged to In Progress in Automattic Prioritization: The One Board ™ Oct 7, 2024
@taipeicoder taipeicoder moved this from In Progress to Triaged in Automattic Prioritization: The One Board ™ Oct 7, 2024
@donnapep
Copy link
Contributor

donnapep commented Oct 8, 2024

Hi @p-jackson. Just checking in on this high priority issue to see if there's anything new to report?

@davemart-in
Copy link
Contributor

Removed from The One Board, since Quake picked it up.

@davemart-in davemart-in removed the Groundskeeping Issues handled through Dotcom Groundskeeping rotations label Oct 14, 2024
@autumnfjeld
Copy link
Contributor

Shouldn't it stay on the One Board for tracking purposes @davemart-in ? Like "issues closed" that is being reported?

@davemart-in
Copy link
Contributor

That's a good question. From my perspective:

A) If someone grabs an issue, but doesn't assign it to their teams board, it's okay to stay in The One Board.
B) But once someone assigns it to a team board, it makes sense to remove from The One Board, else as people are going through The One Board, they then have to sift through a bunch of issues that already have a home. That sifting process can be taxing.

If I'm doing this wrong though, I'm happy to change. cc @inaikem

@p-jackson
Copy link
Member

Hi @p-jackson. Just checking in on this high priority issue to see if there's anything new to report?

@donnapep no news yet sorry

@donnapep
Copy link
Contributor

Shouldn't it stay on the One Board for tracking purposes

We should go ahead and remove issues from The One Board "if they're being accounted for in other ways". Reference - p1728657406004539-slack-C07GZ2UA3TN

@autumnfjeld
Copy link
Contributor

autumnfjeld commented Oct 20, 2024

@p-jackson could you add a quick update to this issue on work still remaining? WOuld be great to have a "Done" and "Next" section to make it clear.

I think this PR was the most recent that contributed to this work.
#95183

@jartes jartes moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Feb 5, 2025
@eduardozulian eduardozulian added the Triaged To be used when issues have been triaged. label Feb 20, 2025
@daledupreez daledupreez self-assigned this Feb 21, 2025
@daledupreez daledupreez added the Groundskeeping Issues handled through Dotcom Groundskeeping rotations label Feb 21, 2025
@daledupreez
Copy link
Contributor

I've started working on a fix in 174382-ghe-Automattic/wpcom.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Default business plan to atomic DIFM Express Built By Express Onboarding Pipeline related tasks [Feature Group] Signup & Site Onboarding Tools for user registration and onboarding new users to the site. [Feature] Site Goals & Onboarding Paths The onboarding flows for all new sites. Groundskeeping Issues handled through Dotcom Groundskeeping rotations [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Escalated to Product Ambassadors [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

No branches or pull requests