Automattic / jetpack

Security, performance, marketing, and design tools β€” Jetpack is made by WordPress experts to make WP sites safer and faster, and help you grow your traffic.
https://jetpack.com/
Other
1.58k stars 795 forks source link

Jetpack connection is broken after importing a site with All-in-one Migration #37892

Open mpkelly opened 1 month ago

mpkelly commented 1 month ago

Impacted plugin

Jetpack

Quick summary

Using All-in-one Migration, I exported a site from Studio and imported it to a new WordPress.com site with the Creator plan. A banner is shown:

Screenshot 2567-06-17 at 12 58 57

The docs tell you to click Jetpack > Dashboard to resolve this issue. In my first test, there was no Dashboard menu item. In the second, even when I click Dashboard, I am redirected to the frontend home.

Steps to reproduce

  1. Create a new site in WordPress Studio (it is probably an issue with sites created with the Docker env and elswhere - TBC)
  2. Add some content, a page or a post
  3. Install All-in-one Migration and export your Studio Site
  4. Import that backup into a new WordPress.com Creator site

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

The Jetpack connection should not need to be fixed. Or at least I should be able to resolve the issue as shown in the docs.

What actually happened

screen-capture (13).webm

Impact

Some (< 50%)

Available workarounds?

No and the platform is unusable

Platform (Simple and/or Atomic)

Atomic

Logs or notes

No response

liviopv commented 1 month ago

πŸ“Œ REPRODUCTION RESULTS

πŸ“Œ FINDINGS/SCREENSHOTS/VIDEO @mpkelly I didn't test this myself, but as an HE, I know this is reproducible since it's a broken flow thoroughly documented internally to the point that there is internal documentation for working around it P9HQHe-1Xi-p2 and user-facing documentation on how to prevent it https://wordpress.com/support/import/import-using-all-in-one-migration/#admin-account

My understanding is that AIOWPM breaks the connection because it overrides the destination site user list. When that user list on the site doesn't match the values expected by the Jetpack connection, the connection breaks. As far as I understand, there's not much we can do from our end to fix this, and past attempts to work with AIOWPM only yielded small adjustments. Pinging @JoshuaGoode to confirm and share more historical context, as needed.

Mike, I'm going to switch the priority to Normal, but please adjust as needed if Quake plans to work on it next.

πŸ“Œ ACTIONS

mpkelly commented 1 month ago

Thanks. @liviopv. I will give it some thought and consider closing this down if I can't think of a solution.

mpkelly commented 1 month ago

One issue I just ran into now which makes this more serious: the last site I had selected was the site with the broken Jetpack connection. I then went to test a diff that required me to buy a Creator plan, and I could not do that until I went to /sites and then chose a different site that did not have a Jetpack connection issue. I saw this on the plans step at first:

Screenshot 2567-06-17 at 18 27 19

More details here: p1718634585904879-slack-C04H4NY6STW

zdenys commented 1 week ago

The Jetpack connection will happen automatically for AIOWPM once this is implemented by @Automattic/serenity:

When migrating with Migrate Guru we do automated cleanup and Jetpack reconnection and the same should happen for AIOWPM.

fbhepr%2Skers%2Sjcpbz%2Snflap%2Qwbof%2Svapyhqrf%2Szvtengvba%2Szvtengvba%2Qpyrna%2Qhc.cuc%3Se%3Q19p18073-og