"We don't have that post on record yet"

  • Resolved agent86ix

    (@agent86ix)


    11 years, 6 months ago

    We’ve been running Jetpack for a while now on our blog. We like to use it to track the views over time on specific posts, which you can do via the stats screen by clicking on the bar graph icon to the right of a post name.

    Recently (I can’t trace it back to any specific event, unfortunately), many of our newer posts started returning this error:

    “We don’t have that post on record yet. (post_id ABCD)” where ABCD is the numeric post id for one of our recent posts.

    I’ve seen this error before on posts that were relatively new (ie, less than one day old) but it’s started popping up on posts that are much older – in some cases, weeks old. Some of the posts still return stats, though, and the stats show all the data, up to the current day. It seems clear that the stats are working, but just not tracking properly (or returning the tracked data) on our newer posts.

    I’ve tried installing the very latest version of the plugin and updating WordPress itself to the latest version, with no luck.

    Is there something we can do to get the per-post stats working again?

    https://www.ads-software.com/plugins/jetpack/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Richard Archambault

    (@richardmtl)

    Could you post your site URL here, so I can have a look?

    If you want it to remain private, you can also contact us via this contact form:
    https://jetpack.me/contact-support/

    Thread Starter agent86ix

    (@agent86ix)

    It’s not a problem, the URL is:

    https://www.withoutthesarcasm.com

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Ok, so I think I see the problem.

    At some point in August, something happened to you rsite. It looks to me like you likely switched host to https://www.nearlyfreespeech.net/ hosting, and you had a temporary URL (wots.nfshost.com). When you did that, you also brought over your database and connected Jetpack. 2 things happened:

    1) the stats and subscribers that you had previously were “lost”
    2) you connected with the temporary URL; this can cause problems for the Jetpack connection and for stats collection.

    So, what happens when Jetpack connects to WordPress.com is that you get assigned a blog id, which is associated with the site’s URL. Stats and subscribers are associated with the id. That’s why you got assigned a new id when you had that temporary URL.

    Here’s what we’re going to do to fix it:

    1) temporarily deactivate any caching plugins you have active
    2) make sure that you have https://www.withoutthesarcasm.com in the Site and WordPress URLs on your Settings -> General page (if you don’t, don’t go any further, and let me know what you have)
    3) you are going to disconnect and reconnect Jetpack to WordPress.com, thus making sure your site is associated with the right blog id
    4) Once you’ve done that, I will migrate your site’s subscribers from the incorrect id to the correct one
    5) then, I will merge the stats from the incorrect id to the correct one, so that you will have seamless stats from when you first connected Jetpack

    For reference, the id that you currently have on your site (associated with the wots.nfshost.com URL) is 43512023

    The id associated with the correct URL, https://www.withoutthesarcasm.com/ is 41351423

    Thread Starter agent86ix

    (@agent86ix)

    Richard,

    Okay, that’s odd. We’ve had the same URL & host for a good while now (almost a year now), but I’ll believe I messed it up good at some point or another.

    I went through your steps, at step 2 the URLs listed are correct. Hopefully I completed the rest of them correctly. If not, let me know so I can attempt again.

    Thanks for the help!

    Plugin Contributor Richard Archambault

    (@richardmtl)

    Great, everything looks fixed now! I have merged your stats and migrated your subscribers to the right blog ID, the one you have on your site now, 41351423. Let me know if anything looks amiss!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘"We don't have that post on record yet"’ is closed to new replies.