stats: "No stats data found, please try again later" -> blog_uri vs blog_id

  1. Frank Goossens
    Aug 4, 2010, 12:27 PM

    I don't get stats for my self-hosted blog in the Android app, just see "No stats data found, please try again later". Stats work great in my web-dashboard.

    Based on some tests, I expect the problem to be that the code uses "blog_uri=xyz" as query parameter instead of "blog_id=123".

    Indeed, for unknown reasons I seem to have 2 blog_id's for the same blog_uri, with the oldest one not collecting any stats. I guess that the stats API, in case the query parameter is blog_uri and there are two entries for that blog_uri, will return the first one?

    so possible solutions:

    • have android-app use blog_id instead of blog_uri (allowing user to select correct value)
    • check stats db for double blog_uri's and remove non-active-ones
    • change stats api to take all entries with blog_uri into account, returning result of the entry for which stats were collected most recently

    hope this helps in solving this bug, just yell if you need more input (or tests) from me!

  2. It looks like you have two entries for the same URI in the stats system, I'm reaching out to some folks to see if we can clear out the one that isn't working.

    The app tries to get the blog_id based on the URI, so that's probably why it's getting confused...

  3. Frank Goossens
    Aug 4, 2010, 4:23 PM

    that's the problem exactly.

    wrong blog_id for blog_uri "": 2184847
    correct blog_id for blog_uri "": 2185033

    thanks for reaching out to some folks! ;-)

  4. @futtta - they attempted a fix for you, can you please try again?

  5. Frank Goossens
    Aug 9, 2010, 4:09 PM

    still the same error, although apparently they did the blog_uri for the old blog? weird ..

  6. OK, try one more time please :)

  7. Frank Goossens
    Aug 9, 2010, 8:53 PM

    same message, still no stats ...

  8. @futtta - Would you be ok with sharing your login details with us so we can troubleshoot? You can email them to android at automattic dot com.

  9. resolved this via email.

  10. Frank Goossens
    Aug 13, 2010, 8:28 AM

    indeed, thanks guys!

Topic Closed

This topic has been closed to new replies.

About this Topic