Ok, and have you ever encountered this in the prod environment too? But of course, &bpc=1 is definitely the recommended thing to do for clearing the cache.
On Mar 26, 4:13 pm, Dhaval Pancholi <[email protected]> wrote: > Hi > When u update your xml you may be clearing your cache and trying to > refresh the page to see sometimes cookie-tokens stored in your machine by > orkut to verify your logged in status get destroyed and when u try to make a > call to orkut client library to request some feature there must be some > default login check with the help of the login cookies. Since those login > cookies were been destroyed you get the error Malformed Security Token > Error. As far as i know this may be the case. > > Reproducing the error does not help you in development but hey instead of > clearing your cache and refreshing you can try appending &bpc=1 in the url > to reload your new xml > > -- > Dhaval Pancholi > 91-9220582314 > > Web Application Developer | ExperienceCommerce.com > India's #1 full-service Digital Agency > ---------------------------------------------------------------- > Fan us on facebook.com/experience.commerce > Read original insights on experiencecommerce.com/blog -- You received this message because you are subscribed to the Google Groups "Orkut Developer Forum" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/opensocial-orkut?hl=en.
