4

For a particular user, the users API v1.1 call returns an association_id that gives a "Page Not Found" error where the Stack Exchange profile should be, though their Stack Exchange profile can be accessed via the "Accounts" link in their profile on another site. Making the API call against the associated accounts on various Stack Exchange sites yields the same association_id. Is there something wrong with this user's account/association?

edit Here is another particular user for whom the users API v1.1 call returns an association_id that gives a "Page Not Found" error where the Stack Exchange profile should be, though their Stack Exchange profile can be accessed via the "Accounts" link in their profile on another site

3
  • Anyone have a suggestion how to fix this? I can't find any similarities between me and the other guy mentioned in the post.. That profile seems quite vacant.
    – Joost
    Dec 19, 2012 at 21:50
  • Hi Isaac, I'm leaving this site. And, I think I could add a bounty for this. Please select the good answer so that bounty may get awarded. Bye & Thanks :-)
    – user14720
    Dec 20, 2012 at 3:50
  • Saw this in global-login.js // WARNING: this happens on EVERY SINGLE PAGE // this the core global login function for every user, even the anonymous ones that have no login // the reason this stays sane is because we set this "gauthed" cookie on the first // attempt to do global auth, and we don't ever try again FOR THE CURRENT BROWSER SESSION
    – brentD
    Dec 22, 2012 at 6:22

0

You must log in to answer this question.

Browse other questions tagged .