Cloned site has messed up WordPress.com connection for Jetpack stats

  • Resolved timbad2

    (@timbad2)


    6 years, 1 month ago

    Hi,
    I added a temporary clone to the above site called “testcache”, so I could try out a plugin.
    I later deleted this clone, but I now find that my WordPress.com account points to https://timbaderonline.com/testcache instead of the original top level domain and there seems to be no way of fixing it, either online or in the iPhone/iPad app.

    Has the cloning process updated some kind of under the hood setting that has caused it to think this URL is the main URL of my site?
    How can this be fixed please?
    Regards,
    Tim

    • This topic was modified 6 years, 1 month ago by timbad2.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Rene Hermenau

    (@renehermi)

    Hi Tim,

    it seems you told jetpack the staging site testcache should be connected to your wordpress.com account. This could also be done automatically by the jetpack plugin but usually jetüpack detects when it is used on the staging site and asks you if it is used on a staging site and you need to confirm that then.

    There should be a setting in jetpack or in your account at wordpress.com to set the main url.

    Thread Starter timbad2

    (@timbad2)

    Hi Rene,
    Apologies, but no I didn’t: the site has been setup in Jetpack for several years now, and was working perfectly well on the top level domain.
    I have also been setting Jetpack to “safe mode” on my staging sites.

    It was only after I setup the testcache staging site (and then deleted it), that the Jetpack/Wordpress connection URL somehow changed.
    And when I checked both on the desktop site and in the mobile app, I was able to set the main URL, but it was still showing up as using the testcache sub-domain…

    FYI, I eventually resolved this by disconnecting and reconnecting the Jetpack WordPress.com connection on my site: it then correctly detected the top level URL.
    Kind Regards,
    Tim

    Plugin Author Rene Hermenau

    (@renehermi)

    Hi Tim,

    thanks for sharing the solution. In the past we never had such an issue with jetpack so it might be related to their latest version. If we get similar reports we will notify jetpack about that “bug”.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cloned site has messed up WordPress.com connection for Jetpack stats’ is closed to new replies.