[Code] php-openid on php 5.3.3 - is the project maintained?

fred trotter fred.trotter at gmail.com
Fri Dec 24 22:16:42 UTC 2010


hi,
       I have been beating my head against the wall trying to get
php-openid to work on php 5.3.3

So far I have rediscovered the "blank screen" bug (not sure who
decided to use @, but holy-moly that makes painful to find bugs) and
have fixed this by installing the latest from git.
But now Google and Yahoo URLs do not appear to work any longer.
Returning "Invalid URL".

I have found many many complaints and "bug fixes" for php 5.3 issues.
I see no source coming forward and saying "Hey, I am the person who
aggregates bug reports, and makes sure they are addressed in the
latest version. The open bug list on github has 30 issues that date
back 7 months. Many of them might apply to the issues I am having.

The "detect" script has a serious bug in it. It expects to be called
from apache, and fails when run form the command line, despite
instructions that specifically say running from command line is fine.
Moreover the error that is generated is the very helpful "Check your
mod_include". That's it. "Check". Not check to see if it is there. Or
if it is not there. Or if it is misconfigured, or if it is painted
yellow. Just check. This from a function that will -always- fail when
run from the command prompt, no matter what your mod_include status
is. That was a 4 hour rabbit hole. Only figured it out when I saw that
there was a patch, months old, that fixes the problem of the error
being displayed when run from the command prompt. Again, one of the
issues floating around git, waiting to integrated into the main tree.

So far there are blog posts, stack overflow entries and multiple
emails on this list suggesting different problems and fixes usnig this
library with php 5.3.x
php 5.3.3. has been out since the summer.

And then I come to the kicker: I read this message from Will Norris
http://lists.openid.net/pipermail/openid-code/2010-July/000142.html

This basically sums up the experience I am having. There is no
"leadership" coordinating this project that I can tell.
This is despite an active community that appears to be providing not
only high-quality bug reports, but often high quality patches.

Which brings me to my question? Is this project maintained? I cannot
afford to lose a week to a debug process on a previously working
library, only to find that many of the issues that I am dealing with
have been reported, patches, and ignored by the library in question.
Viable projects do not act like this.

If you are seeking a maintainer for this project then make that clear
on the main page at git. If people should start looking at other
libraries... please make that clear.
Otherwise, could we please snap out of it? The issues in git need to
be either addressed and removed or verified fixed and removed.
Otherwise users like me have not idea where to even start debugging.

Hope everyone is having a good Christmas..

-FT

-- 
Fred Trotter
http://www.fredtrotter.com


More information about the Code mailing list