Hey Greg,

My apologies for not catching this thread earlier,  but it seems you have
indeed already found the correct solution :) The 1.0.x release branch is,
and will remain stable and what you should use in all cases, unless your
doing 0.9 spec development work on the trunk; The trunk is seeing a couple
of larger changes to accommodate for the 0.9 features, and hence will be
unstable for a little while longer.

Glad to hear your up and running!

  -- Chris

On Tue, Mar 3, 2009 at 10:43 PM, Greg Gay <[email protected]> wrote:

> Ask for help, and you end up solving the problem yourself :-)
>
> Perhaps not completely stable, but,  a checkout of the latest tag
> 1.0.0RC1 resolved the problems we were having on linux. Everything seems
> to be working fine there now.
>
>
>
> Greg Gay wrote:
> > Is there a relatively stable version of Shindig PHP  available that will
> > run on Linux?
> >
> > We've been trying for days to get the PHP shindig setup on a linux
> > system, but have had no luck, though things do work fine on our windows
> > dev environments. We tried various setups with a proper domain, as a
> > subdirectory on an existing domain, on localhost, with host set to
> > "shindig" and a few other combos.
> >
> > Linux1
> > The test script seems to run, but generates:
> > ----
> >
> > PHPUnit 3.2.9 by Sebastian Bergmann.
> >
> > ...................F....................
> >
> > Fatal error:  Class 'UrlGenerator' not found in
> > /****/social.atutor.ca/docs/php/test/common/UrlGeneratorTest.php on line
> 44
> > -----
> >
> > When trying to run the default todo.xml gadget a js error occurs
> >
> > "_IG_Prefs is not defined"
> > We found reports about emptying the browser cache, and system cache, but
> > that did not help. We have not been able to get around the error.
> >
> > Here's what we get from the todo gadget
> >
> http://social.atutor.ca/gadgets/ifr?url=http://www.labpixies.com/campaigns/todo/todo.xml
> >
> > ----------
> >
> > So we tried on another linux system using localhost, with and with out
> > sub directories, making the same sort of config edits as in Linux 1.
> >
> > Linux 2
> > Same output from the test as in Linux 1. But no matter what paths we use
> > in container.js, container.php, and .htaccess the result is always a 404.
> >
> >
> > Would appreciate some guidance, if anyone can help.
> >
> > greg
> >
> >
> >
>
> --
> Greg Gay
> Project Coordinator
> Adaptive Technology Resource Centre
> University of Toronto
> http://atrc.utoronto.ca
>

Reply via email to