Bug #65475 [Com]: wrong session cookie is generated on session.use_strict_mode

2013-08-19 Thread william dot a dot bartlett at gmail dot com
Edit report at https://bugs.php.net/bug.php?id=65475&edit=1

 ID: 65475
 Comment by: william dot a dot bartlett at gmail dot com
 Reported by:php at tokumaru dot org
 Summary:wrong session cookie is generated on
 session.use_strict_mode
 Status: Open
 Type:   Bug
 Package:Session related
 Operating System:   Ubuntu
 PHP Version:5.5.2
 Block user comment: N
 Private report: N

 New Comment:

Could not reproduce using Fedora 19 PHP 5.5.1 - possible regression.


Previous Comments:

[2013-08-19 03:17:03] php at tokumaru dot org

Description:

In the case of session.use_strict_mode = On, a wrong session cookie is 
generated.

Test script:
---
https://bugs.php.net/bug.php?id=65475&edit=1


Bug #65397 [Com]: Mysql_* functions hide their warning

2013-08-19 Thread william dot a dot bartlett at gmail dot com
Edit report at https://bugs.php.net/bug.php?id=65397&edit=1

 ID: 65397
 Comment by: william dot a dot bartlett at gmail dot com
 Reported by:info at markoheijnen dot com
 Summary:Mysql_* functions hide their warning
 Status: Open
 Type:   Bug
 Package:MySQL related
 Operating System:   Debian Wheezy
 PHP Version:5.5.1
 Block user comment: N
 Private report: N

 New Comment:

Not a bug.

mysql_query() is throws a deprecation error, not a deprecation warning.

Try:
---
https://bugs.php.net/bug.php?id=65397&edit=1


Bug #65397 [Com]: Mysql_* functions hide their warning

2013-08-19 Thread william dot a dot bartlett at gmail dot com
Edit report at https://bugs.php.net/bug.php?id=65397&edit=1

 ID: 65397
 Comment by: william dot a dot bartlett at gmail dot com
 Reported by:info at markoheijnen dot com
 Summary:Mysql_* functions hide their warning
 Status: Feedback
 Type:   Bug
 Package:MySQL related
 Operating System:   Debian Wheezy
 PHP Version:5.5.1
 Block user comment: N
 Private report: N

 New Comment:

> It is just a warning. A "notice", even. Not fatal.

No.  As per: http://www.php.net/manual/en/changelog.mysql.php

In PHP5.5, mysql_* functions emit E_DEPRECATED error, not E_DEPRECATED warning. 
It IS fatal.

My example was intended to indicate that the echo statement nevers occurs 
(which is the expected behavior).


Previous Comments:

[2013-08-20 01:43:46] requi...@php.net

It is just a warning. A "notice", even. Not fatal.

@info: It's a silly question but are you sure it didn't connect? What's the 
output of



----------------
[2013-08-20 01:06:14] william dot a dot bartlett at gmail dot com

Not a bug.

mysql_query() is throws a deprecation error, not a deprecation warning.

Try:
---
https://bugs.php.net/bug.php?id=65397&edit=1


Bug #65397 [Com]: Mysql_* functions hide their warning

2013-08-19 Thread william dot a dot bartlett at gmail dot com
Edit report at https://bugs.php.net/bug.php?id=65397&edit=1

 ID: 65397
 Comment by: william dot a dot bartlett at gmail dot com
 Reported by:info at markoheijnen dot com
 Summary:Mysql_* functions hide their warning
 Status: Feedback
 Type:   Bug
 Package:MySQL related
 Operating System:   Debian Wheezy
 PHP Version:5.5.1
 Block user comment: N
 Private report: N

 New Comment:

I mispoke slightly.  As per: 
http://www.php.net/manual/en/function.mysql-query.php

> If the link identifier is not specified, the last link opened by 
> mysql_connect() is assumed. If no such link is found, it will try to create 
> one as if mysql_connect() was called with no arguments. If no connection is 
> found or established, an E_WARNING level error is generated.

when you call mysql_query, it will call mysql_connect().  mysql_connect() 
returns a fatal error, E_DEPRECATED. The E_WARNING is never generated because 
execution crashes before mysql_query is called.  At the most, a documentation 
error.

For goodness sakes, there is no allowable way to call mysql_query() in php5.5 
because there are no valid mysql connections.


Previous Comments:

[2013-08-20 01:48:41] william dot a dot bartlett at gmail dot com

> It is just a warning. A "notice", even. Not fatal.

No.  As per: http://www.php.net/manual/en/changelog.mysql.php

In PHP5.5, mysql_* functions emit E_DEPRECATED error, not E_DEPRECATED warning. 
It IS fatal.

My example was intended to indicate that the echo statement nevers occurs 
(which is the expected behavior).


[2013-08-20 01:43:46] requi...@php.net

It is just a warning. A "notice", even. Not fatal.

@info: It's a silly question but are you sure it didn't connect? What's the 
output of



--------------------
[2013-08-20 01:06:14] william dot a dot bartlett at gmail dot com

Not a bug.

mysql_query() is throws a deprecation error, not a deprecation warning.

Try:
---
https://bugs.php.net/bug.php?id=65397&edit=1