• Hi there folks; I’ve got a production site which I cloned into a staging copy yesterday. Jetpack in the production site is showing as being in Safe Mode, and my client posted a new blog post today. Unfortunately the Subscriptions don’t work in Safe Mode, and she really needed her subscribers to be updated about this piece of news.

    Is there a way around this? Can I just delete Jetpack from the staging copy, reinstall and reconnect it later? I don’t need any of the Jetpack services for a while.

    Our biggest concern is avoiding data loss, specifically the list of several hundred subscribers.

    On a separate note, the Jetpack account is keyed to my email address, but when I sign into WordPress.com I don’t see this site, either the dev or live versions, in my list of websites (a couple dozen other client sites are showing, though). Any suggestions there?

    Thank you.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    Hey @aloeroot – If you don’t need Jetpack on staging site right now then I’d recommend to delete Jetpack plugin from the staging site. If you have Jetpack connected to staging site then first disconnect the Jetpack plugin and then delete it from the staging site. And then disconnect and reconnect Jetpack plugin on production site.

    In order to prevent this issue in future, if you are cloning the site from Production to Staging, then first, please deactivate the Jetpack plugin from the Production site ? and then clone the site to Staging ? then reconnect Jetpack at both Production and Staging site.

    Similarly, if you are deploying the site from Staging to Production, then first, deactivate the Jetpack plugin both at Staging and Production site ? then deploy the Staging site to Production ? and then connect the Jetpack to the Production site.

    Our biggest concern is avoiding data loss, specifically the list of several hundred subscribers.

    You mean the site subscribers that are on Jetpack. Right? If so, if those subscribers get lost for any reason, we can try to find it, and then assign them to correct site. But yes it is good to avoid this situation to avoid more delay. ??

    On a separate note, the Jetpack account is keyed to my email address, but when I sign into WordPress.com I don’t see this site, either the dev or live versions, in my list of websites (a couple dozen other client sites are showing, though). Any suggestions there?

    I also don’t see this site in our database. In your account do you see the staging site or can you share us the staging site address?

    Thread Starter aloeroot

    (@aloeroot)

    Thanks very much, Animesh. I’ll take your advice as far as disconnecting and deleting from the staging site (already done), then disconnecting and reconnecting to the production site for now.

    It is the Jetpack subscriber list we’re most worried about, yes.

    I’m hesitant to disconnect the production site from Jetpack until I’m sure we can reconnect it. We use it for various WooCommerce services as well as the standard Jetpack services.

    On the Production site, I’m seeing “Site Connected” and “User Connected (Owner)” under Connection when I’m logged in, so I’m assuming Jetpack is connected to my own WordPress.com account. It doesn’t show up in my list, but I’ve connected a lot of client sites to Jetpack and I’m hoping the list is just limiting the number of sites visible.

    The staging site address is https://dev.tla-temagami.ca/ (hidden behind a placeholder for now). As of this morning I had already disconnected and deleted Jetpack from the staging site, so you may not see it in your list.

    Thanks again for your help.

    Plugin Support Animesh Gaurav (a11n)

    (@bizanimesh)

    Hey @aloeroot – thanks for sharing the staging site address. I don’t see your production site on our side but can see staging site and I also see subscribers and traffic stats attached to staging site. Since staging site is new, there shouldn’t be subscribers and stats here. With this all, I think the data of your production site has been already transferred to staging site. But we can revert this change so there is nothing to worry about.

    As a next step, on the production site, if it is still showing the safe mode notice, could you please select the “Create a fresh connection” option and connect the production site to Jetpack and then let us know. We will then transfer the data from staging site to production site from our side.

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