Re: PHP upgrade to v5.2.10

On 2009-06-29 , at 21:56 , Ryan Schmidt wrote: Digged a bit in their CVS and this should be the fix: Thanks for finding that. I haven't had a chance to test on PowerPC but I added the patch and it's in

Re: PHP upgrade to v5.2.10

On Jun 29, 2009, at 19:25, Rainer Müller wrote: On 2009-06-26 00:21, Ryan Schmidt wrote: I see they have fixed the problem in CVS, but they have not told us how they fixed it. So we either wait for 5.2.11 and update the port to that version, or someone has to find out what patch fixed the pro

Re: PHP upgrade to v5.2.10

On 2009-06-26 00:21, Ryan Schmidt wrote: > I see they have fixed the problem in CVS, but they have not told us > how they fixed it. So we either wait for 5.2.11 and update the port > to that version, or someone has to find out what patch fixed the > problem and I can apply that patch in the p

Re: PHP upgrade to v5.2.10

On Jun 25, 2009, at 17:55, Chris Janton wrote: On 2009-06-25 , at 07:43 , Peter Oakley wrote: After the PHP upgrade to v5.2.10, this yields "" for $thisYear. Prior to the upgrade, $thisYear would be set to "2009". I also tried using the time function dire

Re: PHP upgrade to v5.2.10

On 2009-06-25 , at 07:43 , Peter Oakley wrote: After the PHP upgrade to v5.2.10, this yields "" for $thisYear. Prior to the upgrade, $thisYear would be set to "2009". I also tried using the time function directly within the date function: $thisYear = date('

Re: PHP upgrade to v5.2.10

On Jun 25, 2009, at 17:10, Peter Oakley wrote: Looks like this problem with the date('Y') function was a PHP bug. It showed up on Mac OS X (my system) and on Mac OS X Server, both v10.4.11, when upgrading from PHP v5.2.8 or v5.2.9 to v5.2.10, and the bug also existed in v5.3.0 RC2. Similar

Re: PHP upgrade to v5.2.10

Looks like this problem with the date('Y') function was a PHP bug. It showed up on Mac OS X (my system) and on Mac OS X Server, both v10.4.11, when upgrading from PHP v5.2.8 or v5.2.9 to v5.2.10, and the bug also existed in v5.3.0 RC2. Similar problem with the DateTime () function. The issue

Re: PHP upgrade to v5.2.10

Bradley, and Chris, you've both suggested some good ways to determine whether these two PHP functions are working right via command line -- thanks. My web server is running Mac OS X v10.4.11 with all available Software Updates installed. I am now beginning the process of setting up a test

Re: PHP upgrade to v5.2.10

On Jun 25, 2009, at 7:43 AM, Peter Oakley wrote: Here is an example usage of the date() and time() functions: snippetStart - - - - - - $timestamp = time(); //echo $timestamp; $thisYear = date('Y', $timestamp); echo $thisYear; - - - - - - snippetEnd After the PHP upgrade to v5.

Re: PHP upgrade to v5.2.10

On 2009-06-25 , at 07:43 , Peter Oakley wrote: snippetStart - - - - - - $timestamp = time(); //echo $timestamp; $thisYear = date('Y', $timestamp); echo $thisYear; - - - - - - snippetEnd After the PHP upgrade to v5.2.10, this yields "" for $thisYear. Prior to th

Re: PHP upgrade to v5.2.10

Peter Oakley wrote: Here is an example usage of the date() and time() functions: snippetStart - - - - - - $timestamp = time(); //echo $timestamp; $thisYear = date('Y', $timestamp); echo $thisYear; - - - - - - snippetEnd After the PHP upgrade to v5.2.10, this yields "

Re: PHP upgrade to v5.2.10

Here is an example usage of the date() and time() functions: snippetStart - - - - - - $timestamp = time(); //echo $timestamp; $thisYear = date('Y', $timestamp); echo $thisYear; - - - - - - snippetEnd After the PHP upgrade to v5.2.10, this yields "" for $thisYear.

Re: PHP upgrade to v5.2.10

On Jun 25, 2009, at 7:09 AM, Peter Oakley wrote: Last night I was upgrading my web server to PHP v5.2.10 (from v5.2.8) and everything seemed to go ok, no warnings or major gotchas. But once I began using it, I could see there were some real problems with the time() and date() functions. It

PHP upgrade to v5.2.10

Last night I was upgrading my web server to PHP v5.2.10 (from v5.2.8) and everything seemed to go ok, no warnings or major gotchas. But once I began using it, I could see there were some real problems with the time() and date() functions. It's possible that I'm just using these two function