I guess I can take a peek, but to get ramped up on the entire php engine might take longer than just waiting for a fix to become available. Maybe, because this is the only bug that seems to be causing problems on my server(s) at this time it is the most important :) This bug seems to have been open for a while, and since many hosting companies use php on the server they might have there own fixes (run in cgi mode only?)
Anyway, thanks for the information, and I will try and make time today and later this weekend to look into learning more about the internal working of php and this one bug. Daniel S On Fri, 2003-08-15 at 01:13, Marcus Börger wrote: > Hello php, > > Friday, August 15, 2003, 9:02:28 AM, you wrote: > > p> I'm just trying to get a possible ETA on when and if somebody is going > p> to look into the bug #23580 (detail below) a bit more. This bug is > p> beginning to cause me a whole lot of pain, and if nobody else was > p> looking at this maybe I could take a stab at it? > > p> ------- Bug #23580 --------- > p> 23580 Open Random values for include_path > > If a bug isn't assigned that means nobody is found guilty for the bug and > nobody has a real clue or enough time to analyze the bug. If the bug is > assigned you can always contact the person to whom the bug is assigned to > query whether any not listed progress in fixing was made. However you can > always invest time in fixing the bug. If you do you should post the news of > your investigations on the bug so the others know about your progress. And > we of course appreciate that :-) > > > -- > Best regards, > Marcus mailto:[EMAIL PROTECTED]
