[PHP-DEV] Bug #15451 Updated: bindtextdomain not work

[choiks]

 ID:   15451
 Updated by:   [EMAIL PROTECTED]
 Reported By:  [EMAIL PROTECTED]
 Status:   Bogus
 Bug Type: IIS related
 Operating System: windows 2000 server
 PHP Version:  4.1.1
 New Comment:

By php manual, php 4.1.1 support bindtextdomain() function.

http://www.php.net/manual/en/function.bindtextdomain.php

but php 4.1.1 ISAPI mode not support bindtextdomain().

Error Message :
Fatal error: Call to undefined
function: bindtextdomain() in F:\htdocs\horde\lib\Lang.php
on line 91



Previous Comments:


[2002-02-08 09:40:12] [EMAIL PROTECTED]

The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit http://www.php.net/support.php



[2002-02-08 09:32:54] [EMAIL PROTECTED]

my windows box is
CPU : PII 400
O/S : Windows 2000
Web Daemon : IIS 5.0
PHP Version : 4.1.1 binary
PHP Mode : ISAPI
Zend Optimizer : 1.2.0

i try to use horde and chora that used by cvs.php.net.

but error message appear.

Error Message :
Fatal error: Call to undefined function: bindtextdomain() in
F:\htdocs\horde\lib\Lang.php on line 91





-- 
Edit this bug report at http://bugs.php.net/?id=15451&edit=1


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Bug #15451: bindtextdomain not work

[choiks]

From: [EMAIL PROTECTED]
Operating system: windows 2000 server
PHP version:  4.1.1
PHP Bug Type: IIS related
Bug description:  bindtextdomain not work

my windows box is
CPU : PII 400
O/S : Windows 2000
Web Daemon : IIS 5.0
PHP Version : 4.1.1 binary
PHP Mode : ISAPI
Zend Optimizer : 1.2.0

i try to use horde and chora that used by cvs.php.net.

but error message appear.

Error Message :
Fatal error: Call to undefined function: bindtextdomain() in
F:\htdocs\horde\lib\Lang.php on line 91

-- 
Edit bug report at http://bugs.php.net/?id=15451&edit=1
-- 
Fixed in CVS:http://bugs.php.net/fix.php?id=15451&r=fixedcvs
Fixed in release:http://bugs.php.net/fix.php?id=15451&r=alreadyfixed
Need backtrace:  http://bugs.php.net/fix.php?id=15451&r=needtrace
Try newer version:   http://bugs.php.net/fix.php?id=15451&r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=15451&r=support
Expected behavior:   http://bugs.php.net/fix.php?id=15451&r=notwrong
Not enough info: http://bugs.php.net/fix.php?id=15451&r=notenoughinfo


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Bug #14520 Updated: experiencing

[choiks]

ID: 14520
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Bogus
Bug Type: IIS related
Operating System: Windows 2000 Server Korean Versi
PHP Version: 4.1.0
New Comment:

I have solved my problem.

I don't modify my source code, but my home page goes well done.

my solution is upgrade to php 4.1.1.

it's php 4.1.0 problem.

Thank you.

Previous Comments:


[2001-12-23 13:14:15] [EMAIL PROTECTED]

User error => bogus

the redeclare message probably comes from a function you define in the
include file, but that is a built in PHP function.
See the manual at www.php.net to verify that.

Derick



[2001-12-23 13:02:49] [EMAIL PROTECTED]

I found my mistake in php.ini file.

My session directory is not exist.
I make Session directory, and then php works fine.

But I have one more question.

Error message is "... Cannot redeclare ..." not session.

Please comment.



[2001-12-14 13:01:09] [EMAIL PROTECTED]

Please submit a short working example that shows your problem.

Derick



[2001-12-14 12:41:13] [EMAIL PROTECTED]

No! I include the file once. but I edit my php file using
include_once(). and Error Message is re-occured.

help me!



[2001-12-14 12:21:39] [EMAIL PROTECTED]

I think you're including the file twice. Use include_once() instead of
include() to avoid this problem. Reopen if this is not the case.
BTW: please do not post your whole ini file :(



The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=14520


Edit this bug report at http://bugs.php.net/?id=14520&edit=1


-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

[PHP-DEV] Bug #14520 Updated: experiencing

[choiks]

  This directive makes most sense if used in a per-directory
; or per-virtualhost web server configuration file.
;
;open_basedir =

; Setting certain environment variables may be a potential security breach.
; This directive contains a comma-delimited list of prefixes.  In Safe Mode,
; the user may only alter environment variables whose names begin with the
; prefixes supplied here.  By default, users will only be able to set
; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
;
; Note:  If this directive is empty, PHP will let the user modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_

; This directive contains a comma-delimited list of environment variables that
; the end user won't be able to change using putenv().  These variables will be
; protected even if safe_mode_allowed_env_vars is set to allow to change them.
safe_mode_protected_env_vars = LD_LIBRARY_PATH

; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names.  This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_functions =

; Colors for Syntax Highlighting mode.  Anything that's acceptable in
;  would work.
highlight.string  = #CC
highlight.comment = #FF9900
highlight.keyword = #006600
highlight.bg  = #FF
highlight.default = #CC
highlight.html= #00


;
; Misc
;
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header).  It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
expose_php = On


