ID: 21984 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Verified Bug Type: Date/time related Operating System: SuSE Linux 8.1 PHP Version: 4.3.0 New Comment:
Then, how about "second monday"? Previous Comments: ------------------------------------------------------------------------ [2003-02-03 08:00:15] [EMAIL PROTECTED] It *is* correct now, because that's how it always should have worked. I agree that it's less intuitive, but that doesn't make it any less correct. (Blame the people who defined the GNU date format!) "Monday", or "first Monday", or "1 Monday" will give you the first Monday which is zero or more days after the specified date (or today). "next Monday" or "2 Monday" will give you the Monday after that. "third Monday" or "3 Monday" will give you the one after that. And so on (except that the text versions run out at "twelfth", so from there onward you can only use "13 Monday", "14 Monday", etc.). Cheers! Mike ------------------------------------------------------------------------ [2003-02-03 05:44:09] [EMAIL PROTECTED] Well, but it isn't correct now, but was before... or is there a new term with with a can determine the "coming Monday" with strtotime? ------------------------------------------------------------------------ [2003-02-03 05:36:56] [EMAIL PROTECTED] H'rumph! Actually, both of your servers are producing the answer they should! In PHP versions prior to 4.3.0, the handling of "next" in strtotime() was incorrect; it was fixed for 4.3.0, so your script will require a minor update. Please see bug http://bugs.php.net/bug.php?id=18655 for the relevent discussion. This bug should be set to Bogus -- I don't think I have karma yet, so would somebody do it, please? Cheers! Mike ------------------------------------------------------------------------ [2003-01-31 11:34:23] [EMAIL PROTECTED] Just some into: I have "downgraded" the server to 4.2.3 - now it works fine... ------------------------------------------------------------------------ [2003-01-31 11:22:59] [EMAIL PROTECTED] Can I do something against that or do I have to wait for 4.3.1? Regards, Rolf ------------------------------------------------------------------------ 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/21984 -- Edit this bug report at http://bugs.php.net/?id=21984&edit=1
