Automattic
Purchasing the Commerce plan and DIFM Express breaks the connection to DIFM Express tools
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
- Browse to the DIFM Express onboarding for stores https://wordpress.com/start/do-it-for-me/new-or-existing-site?ref=supportpage
- Select “Use existing site”
- Select the site with the free domain you used for the Commerce plan
- Go through the onboarding flow to get to the cart
4. Checkout using your free credits
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
If you paste the URL in a new tab, we see this error:
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.’
- Connection is broken.
7. Review the audit trail to see when the connection breaks in the sequence
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:
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
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
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
📌 REPRODUCTION RESULTS Replicated
📌 FINDINGS/SCREENSHOTS/VIDEO Not only user can't submit content, I also found the warning confusing:
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!
@Automattic/quake will be moving this project forward: p58i-icz-p2#comment-64402
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.
The same issue exists with a new flow I discovered: do-it-for-me-store
Fix: D162188-code
@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?
Yes, I agree. It's a good maintenance task and it would be great if we continue work and fix this issue.
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.
Hi @p-jackson. Just checking in on this high priority issue to see if there's anything new to report?
Shouldn't it stay on the One Board for tracking purposes @davemart-in ? Like "issues closed" that is being reported?
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
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
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
@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. https://github.com/Automattic/wp-calypso/pull/95183
Noting that I deployed 174382-ghe-Automattic/wpcom a little while ago, but we still need https://github.com/Automattic/wp-calypso/pull/100536 deployed to get this fully resolved.
@aneeshd16, after your deploy of #100536 yesterday, do you think we can close this issue?
@daledupreez, I think so! @dcoleonline, can you please confirm if the issue has been resolved and we can close this?
