We're using postTo in some of our applications, and the italicized text that says "This comment was sent by your friend via the [app name] app..." links to the wrong place for several of our applications.

For application 107977, it takes the user to http://www.myspace.com/107977, and the resulting page is "Invalid Friend Id", instead of going to the application profile page.

For one of our dev apps, 108979, the link takes you to the app's Google gadget XML page, which is clearly wrong.

What's going on here?

Edit: Here's an example of a profile I came across and the comments link going to the wrong place: http://profile.myspace.com/index.cfm?fuseaction=user.viewprofile&friendid=330942320

Click application name Texas Holdem on the comment from May 28. It takes you to this page: http://lamspo1.presidiomedia.com/poker/www2/myspace/module.xml.php

I assume this is not what the Holdem developers had in mind...

Ok, so I figured out where it's getting the random url from. The url that "This comment was sent by your friend via the [app name] app" sends you to is the oauth consumer key.

I could be wrong, but I didn't realize the oauth consumer key was used for anything. Is the link supposed to be derived from the oauth consumer key? Seems like it would make more sense to be directed to the application profile...

Additionally, for applications that use the Google gadget xml, the oauth consumer key is getting reset to the Google gadget xml url. Is this expected behavior?

Hey,

Thanks for reporting this - it should not be pulling it from there, but since most apps keep that field set to the default it works and the issue wasn't ever seen.

We're fixing!

Thanks again.

Donny

Thanks for the reply, but what about the oauth consumer key getting overwritten to be the gadget xml's path? Then there's also the fact that the application continues to work (with authentication), even though the oauth consumer key that is in the "My Apps" section is different from the oauth consumer key we're using in the PHP code itself.

Do you have any knowledge about this issue with respect to the oauth stuff?

Bumpity bump. See my last question...