Staging to Production with a woocommerce store

  • Unknown's avatar

    I recently built out a woocommerce store using the staging site features of WordPress.com. I want to sync my database and there are no issues with doing so because the store is not live on the previous build of the site. There are no orders or user data that can be lost.

    Using the staging tool without the database leaves the site unusable after migrating from staging. I have been able to use All in One WP Migration to get it live on zepedalearning.org but this has created Jetpack connection errors that I have not been able to solve after reviewing any of the documentation on that. Jetpack has also created an error with woocommerce connecting.

    This is where it gets weird. The site looks nearly flawless on zepedalearning.org after using All in one WP Migration but the migration creates a third WordPress backend.

    3 backends

    1. The WordPress.com backend for zepedalearning.org. This shows upgrades host config…all of the wp.com products but not the plugins (from plugins the installed plugins drop down does not appear, but from this section there is an installed plugins button and if you click it it takes you to the plugins of backend 2) or environment that is live at zepedalearning.org. Even more bizarre is that jetpack which claims to not be connected is backing up and giving me updates in its logs for data on backend 2.
    2. Backend 2 (lets call it purgatory) has the migrated site working as expected, except for jetpack not being connected and thus woocommerce being effected. All buttons and user interfaces are sound except for payments at checkout because woocommerce is not linked.
    3. Backend 3 The staging site where all data and user interfaces are connected and working properly

    The migration is live at zepedalearning.org but I have hidden it behind a coming soon page since jetpack/payments are not working.

    I’m comfortable working with SFTP transfers, changing pointer locations in a .php file if that is what is needed. So my question is as follows.

    How do I reconnect Jetpack?

    Will this merge my Backend 1 with my backend 2 AKA Purgatory? If not how so.

    Again worth noting the transferring the database should not be of ay issue since the store has never been live before and there are no orders or customers to loose in the process. I need to get this site live please help.

    The blog I need help with is: (visible only to logged in users)

  • Hi there,

    Thanks for clarifying the situation. Our staging tool does not include WooCommerce data out of an abundance of caution,  since WooCommerce data cannot be synced back to production without risking the potential to overwrite orders received after the staging site was created.

    We do not have an option at this time for moving woo content in cases where the site is not set up to take orders, but using a 3rd party plugin like All in One WP’s tool is an option that can be used here. The downside (as you have noted) is that 3rd party migration tools are not built with our managed hosting infrastructure in mind, so they can sometimes break the Jetpack connection to your site.

    1. The WordPress.com backend for zepedalearning.org. This shows upgrades host config…all of the wp.com products but not the plugins (from plugins the installed plugins drop down does not appear, but from this section there is an installed plugins button and if you click it it takes you to the plugins of backend 2) or environment that is live at zepedalearning.org. Even more bizarre is that jetpack which claims to not be connected is backing up and giving me updates in its logs for data on backend 2.
    2. Backend 2 (lets call it purgatory) has the migrated site working as expected, except for jetpack not being connected and thus woocommerce being effected. All buttons and user interfaces are sound except for payments at checkout because woocommerce is not linked.
    3. Backend 3 The staging site where all data and user interfaces are connected and working properly

    I’m hoping you can offer a bit more info here. Where are you seeing these? Are you able to share direct links so we can visit each one? We’re not sure how to access these otherwise, and I’m not sure that we will know (at a glance) which of the 3 backends we are looking at without further guidance. Does this issue affect other admins on the site or just you?

    How do I reconnect Jetpack?

    This is not something you are able to do on your end so staff will have to do this for you. Before I proceed though it will help to understand what you are seeing so we have a better sense of what will happen when Jetpack is connected again.

    Thanks for the additional info!

  • Unknown's avatar

    Thanks for clarifying the situation. Our staging tool does not include WooCommerce data out of an abundance of caution,  since WooCommerce data cannot be synced back to production without risking the potential to overwrite orders received after the staging site was created.

    There is no sales data to lose here. As I said this is not an issue.

    Where are you seeing these?

    For the three backends, it is simply the WordPress backends that are visible after signing into wordpress.com. Here is a step-by-step with screenshots loaded onto the purgatory backend.

    1. The staging site backend is the first screen after logging in.
    2. Navigate to manage my sites. The Purgatory back end is not visible.
    3. Select zepedalearning.org site and the back end loads and shows that the plugins button is not acting as expected which would typically have a dropdown menu to select installed plugins.
    4. Nonetheless we click the plunging button and the add new plugins page appears. When I click on the install plugins page I’m taken to the purgatory back end where the site is loading from.
    5. The purgatory backend does not have innate wordpress.com functions available like host configure…. but the live site is loading from here at https://zepedalearning.org

    Are you able to share direct links so we can visit each one?

    Not here as it would require my admin credentials but I’m glad to provide those to you if you have a recommended secure way to do this.

    Does this issue affect other admins on the site or just you?

    Yes, this affects everyone.

    The openness of your servers is very frustrating. Please advise.

  • Hi there,

    It seems that zepedalearning.org is no longer connected to the site hosted at WordPress.com (it shows a parked page of some kind instead) which makes it difficult to see the images you have shown. For me the result in a 404 error.

    Not here as it would require my admin credentials but I’m glad to provide those to you if you have a recommended secure way to do this.

    Staff is able to check in on these, and understanding the URL structure itself may offer some clues. I’ve temporarily set the WordPress.com site back to it’s default address (zepedalearning.wpcomstaging.com) since zepedalearning.org is not loading the site currently.

    Is it the case that the owner of zepedalearning.wpcomstaging.com has removed you as an admin on the site? I do not see that site as listed under your account when I look here: https://wordpress.com/sites

    I do see that zepedalearning.org is listed but that site is connected to a different host as you can see here: https://www.whois.com/whois/zepedalearning.org

    We are not able to troubleshoot your issue since it is not possible for you to connect staging-569a-zepedalearning.wpcomstaging.com to the production site if you are not an admin on zepedalearning.wpcomstaging.com

    Please ask the owner of that site to re-add you as an admin, which they can do by following the steps here:

    https://wordpress.com/support/invite-people/

    Once you have been re-added we are happy to take a closer look, thanks!

  • Unknown's avatar

    All good thanks for getting back to us we did not find the way you run your servers and hosting satisfactory so we went elsewhere.

  • The topic ‘Staging to Production with a woocommerce store’ is closed to new replies.