• Resolved Cory Hughart

    (@cr0ybot)


    We created a staging version of our site for a plugin developer to debug some issues and we think they logged in and clicked the wrong button when prompted with the safe mode popup, transferring data from the live site (https://rainbowtomatoesgarden.com) to staging (https://woocommerce-1207753-4444395.cloudwaysapps.com). When I saw the safe mode popup on the live site, I went back to staging, disconnected Jetpack, and then reconnected Jetpack on live. Only after that did I realize that the data had likely been transferred, and reconnecting essentially created a new connection. I’m not sure what I can do now to restore the live site’s original connection with its historical data. Any way to restore this?

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Cory Hughart

    (@cr0ybot)

    I have found jetpack_persistent_blog_id in the wp_options table and compared it with a backup to find it different. I restored the original ID but nothing seems to have happened. Is there another option in the database that I can restore to reconnect the site? I can’t restore the full database since this is an e-commerce site and there are active orders since the incident.

    Thread Starter Cory Hughart

    (@cr0ybot)

    Found another that looks important, jetpack_private_options, which I also restored, but now I’m just getting a message that says the connection with Jetpack is broken. It’s giving me the option to “restore connection” but I did that before and it seemingly just created a new “site”.

    Thread Starter Cory Hughart

    (@cr0ybot)

    I found some other posts in this forum that suggest that this issue can only be resolved on the Jetpack server side, so I will anxiously await a reply and stop fiddling.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @cr0ybot,

    With Jetpack, your site information is connected to a unique blog ID. Sometimes, if a site owner was using a development site or a different address when they set up Jetpack, disconnecting may create a new blog ID. When this happens, it may appear that your stats were lost.

    That’s what happened on your site; it previously used a different site URL, that was in fact your staging site.

    I have fixed the issue, and you should be able to get your info back by going to the Jetpack menu in your dashboard, and disconnecting/reconnecting to WordPress.com. You can disconnect from WordPress.com thanks to the link at the bottom of the page.

    For future references, you may want to check our Safe Mode and Staging Sites modules, as they will help to avoid such issues the next time you might be encountering it ??

    Please let me know if you have any further questions or doubts, and we’re happy to assist you.

    Cheers,

    Thread Starter Cory Hughart

    (@cr0ybot)

    Thank you @erania-pinnera, we’re relieved to have all the historical data back. Is it possible to merge in the data that got separated back into the main site stats? If it’s too much of a hassle and/or lost I understand.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hey @cr0ybot,

    I can see stats for your site from April 2022 onwards. If you have more stats tied to this Jetpack site, they might be stored and tied to a different URL with which you had the same Identity Crisis.

    I don’t see any other possible URLs, which leads me to believe that all the available stats are from April 2022. Does this make sense to you? If not, we’ll keep investigating.

    Thread Starter Cory Hughart

    (@cr0ybot)

    @erania-pinnera We only lost about 3 days of data, starting sometime on August 29 when the identity moved to the staging site and ending when you reconnected things on September 2. Data was being collected during that time, obviously to some other ID, but the URL was the live site: https://rainbowtomatoesgarden.com. It’s not the end of the world if those are lost.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @cr0ybot,

    I checked the stats and I can see some figures also on August 29-Sep2: ther figures are very low, but that means that the system was fetching the stats, so it was connected enough time to be able to gather some stats.

    I suspect that what could have happened on these few days wasn’t an Identity Crisis, but rather some connection hiccups that affected the Stats too: when Jetpack is disconnected or not well connected, no data can be fetched.

    Would that sound like something that could have happened, in your opinion? Otherwise we could keep digging.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hey @cr0ybot,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.