× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Good morning.

What bothers you more? The notice or the fact that the timezone defaulted to UTC?

The function page for strftime( ) is at http://us3.php.net/manual/en/function.strftime.php
It specifies: "Every call to a date/time function will generate a *E_NOTICE* if the time zone is not valid, and/or a *E_STRICT* message if using the system settings or the TZ environment variable. See also date_default_timezone_set() <http://us3.php.net/manual/en/function.date-default-timezone-set.php>"

Is date.timezone <http://us3.php.net/manual/en/ref.datetime.php#ini.date.timezone> set in your ini file? I can't provide a specific example since I'm STILL not on Zend Core.

If you're happy with the functionality, another route you can take is to turn down the error reporting level in your ini file or just turn it off altogether as is proper for production systems.

e.g.
; - Show all errors, except for notices
error_reporting = E_ALL & ~E_NOTICE

or
display_errors = Off

Thanks,
Alfred

ALopez@xxxxxxxxxx wrote:
I'm getting the following on our Wiki page every morning:

Warning: strftime() [function.strftime]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We had to select 'UTC' because your platform doesn't provide functionality for the guessing algorithm in /www/zendcore/htdocs/pmwiki/pmwiki.php on line 302

Normally I go into the ZCMENU in ZENDCORE and stop/end everything, then start the Zend Core Subsystem, the Apache server instances and the i5_COMD service and the message disappears. That doesn't seem to be working this mornng. Googling doesn't help, as all I pull are web pages having the same PHP error.

Anybody know how to deal with this? Do I have to fiddle with PHP, or is there something in how we're stopping/starting the HTTP server causing this?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.