;;;
; Resource Limits ;
;;;

max_execution_time = 30 ; Maximum execution time of each script, in seconds
memory_limit = 8M  ; Maximum amount of memory a script may consume (8MB)


;;
; Error handling and logging ;
;;

; error_reporting is a bit-field.  Or each number up to get desired error
; reporting level
; E_ALL - All errors and warnings
; E_ERROR   - fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE   - compile-time parse errors
; E_NOTICE  - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_CORE_ERROR  - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING- warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR   - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR  - user-generated error message
; E_USER_WARNING- user-generated warning message
; E_USER_NOTICE - user-generated notice message
;
; Examples:
;
;   - Show all errors, except for notices
;
;error_reporting = E_ALL & ~E_NOTICE
;
;   - Show only errors
;
error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR
;
;   - Show all errors except for notices
;
;error_reporting  =  E_ALL

; Print out errors (as a part of the output).  For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below).  Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = Off

; Even when display_errors is on, errors that occur during PHP's startup
; sequence are not displayed.  It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off

; Log errors into a log file (server-specific log, stderr, or error_log (below))
; As stated above, you're strongly advised to use error logging in place of
; error displaying on production web sites.
log_errors = On

; Store the last error/warning message in $php_errormsg (boolean).
track_errors = On

; Disable the inclusion of HTML tags in error messages.
;html_errors = Off
  
; String to output before an error message.
;error_prepend_string = ""

; String to output after an error message.
;error_append_string = ""

; Log errors to specified file.
error_log = d:\choiks\php\php_error.log

; Log errors to syslog (Event Log on NT, not valid in Windows 95).
;error_log = syslog

; Warn if the + operator is used with strings.
warn_plus_overloading = Off


;
; Data Handling ;
;
;
; Note - track_vars

[PHP-DEV] Bug #14520 Updated: experiencing

[choiks]

ser modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_

; This directive contains a comma-delimited list of environment variables that
; the end user won't be able to change using putenv().  These variables will be
; protected even if safe_mode_allowed_env_vars is set to allow to change them.
safe_mode_protected_env_vars = LD_LIBRARY_PATH

; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names.  This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_functions =

; Colors for Syntax Highlighting mode.  Anything that's acceptable in
;  would work.
highlight.string  = #CC
highlight.comment = #FF9900
highlight.keyword = #006600
highlight.bg  = #FF
highlight.default = #CC
highlight.html= #00


;
; Misc
;
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header).  It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
expose_php = On


;;;
; Resource Limits ;
;;;

max_execution_time = 30 ; Maximum execution time of each script, in seconds
memory_limit = 8M  ; Maximum amount of memory a script may consume (8MB)


;;
; Error handling and logging ;
;;

; error_reporting is a bit-field.  Or each number up to get desired error
; reporting level
; E_ALL - All errors and warnings
; E_ERROR   - fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE   - compile-time parse errors
; E_NOTICE  - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_CORE_ERROR  - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING- warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR   - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR  - user-generated error message
; E_USER_WARNING- user-generated warning message
; E_USER_NOTICE - user-generated notice message
;
; Examples:
;
;   - Show all errors, except for notices
;
;error_reporting = E_ALL & ~E_NOTICE
;
;   - Show only errors
;
error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR
;
;   - Show all errors except for notices
;
;error_reporting  =  E_ALL

; Print out errors (as a part of the output).  For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below).  Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = Off

; Even when display_errors is on, errors that occur during PHP's startup
; sequence are not displayed.  It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off

; Log errors into a log file (server-specific log, stderr, or error_log (below))
; As stated above, you're strongly advised to use error logging in place of
; error displaying on production web sites.
log_errors = On

; Store the last error/warning message in $php_errormsg (boolean).
track_errors = On

; Disable the inclusion of HTML tags in error messages.
;html_errors = Off
  
; String to output before an error message.
;error_prepend_string = ""

; String to output after an error message.
;error_append_string = ""

; Log errors to specified file.
error_log = d:\choiks\php\php_error.log

; Log errors to syslog (Event Log on NT, not valid in Windows 95).
;error_log = syslog

; Warn if the + operator is used with strings.
warn_plus_overloading = Off


;
; Data Handling ;
;
;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3

; The separator used in PHP generated URLs to separate arguments.
; Default is "&". 
;arg_separator.output = "&"

; List of separator(s) used by PHP to parse input URLs into variables.
; Default is "&". 
; NOTE: Every character in this directive is considered as separator!
;arg_separator.input = ";&"

