I think your best bet right now is to use Partuza instead of the static
sample container, it's pretty much a sample container too, but then one
written in PHP and with a MySql database powering it :)

You can find the code & instructions at: http://code.google.com/p/partuza

The reason the sample container is broken at the moment is because we've
recently had a fairly major cleanup of the social api code to implement the
json-rpc protocol and get php-shindig release ready, but the default sample
backend (json-db driven one in shindig/php/src/social/sample/) hasn't been
fully ported to the new changes yet.. Partuza has though (since we're using
that as primary test case) so that's always supposed to work.

A confusing situation I know, my apologies for that, but hope this helps!

   -- Chris

On Wed, Oct 15, 2008 at 1:43 AM, nvgigigan <[EMAIL PROTECTED]> wrote:

>
> I got the same problem, anyone on this ?
>
> Btw I got lots of questions and problems I may post something here as
> I'm losing my hair :D
>
> Have a nice day
> Jerome
>
> On 14 oct, 12:05, pollen8 <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I'm having the same issue did you ever solve this one?
> >
> > Cheers
> > Rob
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Implementing OpenSocial Containers" 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-container?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to