Mailchimp: Disconnecting account doesn't fully remove the token

[tmmbecker]

Impacted plugin

Jetpack

Steps to Reproduce

You'll need two WordPress administrator accounts, two WordPress.com accounts and two admin-level Mailchimp accounts. This is the easiest way to see the issue.

1. Connect each WordPress admin account to a WordPress.com account.
2. In WordPress.com for the first account, go to Tools → Marketing → Connections.
3. Follow the prompts to connect Mailchimp to an MC administrator-level account.
4. Add the block to the site and confirm that it works.
5. Go back to Tools → Marketing → Connections and disconnect that account.
6. In Mailchimp, downgrade this MC account to Viewer.
7. Switch to the other Jetpack-connected admin account.
8. in WordPress.com go to Tools → Marketing → Connections.
9. Follow the prompts to connect Mailchimp to the second MC administrator-level account.
10. On the front-end, open the console → Network tab.
11. navigate to the post or page where you added the Mailchimp block and try to sign up. Note that you get this error:

13. Check the failed call in the Network tab and this error:

15. In the Mailchimp account, upgrade the first user to Admin. 16. Subscribe again and notice that it works.

A clear and concise description of what you expected to happen.

When disconnecting from Mailchimp in one WordPress.com account, I should be able to connect to another Mailchimp account without issue.

What actually happened

No response

Browser

No response

Other information

Newspack sites are heavy users of the Mailchimp block and they tend to experience a higher volume of staff turnover. This has now happened to at least three customers:

1. Atavist Magazine switched to the MC4WP plugin.
2. https://enlacelatinonc.org/ switched to the MC4WP plugin.
3. https://washingtoncitypaper.com/ had to upgrade the MC account for their former admin in order for the Jetpack block to resume functioning. They are heavy users of the Mailchimp block so a switch is not an option.

Platform (Simple, Atomic, or both?)

Self-hosted

Reproducibility

Consistent

Severity

Most (> 50%)

Available workarounds?

None

Workaround details

No response

[github-actions]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, `[Type] Feature Request`, `[Type] Enhancement`, `Good For Community`, `[Type] Good First Bug`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[sdixon194]

Cleaning up stale issues and did some more testing of this one. I wasn't able to figure out what "viewer" was, so I wasn't able to downgrade, but in my testing I was able to disconnect one MC admin, switch to the other account, sign into that account and connect to the alternate MC account, and subscribe successfully.