Automattic / Automattic/wp-calypso

Atomic Domains: Improve Calypso's error messaging for issues setting a primary domain

Open
#59,366 7 comments 0 reactions 1 assignee Assigned to @serabi View on GitHub
[Feature Group] Emails & Domains [Platform] Atomic [Pri] Normal Dotcom Bug Blitz WordPress.com
Dominant language
TypeScript
Stars
12.6k
Forks
2k
Avg merge
1d 18h
Merged PRs (30d)
531

Description

### Quick summary

Users might encounter issues setting a primary domain if the domain has already been used with another Atomic client.

In these cases, Calypso shows a success message: `Primary domain changed: all domains will redirect to [domain]`

However, the domain is not set as the primary.

![Screen Shot on 2021-12-17 at 18:06:59](https://user-images.githubusercontent.com/4887830/146618228-fe3f32c0-b010-4761-90b8-0c2df87340a3.png)

Extended report available internally at p9F6qB-7QU-p2

### Steps to reproduce

Internal notes at p9F6qB-7QU-p2#comment-44342

### What you expected to happen

Calypso to display a relevant error and recommended next steps.

### What actually happened

Calypso incorrectly states `Primary domain changed: all domains will redirect to [domain]`

### Simple, Atomic or both?

Atomic

### Available workarounds?

Yes, easy to implement

### Workaround details

Internal documentation available at P9HQHe-1dG-p2

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.