Automattic / wp-calypso

The JavaScript and API powered WordPress.com
https://developer.wordpress.com
GNU General Public License v2.0
12.42k stars 1.99k forks source link

Free setup flow — Back button not working #94434

Open renancarvalho opened 2 months ago

renancarvalho commented 2 months ago

Quick summary

When creating a user from wordpress.com on the home page, users are redirected to freesetup after adding a site name and description, users are redirected to designSetup https://wordpress.com/setup/free/designSetup?siteSlug={siteSlug}. In that step, the back button does not work.

Steps to reproduce

1 . Navigate incognito to wordpress.com 2 . Go to plans and pricing 3 . Start free plan 4 . Land on freesetup step and add site name and description 5 . Land on designSetup 6 . Click on back button

What you expected to happen

The back button should take me back to the previous step

What actually happened

Nothing happened

Impact

Most (> 50%)

Available workarounds?

No but the platform is still usable

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

No response

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

Addison-Stavlo commented 2 months ago

This seems to be accessed by entering the free flow from https://wordpress.com/pricing/

Screenshot 2024-09-11 at 11 23 31 AM

To Repro:

free-no-back

Expected: Back button to go back to the name/description step.

Workaround: Users are able to revisit the name and description step from the launchpad after selecting their design:

free-workaround

Or later through other interfaces after leaving the launchpad.

Impact Most (> 50%)

I am unsure about this impact classification, as the combination of amount of new users that go through this specific onboarding flow plus also feel a need to go back from this specific page seems much less than 50%.

Im triaging this as normal priority.

m1r0 commented 3 weeks ago

I can't reproduce this. It looks like the flow was updated, and this is possibly no longer relevant. Can you double-check if this is still an issue?