#33778 [Csd]: PHP compile fails --with-t1lib when SUSE 9.1 upgraded to t1lib-5.0.2-3

ID: 33778 User updated by: sibaz at sibaz dot com Reported By: sibaz at sibaz dot com Status: Closed Bug Type: Compile Failure Operating System: Suse 9.1 (Upgraded) PHP Version: 5.0.4 New Comment: Perhaps configure should be fixed to correctly

#33778 [Opn->Csd]: PHP compile fails --with-t1lib when SUSE 9.1 upgraded to t1lib-5.0.2-3

ID: 33778 User updated by: sibaz at sibaz dot com Reported By: sibaz at sibaz dot com -Status: Open +Status: Closed Bug Type: Compile Failure Operating System: Suse 9.1 (Upgraded) PHP Version: 5.0.4 New Comment: t1lib-5.0.2-3 required

#33778 [NEW]: PHP compile fails --with-t1lib when SUSE 9.1 upgraded to t1lib-5.0.2-3

From: sibaz at sibaz dot com Operating system: Suse 9.1 (Upgraded) PHP version: 5.0.4 PHP Bug Type: Compile Failure Bug description: PHP compile fails --with-t1lib when SUSE 9.1 upgraded to t1lib-5.0.2-3 Description: Having upgraded my system with t1lib-5.0.2-3

#33777 [Opn]: PHP fastcgi returns "No input file specified" only when it finds a valid script

ID: 33777 User updated by: sibaz at sibaz dot com Reported By: sibaz at sibaz dot com Status: Open Bug Type: CGI related Operating System: Upgraded Suse (2.6.5-7.155.29) PHP Version: 5.0.4 New Comment: I removed the php.ini file I was using and

#33777 [Opn]: PHP fastcgi returns "No input file specified" only when it finds a valid script

ID: 33777 User updated by: sibaz at sibaz dot com Reported By: sibaz at sibaz dot com Status: Open Bug Type: CGI related Operating System: Upgraded Suse (2.6.5-7.155.29) PHP Version: 5.0.4 New Comment: I've just compiled a fresh version of A

#33777 [NEW]: PHP fastcgi returns "No input file specified" only when it finds a valid script

From: sibaz at sibaz dot com Operating system: Upgraded Suse (2.6.5-7.155.29) PHP version: 5.0.4 PHP Bug Type: CGI related Bug description: PHP fastcgi returns "No input file specified" only when it finds a valid script Description: When accessing v

#18926 [Com]: cannot call self::method() or parent::method() via call_user_func_array()

ID: 18926 Comment by: sibaz at sibaz dot com Reported By: carl at thep dot lu dot se Status: Closed Bug Type: Zend Engine 2 problem Operating System: Linux PHP Version: 5.0.0-dev New Comment: The convention for this is to use array(&

#25139 [Opn]: parse_str should optionally not mangle array index names

ID: 25139 User updated by: sibaz at sibaz dot com -Summary: optionally parse_str shouldn't mangle fieldnames when theyre only array indexes Reported By: sibaz at sibaz dot com Status: Open Bug Type: Feature/Change Re

#25139 [NEW]: optionally parse_str shouldn't mangle fieldnames when theyre only array indexes

From: sibaz at sibaz dot com Operating system: All PHP version: 4.3.2 PHP Bug Type: Feature/Change Request Bug description: optionally parse_str shouldn't mangle fieldnames when theyre only array indexes Description: Understandably parse_str mangles CGI