Issues with dev site

  • Resolved faithdanceart

    (@faithdanceart)


    11 years ago

    I am using Desktop Server when doing more extensive changes. I am using Updraft to migrate the site from the life site to the development site. The last time I migrated the site, I had all kinds of problems and thought it was the fault of the latest Updraft version, but eventually found out that the problems originated from different Jetpack plugins that I started using recently.

    One was Protect which did not allow me to login to my dev site and kept sending me in neverending circles. So, I had to deactivate it before doing the backup used for migration. Since I don’t want to switch back and forth, I can’t use it anymore.

    The other one was Photon – none of the images showed in my portfolio grid and I thought I had lost them or at least the correct links. After a lot of searching I realized that because the dev site is stored on my computer, Photon might not like that. Sure enough, when I deactivated Photon, my images (or most of them) were back.

    I still have a problem with some tiled galleries, but I am not sure what causes it.

    Updraft support was very helpful, but when we discovered that the problems originated with Jetpack, they asked me to let you know.

    https://wordpress.org/plugins/jetpack/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    11 years ago

    One was Protect which did not allow me to login to my dev site and kept sending me in neverending circles.

    That’s something that should have been solved in Jetpack 3.5, as per the discussion here. Could you give it another try with the latest version of Jetpack, and let me know how it goes?

    because the dev site is stored on my computer, Photon might not like that.
    […]
    I still have a problem with some tiled galleries, but I am not sure what causes it.

    That’s correct. Since your images aren’t publicly accessible, Photon can’t download them and serve them from our servers.

    You shouldn’t be able to enable any of these 2 modules on a local environment, but I assume Updraft allowed you to trick our system by copying things from your live site to your development environment.

    When copying sites with Updraft, I’d recommend you to delete the jetpack_options row from the wp_options table in your database. This row contains data that shouldn’t be copied from one site to another, or it will cause conflicts like the ones you’ve experienced.

    And when working in a local installation of WordPress, you can use Jetpack’s Development mode to use only the features that do not require a connection to WordPress.com.

    I hope this helps.

    David Anderson / Team Updraft

    (@davidanderson)

    11 years ago

    When copying sites with Updraft, I’d recommend you to delete the jetpack_options row from the wp_options table in your database. This row contains data that shouldn’t be copied from one site to another, or it will cause conflicts like the ones you’ve experienced.

    Hi,

    Thanks – this is helpful information. We will incorporate this into the next UpdraftPlus release, so that it happens automatically when migrating as site to a new location.

    It’d be handy, though, if you can just re-confirm that for me: that this option should always be entirely deleted if the site changes URL – and that won’t have any unexpected side effects. (Given the very generic name of the option, “jetpack_options”, my immediate suspicion is that users would start complaining that all their options vanished!).

    Best wishes,
    David

    David Anderson / Team Updraft

    (@davidanderson)

    11 years ago

    Sorry – an empty follow-up post, just so that I can tick the “Notify me of follow-up posts via email” box this time…

    David

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    11 years ago

    @david Thanks for jumping in!

    jetpack_options is an array of options, and all these options are related to the site and its connection to WordPress.com: the site URL, its matching ID on WordPress.com, information about the WordPress.com account connected to the site, …

    All this information will be recreated and will match the new site as soon as the site owner goes through the Jetpack connection process on the new site. It’s consequently safe to delete these options when cloning a site.

    That’d be great if this could be done automatically when cloning a site with UpdraftPlus!

    David Anderson / Team Updraft

    (@davidanderson)

    11 years ago

    Thanks! One more thing – is this option always found in the ‘options’ table, or will it be in the sitemeta table on multisite? (i.e. is it a per-site option, or per-install option?).

    David

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    11 years ago

    It’s a per-site option.

    David Anderson / Team Updraft

    (@davidanderson)

    11 years ago

    Hi,

    Thanks again. This is coded now and will be in the next release.

    David

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Issues with dev site’ is closed to new replies.