my code was working fine yesterday but all i see today is [object Object].

any suggestions on what the problem is/could be?

 as its writen in other thread, its a myspace runtime error .. the call to the relax proxy for getting you app crashes, so stay tunned on the forum to see when it will be fixed. i know I am :)

I'm getting this too.  Any eta when this will be fixed?

Also broken.  All day...

 phew! fixed.

 Still broken for me, for over 24 hours now...  Anyone else still experiencing this issue?

Since MDP uses OpenSocial 0.7 now, makeRequest returns an object with text, error, and data properties

Actually, 0.6 requests return responses as per spec (the way it was done) and 0.7 requests return responses as per spec, as phil points out (the OS spec changed inbetween). You'll have to use the properties to access the data you're lloking for.

 If you are still having this problem with the 0.6 version you probably have old javascript files and need to clear your cache.

mine isnt working either. is there a problem with my code or is the server still messed up? 

It's not an error.

You are displaying your object without specifying what to display.

For example if your object is called MyObject and you write:

document.write(MyObject)

you will see:

[object Object]

Try: 

document.write(MyObject.text) 

 This thread is about opensocial.Container.get().makeRequest (kind of hard to tell since it hasn't been referenced directly), which isn't supposed to return an object as the content.

Note that if you are using gadgets.io.makeRequest it is supposed to give you an object and you have to use content.text or content.data

Thanks a ton guys - that fixes it.   

 BTW, I am using opensocial.Container.get().makeRequest, and it is returning an object, and I was only able to fix it when I accessed the data property

This isn't 100% accurate.

I have observed cases where the data.text value is returned as an Object.  This happens to me when the POST to http://api.msappspace.com/proxy/relay.proxy?<blob of params> produces a 500 on MySpace's server, and the MySpace API incorrectly returns a funky error object in the text field.

When this happens, we see traffic on our servers, but the response HTML that we send up never actually makes it through the MySpace proxy.