; This directive describes the order in which PHP registers GET, POST, Cookie,
; Environment and Built-in variables (G, P, C, E & S respectively, ofte

[PHP-DEV] Bug #14520: experiencing

[choiks]

nctions =

; Colors for Syntax Highlighting mode.  Anything that's acceptable in
;  would work.
highlight.string  = #CC
highlight.comment = #FF9900
highlight.keyword = #006600
highlight.bg  = #FF
highlight.default = #CC
highlight.html= #00


;
; Misc
;
; Decides whether PHP may expose the fact that it is installed on the
server
; (e.g. by adding its signature to the Web server header).  It is no
security
; threat in any way, but it makes it possible to determine whether you use
PHP
; on your server or not.
expose_php = On


;;;
; Resource Limits ;
;;;

max_execution_time = 30 ; Maximum execution time of each script, in
seconds
memory_limit = 8M  ; Maximum amount of memory a script may consume
(8MB)


;;
; Error handling and logging ;
;;

; error_reporting is a bit-field.  Or each number up to get desired error
; reporting level
; E_ALL - All errors and warnings
; E_ERROR   - fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE   - compile-time parse errors
; E_NOTICE  - run-time notices (these are warnings which often
result
; from a bug in your code, but it's possible that it
was
; intentional (e.g., using an uninitialized variable
and
; relying on the fact it's automatically initialized to
an
; empty string)
; E_CORE_ERROR  - fatal errors that occur during PHP's initial
startup
; E_CORE_WARNING- warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR   - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR  - user-generated error message
; E_USER_WARNING- user-generated warning message
; E_USER_NOTICE - user-generated notice message
;
; Examples:
;
;   - Show all errors, except for notices
;
;error_reporting = E_ALL & ~E_NOTICE
;
;   - Show only errors
;
error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR
;
;   - Show all errors except for notices
;
;error_reporting  =  E_ALL

; Print out errors (as a part of the output).  For production web sites,
; you're strongly encouraged to turn this feature off, and use error
logging
; instead (see below).  Keeping display_errors enabled on a production web
site
; may reveal security information to end users, such as file paths on your
Web
; server, your database schema or other information.
display_errors = Off

; Even when display_errors is on, errors that occur during PHP's startup
; sequence are not displayed.  It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off

; Log errors into a log file (server-specific log, stderr, or error_log
(below))
; As stated above, you're strongly advised to use error logging in place
of
; error displaying on production web sites.
log_errors = On

; Store the last error/warning message in $php_errormsg (boolean).
track_errors = On

; Disable the inclusion of HTML tags in error messages.
;html_errors = Off
  
; String to output before an error message.
;error_prepend_string = ""

; String to output after an error message.
;error_append_string = ""

; Log errors to specified file.
error_log = d:\choiks\php\php_error.log

; Log errors to syslog (Event Log on NT, not valid in Windows 95).
;error_log = syslog

; Warn if the + operator is used with strings.
warn_plus_overloading = Off


;
; Data Handling ;
;
;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3

; The separator used in PHP generated URLs to separate arguments.
; Default is "&". 
;arg_separator.output = "&"

; List of separator(s) used by PHP to parse input URLs into variables.
; Default is "&". 
; NOTE: Every character in this directive is considered as separator!
;arg_separator.input = ";&"

; This directive describes the order in which PHP registers GET, POST,
Cookie,
; Environment and Built-in variables (G, P, C, E & S respectively, often
; referred to as EGPCS or GPC).  Registration is done from left to right,
newer
; values override older values.
variables_order = "GPCS"

; Whether or not to register the EGPCS variables as global variables.  You
may
; want to turn this off if you don't want to clutter your scripts' global
scope
; with user data.  This makes most sense when coupled with track_vars - in
which
; case you can access all of the GPC variables through the
$HTTP_*_VARS[],
; variables.
;
; You should do your best to write your scripts so that they do not
require
; register_globals to b

[PHP-DEV] Bug #11653: exec() not work

[choiks]

From: [EMAIL PROTECTED]
Operating system: Windows NT 4.0 Workstation
PHP version:  4.0.6
PHP Bug Type: Feature/Change Request
Bug description:  exec() not work

System : Window NT Workstation 4.0 SP6a
PHP : 4.0.6 apache sapi mode
WebServer Apache 1.3.20

-

php 4.0.6 not support exec().

error message is unable to fork.
I need exec() function.

and 4.0.7dev is not support crypt().
I need crypt() function too.


-- 
Edit Bug report at: http://bugs.php.net/?id=11653&edit=1



-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

[PHP-DEV] Bug #10601: crypt() not work

[choiks]

From: [EMAIL PROTECTED]
Operating system: Windows NT 4.0 Workstation
PHP version:  4.0.5
PHP Bug Type: Feature/Change Request
Bug description:  crypt() not work

windows php 4.0.4pl1 work with crypt(), but
windows php 4.0.5 not work with crypt().
really?

I necessarily need crypt() with windows php.
please help me.


-- 
Edit Bug report at: http://bugs.php.net/?id=10601&edit=1



-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]